Any chance to have a similar tool for Vegas Pro?
Should be possible, yes.
This might seem like a dumb question, but can someone please explain how to run this test?
- Download it
- Copy the PRM file to the plugin folder
- Open your project in premiere
- Export it and select it on the format selection dropdown box
I could swear that there was no sign of this posting last time I scrolled through this topic, but, I guess, I just need to pay more attention to things, LOL.
Anyway, thanks for your answer.
This is the result I got with Premiere Pro CS6 (v. 6.0.5) on my main rig - 244 fps @ 1920x1080:
I also tested a few different encodes of the same files to better examine Premiere's decode speed with VRPT. For that, I created 5 identical timelines each containing 5 identical video clips without audio, effects, or transitions, with identical resolutions and framerates. The only difference between these timelines was video codecs used to encode said clips.
Original ProRes 444 LOG source footage (avg. 215 Mb/s-) - 48 fps:
The same footage encoded with HandBrake's Production Max preset (avg. 127 Mb/s) - 78 fps:
The same footage encoded with HandBrake's Production Standard preset (avg. 55 Mb/s) - 140 fps:
The same footage encoded with HandBrake's Production Proxy 1080p preset (avg. 19 Mb/s) - 248 fps:
The same footage encoded with a custom NVENC CQP18 HQ preset in HandBrake (avg. 5 Mb/s) - 356 fps:
Interestingly enough, despite the fact that ProRes and Production Proxy timelines were the fastest in terms of forward and backward live playback and playhead scrubbing, due to their I-frame-only nature, it was actually much faster to render an NVENC timeline, which was the only one among these timelines to actually contain all 3 frame types (I, P, B). You might think that this was due to disk throughput (the smaller the videos the faster the render), but all these videos were stored on a fast modern SSD with DRAM cache, and the disk load during rendering was fairly low.
All the above tests were run with Mercury Playback Engine GPU Accelerated (CUDA).
I did try to disable CUDA, but, I didn't notice any significant speed change when rendering these effectless/transitionless timelines with CUDA disabled.
It is possible to get a rigged result with VRPT by creating a timeline with multiple instances of the same clip. The more duplicates you'll create, the higher result you'll get. I guess this is just the way Premiere handles identical clips that were previously rendered. Here's an example of a 1m clip duplicated 60 times into a 1h timeline - 7940 fps: https://i.imgur.com/xsJaJUH.png
Another way of getting an invalid, but a very high result is by exporting a timeline you already just exported before (without closing Premiere). I don't really know how this works. The timeline probably gets cached into RAM. But, this way, you'll get an even higher, absolutely ridiculous result - 15584 fps: https://i.imgur.com/AVuT8Ui.png
Premier only use H264 and H265 hardware decoding with Intel integrated graphics, not with Nvidia or AMD cards.
It changed. In the new Premiere you can select between Itel and NVIDIA decoders.
I wanted to see how different source formats compare in 4K. So, for that, I encoded a 1m40s 4K drone video into several different video formats and compared the decode speed of each video with VRPT in PrPro CS6.
DNxHR HQ 422 (avg. 698 Mb/s) - 18 fps: https://i.imgur.com/DTx8y65.png
ProRes 422 HQ (avg. 670 Mb/s) - 39 fps: https://i.imgur.com/Y1afSi7.png
HandBrake Production Max preset (avg. 350 Mb/s) - 26 fps: https://i.imgur.com/CYmtX4h.png
HandBrake Production Standard preset (avg. 144 Mb/s) - 44 fps: https://i.imgur.com/ECJQAPm.png
HandBrake Production Proxy 1080p preset (avg. 114 Mb/s) - 52 fps: https://i.imgur.com/jP52IPS.png
HandBrake custom NVENC CQP18 HQ preset (avg. 30 Mb/s) - 66 fps: https://i.imgur.com/ByuRhmo.png
The results almost linearly scale if you compare the difference in fps between formats used in my previous comparison and the number of pixels per frame. The only discrepancy is that unlike with 1856x776, HandBrake Production Max turned out to be slower than ProRes in 3840x2160.