VEGAS Pro 22 Build 122 General Discussion

VEGAS_CommunityManager wrote on 9/9/2024, 5:58 AM

Hello everyone,

The VEGAS Team is happy to announce the release of VEGAS Pro 22 build 122. Please use this thread to post general comments on this update. For details on this update, please read this post in the News forum.

If you are having any issues using the update or have specific questions, please create a new thread.

Thank you,

The VEGAS Creative Software Team

Comments

pierre-k wrote on 9/9/2024, 6:29 AM

MXF - too bad you didn't include this fix in the list. I will still have to stick with the VP21 b208

https://www.vegascreativesoftware.info/us/forum/vp21-b300-and-big-problem-with-mxf--145196/?page=5#ca922835

bitman wrote on 9/9/2024, 7:15 AM

Installation process of build 122 had some issues I never seen before, like always asking to remove (or delete, forgot the exact wording), then Vegas 22 was gone... and complaining about # devices exceeded.

I had to run the installation 3x

- 1x install from the update screen- deleted everything.

- 1x install after downloading the install files from my magix account, again deleted everything.

- 1x install, finally (almost OK), it did not delete, but the activation failed due to:

reached the maximum number of simultaneously useable devices for this program, which is weird, as I only use Vegas on one device anyway (note that windows version is wrong - I have been using windows 11 for several years now),

Also I use vp21 occasionally to check stuff if it is a new issue in VP22, surely you can have 2 main versions on the same machine right? Even if it is 365.

I do update the BIOS when needed or enable/disable Hyperthread etc.. in BIOS, surely these changes should not be considered a new device?

Device information (as given by the Vegas account check) :
Windows computer with:
- Windows 10 Pro, 64-Bit
- 13th Gen Intel(R) Core(TM) i9-13900K
- 65299 MB RAM
Activated product:
VEGAS Pro Suite 21
Last activated on:
08/17/2024

 

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from 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

 

 

vkmast wrote on 9/9/2024, 7:29 AM

@bitman re BIOS change, please read Nick's comment in p. 4. in this FAQ:

"The error can also be triggered by a change in hardware or a BIOS update/reset"

Re deactivation, note though also p.9 in this FAQ

bitman wrote on 9/9/2024, 9:02 AM

@vkmast I figured as much, I updated my BIOS version with new microcode recently, as needed for the INTEL 13/14 generation CPU debacle as not to fry my CPU...

But all is well now!

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from 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

 

 

bitman wrote on 9/9/2024, 9:15 AM

And I disabled hyperthreading, as I find it does nothing to improve Vegas rendering speed (I have 24 real cores), so the extra 8 with hyperthreading enabled on the P-cores I can do without. In fact, disabling hyperthreading helps to bring the core temperature down (and improve L1 L2 cache use and latency). Heck, one can reduce the CPU voltage a tiny bit with HT disabled, further reducing the temperature. But I am going too technical I guess 🤓

Last changed by bitman on 9/9/2024, 9:17 AM, changed a total of 1 times.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from 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

 

 

Howard-Vigorita wrote on 9/9/2024, 9:48 AM

MXF - too bad you didn't include this fix in the list. I will still have to stick with the VP21 b208

https://www.vegascreativesoftware.info/us/forum/vp21-b300-and-big-problem-with-mxf--145196/?page=5#ca922835

Looks like one mxf issue with multitrack audio is mostly fixed in vp22 build 122. The mxf setting won't drop mxf dual-mono audio onto Vegas mono audio tracks like it used to. Always converts dual-mono mxf to a single stereo track. Throws a monkey wrench into processing M-S output from shotgun camera mics. But if the mxf has 4 mono tracks the option now works as expected... creates a single stereo track from 1-2, or 4 mono tracks.

Abubakar wrote on 9/9/2024, 4:50 PM

Whenever i use Lut filter it uses all of VRAM on my RTX 3060 and after that Vegas Pro 22 will use all of the available RAM making rendering slow and eventually hang. This Problem started to appear in Vegas pro 22 and still continues in this patch also. This VRAM & RAM problem with some video fx plugins didn't exist in Vegas pro 21 it only had VRAM & RAM issues with adjustment events not with the video fx plugins itself. I hope we get a fix for this memory leak in the next patch.

Intel Core i7 12770K
Nvidia RTX 3060 / Intel Arc A380
Corsair Vengeance DDR5 5200MHz 32 GB
ASUS ProArt Z690 Creative Wifi Motherboard
2 Samsung NVME SSD
Corsair iCUE H100i ELITE CAPELLIX Liquid CPU Cooler
Corsair RM850X Power Supply

Intel Core i5 13600K
Nvidia RTX 3090
Corsair Vengeance DDR5 5200MHz 32 GB
ASUS ProArt Z690 Creative Wifi Motherboard
2 Samsung NVME SSD
Corsair iCUE H100i ELITE CAPELLIX Liquid CPU Cooler
Corsair AX1600i Digital ATX Power Supply 

prince-pep wrote on 9/9/2024, 6:05 PM

after installing vegas 22 build 122,vegas doesnt show or open...just updated my BIOS but still doesn't open...any help??disabled the hyper trending in my bios but still Vegas doesn't open

