Better FFmpeg Progress
Runs an FFmpeg command and shows a progress bar with percentage progress, elapsed time and ETA.
FFmpeg outputs something like:
frame= 692 fps= 58 q=28.0 size= 5376KiB time=00:00:28.77 bitrate=1530.3kbits/s speed=2.43x
Better FFmpeg Progress outputs something like:
⠏ Processing abc.webm (5.50 MB / ~23.91 MB) ━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 23% 0:00:04 00:15
Where:
Processing abc.webmis the description of the progresss bar. Filenames longer than 60 characters are truncated.(5.50 MB / ~23.91 MB)is the current output size and the estimated final output size.23%is the percentage progress.0:00:04is the time elapsed.00:15is the estimated time until the FFmpeg process completes.
Installation
pip install better-ffmpeg-progress --upgrade
Usage
Create an instance of the FfmpegProcess class and supply a list of arguments like you would when using subprocess.run() or subprocess.Popen(). Example:
from better_ffmpeg_progress import FfmpegProcess, FfmpegProcessError
command = [
"ffmpeg",
"-i",
"https://media.xiph.org/video/derf/y4m/ducks_take_off_1080p50.y4m",
"-map",
"0:V",
"-c:V",
"libx264",
"-preset",
"ultrafast",
"-f",
"null",
"-",
]
try:
process = FfmpegProcess(command)
# Uncomment this line to use tqdm instead of Rich.
# process.use_tqdm = True
process.run()
except FfmpegProcessError as e:
print(
"An error occurred when running Better FFmpeg Progress:\n"
f"{e}"
)
Trimming
If your command trims the input with -ss, -sseof, -t or -to (as input or output options), the expected duration of the output is calculated automatically, so the progress bar and ETA reflect the trimmed output rather than the whole input file. This adjustment is skipped when -copyts is used.
Duration Override
By default, Better FFmpeg Progress detects the duration of the input file and uses it to calculate percentage progress and ETA.
For partial, damaged, streamed or synthetic inputs, FFmpeg may be unable to detect the duration correctly. In these cases, you can provide the duration manually using duration_override.
The value should be the duration of the input file, in seconds:
from better_ffmpeg_progress import FfmpegProcess
command = [
"ffmpeg",
"-i",
"partial-input.flv",
"-c",
"copy",
"recovered-output.mkv",
]
process = FfmpegProcess(
command,
duration_override=1222.64,
print_detected_duration=True,
)
process.run()
Generated (lavfi) Inputs
Inputs generated by FFmpeg's lavfi device, such as test patterns, are supported. FFprobe cannot detect the duration of these inputs, so provide it with duration_override:
from better_ffmpeg_progress import FfmpegProcess
command = [
"ffmpeg",
"-f",
"lavfi",
"-i",
"testsrc2=duration=30:size=1920x1080:rate=30",
"-c:v",
"libx264",
"output.mp4",
]
process = FfmpegProcess(command, duration_override=30)
process.run()
By default, the FFmpeg log file is named after the source, e.g. lavfi_testsrc2_ffmpeg_log.txt.
Optional Arguments
An instance of FfmpegProcess accepts the following optional arguments:
ffmpeg_log_level— Set a value for FFmpeg's-logleveloption. Default:"verbose".ffmpeg_log_file— Filepath or file-like object to which FFmpeg stderr will be written. Default:<input filename>_ffmpeg_log.txt.print_detected_duration— Print the detected duration. Default:False.duration_override— Specify input file duration in seconds to use for progress calculation, instead of trying to detect this automatically with FFprobe. Default:None.
The run method accepts the following optional argument:
print_command— Print the FFmpeg command being executed. Default:False.
Using tqdm
By default, the Rich library is used to display a progress bar. tqdm can be used instead by setting process.use_tqdm = True:
process = FfmpegProcess(command)
process.use_tqdm = True
process.run()
Metadata
Release files for better-ffmpeg-progress 5.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| better_ffmpeg_progress-5.4.2.tar.gz | 14.7 kB | Without provenance | Details for better_ffmpeg_progress-5.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| better_ffmpeg_progress-5.4.2-py3-none-any.whl | Python 3 | none | any | Details for better_ffmpeg_progress-5.4.2-py3-none-any.whl |
Total release size: 30.0 kB
Release files / better_ffmpeg_progress-5.4.2.tar.gz
| Download URL | better_ffmpeg_progress-5.4.2.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c30847214daa70087ae0b4186d683356677451b8fa71b4c076b1e833557d98d5
|
|
BLAKE2b-256 checksum How to use checksums |
fb8069a61f984104d58e58f5d50f3ddc97b402a684d9227f57a9f819492757df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Release files / better_ffmpeg_progress-5.4.2-py3-none-any.whl
| Download URL | better_ffmpeg_progress-5.4.2-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2630a2c72283d457d5f132c8287509730f1d7c87df57e324a678891ff47dd67
|
|
BLAKE2b-256 checksum How to use checksums |
47067764dba751001474d0ccecb7051d0b28b19c94a973cd0ed6e624a0221208
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Security for better-ffmpeg-progress 5.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.