![]() ![]() The iMP was already faster on H264 1080p Fast and HQ output, also 4k HQ output the slower iMP 4k H264 "Fast" encoding was an anomaly which seems now corrected. It was formerly slower than the 2017 iMac. It seems 422 is a special case or else there's some kind of performance bug in the other code paths.Īnother interesting behavior is the iMac Pro's 4k H.264 "Fast" encoding performance has improved. However it also doesn't happen when using 4444 media, 4444 render files and output. It also doesn't show the fast ProRes 422 output behavior if the media is H264, even though the timeline is fully rendered (which means it exists as cached ProRes 422 files). On the iMP the super-fast ProRes 422 output for pre-rendered timelines happens for most effects I've tested, but not for stabilization. It appears to re-encode the ProRes 422 output. Picking 422 LT or 4444 output causes re-encoding (as expected).įor reasons I don't understand it doesn't do this on my 2017 iMac 27, even though it's also running Mojave 10.14.1, FCPX 10.4.4 and PVF 2.0.7. ![]() This only works if the output is the same as the render format, ProRes 422. The I/O rates total about 1 gigabyte per second. On the iMac Pro running FCPX 10.4.4 and PVF 2.0.7 that's now what it does. It should be able to just copy the render files which by default are ProRes 422. There has always been a question of why FCPX re-encoded fully-rendered ProRes 422 material if the output codec was also ProRes 422. The most interesting behavioral change is the hyper-fast ProRes 422 output only happens (1) On the iMac Pro, (2) If the timeline is fully rendered and (3) Source media is also ProRes 422. It didn't completely restore all previous behaviors but it reverted the previous super-fast iMac Pro behavior on ProRes 422 export - even though I was still running FCPX 10.4.4 and Mojave 10.14.1.Įxamination of the ~/Library/Quicktime and ~/Library/Video/Professional Video Workflow Plug-Ins shows that most of the codecs are changed by the PVF 2.0.7 update. ![]() In attempting to isolate this I manually rolled back to PVF 2.0.6 by restoring the files from a Time Machine backup to ~/Library/Quicktime and ~/Library/Video/Professional Video Workflow Plug-Ins Tests with 1 min 3 sec 4k ProRes 422 source materialĮncoding choice: Master File, Video and Audio, ProRes 422Ĥk ProRes422 Src, ProRes422 Out, no FX: 00:43, with PVF 2.07 = 00:26Ĥk ProRes422 Src, ProRes422 Out, Color+Aged Film+Water Pane, No Pre-Render: 01:09, with PVF 2.07 = 00:12.8 (!)Ĥk ProRes422 Src, ProRes422 Out, Color+Aged Film+Water Pane, With Pre-Render: 01:09, with PVF 2.07 = 00:12.8 (!) If anyone is running Mojave and FCPX on an iMac Pro and if you have *not* yet upgraded to Pro Video Formats 2.0.7, you might run some encoding tests before and after the 2.0.7 update and see if you notice anything similar.ĭetails: 10-core Vega64 iMac Pro, 64GB, 2TB SSD It's possible I made a mistake but I can't easily revert to the previous Pro Video Format to double check it. I tested the same sequence on my 2017 iMac 27 and don't see any difference, so it seems isolated to the iMac Pro. After upgrading to Mojave 10.14.1 and FCPX 10.4.4, I did a few basic encoding tests, then upgraded to Pro Video Formats 2.0.7 (previously was on 2.0.6, I think).įor certain codecs and especially for ProRes 422 output, I'm seeing a significant improvement in encoding performance after the 2.0.7 update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |