VEGAS Pro 20 Build 214 General Thread

Comments

set wrote on 10/19/2022, 10:20 PM

There are times that I also had frequent crashes and after having system restart, everything then goes smooth.

Former user wrote on 10/20/2022, 4:49 AM

Any thought on stability and bugs yet, better than VP19b550?

How about those memory problems?

elliot-f wrote on 10/20/2022, 7:37 AM

I have to say I'm very disappointed in this new update, just went from Vegas 19 to 20 with today's update but the timeline is incredibly laggy in Vegas 20, to the point where I'm sitting banging my fist on my table in frustration. I can't figure out why this new version is so much worse and I tried copying over my preferences but that didn't help either. What is going on with this new update?

The same happened to me until I realized that colour grading was activated above the preview window (not by me) removing this changed the rate on my project from 6-11 fps to the expected 25.

Hmm what exact setting are you referring to? Can't seem to spot anything about color grading above the preview window. Do you mean that a Video Output FX has been added with color grading?

jetdv wrote on 10/20/2022, 8:35 AM

Can confirm. Titler Pro 7 still fails to launch.

@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.

Jack S wrote on 10/20/2022, 10:07 AM

@Elynde Uninstall TP7 then re-install. See if that cures the problem.

My system
Dell XPS 8700 (I know, it's a little outdated, but it handles VP20 quite well)
Windows 10 Home (x64)
3.1 GHz Intel Core i5-4440
16GB RAM
NVIDIA GeForce GTX 1050 Ti display adapter
System drive Samsung SSD 850 EVO 250GB

Camcorder
SONY Handycam HDR-XR550VE

janndk wrote on 10/20/2022, 10:30 AM

Can confirm. Titler Pro 7 still fails to launch.

@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.

NewBlue says they are trying to figure out what the problem, but not doing mutch to fix it 😕 Anyway - it's sold by Vegas (Magix), so it's also a Vegas issue ☝️

flyerstl wrote on 10/20/2022, 11:19 AM

The "auto FX resize" issue is still here--if any VST2 (non Magix audio plugins) are in the chain, the windows resizes no matter if the box is checked. Any hope for this, as it's a big one for me who does a lot of audio post.

 

Last changed by flyerstl on 10/20/2022, 11:21 AM, changed a total of 2 times.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

jetdv wrote on 10/20/2022, 11:23 AM

@janndk, @Elynde I have seen several reports of TP7 working correctly in VEGAS Pro 20 build 214. If it's not working, my first suggestion would be to do a clean install which, basically, means uninstalling TP7, deleting any left over files and registry entries, and then reinstalling. But Magix did work on issues with TP7 and Boris not properly loading in build 214.

TV-Slupsk wrote on 10/20/2022, 12:37 PM

Got lots of problems with latest build. Lots of crashes caused in most by TP7. Sometimes it happens during playback, secondly while put TP7 media generator to the timeline.

VEGASDerek wrote on 10/20/2022, 12:59 PM

The "auto FX resize" issue is still here--if any VST2 (non Magix audio plugins) are in the chain, the windows resizes no matter if the box is checked. Any hope for this, as it's a big one for me who does a lot of audio post.

 

This will be fixed in the next update. The fix was made just after the code freeze for this update.

fr0sty wrote on 10/20/2022, 1:36 PM

Got lots of problems with latest build. Lots of crashes caused in most by TP7. Sometimes it happens during playback, secondly while put TP7 media generator to the timeline.

That sounds like a TP 7 issue. I gave up on using new Blue products years ago, I've never had one that worked properly for me.

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)

Elynde wrote on 10/20/2022, 3:37 PM

Can confirm. Titler Pro 7 still fails to launch.

@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.

Yes, I will contact NewBlue again and update my existing ticket. I have removed Titler Pro 7, its caches, the app data folders, and reset the Vegas cache before rebooting my system entirely for good measure. Installed Titler Pro 7 again and allowed Vegas to boot up after. I thought that did it at first, but it still hangs if you need to change a title in a saved project.

