Opened 12 years ago
Closed 4 years ago
#2349 closed defect (wontfix)
Windows, continuously write progress on one line
Reported by: | svnpenn | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | ffmpeg |
Version: | git-master | Keywords: | win |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | yes | |
Analyzed by developer: | no |
Description
When encoding FFmpeg prints a new line every second with the progress, example
frame= 31 fps=0.0 q=0.0 size= 152kB time=00:00:00.72 bitrate=1726.3kbits/s
frame= 59 fps= 57 q=0.0 size= 175kB time=00:00:01.90 bitrate= 751.1kbits/s
frame= 89 fps= 58 q=0.0 size= 204kB time=00:00:03.04 bitrate= 549.8kbits/s
With a large file these lines can quickly fill the console screen. I would like to see the progress on one line if possible, that is to say each second the same line is overwritten with the updated progress.
http://superuser.com/questions/564483/how-to-make-ffmpeg-continuously-write-progress-on-one-line
Change History (6)
comment:1 by , 12 years ago
comment:3 by , 12 years ago
At least with Windows, FFmpeg requires 85 columns to print progress correctly. I set this using the registry
reg add "hkcu\console" -v WindowSize -d 0x00190055 -f -t reg_dword reg add "hkcu\console" -v ScreenBufferSize -d 0x03e80055 -f -t reg_dword
comment:4 by , 12 years ago
Keywords: | win added |
---|---|
Reproduced by developer: | set |
Status: | new → open |
Version: | unspecified → git-master |
comment:5 by , 7 years ago
This has been open for five years. Can it be fixed? See #6942. Personally, an ETA would suffice as a progress line for me -- or time/size/bitrate tops! The remaining information seems quite low-level.
comment:6 by , 4 years ago
Component: | undetermined → ffmpeg |
---|---|
Resolution: | → wontfix |
Status: | open → closed |
Given that Windows 10 allows to resize the cmd Window, this is less likely to be fixed now.
Did you try to make your console slightly larger?