There are times that I also had frequent crashes and after having system restart, everything then goes smooth.
Hi. Today I tested the new version for a while. On my 4 core Xenon the following bugs still remain:
https://www.vegascreativesoftware.info/us/forum/vegas-pro-20-feedback--136686/?page=1#ca854194
Can anyone confirm this?
Any thought on stability and bugs yet, better than VP19b550?
How about those memory problems?
I have to say I'm very disappointed in this new update, just went from Vegas 19 to 20 with today's update but the timeline is incredibly laggy in Vegas 20, to the point where I'm sitting banging my fist on my table in frustration. I can't figure out why this new version is so much worse and I tried copying over my preferences but that didn't help either. What is going on with this new update?
The same happened to me until I realized that colour grading was activated above the preview window (not by me) removing this changed the rate on my project from 6-11 fps to the expected 25.
Hmm what exact setting are you referring to? Can't seem to spot anything about color grading above the preview window. Do you mean that a Video Output FX has been added with color grading?
Can confirm. Titler Pro 7 still fails to launch.
@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.
NewBlue says they are trying to figure out what the problem, but not doing mutch to fix it 😕 Anyway - it's sold by Vegas (Magix), so it's also a Vegas issue ☝️
The "auto FX resize" issue is still here--if any VST2 (non Magix audio plugins) are in the chain, the windows resizes no matter if the box is checked. Any hope for this, as it's a big one for me who does a lot of audio post.
@janndk, @Elynde I have seen several reports of TP7 working correctly in VEGAS Pro 20 build 214. If it's not working, my first suggestion would be to do a clean install which, basically, means uninstalling TP7, deleting any left over files and registry entries, and then reinstalling. But Magix did work on issues with TP7 and Boris not properly loading in build 214.
Got lots of problems with latest build. Lots of crashes caused in most by TP7. Sometimes it happens during playback, secondly while put TP7 media generator to the timeline.
The "auto FX resize" issue is still here--if any VST2 (non Magix audio plugins) are in the chain, the windows resizes no matter if the box is checked. Any hope for this, as it's a big one for me who does a lot of audio post.
This will be fixed in the next update. The fix was made just after the code freeze for this update.
Got lots of problems with latest build. Lots of crashes caused in most by TP7. Sometimes it happens during playback, secondly while put TP7 media generator to the timeline.
That sounds like a TP 7 issue. I gave up on using new Blue products years ago, I've never had one that worked properly for me.
Can confirm. Titler Pro 7 still fails to launch.
@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.
Yes, I will contact NewBlue again and update my existing ticket. I have removed Titler Pro 7, its caches, the app data folders, and reset the Vegas cache before rebooting my system entirely for good measure. Installed Titler Pro 7 again and allowed Vegas to boot up after. I thought that did it at first, but it still hangs if you need to change a title in a saved project.
Video of the issue after repeating my test (note it did not hang on initial launch the first time, only on the launches after it failed to open a saved project's title): 
Apparently you need to download deep Learning 20.2 but I can't find it, anyone have a link? Thanks.
Nice to hear, that the 360°-Bug is fixed now. I will try to get a new trial-key for Vegas Pro to test it and perhaps than I buy the new version.
Do you think, that it is possible to support some most used cameras, like from Insta360?
Apparently you need to download deep Learning 20.2 but I can't find it, anyone have a link? Thanks.
@andyrpsmithIt was in the forum announcement (news) page: https://www.vegascreativesoftware.info/us/forum/vegas-pro-20-build-214--137660/
Can confirm. Titler Pro 7 still fails to launch.
@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.
Yes, I will contact NewBlue again and update my existing ticket. I have removed Titler Pro 7, its caches, the app data folders, and reset the Vegas cache before rebooting my system entirely for good measure. Installed Titler Pro 7 again and allowed Vegas to boot up after. I thought that did it at first, but it still hangs if you need to change a title in a saved project.
Video of the issue after repeating my test (note it did not hang on initial launch the first time, only on the launches after it failed to open a saved project's title):
Just in case, try this, run VP and TP as Administrator. You can change the setting by right clicking on the 2 apps icons then using properties click on the "Compatibility" tab and click on the box labeled "Run the program as an Administrator".
@janndk, @Elynde I have seen several reports of TP7 working correctly in VEGAS Pro 20 build 214. If it's not working, my first suggestion would be to do a clean install which, basically, means uninstalling TP7, deleting any left over files and registry entries, and then reinstalling. But Magix did work on issues with TP7 and Boris not properly loading in build 214.
I did the clean install. When that didn't work, I went to update my existing ticket with NewBlue. They responded by having me completely remove Titler 7 again, and sent me a beta version to test that works beautifully. However, the beta comes up as a trial version and doesn't take my keys, so I am working on getting a non-watermarked version of the beta update from NewBlue. ... I am so happy I will be able to access my titles again without having to render them stand-alone!
Glad to hear they've been responsive!
Glad to hear they've been responsive!
Yay! Problem finally resolved! Between that and the continued improvements to Vegas, I am a very happy camper.
Is there a way to check the version of deep Learning? I would like to know if it is version 20.2.
Build 214 was updated via the default method. I must have been one of the early birds, as nothing was mentioned at that time of a new build on this forum... The update downloaded reasonably fast and updated flawless, so not downloaded via the links. If I would have downloaded via the links provided here now, then I would have known for sure.
Or in Windows 11, R click on the Start button, select the top item - Installed Apps - and scroll down to the Vegas Pro 20.0 (Deep Learning Models) entry. The full version number (e.g. 20.2.0.0) is displayed there.