Did the Universe products work in the last build? (243 or 239?) PluralEyes still works.

Hi everyone,

I've noticed a problem when exporting 5.1 audio in VEGAS Pro 22 Build 248.

🔹 Issue:
After rendering a project with 5.1 surround audio, when I reimport the exported file into VEGAS, only the first two stereo channels (L+R) are visible. The rest of the surround channels (Center, LFE, LS, RS) appear blank or are missing entirely.

🔹 Notes:

This issue didn't happen before with older builds.

I'm using standard 5.1 settings, and the timeline is properly configured.

The export format is WAV with 5.1 configuration.

The exported file seems incomplete when checked in external tools as well.

Is anyone else experiencing this issue?
Does 5.1 export work correctly for you in Build 248?

Any help or confirmation would be appreciated!

Thanks in advance.

Ontem atualizei para o build 248 e meus projetos pararam de abrir. Depois de tentar bastante precisei até formatar meu pc. agora fiz instalei novamente a versão anterior e começou a travar novamente!
Criei um ponto de restauraçao do meu windows e agora estou seguindo novamente para a versão 248 novamente conforme me indicaram por email.

@RogerS Every time I open Vegas, it nearly maxes out the full 12GB of GPU RAM no difference whether it’s a small or large project. Once I close Vegas, GPU usage drops back to 2–3GB. This full memory load often causes sudden lag, playback issues, and occasional freezes where Vegas stops responding altogether.

@Nizar-AbuZayyad Did you already create a post about this (if so can you link to it)?

I have two NVIDIA 8GB GPUs and am not seeing problematic behavior. It does use most of the video ram (pre-buffering I assume) but enough is left not to cause issues. It would be good to see what's causing problems in your case.

@Nizar-AbuZayyad before opening VP22 B248, my GPU usage is 2.7GB. Opening to a blank timeline, 3.4GB GPU RAM is used on my computer.

Opening a 4K project where I used a lot of BorisFX and proDAD plugins, GPU RAM usage increases to 10.1GB.

I'm not in the market for a new GPU, but considering increasing system RAM to 64GB.

my gpu usage is similar to Reyfox.

previous universe version works

@Tamas-Maj  ... you might want to contact MAXON via the support link given at the bottom of:

https://www.maxon.net/en/article/support-for-red-giant-tools-in-sony-vegas-to-enter-limited-maintenance-mode

... to seek advice from them about whether or not the latest build is expected or not expected to work in Vegas Pro build 248 or any other Vegas Pro versions/builds.

If you do, it would be helpful if you would post the response on this forum as that could help others with Universe trying to navigate MAXON's changes.

As typical, latest update won't install nicely from within app (either while open or 'after program close'. Had to come to the forum for links and do fully manual, as is almost all but one time, the only way it will work for me.

I was excited to install the new update, hoping that it would fix the problems that had earlier made me stay with VPro21 and stay away from 22. But alas, the problems are still there in the new release. Where two clips come together, there is (not always) blackframing and/or "stuttering". Happens in the footage from both cameras on my two-camera shoot. So sadly, It looks like Version 21 is my "Last" Vegas release. Sad because I've been using Vegas since the Prehistoric days before Sony acquired the product, Way Back when it was an audio-only environment. Fortunately for me, Release 21 does everything I really need to do. The newest features sound like fun, but I've lived without them since forever so I won't "miss" them. (I posted my system configuration info when I reported these problems a while ago.Don't have time to re-gather the techspecs just now.)

Vegas is still crashing when copying keyframes from pan/crop menu and then closing the menu. Is this on radar to be fixed?

Yes, it is fixed. However, it was not included in this update.

I am very concerned by reading this post from an official VEGAS forum poster.
Please!, correct me if I am off base or plainly wrong here.

It just never occurred to me that a fixed bug fix would be not included at a VEGAS
update fix release... by choice, not because the bug is not fixed yet!

Furthermore, adding to this 22 version's pathway track; the VRAM & Ram leak resulting in frequent crashes of LUT plus 22's reported regular high GPU RAM usage, so far is rendering my decision to support Magix and buy this version update (something I press my budget to do only when proven improvement actually comes with a VEGAS version release)... the wrong one.

Therefore, is there in the developer's aim, the product owner and new management goals, the intent to fix and deliver the features and actual functioning promoted at version 22 release? Are we Magix VEGAS 22 customers going to receive actual effective updates tending to that deliverance goal, or instead is there going to be neglect and choice disdain to let go into whatever functioning state VEGAS 22 results, when the chosen calendar date for the new version falls?

>t just never occurred to me that a fixed bug fix would be not included at a VEGAS
update fix release

Just becasue a bug is fixed doesn't mean it is ready for release. For example, it probably needs to be regression tested, and go through QA and UAT. So decisions are taken which bug fixes will be included in a given patch release becasue there is only so much time and resource available to the development team.

The fact that it has been acknowledged that this bug has been fixed means the fix will probably come in the next patch.

This bug was fixed after code freeze for this update. We have it targeted for the next update for Vegas Pro 22.

Hi everyone,

I've noticed a problem when exporting 5.1 audio in VEGAS Pro 22 Build 248.

🔹 Issue:
After rendering a project with 5.1 surround audio, when I reimport the exported file into VEGAS, only the first two stereo channels (L+R) are visible. The rest of the surround channels (Center, LFE, LS, RS) appear blank or are missing entirely.

🔹 Notes:

This issue didn't happen before with older builds.

I'm using standard 5.1 settings, and the timeline is properly configured.

The export format is WAV with 5.1 configuration.

The exported file seems incomplete when checked in external tools as well.

Is anyone else experiencing this issue?
Does 5.1 export work correctly for you in Build 248?

Any help or confirmation would be appreciated!

Thanks in advance.

@mamomo 5.1 only works on my system when the project setting audio master bus setting is in 5.1 (obviously) but also requires my audio device type (on the preference tab: audio device) to be changed from the default audio device type Microsoft sound mapper to the audio device type direct sound surround mapper

@mamomo 5.1 sólo funciona en mi sistema cuando la configuración del autobús maestro de audio del proyecto está en 5.1 (obviamente) pero también requiere que mi tipo de dispositivo de audio (en la pestaña de preferencia: dispositivo de audio) se cambie de dispositivo de audio predeterminado tipo de sonido Microsoft mapaper al tipo de dispositivo de audio directamente mapa envolvente de sonido

I'm going to try this, thanks

This bug was fixed after code freeze for this update. We have it targeted for the next update for Vegas Pro 22.

Thank you for your confirmation. That (fortunately fleeting) possibility of an existing bug fix not being released for the present version... was somehow unsettling.

Your answer also lights up the chance for those other few mentioned remaining (and sore) issues in this rather stable version 22, to be resolved as well.

These are cheering news, indeed.

b248 crashes instantly when I load a certain project - but not when I downgrade to build 122.

I'd like to send the project directly to the devs.

@David File a support ticket and make the project available to them.

I installed build 248 and now Vegas Pro hangs adding effects to audio tracks and crashes - how do I roll back to the previous revision?

@Paul-O how about posting what specific effects you've added to the audio track?

Program crash on start-up when "loading video plug-in factory'. I thought fixing start up crashes was one of the features of this update. Unacceptable.