VEGAS Pro 20 Build 326 General Thread

Comments

Former user wrote on 2/21/2023, 5:22 PM

I've been a Vegas user for almost 20 years now since version 4. It's arguably the best software on the planet to use to edit videos. (when it works) However, version 20 has been atrocious for me. Slow and choppy preview, unpredictable problems, crashes during rendering, wasting SO much time on things that shouldn't have to be thought about.


Yes I can use version 19 without problems - but why should I be forced to do so? This is extremely disappointing, frustrating and draining of real resources in my small business.

There are many that agree with you, but others say it's very stable, less crashes than previous versions. Have to find out the difference between those 2 groups of people. Your hardware seems fine

i9-9900KF @ 3.6Ghz 8 Core, NVIDIA GeForce RTX 2080Ti, 32GB ram

My speculation has always been about lack of ram or Vram, VP20 will eat up all my Vram and start using system ram. This is very bad and shouldn't be happening. Of the 3 pro editors I use, Vegas uses the most ram and Vram but performs the worst buy a huge margin. I make 2 guesses, their software is riddled with memory leaks, or they are doing something equivalent to overclocking a CPU or GPU that you shouldn't be overclocked, throwing way too many resources at a problem for minimal gain..

Maybe with with enough ram and enough vram it works great, but the amount could be unreasonable. As for me, I don't see the problems you and many others see with VP20b326, you have same ram and 1GB more Vram. I guess it could be the complexity or length of your productions, OR, whatever this problem, it's unrelated to Ram or Vram.

@jeremyscottproductions When you say VP19 worked great, what was the most latest build that worked great, after VP19b550 it's more like VP20 (uses more Vram and ram), so if you have no problems with VP19b643 then that would be useful info

 

 

jeremyscottproductions wrote on 2/21/2023, 5:33 PM

I've been a Vegas user for almost 20 years now since version 4. It's arguably the best software on the planet to use to edit videos. (when it works) However, version 20 has been atrocious for me. Slow and choppy preview, unpredictable problems, crashes during rendering, wasting SO much time on things that shouldn't have to be thought about.


Yes I can use version 19 without problems - but why should I be forced to do so? This is extremely disappointing, frustrating and draining of real resources in my small business.

There are many that agree with you, but others say it's very stable, less crashes than previous versions. Have to find out the difference between those 2 groups of people. Your hardware seems fine

i9-9900KF @ 3.6Ghz 8 Core, NVIDIA GeForce RTX 2080Ti, 32GB ram

My speculation has always been about lack of ram or Vram, VP20 will eat up all my Vram and start using system ram. This is very bad and shouldn't be happening. Of the 3 pro editors I use, Vegas uses the most ram and Vram but performs the worst buy a huge margin. I make 2 guesses, their software is riddled with memory leaks, or they are doing something equivalent to overclocking a CPU or GPU that you shouldn't be overclocked, throwing way too many resources at a problem for minimal gain..

Maybe with with enough ram and enough vram it works great, but the amount could be unreasonable. As for me, I don't see the problems you and many others see with VP20b316, you have same ram and 1GB more Vram. I guess it could be the complexity or length of your productions, OR, whatever this problem, it's unrelated to Ram or Vram.

@jeremyscottproductions When you say VP19 worked great, what was the most latest build that worked great, after VP19b550 it's more like VP20 (uses more Vram and ram), so if you have no problems with VP19b643 then that would be useful info

 

 

I remember recently updating V19 as well, so I believe I have the most up to date version of that. I really appreciate the thoughtful reply! Was frustrated earlier. 👀🤣🫣

RogerS wrote on 2/21/2023, 8:29 PM

I am surprised there is any difference between 19.648 and 20.326 as both have the same fixes to HEVC and 20 also has other bug fixes. I did stick with 19.550 for a while as there were performance issues after that that 648 appears to have resolved. The other big change between 19 and 20 is the audio VST engine if you are using audio Fx.

Maybe create your own thread with pertinent info about hardware, settings, and media.

mofobo wrote on 2/22/2023, 3:23 PM

I've been a Vegas user for almost 20 years now since version 4. It's arguably the best software on the planet to use to edit videos. (when it works) However, version 20 has been atrocious for me. Slow speeds, having to scour the web for fixes to things that should never be broken. All other versions of this software work on my computer - but this version is frustrating beyond belief at every turn. Slow and choppy preview, unpredictable problems, crashes during rendering, wasting SO much time on things that shouldn't have to be thought about.

Searching for hours online shouldn't be a normal thing for any program. Tweaking random settings buried in menus which don't make any logical sense to the layperson without a degree in computing. The basics should just work. My edits aren't that complicated. (basic cuts, text, color grading) I have a maxed out machine that has always worked on all other previous versions and was meticulously researched to work with Vegas. No updates made to have that change other than video card drivers are always updated to the latest (but again, all other versions work just not 20.)

Yes I can use version 19 without problems - but why should I be forced to do so? This is extremely disappointing, frustrating and draining of real resources in my small business. Yes this is a rant, and I've seen others crap on rants, but again no other professional program I have has been this un-intuitive in finding answers. I could understand if some very complex features didn't work and needed to be ironed out - but these are the basics.

