![]() System: 2GB RAM Athlon X2 4200+ (operating at 2x 2.4GHz) WinXP + no excess programs/processes running.ĭNxHD 1080p 23.976 175Mb/s 8-bit Millions+ & 709-colourspaceĭNxHD 1080p 23.976 175Mb/s 8-bit (unknown colour count and colourspace)īased on my experience using Blender (another free tool), I found that letting ffmpeg assign CPU core affinity to only 2-threads on my system, actually hampered the speed. Source: 1920x1080p H.264 Trailer 2:27 running time 23.976fps (No audio for this test) Then scroll up and you'll see DNxHD as "VC3/DNxHD" Package and open a command prompt in the extracted folder where ffmpeg.exe resides and type: To confirm that DNxHD is an available encode option (if you're curious), extract the ![]() There are too many neat things to mention about the combination of the two to post here, so let's stick purely with DNxHD.įirstly, Here's the version of ffmpeg I've been using (Windows Build 13778): Personally I use Avanti-GUI as a front-end to ffmpeg regularly, and find it's quite a nice combination for many day-to-day tasks. (The implementation may have been made many months ago, but hey, I can only report what I find when I actually find it ) Recently I noticed that the ffmpeg builds included DNxHD encoding support. ffmpeg functions not only under Windows, but can also be found on Linux and Mac operating systems. I've started this new thread to objectively discuss and explore DNxHD encoding via 3rd-party software, namely: ffmpeg.įor those not 'in the know', ffmpeg is a command-line tool for compressing/transcoding/converting video and audio files. ![]() So as to prevent a previous thread not only being hijacked, but forced to eventually land with grissly results.
0 Comments
Leave a Reply. |