I have been using Vegas Pro 13.0 for a long time. I recently tried Premiere Pro and Vegas 19 since I upgraded my PC several months ago. I'm running i5-11600k, 3080TI, 32GB of memory, and NVMe M.2 Drives.


I open the same files in Vegas 13 and it is much smoother. There might be a touch of lag when clicking play but then it's gone.

Do I need to change some more settings? I am worried I won't receive a refund if I try to request one. After seeing the rendering time and having a good experience with 13 I just assumed 19 would handle the same or better than 13. Guess it's my bad for assuming.

 

If you go to options/prefs/FileIO , change decoder settings to Legacy AVC/ restart, will Vegas operate more like VP13 as far as smoothness with the same file?

Change dynamic range back to 5-10%. Comparing VP19 to VP13 seems like a good place to start, you want to at least get the same file to play the same, and not worse.

If you go to options/prefs/FileIO , change decoder settings to Legacy AVC/ restart, will Vegas operate more like VP13 as far as smoothness with the same file?

Change dynamic range back to 5-10%. Comparing VP19 to VP13 seems like a good place to start, you want to at least get the same file to play the same, and not worse.

This made a huge difference. This seems to be on par with Pro 13. I will do some more reading up on dynamic preview. It seems more may not be better in this case (75%). I see you were involved in this thread too: https://www.vegascreativesoftware.info/us/forum/the-truth-about-the-dynamic-ram-preview-max-setting--132191/

I sometimes use the ram render when previewing transitions and the like.

Thank you for your reply, Todd.

This is my first experience working with UHD footage. I expect it to be a bit of a load on the system compared to HD.

At 4K if you are using ram previews you'll want to turn it up, but the high figures don't help normal playback 1000 or even 200 is just as good for that. Problem if you use Legacy decoder you not have GPU decoding, which you may need with some of your 4K content, and there's also media that won't play without using default decoder (SO4)

The 75% figure is not so good, because you have a good processor and GPU, and they build on the old sony vegas, you would expect processing requirements to go up, but the hope would be with enough processing power it would playback just as well

This made a huge difference. 

@Joshua-Polloni Hi, can you share some of your footages by Google Drive, so that Vegas Team might research it and improve the new decoder?

 Hi, can you share some of your footages by Google Drive, so that Vegas Team might research it and improve the new decoder?

https://drive.google.com/file/d/1ukXeLcSjOmG2Dh5nIqQgcJJryeRpPv9S/view?usp=sharing

 

I sometimes use the ram render when previewing transitions and the like.
 

Instead of RAM preview use the updated prerender option of VP19. No need to preserve RAM and almost as quick, also prerender files remain as long as needed.

 Hi, can you share some of your footages by Google Drive, so that Vegas Team might research it and improve the new decoder?

https://drive.google.com/file/d/1ukXeLcSjOmG2Dh5nIqQgcJJryeRpPv9S/view?usp=sharing

I cut small slithers out of the file to prevent ram caching. Then played back in Resolve and Vegas, Resolve no problem, Vegas not good, playing without cuts in Vegas seems to be on verge of wanting to drop frames.

I"M an amateur at looking at files and understanding how complex and computational heavy they are, but in the absence of an expert.... The file structure looks unremarkable

compared to a high quality encode of same file will require more processing to read

Something else to consider. What sort of AVC does Vegas actually like. I recall a disagreement between @Musicvid and @RogerS, it involved a similar situation a 4K AVC that edited poorly in Vegas with default decoder. Roger recommending lower GOP values for a re-encode such as 60, MusicVid aggressively disagreed, said he didn't know what he was talking about, and Vegas has no problem playing back GOP 250 and higher

So I encoded a file using default AVC values with GOP 250, then changed GOP to 60 and removed B frames, brought both files back onto timeline, this is the result. I tried removing B frames keeping GOP at 250 but remained laggy.

Clearly @RogerS was correct but due to the belittlement he received that day I've never heard him repeat that correct information again. @Musicvid try and control your toxicity towards people over disagreements, it makes people less likely to want to help and there's always the chance you're not right.