When you mention, can't "revert" are you talking about going to a previous version of Vegas? If so, just highlight and copy the timeline and paste it in a previous version.

Yes, I can't revert to V17 or V19 after having started it in V20.

This has never worked in Vegas pro - or in most programs I know.
Computer-Programs are (conditionally) upward compatible, but not downward compatible.

@Roger Bansemer all you have to do is open VP20 and the project. Highlight the entire project, copy (Ctrl c) and paste (Ctrl v) into 17 or 19.

That works with the clips themselves and audio but if you have color balance, etc on the track level it would not carry over.

. Working with V20 is horrible. Even with a new project with only a few video clips and one audio track on the timeline, the lag time and crashes are almost continues.

I think I'm very lucky not seeings those problems and therefore I like to help you if possible.
Therefore it's needed to see a few of your settings, screenshots of
- Options/Preferences/Video
- Options/Preferences/File I/O
- Screen you get after Help/Check for Driver Updates
 

 

Thank you. That is very kind of you. Hope you can spot something.

Thank you for the pics but I see 2x the same pic of File I/O and not one of the Video tab

Thank you for the pics but I see 2x the same pic of File I/O and not one of the Video tab

Sorry, my mistake.

Set your Dynamic RAM Preview max back to default if you use that option a lot.
When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore.

@Roger Bansemer all you have to do is open VP20 and the project. Highlight the entire project, copy (Ctrl c) and paste (Ctrl v) into 17 or 19.

That works with the clips themselves and audio but if you have color balance, etc on the track level it would not carry over.

This is exactly the limitation why upward compatibility cannot work.
If certain functions were added in later versions, or possibly changed, how should a previous version be able to display that?
What Reyfox suggested to you is a workaround, a crutch, but nothing more.

Set your Dynamic RAM Preview max back to default if you use that option a lot.
When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore.

I'll give that a try however I do use the preview render quite a bit.

Selectively Prerender Video (Shift+M) has nothing to do with Build Dynamic RAM Preview(Shift+B).
If you select an amount of RAM for the latter it is not anymore available for other tasks on your computer as f.i, making edits or outside Vegas looking at the internet.

Settings look fine here though I agree the dynamic ram preview/ shift b allocated is on the high side! At least you have a lot of ram.

There is a newer NVIDIA studio driver but changes appear minor.

If you have track level changes you could save the presets and apply them to the copied project in 19 or 17. Or just do it manually with both programs open at the same time.

Set your Dynamic RAM Preview max back to default if you use that option a lot.
When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore.

I'm watching a Vegas tutorial on youtube by "scrapyard films" and he says to set dynamic range as high as possible and your advice is the opposite. I'm confused

His video states this at about 1:00

It is you who can and must decide, fortunately I have no problems

Set your Dynamic RAM Preview max back to default if you use that option a lot.
When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore.

I'm watching a Vegas tutorial on youtube by "scrapyard films" and he says to set dynamic range as high as possible and your advice is the opposite. I'm confused

His video states this at about 1:00

Hi @Roger Bansemer I like using shift B and use it often, so I have always had DRP set high and I've never had an issue with it causing crashes or lagging.

Edited comment: But now reading Roger's comments below and proving it to myself with some tests, I realise there are disadvantages of assigning too much RAM to DRP. So I will go with 5% of my 64gigs from now on and see how I get on. I'll just increase it a little if I regularly find that sections I want to preview require it 😊

I'm watching a Vegas tutorial on youtube by "scrapyard films" and he says to set dynamic range as high as possible and your advice is the opposite. I'm confused

I would simply try both.
Not even on the Internet do you have a guarantee for the all-embracing truth.

It's a preview buffer, nothing more, and you'll see there are diminishing returns for playback framerate which you can confirm yourself.

If system ram amounts are low (16GB) you can slow down Vegas by overassigning ram to dynamic ram preview. Even with 32GB Vegas may run short on ram it needs to do other things. That depends on the nature of your project and footage. So saying one number like 75% of system ram isn't really helpful in my opinion.

It should also have no positive impact on stability and potentially negative at the rendering stage as it can conflict with GPU encoding, at least in pre Vegas Pro 19 versions.

@RogerS I used to think it was just "a preview buffer", that I could render a section into RAM and then get a smooth preview of the final render from the RAM, that’s why I like it. But now I’m well confused. If it’s just a preview buffer and nothing more, why does it have an affect on render times and frame rate?

