That looks like that you have Ripple activated. The red cursor is one of the new indicators in the new build of VP20 that Ripple has been activated - and it is brilliant. Over the last couple of days, I've avoided making an edit with Ripple activated when rippling wasn't intended. You'll also find that highlighting a video or audio event will also be edged in a red border - that means that everything after that event will be ripple moved. It is so good!

If you don't want it, turn off auto rippling.

That darn thing is a new function indicating the Auto-Ripple is on/off.

Ups, @Dexcon quicker.

Bom dia a todos, gostaria de informar não sei se o problema e somente no meu mais a nova versão do Vegas pro não me deixa alterar o Curves como na versão anterior Build 214

Alguem pode me ajudar?

I'm seeing an issue with V20 (326) not opening the last saved project on start, if I disabled the welcome screen. I have the option/preferences checked to load last project on startup. I was able to replicate this issue several times.

Otherwise, build 326 seems "more" stable than "214", however, it will freeze (on my setup) on both editing and rendering, just a bit less often now. Less editing issues if I lower the playback resolution. (Good/Half seems to work fairly well for editing stability). GoPro 4K-24 HEVC, Nvidia GX1070, Series 7 Intel.

Yes me too, uncheck enable welcome screen and load last project does not work.

Hello,

I just happen to update the new build for Vegas Pro 20. However, as soon as I save the project, big or small it is, 15-20 seconds of lagging occur after I save. I'm trying to figure out this issue from build 214. Any ideas? I don't know if it's a Vegas or my Pc problem, which by the way meets all the requirements. Thanks!

If this happened also on build 214, try first to reset Vegas by following this tutorial exactly with also delete your cached files : https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
If that does not help it is better to start your own post and start with the needed information shown here: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Hello,

I just happen to update the new build for Vegas Pro 20. However, as soon as I save the project, big or small it is, 15-20 seconds of lagging occur after I save. I'm trying to figure out this issue from build 214. Any ideas? I don't know if it's a Vegas or my Pc problem, which by the way meets all the requirements. Thanks!

Try turning off project collections in Hub. That helped me.

The "sluggishness" still continues - not as bad once project hub thing was turned off (I also unchecked the close media option, so everything would still be "loaded up" when I go back to VP20).

I wonder if it's some kind of cache thing? I notice that there is a decent "one-Mississippi & change" before playback starts. But if I stop and start at the same point, it starts playing immediately. Move the cursor to a different point in the timeline, hit play - another good second or so delay. It's acting the same as it does when it hits an event with a lot on it (especially time-altered clips) where the cursor starts to stutter on the timeline.

Looking at some of the other comments, I can say that it is exclusive to this build - the one just before was working great - though VP20 has driver crashes a lot more frequently than 19 did (which was seldom to never on my system).

The "sluggishness" still continues - not as bad once project hub thing was turned off (I also unchecked the close media option, so everything would still be "loaded up" when I go back to VP20).

I wonder if it's some kind of cache thing? I notice that there is a decent "one-Mississippi & change" before playback starts. But if I stop and start at the same point, it starts playing immediately.

@Jessariah67 That is how it's always operated in the past, except it would play immediately and cache at the same time, this would often result in GPU decoder overload lag and cause the first few seconds or more of lagging, the solution was often to pause/play as you're doing now. At first I considered this approach 'cheating' a way to playback a file in real time that Vegas couldn't actually playback in real time, but give it enough cache it can. Note that Premiere has a similar system, which is more transparent(easy to see) you can see the GPU decoder turn off before it gets to the end of the timeline.

It's why to test playback on Vegas, you can't use a single clip, you have to cut it up then do a short fade transition. This prevents caching when it gets to an edit point. I still don't see the delays with the amplitude you do. You should check Vram and System Ram, make sure either are not overloaded. Especially check if Vram is full or nearly full and overflowing into shared GPU ram... which is system ram.

Thanks for that - and I'll be sure to check those things out. There is still a noticeable difference between the last two builds in timeline smoothness and playback latency. I know for me, I get the "Windows" driver crash about 4Xs as much as the "Vegas" crash.

I cannot open Vegas 20 at all. I have waited a long time several times just in case there was a possible delay as described in this thread.

