20 seems to be more stable than 19, no crash so far with this new version.
My thanks to the development team for that !But ... the "Video Stabilizer" media effect seems to be broken in VP 20 (build 214). Any insight ?
Not seen that so far, been using both the legacy stabilization (note that this will crash Vegas on about 10% of clips) and the current video stabilization option which has never crashed.
Considering that Vegas is moving to the gradual release of new functions, every new upgrade should be a trial again.
Considering that Vegas is moving to the gradual release of new functions, every new upgrade should be a trial again.
I have to agree with this. We need to figure out a new model for letting users test out the product as new features are released. Currently we are sort of stuck in a situation where our development team has moved on to continuous delivery of features, but the other aspects of the company are still working to convert over to this model, so things are a little mixed up right now.
Considering that Vegas is moving to the gradual release of new functions, every new upgrade should be a trial again.
I have to agree with this. We need to figure out a new model for letting users test out the product as new features are released. Currently we are sort of stuck in a situation where our development team has moved on to continuous delivery of features, but the other aspects of the company are still working to convert over to this model, so things are a little mixed up right now.
Being Vegas such a complex multiuse tool as it is, its Beta testing team already needs to comprise enough specialized usages and thorough participants. More so, with the actual continuous feature delivery policy.
By reading this forum, one could easily spot some potential participants that'd be quite fitting to those role requirements, assuming they'd accept.
In fact, there is a second measure that could be implemented by Magix to better adapt their recently adopted frequent development and implementation cycles; some kind of reward system (and possibly compensation) could be devised for those acute non-beta tester users that discover a newly introduced bug.
This build crashes all the time. Not possible to work. What do I do? Can I get another version please?
@Ola-Forsslund There is no other version for now!
Vegas build 214 is a solid, stable version, So what specifically is causing it to be crashing all the time on you?
they really need to address the updater in Vegas. Slow.. been that way for a long time. More bandwidth needed :) Or give us the downloadable link..
The bandwidth issue is something high on the priority list for our IT department. The just finished a major update of the customer service system, which had taken almost a year to implement. Hopefully they will now be freed up to try to address this issue.
It took about one hour to download 😕 Anyway - the update process went smoothly, and everything seems to work just fine 👍
…or almost everything. VEGAS Movie Expansion Pack still not compatible with Vegas Pro 20 😒
Can confirm. Titler Pro 7 still fails to launch.
I am having major problems with Titler Pro7, it will not launch and causes Vegas 20 to crash as well. I submitted a ticket but not yet received a reply. I notice also it now does the same on Vegas Pro19 -which was ok before the 214 update, but works fine on Pro17, I kept these versions installed as a safeguard.
This build crashes all the time. Not possible to work. What do I do? Can I get another version please?
I agree that Build 214 is not as stable on my system as 139. I am taking V18 projects which were configured for Blu-Ray and had 25p XAVCS time stretched to 24p. I'm doing simple things such as levels filter, stabilization, pan crop, volume adjustment and on a 5 min project I get 214 randomly freeze with not responding white screen which is not recoverable five or even ten times. I have even tried replacing the 24p clips with original 25p and re-edit but still 214 will crash - albeit slightly less often. Changing back to 139 has brought much improved stability maybe one crash rather than ten. XAVCS is not and should not be a difficult codec for Vegas to play with. I am also using Titler Pro 5 and it is working well (again very simple stuff).
@Graham-Hilton I found that the solution to the TP7 problem was to completely uninstall it, then re-install. After doing that, it is working as expected for me now.
Hello Jack, well in my case I downloaded the beta version from Newblue. This cured the problem of titler pro not working but left another one. Now after using titler pro and then closing down Vegas a fault pop up screen appears saying Vegas has stopped working and sends a report off (somewhere). I have been in contact with Newblue who are very helpful and reply quickly. They seem to think the problem is because it's still in beta and will be resolved when it's completed. I read somewhere on here that a cure was to install the beta, uninstall it then install the original. I tried this but it just came back to square on with titler not working so I reinstalled the beta. I did carry out the full removal instructions as well. I can cope with the pop up screen appearing at the end of a session for the time being.
@Graham-Hilton I found that the solution to the TP7 problem was to completely uninstall it, then re-install. After doing that, it is working as expected for me now.
This build crashes all the time. Not possible to work. What do I do? Can I get another version please?
I agree that Build 214 is not as stable on my system as 139. I am taking V18 projects which were configured for Blu-Ray and had 25p XAVCS time stretched to 24p. I'm doing simple things such as levels filter, stabilization, pan crop, volume adjustment and on a 5 min project I get 214 randomly freeze with not responding white screen which is not recoverable five or even ten times. I have even tried replacing the 24p clips with original 25p and re-edit but still 214 will crash - albeit slightly less often. Changing back to 139 has brought much improved stability maybe one crash rather than ten. XAVCS is not and should not be a difficult codec for Vegas to play with. I am also using Titler Pro 5 and it is working well (again very simple stuff).
Andy, how do you find the link to download build 139 please?
Regards
Graham
Great that the forum has links to previous versions, so helpful. So far since going back to 139 my re-editing of previous projects is a pleasant experience with minimal to no misbehaviour. It maybe different for you depending on the media you are using and what editing activities you are doing. I now have a Vegas folder where I keep previous versions that are more stable on my now fairly old system.
I found 214 much more stable than 139. It rarely crashes unless I'm using a large file inside the trimmer. Proxy files will allow even more stability and no trimmer crashes, if you can endure the length of time it takes to render them :-)
I agree it is likely that proxy files will allow greater stability. You are using HEVC and I'm using H264 XAVCS.
@Graham-Hilton Now after using titler pro and then closing down Vegas a fault pop up screen appears saying Vegas has stopped working and sends a report off (somewhere).
Yes, unfortunately I get that as well If I remember right, this started happening when I updated to TP7 build 210922. It doesn't happen with TP build 210724. I think I'm right with those two statements. It was over 12 months ago.
It's annoying, but I've learnt to ignore it and choose not to send. Just wait a few seconds after VP closes before you use the mouse, otherwise you may ineadvertently send off the report, as the mouse defaults to the send button.
Thanks for the info Jack I will give that a try.
Just updated to Soundforge Suite 16 which includes RX10 Elements (currently have RX7). Problem with running RX10 Voice Denoise. Vegas does not behave correctly in that in rate adaptive mode the Timeline stops moving, sound is heard, no mouse control anywhere in Vegas, preview window shows video, Vegas is stuck with only way out is kill Vegas via Task manager. When RX10 set to learn it plays but timeline freezes during learn but control comes back at end of clip. Better but not correct. When using RX7 voice denoise it works correctly with Timeline control working during the analysis. I am using V20(139) and XAVCS 4K. Anyone else seen this?
Weren't VST issues fixed in 214? I found too many issues with the first build and iZotope to rely on it.
Weren't VST issues fixed in 214? I found too many issues with the first build and iZotope to rely on it.
Roger do you have RX10 Voice denoise and 214 to try it. I am running 139 while I go through some back projects as it is much more stable so I do not want to go to 214 again just yet?
At least on my system, it does not like any RX10 plugins at all. Anything RX10 will randomly cause a crash or randomly cut the audio during playback..I'm also finding I cannot use the Spectral De-noise plugin from RX8, RX9, or RX10. As soon as I select it to adjust the settings, Vegas will display the plugin and then hang on updating the plugin row at the top of the window. It will sit there at 100% load on a single core. I have to use Task Manager to cleanly close Vegas. This is also with "Enable Automatic FX Window Resizing" uncheck in Preferences. The other RX9 plugins are working without issue.
Hi Andy I don't have RX 10 as I don't want to be stuck with VST 3 yet. I'm on RX 9 and mainly using VP 19 while I test 20. For audio I didn't find 139 usable with Izotope. I'll test 214 soon in more depth.