VEGAS Pro 19 update 1 has been released. Build 381 is a revised version of the original update 1 (build 361), addressing some of the major issues uncovered with that release. Please give us your feedback in this thread.
After download successful, go to temporary folder location of VP19 (in my case in C:\Users\[username]\AppData\Local\VEGAS Pro\19.0) and look at the exe installer file - copy to other safe folder for backup purpose, before proceed with installation progress (I always set install after application closed).
After I opened Vegas Pro 19 today an upgrade message box appeared. I downloaded and installed build 381. Before completion an error message box indicated that one of the plugins is corrupt. The update failed. What is left of Vegas Pro 19 does not run. On start Application Initialization message reports "error code: -1" then Vegas Pro message is "An error occurred starting VEGAS Pro. There is no license to use this software." What is the procedure from here?
Former user
wrote on 9/30/2021, 12:58 AM
my first complaint is using the mouse wheel to zoom in on the clips moves everything the scroll bar moves out so I had to keep clicking on the scroll bar to move it to the beginning, don't think that happened in the older version.
@Steve-L Hi, I've just been editing & it feels like it used to, wherever the timeline play thing is, it centralises as you scroll/zoom with the mouse...?
I'm sorry you ran into this. We haven't resolved an issue that can appear in some cases. But in the next update we will at least fail gracefully and use your CPU so you can still use the Slow Motion tool. And I'm sorry for the wording of the warning message. That's my fault for not reviewing it before it was implemented. That's already been fixed for the next update.
The UI issues and most of the random crashes are fixed for me but I now can't complete a render beyond 25% and it seems to be struggling on some text I've overlaid.
I'll check to see if there is a new GPU driver but it was only updated a few days ago and it hangs whether its CPU/GPU set as the renderer.
After I opened Vegas Pro 19 today an upgrade message box appeared. I downloaded and installed build 381. Before completion an error message box indicated that one of the plugins is corrupt. The update failed. What is left of Vegas Pro 19 does not run. On start Application Initialization message reports "error code: -1" then Vegas Pro message is "An error occurred starting VEGAS Pro. There is no license to use this software." What is the procedure from here?
I uninstalled VP19 then re-installed using the original link given with the purchase. I was pleasantly surprised to see that the Build 381 update is incorporated into the download package making the installation a one-step process. No failures on install or start after completion. So far okay.
Nvidia Geforce GTX1050 TI graphics card and I get this???
What??
am I missing something here??
Tried out the slow motion on my xps15 laptop with same gpu, ram, and driver as you and no problem. However the igpu is enabled and decoding. Also tried it on a 9900k system with amd gpu plus igpu active and decoding and that's good too. Another possibility is maybe it has something to do with your media? I tried 4k hevc and hd mxf clips.
Every time I close down Vegas after this update The program assumes it has crashed and sends a report. I could open the prog then just close it down and still the same result. Anyone got an idea or is it possible to reinstall the previous version for the time being?
We are seeing a large number of reports of a crash on shutdown. We are investigating. It should not have any major effect on the application, so we suggest you still use build 381.
Gary - Build 381 fixed all my app stability issues. I've used it 6-8 hours without a crash. Prior to that, it was basically unusable even with GPU acceleration disabled. Quite happy with it now.
Nvidia Geforce GTX1050 TI graphics card and I get this???
What??
am I missing something here??
Tried out the slow motion on my xps15 laptop with same gpu, ram, and driver as you and no problem. However the igpu is enabled and decoding. Also tried it on a 9900k system with amd gpu plus igpu active and decoding and that's good too. Another possibility is maybe it has something to do with your media? I tried 4k hevc and hd mxf clips.
It also works perfectly for me with 50p HD material from the Sony FDR-AX53.
We are seeing a large number of reports of a crash on shutdown. We are investigating. It should not have any major effect on the application, so we suggest you still use build 381.
I had that issue with the last build, all is well with build 381. 🙂🙂🙂
We are seeing a large number of reports of a crash on shutdown. We are investigating. It should not have any major effect on the application, so we suggest you still use build 381.
Had a crash on exit every time with 361 but not 381.