Dexcon wrote on 9/9/2024, 6:26 PM

@prince-pep .. A remote possibility is that VP22 is stuck in the computer's memory which can usually be fixed by opening the Task Manager and under the Background Processes tab 'End Task' any Vegas Pro instances in that list.

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

prince-pep wrote on 9/9/2024, 6:45 PM

@Dexcon

There's no background processes of Vegas pro, I just installed the biuld 93 of vegas 22 it opens and works well but the build 122 doesn't even open at all

 

fr0sty wrote on 9/9/2024, 11:33 PM

Whenever i use Lut filter it uses all of VRAM on my RTX 3060 and after that Vegas Pro 22 will use all of the available RAM making rendering slow and eventually hang. This Problem started to appear in Vegas pro 22 and still continues in this patch also. This VRAM & RAM problem with some video fx plugins didn't exist in Vegas pro 21 it only had VRAM & RAM issues with adjustment events not with the video fx plugins itself. I hope we get a fix for this memory leak in the next patch.

How are you applying the LUT, as an effect, or using the color grading panel? Try using the CGP if you haven't.

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)

bitman wrote on 9/10/2024, 12:46 AM

@prince-pep seems you have the same update issues I had, the fact that Vegas 22 b122 does not open at all after installing, points to this (that Vegas 22 is removed instead of installed)

Download the install file from your Magix account, next run the install file, acknowledge the deactivate prompt (or delete, or similar prompt), and Vegas is removed (possibly because you updated your BIOS).

Next restart your PC.

Next run the install file again and do NOT acknowledge the deactivate, remove or delete prompt (if it would appear, not sure if it would appear at all), and the install will be successful.

Next you may need to activate again, as Vegas may think you are installing on a new (extra) device.

Last changed by bitman on 9/10/2024, 12:49 AM, changed a total of 1 times.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from 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

 

 

davewire35 wrote on 9/10/2024, 7:24 AM

Since the build 122 update, I have the impression that the reading of my timeline in the monitoring window is less fluid than before. I use osmo pocket videos in .mp4 and I play a lot with the rhythm of the music to cut my sequences which I align to time. But since yesterday, I have had more latency in reading everything, it's a bit heavy. And you ?
Otherwise when you turn off vegas pro, there is a lot of time left in the background in the task manager and makes the computer slow down for a few seconds. Don't you think that Vegas is consuming more resources than usual?

EDIT : I forgot to check but I could no longer use my old saved presets (from an old version of Vegas, at the time when it was sony vegas on the other hand it worked in vegas 19)) in vegas 22 build 93. For example, my light and contrast presets or even color correctors. Has this been fixed or do we need to redo and save them all again?

ChrisD wrote on 9/10/2024, 10:42 AM

Otherwise when you turn off vegas pro, there is a lot of time left in the background in the task manager and makes the computer slow down for a few seconds.

@davewire35 FWIW, this has been an issue for me since v19, where after close, it remains active / in memory until it self-terminates a few minutes later.

The delay might be due to it recording an error. Perhaps check your event log or reliability history.

For me it's benign, but annoying.

Faulting application name: vegas220.exe, version: 22.0.0.122, time stamp: 0x66bfba3a
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe
Faulting process id: 0x0x4084
Faulting application start time: 0x0x1DB0395DC02F8CB
Faulting application path: C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
prince-pep wrote on 9/10/2024, 2:41 PM

@prince-pep seems you have the same update issues I had, the fact that Vegas 22 b122 does not open at all after installing, points to this (that Vegas 22 is removed instead of installed)

Download the install file from your Magix account, next run the install file, acknowledge the deactivate prompt (or delete, or similar prompt), and Vegas is removed (possibly because you updated your BIOS).

Next restart your PC.

Next run the install file again and do NOT acknowledge the deactivate, remove or delete prompt (if it would appear, not sure if it would appear at all), and the install will be successful.

Next you may need to activate again, as Vegas may think you are installing on a new (extra) device.

I DID EVERYTHING YOU SAID BUT STILL VEGAS PRO 22 BIULD 122 DOESNT OPEN OR RUN

RogerS wrote on 9/10/2024, 3:55 PM

@prince-pep I assume you aren't using a French language install?

Abubakar wrote on 9/10/2024, 4:51 PM

Whenever i use Lut filter it uses all of VRAM on my RTX 3060 and after that Vegas Pro 22 will use all of the available RAM making rendering slow and eventually hang. This Problem started to appear in Vegas pro 22 and still continues in this patch also. This VRAM & RAM problem with some video fx plugins didn't exist in Vegas pro 21 it only had VRAM & RAM issues with adjustment events not with the video fx plugins itself. I hope we get a fix for this memory leak in the next patch.

How are you applying the LUT, as an effect, or using the color grading panel? Try using the CGP if you haven't.

