> Thank you for responding, I tried after changing the command to -v info and
> got some output. I am sharing the information file. Could you please check
> it once.
Nothing seems out of order, what did you mean when you said “destroy a good cbr
2-pass coding”? It seems like the video was
Hi Ted,
Thank you for responding, I tried after changing the command to -v info and
got some output. I am sharing the information file. Could you please check
it once.
Regards,
Saurav
On Wed, Apr 10, 2019 at 12:34 AM Ted Park wrote:
> Set the verbosity level lower (higher?), try -v info
Set the verbosity level lower (higher?), try -v info instead of -v error. That
might be suppressing everything except errors.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link
Hi Carl,
As required please find the attached file.
I have shared the console command (copied from the CMD prompt) and Batch
file in notepad(.bat file to call the ffmpeg.exe file) . Unable to attach
the error log file because it is empty(0 bytes)
File1: Console_CMD[1] : command copied from the
2019-04-09 11:59 GMT+02:00, Nick :
> Can it happen that force_key_frames option will destroy a
> good cbr 2-pass coding?
Command lines and complete, uncut console output missing.
(Changing parameters over passes will affect quality.)
Carl Eugen
___
Can it happen that force_key_frames option will destroy a good cbr
2-pass coding?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