I would list my machine or RAM preview settings or any of those things - but the frustrating part is I've tried all those things. V19 works perfectly, V20 does not work reliably at all. Preview is very choppy and rendering goes to about 30% and stops (no matter what codec, I've tried all the normal Vegas hacks after being a user for so many years.)

I only humbly ask this - before adding any more features - please work on stability first and foremost. Real people are loosing tens of thousands of dollars when these simplest of basics aren't addressed. It's not an unreasonable request. I really do appreciate the program and the years I've been able to use it. I can't fathom the work it takes to put this all together and make it work. It just desperately needs basic stability as a priority - especially on a machine that has worked for years (almost) flawlessly.

I am on the exact same boat. I went back to V19 today, the latest update of V20 has been absolutely atrocious.
I've sent over 20 crash reports over the past week and I'm just not in the mood for essentially beta testing and submitting more faults and PC data for a program that I pay a monthly subscription for - it should be fit for purpose when it's offered to consumers. A 7950x, 4090 and 64gb DDR5 ram (along with fresh installs of Windows, Vegas and associated graphics drivers) should be tearing through this program but nope, its a nightmare.

I know others havent had issues, but I have constant crashes now and it's effecting my ability to earn money (I'm a full time video editor). So I'm out after this subscription ends.

I really like Vegas, I had a few hiccups in the past but I could always deal with them. I've got a really efficient vegas workflow that helps me with my job, but I'm going to spend a few months learning a different program.

jeremyscottproductions wrote on 2/22/2023, 7:23 PM

Just had an epiphany about users who have troubles with V20 and V19..... could the difference between using Windows 10 and Windows 11 be the difference maker? The ONLY reason I haven't upgraded to Windows11 is because I've been terrified that it will break Vegas, and that's my only reason for having my computer. I'm curious however if the way Windows 11 runs and handles Vegas could be the difference maker?

Not smart with the finer details of computing -so just throwing it out there. :) Thank you!

RogerS wrote on 2/22/2023, 8:43 PM

Windows 11 and 10 both work with Vegas. The main difference may be in handling of P and E cores with newer Intel processors and not sure what else.

Reyfox wrote on 2/23/2023, 4:42 AM

Dreaded the move to Win11, but wanted to start with a fresh install of Windows. So, either install Win 10 Pro or Win 11 Pro on a new NVME. Decided Win11 Pro. The migration over to it is almost complete with everything related to Vegas. And so far, I can't tell the difference between the performance of Win10 or 11.

I've often wondered too how someone can have the same program, and even sometimes a very similar PC build, yet they are stable while I might not be. But there is an infinite number of variables in computer hard/software installations. But on a fresh clean install, everything "should" work.

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: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Dexcon wrote on 2/23/2023, 5:21 AM

And so far, I can't tell the difference between the performance of Win10 or 11.

Agreed. When W11 was released, I first tried it on my laptop and it seemed okay - just a different look - and Vegas Pro worked the same way that it did under W10 - no noticeable difference that I could see.

I inadvertently hit the W11 update button on my desktop - my main editing machine - some weeks later. Fortunately, I didn't find a need to roll back to W10 within the roll back period (14 days I think). Vegas Pro worked just as well as it did under W10. Phew! The only thing was that under W11 there were more failures to open Vegas Pro (and MS Outlook as well) than happened with W10, the workaround being to kill Vegas Pro (and Outlook as well) in the task manager. I'm fairly sure that the Vegas team posted on the forum a while back an MS fix to eliminate this problem, but I haven't done it as yet.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

fr0sty wrote on 2/23/2023, 8:10 PM

There was a windows bug recently that MS patched that was causing many shortcuts to not function properly, not sure if that was tied in with the issue you mention or not.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

RogerS wrote on 2/23/2023, 8:42 PM

I don't think the failure of Vegas to open was related to a W11 update- I also see it intermittently on my Win 11 system and VP 20 but not previous versions.

fr0sty wrote on 2/23/2023, 8:47 PM

IF YOU ARE EXPERIENCING ISSUES WITH BUILD 326

Please report the bug in this thread, making sure to follow the 7 step instructions as closely as your technical proficiency will allow, don't worry if you can't figure out how to do some of it, just do what you can:

https://www.vegascreativesoftware.info/us/forum/having-problems-with-vegas-20-only-users-of-v20-build-326-please--139920/

The purpose of that thread is not to help you sort the bug, we want you to make your own thread about the bug so we can respond just to you about your issue without other people posting about unrelated stuff... The purpose of the thread linked to above is to give the developers a place where all reported bugs for this build can be tracked. Their error report system does some of that automatically, but sometimes VEGAS will crash without the error report launcher working, and we want to know about those crashes too.

After making the bug report in the above thread, please make a new thread about your issue, making sure to follow the steps detailed in the link below first (this part is very important, if you want to get helped fast and get back to work, these steps will dramatically reduce the time it takes to sort your problem):

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

 

