@Todd-AO 👍 Do you have Adobe PP? I used to have AE, however much people hype about it playback wasn't great until it prerendered, that prerender works in two directions at the same time, backwards & forwards from the cursor/marker doubling the speed of the prerender, this is auto also so no Shift+B etc. needed, it just does it itself. + I'm fairly sure this prerender is used in the export, I can't remember so I might be wrong? Resolve also has a Smart cache option,
@Gid In premiere it has all these various caching options which I turn off, and you can tell by the color of the cache line if it's been cached or not, but also I agree in Premiere it does a form of secret caching as well, because I see the decoder turn off before the end of an encode. This likely isn't sinister/cheating, and is working in real time but if the decoder is working faster then the renderer it caches the decoding data and has stopped reading the file before the encode is over.
With Resolve I don't see the same, I have smart caching turned on, but you can see by the color of the cache line when it's active, you can also cache the timeline, you can then have a choice to render from cache. Using it that way is really just pushing the frames into the encoder at the fastest possible speed and is no good for benchmarks. Choosing to render from cache is a manual process, so people shouldn't do it by accident, and you probably wont see any decode activity, but not certain about that.
@Todd-AO 👍
How the program renders goes over most peoples heads unless you're a programmer & if anyone could improve things I'm sure Vegas would like to hear about it. Me personally I've been editing for 20yrs & a lot of this goes way way over my head, I'm still a bit with the people who don't understand why if Vegas can play it why can't it just 'save' it 😂 Of course I understand there's a hell of a lot more to it than that.
I do wonder tho why Voukoder can render the project faster than Vegas's options can, what is it doing to be able to do that & why can't that be implemented into Vegas 🤷♂️ Again novice talk, I'm sure there's a reason.
---------------
You added your second comment while I was typing, Yep the line at the top of the timeline 👍 I only occasionally open Resolve & I had AE for 2yrs but didn't use that much either, it was just for playing with Boris effects.. They used to crash Vegas regularly but I stopped AE when VP21 came out I found playing with effects & just general editing with these new versions are a lot more stable, like I said in a comment earlier this one hardly if ever crashes for me.
@Gid I'd bet Voukoder guy would know, it doesn't seem to make sense, especially when you can see by the graphs Vegas via voukoder still has pauses and most likely still every 50 frames(from memory) but they are tiny compared to Vegas native encoders.
In Vegas I'd often see the gray screen of death with not responding when opening Boris FX editor, either it would crash, Vegas would crash or just a long delay, now it's very snappy and reliable.
I do wonder tho why Voukoder can render the project faster than Vegas's options can, what is it doing to be able to do that & why can't that be implemented into Vegas 🤷♂️ Again novice talk, I'm sure there's a reason.
@Gid For equal quality, Magix presets are similar to Voukoder in speed, maybe even a little faster and smaller. Fully accelerated ABR or CBR hand-off renders are essentially identical with only deviations in the container and gui options possible. But I have a sense that Voukoder's implementation of ffmpeg-style CRF and CQ are more popular than Vegas which only supports ABR and CBR.
@Gid For equal quality, Magix presets are similar to Voukoder in speed, maybe even a little faster and smaller.
@Howard-Vigorita You love efficiency, don't pretend you don't, Vegas should not pause every 50fps encoding to native hardware encoder, that's the slow down many have noticed and mentioned for many years. Why does that happen?
I remember MusicVid said, well it has to work like that, read, cache, write, read cache. and that just was the accepted wisdom, but I don't see other editors doing that, and it doesn't happen very noticeably with Voukoder. And between you and me Howard, I bet they're going to fix it in VP22, I feel it in my waters.
Seeing as how NVDEC was overhauled in 21 (and I can actually use it now instead of avoiding it as I have since it turned VP 18 into a crashing mess), it's not hard to imagine bottlenecks in the rendering engine and NVENC is up next.
I was happy to see the longstanding text + image bleed issue fixed with NVENC somewhere along the way in VP 21 so some development already happened there.