Return to Answer

Clear out the command line.

Source Link

edit approved Sep 3, 2016 at 15:29

This is the command line I have used to encode ProRes 4444. If you do not include -bits_per_mb you will get low res results in Windows 10. Many posts do not mention this little aspect.

ffmpeg -y -f mov -i smokeinput-file.mov -vcodec prores_ks -pix_fmt yuva444p10le -profile:v 4444 -bits_per_mb 8000 -s 1920x1080 testoutput-file.mov

This is the command line I have used to encode ProRes 4444. If you do not include -bits_per_mb you will get low res results in Windows 10. Many posts do not mention this little aspect.

ffmpeg -y -f mov -i smoke.mov -vcodec prores_ks -pix_fmt yuva444p10le -profile:v 4444 -bits_per_mb 8000 -s 1920x1080 test.mov

This is the command line I have used to encode ProRes 4444. If you do not include -bits_per_mb you will get low res results in Windows 10. Many posts do not mention this little aspect.

ffmpeg -y -f mov -i input-file.mov -vcodec prores_ks -pix_fmt yuva444p10le -profile:v 4444 -bits_per_mb 8000 -s 1920x1080 output-file.mov

Source Link

created Sep 3, 2016 at 14:34

vjgalaxy

This is the command line I have used to encode ProRes 4444. If you do not include -bits_per_mb you will get low res results in Windows 10. Many posts do not mention this little aspect.

ffmpeg -y -f mov -i smoke.mov -vcodec prores_ks -pix_fmt yuva444p10le -profile:v 4444 -bits_per_mb 8000 -s 1920x1080 test.mov