Stuttering and Massive Frame Rate drops during transitions in preview

Mike_S wrote on 10/21/2019, 8:40 PM

hey everyone, this problem has plagued me when working on Vegas Pro 16 and now it continues with Vegas Pro 17. Usually the video preview will run fine but the moment it hits a transition, not only does it not show the transition but the performance tanks. I've done a bunch of research, tried all sorts of troubleshooting steps such as raising the dynamic RAM preview, lowering the dynamic RAM preview to 0, going into the hidden "Internal" menu in preferences and turning OpenCL/GL Interop to FALSE, disabling resampling, setting the priority to Vegas to High in Windows task manager, and of course setting the preview resolution to Auto. Nothing has fixed the issue and with me trying to use this software for more professional work, it's really starting to hinder my workflow.

Is there some trick that I'm missing? There's no way the software is meant to run this poorly, right?

My specs are below, any help or suggestions would be greatly appreciated.

CPU: Ryzen 2700x

GPU: nVidia 1080ti

RAM: 32GB 3200 DDR4

Thanks as always.

-Mike

Comments

Musicvid wrote on 10/21/2019, 9:16 PM

Yes, transitions are not video.

They must be rendered pixel-by-pixel, frame-by-frame, and if your cpu can't keep up, neither will your preview.

Vegas has a number of options for prerendering your effects, transitions, and generated media. For just looking at transitions in realtime, dynamic ram preview works well.

Mike_S wrote on 10/21/2019, 9:20 PM

Yes, transitions are not video.

They must be rendered pixel-by-pixel, frame-by-frame, and if your cpu can't keep up, neither will your preview.

Vegas has a number of options for prerendering your effects, transitions, and generated media. For just looking at transitions in realtime, dynamic ram preview works well.

Is there a recommended setting for dynamic ram preview? I changed it to 0 and also raised it from the default 200 to 8000 and neither setting made any difference.

I find it hard to believe that transitions aren't meant to be viewed in the preview window. How else would the editor see how the transition works or how it fits with audio cues? My CPU meets the recommended requirements, so I don't think my CPU would be the issue here.

Sylk wrote on 10/21/2019, 10:12 PM

Set Dynamic RAM non zero and define a Region loop to render, next Shift+B.

No recommended setting. Depending of loop duration, project size and framerate, fx applied, involved events... Try to know it.

EricLNZ wrote on 10/21/2019, 10:13 PM

Two things you haven't mentioned.

1 - what is your source material

2 - what type of transitions are giving you the problem.

Mike_S wrote on 10/21/2019, 11:54 PM

Two things you haven't mentioned.

1 - what is your source material

2 - what type of transitions are giving you the problem.

My source material is a series of 4K mp4 files captured from OBS at 100mbps.

I think I should clarify, it's not just transitions but also cuts from one clip to another. Any carry over from one clip to the next occurs a massive hit, forcing me to pause until the program can catch up.

Also Sylk, sorry but I don't know how to tag multiple posts, at least on mobile but what do you mean by define a Region loop to render, next shift+B? I have set the dynamic RAM to 0 and it had no impact.

Thanks.

Sylk wrote on 10/22/2019, 4:12 AM

(...) what do you mean by define a Region loop to render, next shift+B? I have set the dynamic RAM to 0 and it had no impact.

Former user wrote on 10/22/2019, 5:23 AM

s of 4K mp4 files captured from OBS at 100mbps.

I think I should clarify, it's not just transitions but also cuts from one clip to another. Any carry over from one clip to the next occurs a massive hit, forcing me to pause until the program can catch up.

That is interesting. I see that problem with my 4core. the solution I was lead to believe was an 8 core processor, which you're using, but see the same problems. Hopefully there's a solution for you.

(...) what do you mean by define a Region loop to render, next shift+B? I have set the dynamic RAM to 0 and it had no impact.

That transition confuses things a little, as such effect will stutter on any computer. The gentleman believes a simple merge between 2 4k clips should not create such a problem, can you try that?

Mike_S wrote on 10/22/2019, 7:43 AM

s of 4K mp4 files captured from OBS at 100mbps.

I think I should clarify, it's not just transitions but also cuts from one clip to another. Any carry over from one clip to the next occurs a massive hit, forcing me to pause until the program can catch up.

That is interesting. I see that problem with my 4core. the solution I was lead to believe was an 8 core processor, which you're using, but see the same problems. Hopefully there's a solution for you.

Yeah and my CPU isn't really being pushed to any extremes. Certain threads will see a random spike but I don't think my CPU as the bottleneck.

Thanks for the video Sylk, I'll check it out when I get a chance and try it tonight when I get home.

OldSmoke wrote on 10/22/2019, 8:30 AM

Two things you haven't mentioned.

1 - what is your source material

2 - what type of transitions are giving you the problem.

My source material is a series of 4K mp4 files captured from OBS at 100mbps.

I think I should clarify, it's not just transitions but also cuts from one clip to another. Any carry over from one clip to the next occurs a massive hit, forcing me to pause until the program can catch up.

Also Sylk, sorry but I don't know how to tag multiple posts, at least on mobile but what do you mean by define a Region loop to render, next shift+B? I have set the dynamic RAM to 0 and it had no impact.

Thanks.

Where are your files located, internal drive, USB, ... ?

Sylk wrote on 10/22/2019, 5:11 PM

The gentleman believes a simple merge between 2 4k clips should not create such a problem, can you try that?

@Former user 4k30fps 60MB/s from Hero4, on C ssd. Dynamic Ram to 0.

Not sure is comparable with @Mike_S files, anyway:

Musicvid wrote on 10/22/2019, 6:08 PM

Is there a recommended setting for dynamic ram preview? I changed it to 0 and also raised it from the default 200 to 8000 and neither setting made any difference.

Wrong place.

Create Dynamic RAM Preview is a utility used to preview short selections your video. Yes, you need to allocate a substantial amount of RAM in Settings in order preview any length of video. Then use the command in bold below to actually render your section for smooth preview.

So, allocate some RAM, Select a Transition or short section, and call Tools-> Create Dynamic RAM Preview, which willl render your transition so you can preview it in real time.

Oh, pay no attention to the sh*tpile of hype on setting the amount of ram, set what you need to do the task and use it as intended. If you are not happy with Dynamic RAM Preview, use Selective Preview. That's it.

NickHope wrote on 10/23/2019, 1:01 AM

Before a deep discussion on dynamic RAM preview, there is plenty of basic info that we still don't know, to troubleshoot this issue effectively. Especially, how your footage is being decoded.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/ (don't skip parts C2, C6 & C7).