Mixing Console causing gui to crash

richard-leney wrote on 5/5/2024, 3:55 AM

Good Morning , I'm having issues with mixing console. Vegas 21 build 300.

My project contains 20 music tracks and i'm mixing them together to form a mixed album.

Whilst having mixing console open full screen on monitor 2, after adjusting the volume for each track the Screen starts to play up with Blue inserts for the meters , and the main editing window gets corrupted dotted lines and the drop down menus fail to appear.

I'm able to hit the save icon , exit the program and reload.

it appears to happen around the 15 track mark. (+-5)

It does not seem to matter if I'm adding track Eq or not to the mix.

my latest test was just adjusting the volume looking at the VU meters and problem occurred at track 20

it happens every single time i edit a file.

 

Ps it also happens on my laptop running windows 11 home build 22621 amd ryzen 5 radion graphics 2301mhz 6 cores 8g ram

Many Thanks

Leney

 

Windows 10 Pro build 19045

Processor    AMD Ryzen Threadripper 1950X 16-Core Processor, 3400 Mhz, 16 Core(s), 32 Logical Processor(s)
 

Installed Physical Memory (RAM)    64.0 GB
Total Physical Memory    63.9 GB
Available Physical Memory    57.4 GB
Total Virtual Memory    73.4 GB
Available Virtual Memory    63.7 GB
Page File Space    9.50 GB

NVIDIA GeForce GTX 1080    OK
 

Comments

Dexcon wrote on 5/5/2024, 4:51 AM

I wish that I had a solution to suggest to you for that. I have had that 'blue crash' - which happens randomly - so many times with Sound Forge Pro from SF10-16 for over a decade. I've often had the feeling that its caused by using the volume icon in SF too many times in the one editing session because the 'blue crash' always seems to happen when hitting the volume icon. Your image looks remarkably similar to what happens in Sound Forge. I see that you are using .mp3 audio events whereas I use .wav in Sound Forge.

But if its happening at the same point on the timeline and with the same audio event/s, the audio event/s might be corrupted in some way. If you know which audio event or group of audio events are at the point where the 'blue crash' occurs, try transcoding them to another codec such as .wav in an audio editor or separately in Vegas Pro and then replace them on your project's timeline. Then go to the Project Media window and click on the "Remove All Unused Media from the Project" button in the top LH corner of the Project Media window in order to get rid of any memory of the now deleted media from the project's .veg file.

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 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 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

richard-leney wrote on 5/5/2024, 5:51 AM

Thank you , I agree with the 'adjusting the volume' thing too many times as that's the part of my process for levelling the each track.

It's random and never the same track. I've created 7 different albums and every one has had the same issue .

At the moment , I just save after every track is at the right level so I don't loose my work if VP decides to crash out completely

Many Thanks for your tips , I'll give them a try

Best regards

Leney

VEGASDerek wrote on 5/5/2024, 1:19 PM

We have a fix for this problem which will available in the next patch for VP 21.

richard-leney wrote on 5/5/2024, 1:52 PM

Thank you Derek. much appreciated