Last changed by fr0sty on 2/23/2023, 8:50 PM, changed a total of 3 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Howard-Vigorita wrote on 2/24/2023, 9:50 AM

Windows 11 and 10 both work with Vegas. The main difference may be in handling of P and E cores with newer Intel processors and not sure what else.

Not sure that's as big a factor as it seems. Since core prioritization has traditionally been handled in bios and still is for Ryzen and Xeon cpus. Could give a big advantage to Window's processes on latest Intel cpus if it's allowed to do that. Which I find suspect since it won't necessarily help out Vegas if it's processes are competing for resources. But I think the Win11 strategy is still evolving. Selectively throttling some Win background processes onto e-cores might yield better results for apps like Vegas. Fwiw, I've noticed that when updates seem to cause performance dips for Vegas in Win11, they also show up on my Win10 machines a few WinUpdates later.

I think a bigger area of Win evolution concerns Graphics control. Nvidia has always been notorious for trying to get it's drivers underneath competing graphics drivers to override control. When Win11 came out, Microsoft began taking over graphics routing. But I also see similar Graphics preferences screens showing up in Win10, just more stripped down or absent completely on some of my systems with no Nvidia gpu. And Nvidia seems to be up to its old tricks on my Intel/Nvidia 12th gen laptop. My impression is that the net results for Vegas users has not been positive. And certainly must be complicating the mission of Vegas developers to have their app perform consistently on all systems without outside interference.

Only way I see through this quagmire is to provide as much info as possible in success and bug reports to help fellow users and Vegas developers navigate around all the roadblocks.

Philip-Adams wrote on 3/4/2023, 6:32 AM

Hello there!

Anyone had a problem with rendering audio on the new Vegas?

I've been getting a sound like a scratched record put at the tail end of my audio track.

Otherwise, no other problems, as yet!

 

walter-i. wrote on 3/4/2023, 2:24 PM

Hello there!

Anyone had a problem with rendering audio on the new Vegas?

I've been getting a sound like a scratched record put at the tail end of my audio track.

Otherwise, no other problems, as yet!

@Philip-Adams
Do a forum search and type in "white noise" - you might get some help there.
If not, open a separate thread (this one is for feedback only) and describe your problems in detail, and don't forget to include your system environment and media file properties.
https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Philip-Adams wrote on 3/4/2023, 10:54 PM

Thanks Walter. Found someone with the same problem. Not a rendering issue as I first thought, but for some reason the program writes a faulty sfk file when loading audio files to the timeline. I'm now waiting on tech support to reply.

fr0sty wrote on 3/5/2023, 10:43 PM

There's been some reports of similar audio glitches internally as well, the team is aware of the issues and is working to fix them.

Erkki wrote on 3/7/2023, 11:32 PM

Had some stability problems. Then based suggestion here, turned off "Create project collection". Situation improved. Then decided turn HW acceleration (NVidia 1050 TI) off. Then it (stability) was ok. Then tried removing display adapter and use HD Graphics only. Turned HW acceleration on:

Display refresh rate is 25Hz, Performance monitor shows that GPU 'Copy' operation load dropped to 0. Editing (basic videos - marginal color correction and cuts) works reliably. No lag when using scrub, no hangs. Preview it bit jerky (probably dropping frames (preview quality)) but when doing preview render playback is ok.

Sticking on this setup for now as it fits my use case (simple cuts and color grade only, 1080p) and program works well.

Hope this helps debugging.

 

RedRob-CandlelightProdctns wrote on 3/8/2023, 5:14 PM


It would be really cool if when we drag a preset from the Plug-in Manager with the right mouse button a context menu appears with the options of "Add And Replace"

Short of having that right-mouse drag-drop to drag a plug-in chain onto an event (I just tried it intuitively but it didn't do anything), how do we tell Vegas to add (and not replace) the FX when i drag it on? I don't see any options for that.

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

Terry-Pike wrote on 3/15/2023, 3:46 PM

I've installed to the latest update for Vegas Pro 20.0, Build 326 and noticed that it doesn't automatically load the last project. The check mark is on in the general tab of options to load the last project. Any update for this issue.

RogerS wrote on 3/15/2023, 7:01 PM

Disable the welcome screen to go straight to it? Otherwise it should be on that screen with a single click.

Reyfox wrote on 3/16/2023, 3:59 AM

I have the Welcome screen still enabled, and Vegas 20 will still load the last project I've had open.

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: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

VEGASDerek wrote on 3/16/2023, 8:49 AM

We have a bug in the loading of the last project stuff. This will be fixed in the next major update of VEGAS Pro 20.

 

Raffaele-Veneri wrote on 3/18/2023, 8:35 AM

Hi. I noticed that in the last version of Vegas Pro 20 (build 326) something is wrong in multicam, when I want to switch track pressing Ctrl to generate an overlap at the split point: switching from Track1 to Track2 works fine, but when I want switch back to Trak1 from Track2, nothing happens!
This is happening when the "1" key of the Num Pad is pressed in combination with "Ctrl". Everything works fine if using the number 1 key of the main keypad.