A FAST PreRender Template?

Grazie wrote on 8/26/2019, 1:07 PM

I'm using 1080 30p on a complex Nested Timeline. I'm wanting to get to the flow of the piece by using a PreRender. Presently I've tried HEVC and AVC NVENC using the Default Factory Template. Is there anything I can do to the Defaults of these two Templates to hasten the PreRendering. I wish to get to a quick Flowing Preview faster.

TIA

Comments

Musicvid wrote on 8/26/2019, 1:10 PM

Fastest with tolerable quality on my new four-banger is still XDCAM-EX35.

Grazie wrote on 8/26/2019, 1:21 PM

@Musicvid - I’ll give it a go. Any tweaks to that Template?

Musicvid wrote on 8/26/2019, 1:35 PM

For FAST, I use the 720p template regardless of source.

Here's a barebones 720p 18Mbps CBR template I made that suits me nicely for quick, portable proofs.

My own tests with QSV h264 were deplorable quality.

Grazie wrote on 8/26/2019, 1:53 PM

@Musicvid - Thank you, from the bottom of my wallet! Finished for the day, but this’ll be the first thing on the morrow.

Grazie wrote on 8/27/2019, 2:20 AM

@Musicvid - Made the Template, but it didn't reduce the PreRenders time taken for render. I need to reflect on just how efficiently VP Previews Nested Timelines. Hmmm... 😔

Musicvid wrote on 8/27/2019, 8:36 AM

It's really very close to being the same as Vegas' native prerender format, except I came at it from the same place as you -- starting with HW codecs and working my way down.

I did finally get the O'Jays tv special looking good with QSV h264, by setting it at CQ 14. That made it larger than with x264.

So yes, our parallel investigations seem to have left us "culdesacked" once again.

Grazie wrote on 8/27/2019, 9:00 AM

@Musicvid - Well, I tried. But, at the end of the day, shouldn’t VP be able to Preview with all my extra muscle in this MONSTA!

Musicvid wrote on 8/27/2019, 9:13 AM

Fortunately for you, it's the codecs holding back your CPU, not the other way around.

Kinvermark wrote on 8/27/2019, 10:05 AM

@Grazie Have you tried a pre-render with one of the NVENC templates? That may be the fastest option.

Regardless, I do think your experience points out the need for a Vegas intelligent caching system that works in the background to pre-render slow sections of the timeline. This is how other NLE's achieve the appearance of smooth playback. Vegas is able to play back simple events at full frame rate, but always seems to hiccup on transitions, titles, and other composited elements (nested timelines included?) A background caching system would pre-render just those parts.

Grazie wrote on 8/27/2019, 10:13 AM

@Grazie Have you tried a pre-render with one of the NVENC templates? That may be the fastest option.

@Kinvermark - Yup, see my opening statement. First thing I tried.

Regardless, I do think your experience points out the need for a Vegas intelligent caching system that works in the background to pre-render slow sections of the timeline.

@Kinvermark - Well, these are Nested Timelines in a Parent Project. This raises the possibility/question that these Children Nests aren’t actually a proxy? Is this true? If so this is a big trick/opportunity lost. Any thoughts?

Kinvermark wrote on 8/27/2019, 10:26 AM

I can see SFAP0 files for the nested timelines, but I think these are only audio proxies. I am not sure there is a video proxy being generated... maybe someone else knows for sure?

Grazie wrote on 8/27/2019, 11:44 AM

I am not sure there is a video proxy being generated... maybe someone else knows for sure?

@Kinvermark - There has to be some kind of single file to make it Play frame-rates etc etc. What is this “thing”?

wwaag wrote on 8/27/2019, 12:05 PM

I may be mistaken, but I believe there is an SFVP0 file that is created for nested projects.

Have you tried preview and pre-rendering without nesting? Do you have the same performance issues?

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Kinvermark wrote on 8/27/2019, 12:20 PM

I have looked in all the likely places... can't see any.

Grazie wrote on 8/27/2019, 1:04 PM

Have you tried preview and pre-rendering without nesting? Do you have the same performance issues?

@wwaag - I’ll give it a go tomorrow. However, it’s a complex Parent (lol 😆) and whole point was to experiment with the NEW Nesting. Oh, I found a Bug and had it confirmed by MAGIX. Another thought..... I’m wondering what would happen if I made a Parent, which has Track a Motion, of the Parent? Would that make things slicker?

 

matthias-krutz wrote on 8/27/2019, 1:09 PM

It makes no difference between Preview or Good / Best preview quality.
It is possible that sfvp0 is just an audio proxy. That would also explain the sluggish and sometimes faulty playback, such as a lost video stabilization. To speed up the rendering, I render the subproject into a new track and hide the others.

Much more bothers me, especially on longer projects, the unload / load procedure. Although only one subproject is changed, all must be unloaded and reloaded.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

Marco. wrote on 8/27/2019, 1:55 PM

Yes, it is an audio proxy.

Grazie wrote on 8/27/2019, 2:32 PM

Yes, it is an audio proxy.

@Marco. - Understood. So, what’s the thing that’s Video sitting on the Timeline?

Kinvermark wrote on 8/27/2019, 2:52 PM

For the sake of simplicity, let's say a project is just a set of pointers to a "bunch" of media files in some configuration. That's what is sitting as "video" on the master timeline.

Grazie wrote on 8/27/2019, 3:43 PM

.......let's say a project is just a set of pointers to a "bunch" of media files in some configuration.

@Kinvermark - Yeah, I guess so . . . dang.

 

Musicvid wrote on 8/27/2019, 4:08 PM

I am not using a nested timeline -- but I think that must make a difference -- prerenders seem perky here.

wwaag wrote on 8/27/2019, 5:09 PM

I gave up on nested projects years ago (albeit with earlier versions) since the render time was increased substantially. I found it much easier to render out individual projects and then combine them afterward using readily-available 3rd party tools. Hopefully, that has changed with later versions, but perhaps not.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Musicvid wrote on 8/27/2019, 5:19 PM

I gave up on nested projects years ago (albeit with earlier versions) since the render time was increased substantially.

Ooh, that sounds like a worthy test. Then lots of speculative cause-and-effect discussion. Isn't that what we like around here?

Stay tuned.

Musicvid wrote on 8/27/2019, 5:44 PM

VP14 on i5-8250 4 core / 8 threads

Source: 1080 p60, ~05:30 length.

Renderer: 720 p60, 18Mb/s CBR, XDCAM EX MTS

Original Render: 3:31

Nested Render same project settings: 3:40

Nested Render with project change: 3:42

And therein lies my pet theory du jour. Vegas must process the old project settings and map them to the new project settings in real time for preview, right? (Too bad they don't just pass the values for <null> changes as they do for video resolution). Thus the 4% or thereabouts rendering time increase. Doesn't sound like much, but it will drive me mad on an overnight render.

Got comp tests or juicy theories anyone?