The Final Cut Pro X Project timeline was a few seconds longer than the equivalent in Premiere Pro.
Final cut pro export mp4 code#
(Again likely code Adobe can’t optimize themselves.) Final Cut Pro X
Final cut pro export mp4 1080p#
The export to H.264 for Apple devices, with only one GPU in use, took 13’38”, confirming without doubt that Adobe are a) doing a great implementation of OpenCL and b) definitely using the second GPU when they have the chance to optimize the code themselves.įor comparison, I did a similar export to 1080P MXF Opt1A DNX 170 1080P, which took 2’20” with one or two GPUs enabled. There was little change to the export to UltraHD ProRes 422, confirming that the code is obviously not optimized for Adobe’s Mercury Engine (OpenCL) being used on the Mac Pro. What got interesting is when I disabled the second GPU for Premiere Pro and AME. I also attribute the relatively slow encode to ProRes 422 to code that Adobe has little opportunity to optimize (or even move to the GPU). These times do not include AME’s startup time, but in fair comparison with Final Cut Pro X, it should be added.Ĭlearly there is some optimized code for the export to H.264 for Apple Devices. There is no corresponding delay when exporting from Final Cut Pro X. The first export you do, there is a 31 second (on the test Mac Pro with SSD) to start up AME. When you export from Premiere Pro the actual encode is handled by Adobe Media Encoder. All encode tests were done with no other apps running and limited interactivity with the computer. I chose not to continue to work as that would have created a variability to the encode times as resources are split between playback and the encode. In both Premiere Pro CC and Final Cut Pro X the export is handled in the background, so work can continue on the edit. ProRes is an all I-frame codec and should be faster to encode that a typical long GOP H.264 encode. I started with the same RED UltraHD timeline I had for the real time performance tests for Final Cut Pro X 10.1 and Premiere Pro CC, except that I copied everything and pasted it twice again to the end of the project/sequence.Īs a test I exported that timeline to 4K ProRes 422 and to 1080P HD (scaled from the UltraHD for Apple Devices). Definite proof that second GPU is being used, and worth it! I had time to do some export testing from Premiere Pro CC and Final Cut Pro X 10.1.
0 kommentar(er)
