Sapphire plugins are appearing in my paid Vegas Pro 20 since I first installed VP20 and updated with each update. Now on Build 403
Thankfully Build 403 retains the compatibility of Build 214. Intermediate builds have been crashing with the files from my camcorder.
No more having to dodge the "Update" button :)
My problem seems to be that Vegas 19 refuses to open my Vegas 20 current WIP. Now what? I could live with this serious error if someone would tell me how long will it take to get Vegs 20 running again. Anyone?
My problem seems to be that Vegas 19 refuses to open my Vegas 20 current WIP. Now what? I could live with this serious error if someone would tell me how long will it take to get Vegs 20 running again. Anyone?
What's your error with 20? I didn't see that in this thread. The startup issue is already patched for 20. If you can open both you could try copy and pasting the timeline.
My problem seems to be that the patch hadn't worked either. I'll go back and give it a try again.
My problem seems to be that Vegas 19 refuses to open my Vegas 20 current WIP.
Correct. Vegas Pro 20 .veg projects are not able to be opened in earlier Vegas Pro versions. In the last 13 years, the only .veg projects able to be opened in the immediately previous version was Vegas Pro 12.
In that case the patch to open an earlier version becomes meaningless, doesn't it?
Have you tried this intermediate solution for Vegas Pro 19, Paul?
I think that build 403 for Vegas Pro 20 should work. Another patch for Vegas Pro 19 will take longer.
In that case the patch to open an earlier version becomes meaningless, doesn't it?
Just curious - where do you see that the patch enables VP20 projects to be opened in VP19 - I've not seen that myself.
I installed the update to 20 what a tragedy, it helps to physically disconnect the cable from the network (interestingly, version 18 works) Looks like a problem with logging in Vegas HUB
I've been using DAVINCI studio version 18 for half a year and my problems are over. It hurt a bit because I've been working on VEGAS for 12 years since version 11... unfortunately MAGIX if it doesn't do anything... nobody wants to work on VEGAS and when it does, it's a shame in the industry :( I grit my teeth but I was just stupid...
I updated to build 403, and no problems. I did this both on a Win11 Pro and Win 10 Pro build. For me, I can't see how it was a tragedy since the patch for 20 was put out fairly quick. So what specifically does Magix have to do? Vegas is working for me with the only downtime of waiting for the downloads (2 of them).
I've had Resolve Studio for a few years now. And it's not perfect either.
I installed the update to 20 what a tragedy, it helps to physically disconnect the cable from the network (interestingly, version 18 works) Looks like a problem with logging in Vegas HUB
So are you saying that the new VP20 build 403 hasn't solved the opening problem? It has for me and many others. There are dozens of posts/comments about this problem in the last 12 hours or so which have included workarounds and the build 403 fix - have you explored these?
I installed the update to 20 what a tragedy, it helps to physically disconnect the cable from the network (interestingly, version 18 works) Looks like a problem with logging in Vegas HUB
I've been using DAVINCI studio version 18 for half a year and my problems are over. It hurt a bit because I've been working on VEGAS for 12 years since version 11... unfortunately MAGIX if it doesn't do anything... nobody wants to work on VEGAS and when it does, it's a shame in the industry :( I grit my teeth but I was just stupid...
The solution was published some hours after the issue was detected only. The development team did a night-shift here, and came up with a very fast solution for Vegas Pro 20. I think that should be appreciated too.
While I understand that Resolve is a very good product, it is also correct that the development team has reacted here with an impressive performance. No need to be ashamed really.
Props to the entire team for moving so quickly on this.
Props to all the Vegas Gladiators! Appreciate your dedication. It looks good on you!
I'm glad the bug was fixed in under 10 hours and a patch released so quickly.
Thank you to those who worked hard and swift to get that out -- I'd send donuts but .. not sure how many or where :-) Go get a coffee or some sleep!
I did read the e-mail and posts urging people to install 403 ASAP.. this is good. I'd love if it went one step farther and explained what the problem was -- how does a system just stop launching on a specific date when connected to the Internet... was it something funny a dev put in that accidentally wasn't removed? And so customers can keep confidence, what measures are being taken to avoid this happening again?
Download of 403 is stuck at half the file size (292 out of 627). Also question, why should I reinstall the whole 1gb while patch is probably one small library???
Info for those who needs VP19b651
https://www.vegascreativesoftware.info/us/forum/patch-vegas-pro-19-build-651--140802/
@LennyK - because the installation process require from a package big file.
Thank you for quick patch and quick reply. But such a huge size to be replaced (the whole executable) means that probably package architecture is not optimal/modular enough.
But what is more importan, can Vegas do something to scale up download capability - I have to finish video today but spent 2 last hours watching download time increasing.
Slightly differing download links for the installers. If the first one is slow, one of the others *might* be faster:
VP19
VP20
Agreed that we need to improve the patch optimization for our updates. It is something we are actively working on and one of the reasons we moved to a new installer for VEGAS Pro 20. We had hoped to have been able to roll out the new patch mechanism by now, but it simply is not ready yet.
As far as bandwidth on our download server, that is also something else we are working on. It has been an acknowledged problem that we have had for a long time. I can tell you that our remote engineers (which is most of us) use the same pipeline as the download server are even more frustrated by these speeds on a daily basis, especially at times when we release a patch.
Can anyone explain why I have the problem and I have not updated VP, I'm running VP20 B360.
Yay; victory over defeat! I'm working with the real V20 right now. Thanks to all who patiently led me through the fog.