Hello fr0sty i apply Luts using LUT filter plugin in video fx tab. I use it on a adjustment event on top of multiple clips its easier this way for then applying luts on each individual clip. I am well aware of the CGP as much as i love to use it its always buggy it might work fine on one version but on later patches working on the same project the same CGP becomes very slow unresponsive and hangs allot even thought i just need to use the input Lut tab. although it doesn't have a memory leak like LUT Filter plugin but i cant deal with CGP being slow sluggish and unresponsive. If vegas team had fixed the VRAM & RAM error issues with adjustment events in vegas pro 21 i would still be using vegas pro 21 i wish they wont stop support for vegas pro 21 atleast till the end of this year we don't need new plugins or anything else just bug fixes like this.

Intel Core i7 12770K
Nvidia RTX 3060 / Intel Arc A380
Corsair Vengeance DDR5 5200MHz 32 GB
ASUS ProArt Z690 Creative Wifi Motherboard
2 Samsung NVME SSD
Corsair iCUE H100i ELITE CAPELLIX Liquid CPU Cooler
Corsair RM850X Power Supply

Intel Core i5 13600K
Nvidia RTX 3090
Corsair Vengeance DDR5 5200MHz 32 GB
ASUS ProArt Z690 Creative Wifi Motherboard
2 Samsung NVME SSD
Corsair iCUE H100i ELITE CAPELLIX Liquid CPU Cooler
Corsair AX1600i Digital ATX Power Supply 

vkmast wrote on 9/10/2024, 4:53 PM

@RogerS prince-pep may need to check that he has actually bought a legit copy of the software.

prince-pep wrote on 9/10/2024, 5:34 PM

@prince-pep I assume you aren't using a French language install?

am using English language please

Justin-Halliday wrote on 9/10/2024, 6:34 PM

VEGAS 122 also doesn't launch for me. Installs okay, all the files are in Program Files, but when I try to launch, I get the little spinning thing for a couple of seconds then nothing happens.

iEmby wrote on 9/11/2024, 1:23 AM

@VEGASDerek & team... I hope we will get a complete fix of the below problem in next big update of VP22.

https://www.vegascreativesoftware.info/us/forum/need-help-in-multi-camera-sync-by-audio--146789/

As many other users facing this issue too. It means, it should be fixed soon.

Thankyou in advance.

Last changed by iEmby on 9/11/2024, 1:25 AM, changed a total of 2 times.

PROCESSOR
     

Operating System: Windows 11 Pro 64-bit (Always Updated)
System Manufacturer: ASUS
12th Gen Intel(R) Core(TM) i7-12700 (20 CPUs), ~2.1GHz - 4.90GHz
Memory: 32GB RAM
Page File: 11134MB used, 7934MB Available
DirectX Version: DirectX 12

-----------------------------------------------

MOTHERBOARD

 

ASUS PRIME H610-CS D4
Intel® H610 (LGA 1700)
Ready for 12th Gen Intel® Processors
Micro-ATX Motherboard with DDR4
Realtek 1 Gb Ethernet
PCH Heatsink
PCIe 4.0 | M.2 slot (32Gbps) 
HDMI® | D-Sub | USB 3.2 Gen 1 ports
SATA 6 Gbps | COM header
LPT header | TPM header
Luminous Anti-Moisture Coating
5X Protection III
(Multiple Hardware Safeguards
For all-round protection)

-----------------------------------------------
EXTERNAL GRAPHIC CARD

-----------------------------------------------

INTERNAL GRAPHIC CARD (iGPU)

------------------------------------------------

LED - MONITOR

Monitor Name: Generic PnP Monitor
Monitor Model: HP 22es
Monitor Id: HWP331B
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI

-----------------------------------------------

STORAGE DRIVE

Drive: C:
Free Space: 182.3 GB
Total Space: 253.9 GB
File System: NTFS
Model: WD Blue SN570 1TB (NVMe)

---------------O----------------

My System Info (PDF File).

https://drive.google.com/open?id=1-eoLmuXzshTRH_8RunAYAuNocKpiLoiV&usp=drive_fs

 

Also Check

VEGAS Scripts Collection By Me

GitHub Profile

My YouTube Channel Dedicated to Only VEGAS Pro Tutorials

EDITROOM : My YouTube Channel (For VEGAS Tutorials)

VEGASDerek wrote on 9/11/2024, 5:46 AM

@VEGASDerek & team... I hope we will get a complete fix of the below problem in next big update of VP22.

https://www.vegascreativesoftware.info/us/forum/need-help-in-multi-camera-sync-by-audio--146789/

We have a significant enhancement of the audio sync feature that we hope to release with the next major update. It was a bit too big for us to effectively test and release in time for this latest patch (which we consider only a minor update).

Howard-Vigorita wrote on 9/11/2024, 11:15 AM

seems you have the same update issues I had, the fact that Vegas 22 b122 does not open at all after installing, points to this (that Vegas 22 is removed instead of installed)

I wonder if your experience is from a double-click causing double execution. That sometimes happens to me when I open Vegas with a double-click and get two instances. I avoid that by right-clicking and selecting Open from the context menu. I install my updates the same way. I think there's a way to tell Windows or the mouse driver to use a longer time constant for double-clicks, which might also minimize the issue.

I too see Win11 machines reported in my Magix account as win10.

killacyst wrote on 9/11/2024, 4:50 PM

just updated and instant crashes can't even open the program