These are my results with the 4K Sample Project:

GPU decoding            
DRP %    MB     Render time    Section ave FPS
0     0     02:18     18
5     3274     00:58     20
75     49111     00:56     8
            
Legacy AVC decoding            
DRP %    MB     Render time    Section ave FPS
0     0     02:15     19.5
5     3274     00:54     20.5
75     49111     00:54     9.5

Exactly as you said, “diminishing returns for playback framerate” if set too high. But the render time, over two minutes with no DRP, and then a consistent 54 seconds when set on anything from 1% - 75%

This has made me realise how little I understand and that my comments may just confuse things, so I wish I could retract my previous comment to @Roger Bansemer. As a proverb says “Even a fool who keeps silent will be considered wise”. So, in future I will be an avid reader of the forum, and maybe ask the odd question, but leave the commenting to you big boys, of which I have to say, I really appreciate 😀

It's a preview buffer that also buffers frames during normal timeline playback, not just when you explicitly make a ram preview. It's also active doing the same thing during rendering, though until VP 19 (from 15-18?) it was improperly interacting with the GPU encoder leaving artifacts (which caused me all kinds of headaches in the VP 15/16 days).

You and I did similar tests and it seems that only a very small amount matters for rendering, so the old default of just 200MB is fine. I leave it on the new default of 5% for VP 19 and 20.

I don't think it matters for stability, and the other changes in that video and ones like it have greater impact, but making multiple changes at once makes it hard to distinguish what is effective.

Edit: please do continue to comment as it's how we all learn. I've been corrected here as well and that's fine by me- I'd rather understand more fully than be right or protect my ego.

@Vincent-Brice You can edit your post. There should be a red Edit button on the right of your post.

@Vincent-Brice You can edit your post. There should be a red Edit button on the right of your post.

Haha, just proved my point entirely, I was clicking the MORE option and forgot about that massive red edit button!! 😂 Thanks.

You are so lucky. I'm using 365. Maybe that a problem. I have no idea except now that I've started multiple projects with V20 I can't revert and it's made editing unpleasant where it use to be a joy.

I also have the subscription one but cant use for all the same reasons and have raised a call in with Magix for a few weeks with no luck yet and have sent them all the info they requested except a screen shot of the lagging 😂, but I did say I could do a screen recording if they wanted it.

On 20 I have a laggy timeline, a second or two before anything happens after a click of the mouse on anything and constant crashing. I have given up on 20 until its fixed and have gone back to 19 which is perfect, same media used on both as they are all weddings filmed the same way, the last wedding I edited with 20 took twice as long to finish as normal and that was a HD one. The one I am editing now in 19 is 4K one and no issues at all in 19 and flying through it and with no proxies , even though I have now gone with the subscription I am sticking with 19 for this season's weddings.

Just something I noticed and to perhaps note, I accidently opened a 4K edit up in 20 which I had started in 19 and it was perfect and all normal as like when in 19, no lagging, no crashing and ran just like 19, UNTIL I clicked save and it said do you want to save to a newer file type, so after backing up the file, I tried it and as soon as it converted to 20 all the bad issues started again making me think its something to do with the new file type, not sure but there's a strong clue there, I'm now back in 19 to finish it.

Sorry I also posted this as a quote to someone in another post who is having the same issue but wanted to share here as well due to the file type issue I noticed, so hope that's ok to repeat.

Kind Regards

Stephen

@Sging2 curios as to what type of 4K clips you have, what created them and what you have done ot them on the the timeline. How long is the project?

I've been quite happy editing 4K 10 bit 422 MOV clips from my Panasonic camera. Using Boris, NBFX, Ignite Pro and some Vegas effects and nary an issue saving. I've turned off in Vegas Hub "Create Project Collection" which is on by default. I do my own incremental saves and don't want any "automated" software tick doing it for me.

A buddy of mine, @Wiew, does corporate videos also using Panasonic 4K and Mavic Mini 3 Pro 4K. He said to me that he has basically only had one crash, and that could have been because of a third party plugin. He re-imaged his hard drive, updated drivers and installed his necessary video and music creation software.

@Reyfox I had 2 ;-)

One working mercalli , it woud not go back to V20

Two working with waves vst 3 equaiser .

Both things happppend ony one time , the next time it worked ok

I did a clean install on a clean windows pc