Video of the issue after repeating my test (note it did not hang on initial launch the first time, only on the launches after it failed to open a saved project's title):

andyrpsmith wrote on 10/20/2022, 4:27 PM

Apparently you need to download deep Learning 20.2 but I can't find it, anyone have a link? Thanks.

DasFragezeichen wrote on 10/20/2022, 4:29 PM

Nice to hear, that the 360°-Bug is fixed now. I will try to get a new trial-key for Vegas Pro to test it and perhaps than I buy the new version.

Do you think, that it is possible to support some most used cameras, like from Insta360?

RogerS wrote on 10/20/2022, 4:31 PM

Apparently you need to download deep Learning 20.2 but I can't find it, anyone have a link? Thanks.

@andyrpsmithIt was in the forum announcement (news) page: https://www.vegascreativesoftware.info/us/forum/vegas-pro-20-build-214--137660/

 

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.236

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

james-ollick wrote on 10/20/2022, 6:24 PM

Can confirm. Titler Pro 7 still fails to launch.

@Elynde Actually, Titler Pro 7 has been tested and confirmed to work in VEGAS Pro 20 build 214. If you're having an issue, please contact NewBlue support.

Yes, I will contact NewBlue again and update my existing ticket. I have removed Titler Pro 7, its caches, the app data folders, and reset the Vegas cache before rebooting my system entirely for good measure. Installed Titler Pro 7 again and allowed Vegas to boot up after. I thought that did it at first, but it still hangs if you need to change a title in a saved project.

Video of the issue after repeating my test (note it did not hang on initial launch the first time, only on the launches after it failed to open a saved project's title):

Just in case, try this, run VP and TP as Administrator. You can change the setting by right clicking on the 2 apps icons then using properties click on the "Compatibility" tab and click on the box labeled "Run the program as an Administrator".

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply. Windows 11.

VP 19, BCC 2022 Continuum Complete, Titler Pro v7.

Elynde wrote on 10/20/2022, 6:52 PM

@janndk, @Elynde I have seen several reports of TP7 working correctly in VEGAS Pro 20 build 214. If it's not working, my first suggestion would be to do a clean install which, basically, means uninstalling TP7, deleting any left over files and registry entries, and then reinstalling. But Magix did work on issues with TP7 and Boris not properly loading in build 214.

I did the clean install. When that didn't work, I went to update my existing ticket with NewBlue. They responded by having me completely remove Titler 7 again, and sent me a beta version to test that works beautifully. However, the beta comes up as a trial version and doesn't take my keys, so I am working on getting a non-watermarked version of the beta update from NewBlue. ... I am so happy I will be able to access my titles again without having to render them stand-alone!

RogerS wrote on 10/20/2022, 7:13 PM

Glad to hear they've been responsive!

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.236

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Elynde wrote on 10/20/2022, 7:20 PM

Glad to hear they've been responsive!

Yay! Problem finally resolved! Between that and the continued improvements to Vegas, I am a very happy camper.

bitman wrote on 10/21/2022, 1:14 AM

Is there a way to check the version of deep Learning? I would like to know if it is version 20.2.

Build 214 was updated via the default method. I must have been one of the early birds, as nothing was mentioned at that time of a new build on this forum... The update downloaded reasonably fast and updated flawless, so not downloaded via the links. If I would have downloaded via the links provided here now, then I would have known for sure.

Last changed by bitman on 10/21/2022, 1:20 AM, changed a total of 1 times.

APPS: VIDEO: VP 365 (20 - build 370), VP 19 post (latest build -648), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 15 HDpro XXL, Boris Continuum 2022.5, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Audio Clean Lab 3, Sound Forge Audio Studio 16, Sound Forge Pro 16, Spectral Layers Pro 9, Audacity, FOTO: Zoner, DXO, Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 22H2
  • CPU: i9-13900K (upgraded my former CPU i9-12900K), Air Cooler: Noctua NH-D15s
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Dexcon wrote on 10/21/2022, 2:27 AM

Or in Windows 11, R click on the Start button, select the top item - Installed Apps - and scroll down to the Vegas Pro 20.0 (Deep Learning Models) entry. The full version number (e.g. 20.2.0.0) is displayed there.

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

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, 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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

bitman wrote on 10/21/2022, 3:22 AM

@Dexcon @lan-mLMC Thanks for the info - I should have thought of that :)

@VEGASDerek

I checked and it is still the 20.0.0.0; which means that the "default" update method (the one that asks you if you want to update) does not update the deep learning. That is a big oversight...

APPS: VIDEO: VP 365 (20 - build 370), VP 19 post (latest build -648), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 15 HDpro XXL, Boris Continuum 2022.5, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Audio Clean Lab 3, Sound Forge Audio Studio 16, Sound Forge Pro 16, Spectral Layers Pro 9, Audacity, FOTO: Zoner, DXO, Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 22H2
  • CPU: i9-13900K (upgraded my former CPU i9-12900K), Air Cooler: Noctua NH-D15s
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2