@mark-y you disconnect the ethernet, start VP20 and let it fully load. And then plug the ethernet cable back in. It really can't be more simple than that. I did it and it worked until I installed Build 403.
What I don't understand is, this is an easy working solution until the servers get straightened out. Vegas will work, and then your internet for the computer will work.
I can see if VP20 was totally borked by all of this, but it isn't, and you can still edit with it. You just can't start it while you are connected to the internet.
Anyone having #problems with #VegasPro 19 or 20 has tried blocking the #MAGIX server addresses in the windows HOSTS file to see if that works?
I tried, but since I don't know all the address, it didn't work at first.
have i tried everything? did I turn off the internet? I changed the date, and it does not open vegas. "File I/O surrogate ( not visible ) / error reporting client launcher "
vegas trial 20, I can't take the test😡😥😩😭😭😭
have i tried everything? did I turn off the internet? I changed the date, and it does not open vegas. "File I/O surrogate ( not visible ) / error reporting client launcher "
vegas trial 20, I can't take the test😡😥😩😭😭😭
Read my message above yours.
By installing Vegas Deep Learning Models 20, it solved the Message issue. However, it presented a problem in Vegas Pro 20. When loading it to open, it gave an error and closed by itself. I had to reinstall Vegas Pro 20 to fix the problem. That is, with each update, Vegas Pro 20 presents a new failure.
@Evanilson-DjCandir A razão pela qual você recebeu essa notificação é porque você precisa instalar os modelos de Deep Learning mais recentes junto com a instalação do Vegas!
By installing Vegas Deep Learning Models 20, it solved the Message issue. However, it presented a problem in Vegas Pro 20. When loading it to open, it gave an error and closed by itself. I had to reinstall Vegas Pro 20 to fix the problem. That is, with each update, Vegas Pro 20 presents a new failure.
I've been trying all the mirrors to download, but it's been 5 hours already and I still trying to download. I only get 50Kb/s, estimated downlaod times 4+hours.
I am getting about 50kb/s as well, spikes a little higher and then a little lower but the average download will take about 4-5hrs... Downloaded Internet Download Manager, it is downloading at 500kb/s as it seems to be downloading multiple chunks at a time to boost the speed.
is anyone else's update taking forever? it says estimated 8 hours ... that's another day of work i lost.
is anyone else's update taking forever?
@SunflowerSamu please check the multitude of previous posts/comments on the issue.
I am getting about 50kb/s as well, spikes a little higher and then a little lower but the average download will take about 4-5hrs... Downloaded Internet Download Manager, it is downloading at 500kb/s as it seems to be downloading multiple chunks at a time to boost the speed.
Thanks for this tip! It's downloading the deep learning models for me now.
where is a link to 403, this is 402
never mind I got it
Users of Voukoder may find that build 403 crashes when you try to render. My machine does (but mine's ancient). Workaround is to use a different encoder. I've not tried poking at Voukoder's settings yet, but I have upgraded to the latest version and it's made no difference.
Direct downloads as provided here always work well for me. I never use the download manager, although it is a mystery why it is so slow.
Even though it doesn't seem fashionable lately, I would like to thank the Magix Vegas team for a speedy fix for an issue that apparently wasn't their fault, as it also occurred with earlier versions.
I received the message about a needed update VEGAS Pro 20 (Build 403). BUT when I go to the website to download, I do not understand which download to click on. I am in the United States, and can't figure out which of the many download links I should use. My Vegas Pro 20 WILL NOT open and I ned to do the right download. Please advise.
This "New" ""FORCED UPDATE"" because of the May 3rd debacle has totally messed up our program.
After installing this update, Project Media is no longer connected to edits within the time line forcing us to replace all the project media within the project and reconnect and then redo most of the edits... undo attempts causes the program to crash, and the whole environment in now completely unstable.
And of course this all happens at the end of a project at the day of final rendering.
This is the last project our company will do in this environment of VEGAS 20. We're now moving to Premiere.
We have been loyal customers since 1998 and this was the final straw. Goodbye everyone.
Users of Voukoder may find that build 403 crashes when you try to render. My machine does (but mine's ancient). Workaround is to use a different encoder. I've not tried poking at Voukoder's settings yet, but I have upgraded to the latest version and it's made no difference.
I've not found that. Are you using X264 or x265 or GPU encoding?
You have both the plugin and the connector installed for VP 20? https://www.voukoder.org/forum/thread/783-downloads-instructions/
If it's NVIDIA "For using NVENC (SDK 12) encoders driver version 522.25 or later is required."
I received the message about a needed update VEGAS Pro 20 (Build 403). BUT when I go to the website to download, I do not understand which download to click on. I am in the United States, and can't figure out which of the many download links I should use. My Vegas Pro 20 WILL NOT open and I ned to do the right download. Please advise.
@Jere-Whitehouse There is a full index of downloads, with some explanations, here:
At the moment, because of very heavy traffic on MAGIX' servers, you may be better downloading VEGAS_Pro_20.0.0.403_DLV_DE-EN-FR-ES-BR_230504_07-19_FAF9119E.exe (the installer) from one of the cloud links that others have posted in this thread and elsewhere on the forum.
If anyone wants to do an MD5 checksum to verify the validity of one of the installers that users are posting in the cloud...
1. Open a command prompt
2. Navigate to the folder containing the download
3. For VP20 build 403, type:
certutil -hashfile VEGAS_Pro_20.0.0.403_DLV_DE-EN-FR-ES-BR_230504_07-19_FAF9119E.exe MD5
The value returned should be d63852078f3e26303ce17cf0baba70c4
For VP19 build 651, type:
certutil -hashfile VEGAS_Pro_19.0.0.651_DE-EN-FR-ES-BR_865A072F.exe MD5
The value returned should be 16f0452592106e50613beccd89125d34
The reason the Vegas software is so slow to download is probably because there are 2 many people downloading it at the same time
This "New" ""FORCED UPDATE"" because of the May 3rd debacle has totally messed up our program.
After installing this update, Project Media is no longer connected to edits within the time line forcing us to replace all the project media within the project and reconnect and then redo most of the edits... undo attempts causes the program to crash, and the whole environment in now completely unstable.
And of course this all happens at the end of a project at the day of final rendering.
This is the last project our company will do in this environment of VEGAS 20. We're now moving to Premiere.
We have been loyal customers since 1998 and this was the final straw. Goodbye everyone.
I opened a project in build 403 which I made with V20 builds prior to 402/403 and the project media is still connected to edits. It is working fine for me.
After installing Build 403 and having the "New to Vegas" window still active, in addition, making sure that Preferences>Automatically open the last project on startup is check marked, the last project doesn't load when exiting and restarting Build 403.
Not the end of the world, just a couple more mouse clicks, but just wanted to know if I was the only one experiencing this.
I am sure that Vegas developers have more pressing issues to handle right now.
Glad I did this update early this morning ...
Indeed, last project opened does not load anymore on start - However, if you disable the new welcome screen (left down corner, or via the preferences), then the last project does load on startup (providing last project on startup is check marked) !
This "New" ""FORCED UPDATE"" because of the May 3rd debacle has totally messed up our program.
After installing this update, Project Media is no longer connected to edits within the time line forcing us to replace all the project media within the project and reconnect and then redo most of the edits... undo attempts causes the program to crash, and the whole environment in now completely unstable.
And of course this all happens at the end of a project at the day of final rendering.
This is the last project our company will do in this environment of VEGAS 20. We're now moving to Premiere.
We have been loyal customers since 1998 and this was the final straw. Goodbye everyone.
@Joe-Marshalla I have also never seen this problem, that medias have become disconnected by an update. Could it be that it was another issue with your network? Do you have stored the footage on an external network device, maybe a NAS? Were the network IPs maybe changed because of disabling the router, what could act as DNA-server?
I do not know. But even if the situation with the update was an emergency situation, what was solved within few hours, you should be aware that also other software tools may require a stable network and internet connection for the confirmation from their home server. I recommend you to check this - I know for example, that the broadcast version of Edius X does not require those calls home, but I am not sure about Premiere.