I had opened Vegas Pro Edit today, probably the first time in a month and got the major update dialogue box, which I completed.

Now nothing even after multiple reboots. Tried the Start menu, the taskbar, the "Open File Location", plus the Vegas200  DOT exe in the C-drive Program Files. Now it does not work for Vegas 19 or 18 either

No issues at all on any other software e.g. Davinci Studio 18.1.2, Capture One 22 Pro, Affinity Photo 2.0.4

Laptop Dell Alienware, Windows 11 home bang up to date, BIOS also is up to date as are Ryzen 7 5800H & RTX3060 studio, 32GB ram, 1tb SSD on main drive, 2tb internal SSD for media etc

Thanks

Thanks

For what ???

@Peter-Riding, I don't have a laptop, but a desktop. Specs in signature below. Vegas has never failed to open for me unless for some strange instance, I exit, and Vegas hasn't fully closed. Using Task Manager, ending it, it opens.

Right now, with Win11 VP20 opens fine. With Win10 on my dual boot computer (NVME for Win11 and another for Win10), no issues. But then, I have zero knowledge of laptops with 2 GPU's, nor how you have them configured as far as GPU's and if the drivers are current.

Thanks

For what ???

 

In anticipation of a solution

When VPro 18, 19 and 20 are not working I think there is something more wrong than the the update of version 20 what this post is about.
We need more information about your hardware ( driverversions) and (customized?) settings of Vegas Pro 20, but you can now start with a reset to the default factory settings exactly following this instruction : https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Okay. The update went smooth and works great on my desktop. Here I am a few weeks later trying to apply the same update to my laptop, and no the in-app update fails repeatedly. So, I am stuck waiting for the download link to work....and am honestly thinking the Magix update servers need some serious upgrades. I am getting bits and kilobytes of download speed on a fully functioning gigabit connection. >.<

AMD Ryzen 5 5000 series, 16gb ram, AMD Radeon (I think Vega 8, no hate as this is for raw photos, and 720p vids while traveling), 500gb ssd.

Edited to fix spelling.

Thanks, got there in the end. This initial method as described in Nick Hope's thread did not work as it only showed a dialogue box requesting registration but already had the full registration details showing. There was no opportunity to go the Reset route.

I then tried to remove V20 using the standard Windows 11 process but that froze at around 30%. So I tried installing V20 (the previous version I already had an EXE for) on the basis that with some programs it may go the repair route; but that froze at 3%

Went back to the Nick Hope CTRL+Shift route and clicked on register even though the dialogue box described it as already registered and showed the full name and serial no. etc.

That worked and I can now open V20. It had already accepted build 326. It had also retained my personal preferences and settings including Pluraleyes and Vegasaur etc. (which I save anyway).

Weird. I had become concerned about the continued feasibility of Vegas over the last couple of years as there were so many problems posted on this forum. Therefore I got up to speed with Resolve Studio version as well  as I need reliability for earning a living. Its interesting to delve into the two e.g. Vegas is extremely easy to back up archive and restore compared to Resolve which uses a nightmare database process. Vegas is also much easier for multicam when using Pluraleyes whereas Resolve is a convoluted mess when you need to use Pluraleyes. But Resolve is much cleaner once multicam is actually set up in my view. Resolve has been streets ahead in colour editing but I suspect Vegas has now caught up.

I've just upgraded from Vegas Pro 17 to Vs 20. It's a mess! Multiple crashes...most requiring a PC reboot. The menu items are a hodgepodge of confusion...scattered everywhere with locations not at all intuitive. Editing tools are difficult if not impossible to locate! At this point I'm wondering if Vs 20 was ever Beta tested!

Under Options\General Preferences I have checked Automatically open last project on startup but nothing opens upon opening Vegas 20. Note: I have selected to uncheck the Welcome Screen. Is that the issue?

O.K. I think I get it. Vegas will indeed open the last project but with Welcome Screen opened as well, which I must close manually to continue my work. If this is how it is designed to work I suggest that a better way would be to have the last project open without the Welcome screen once the user elects to deselect the screen. Right now it amounts to a useless redundancy.

My goodness, what's up with these update servers? 4 hours to download in Europe... 🙁