VEGAS Pro 21 Build 314 and 315 General Thread

Comments

Reyfox wrote on 1/23/2025, 2:38 PM

Well, no one here in the EU that I am aware of or in the US have complained. It's like buying a "closeout" item. They have said they've reached 12 million customers, so I would think if what they are doing would have ruffled either EU or US customers, something would have been done by now about it. It is based in Delaware. And I now live in the EU.

Their Terms and Conditions. Look at Part 5.

Last changed by Reyfox on 1/23/2025, 2:39 PM, changed a total of 2 times.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

RogerS wrote on 1/23/2025, 8:28 PM

@ccscotty For green frames that has been a problem since build 300 of 21 and NVIDIA GPUs. Personally I stayed on build 208 for that reason (you can get it here). While I also have 22, I stayed with build 208 of 21 until this week when build 239 of 22 was released which seems to fix the green frames once and for all.

The software is still supported in the sense that you can contact support, but it isn't in active development and hasn't been since last spring. VEGAS only provides updates within a version for free unless you have the subscription.

For the crash I would love to test such a project just so we can fully compare apples to apples.

ccscotty wrote on 1/23/2025, 10:03 PM

@ccscotty For green frames that has been a problem since build 300 of 21 and NVIDIA GPUs. Personally I stayed on build 208 for that reason (you can get it here). While I also have 22, I stayed with build 208 of 21 until this week when build 239 of 22 was released which seems to fix the green frames once and for all.

The software is still supported in the sense that you can contact support, but it isn't in active development and hasn't been since last spring. VEGAS only provides updates within a version for free unless you have the subscription.

For the crash I would love to test such a project just so we can fully compare apples to apples.

Here is a small test project. In a quick test with the second project file that was transformed into got it to show a GPU error (image attached in the project folder).

https://www.dropbox.com/scl/fi/5sl0kv8vbplydoxlv9i2y/20250123-VegasPro21CrashTestProject.zip?rlkey=bnjyv283isoyvtwhphtma6c3a&st=bldgea4y&dl=0

I would have uploaded the zip here because it is only ~700kb, but they don't support that file type.

Details:

  • I had OBS 31.0.0 running on my second monitor, but I wasn't streaming at the time. I also had a Chrome window (version 131.0.6778.267) open on that second monitor.
  • The video clip was recorded in OBS. Nvidia NVENC HEVC with FFmpeg AAC (empty audio because I had the MIC muted)
  • The two graphics were made in Affinity Photo 2.
  • Nvidia studio drivers 566.36 (released December 10th)
  • Again, Vegas 21 has been troublesome since I purchased it with this on two different computers with only a few mutual components. It feels unlikely it's my PCI-e storage card or 4060 GPU, but I guess anything is possible. I haven't had a chance to update my BIOS or chipset drivers that I noticed while posting the message about the blue-screen crash.
  • Add a picture-in-picture to the PNG clip to potentially have something bad happen (do at your own risk, lol). This time for me I got a pop-up instead of a blue-screen. Maybe whatever Windows dev teams monitor telemetry and crash data did something about it, who knows. There is a screenshot of the error in the project folder.
  • I haven't tested this recently, but text objects have also been problematic when transitioning a normal 1920x1080 video project to a vertical video one (1080x1920). You'd have to add one in the original project and then make a copy. Then transform that project's aspect ratio in the project settings to 1080x1920 if you want to experiment with the stability of that.

 

Error:

A few more details:

  • Quantize frames off (with it on I tend to get empty space when editing and it doesn't feel as accurate)
  • File I/O settings Enable legacy AVC decoding checked. Enable experimental HEVC decoding checked.

 

 

 

RogerS wrote on 1/23/2025, 10:17 PM

Thank you so much!

I downloaded the project, opened it in 22.239 and added PiP to the PNG and then moved it around and played back. No issue as far as I can tell. Do I need to do something else?

I am using the NVIDIA 4060 mobile (older driver from July supplied by the OEM as the newest ones crash the system on sleep).

I then added a text event, changed it to vertical and played it repeatedly. Still stable.

I have Firefox and Chrome open but not OBS.

I can try with 21.208 in a minute (not planning to reinstall 315 given the known issues with NVIDIA GPUs making it useless to me).

RogerS wrote on 1/23/2025, 10:28 PM

I copied and pasted the project from 22 to 21.208, added PiP, played back on a loop and no crash.

Added text event, changed to vertical 1080x1920, played on loop, no crash.

Since there is no video media here the decoder choice shouldn't matter. Do make sure the frames are quantized (no red edges) before rendering.

RogerS wrote on 1/23/2025, 10:34 PM

For the second project what are you trying to do? If you right click and select "match output aspect" it should scale properly.

No GPU error with my 4060.

ccscotty wrote on 1/24/2025, 3:27 AM

For the second project what are you trying to do? If you right click and select "match output aspect" it should scale properly.

No GPU error with my 4060.

 

Sorry, I should have tried to explain it a bit better. I didn't need anything demonstrated with the normal ratio project. I'm able to get projects done that way. It's all about once I try to convert that finished project into vertical format.

With PiP, It's easier to move around objects than solely using the crop tool.

I think I had purchased v21 after build 208 because their "edit with text" feature sounded interesting (it relying on a slow web service to generate speech to text made it a no go). I have quite a lot that at this point that probably won't open in that previous build. I'll probably go back to doing the v19 copy paste thing until v23 comes out and hits a managable price point. Though maybe the dev team has changed their processes with mention of that beta testing user group they set up so 22 might be an option at some point (humble bundle, etc).

Thanks for trying here to reproduce it. 👍

RogerS wrote on 1/24/2025, 3:47 AM

@ccscotty If you want to discus further I'd suggest starting a new thread. Happy to keep testing things with you. I like the PiP interface as well and use it. It really shouldn't ever crash.

Copying projects from 21.315 to 19 and then reinstalling 21.208 and going from there could work for existing projects.

I think 22.239 is pretty good and am moving to make that my main version of VEGAS now as it cleans up most of the issues 21.300/315 had.