After adding audio effects "fx" won't let me edit the audio in Vegas

Mara-Martnez wrote on 5/30/2023, 7:20 AM

After adding audio effects "fx" won't let me edit the audio smoothly, it freezes for seconds when cutting and splitting events. Neither does the event that I select, it accompanies the pointer when I press/select it to move it, it moves after a few seconds frozen at once.Add that when the audio does not have any effect on it, it works perfectly when editing it, separating, cutting...etc it goes smoothly, but if I add the effects, it is impossible to work with it. However the video and texts work perfectly. It only happens with the audio. I have vegas pro 20 pack, that includes sound forge audio studio 16 and add that I also bought the upgrade to sound forge audio studio 17 because of some extra plugins that it contained.
This time, I recorded the audio in vegas, but the other time I did it in sound forge but when I opened it in sony vegas the exact same thing happened to me, impossible to edit the audio, it freezes every step I take for a few seconds (it doesn't react)
Hopefully someone else has experienced the same thing and found a solution.
Thanks for the help!

Comments

Dexcon wrote on 5/30/2023, 7:30 AM

First of all, you do not have Sony Vegas Pro 20 unless you have a pirated version of Vegas Pro 20 (pirates still name it Sony) - https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

Please advise the tech specs of your audio media being used in Vegas Pro via a MediaInfo report - https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/ - as well as advising exactly what audio FX you are using as well as if they are VST2 or VST3.

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

Mara-Martnez wrote on 5/30/2023, 7:53 AM

Of course I have Vegas pro 20! It's just that I've been using it since I bought version 9 many years ago...

I don't know if I can do what you ask. The sound effects that I have used are varied, gate, deesser, noise reduction and some equalizers

rraud wrote on 5/30/2023, 10:03 AM

Are the Fx plug-ins third-party, or from Magix?
Are the plug-ins VST-2, 32 or 64 bit or VST-3?
Exactly which plug-ins cause the issue?

rraud, Magix forums moderator

DMT3 wrote on 5/30/2023, 10:12 AM

and which audio driver are you using?

Petersson wrote on 5/30/2023, 2:02 PM

@Mara-Martnez

Try turning off "create undo's for audio FX".

Mara-Martnez wrote on 5/31/2023, 5:42 AM

@Mara-Martnez

Try turning off "create undo's for audio FX".

 

Mara-Martnez wrote on 5/31/2023, 6:05 AM

Unfortunately I don't have that specific option, I have looked for the most similar one that says "create undo versions for effect parameter changes" I had this option activated and I have deactivated it but it still does not work.
The effects that I have used, some are VST2 (Magix soundforge 17 audio studio) and others from Vegas.
64 bits

Audio drivers:

Nvidia High definition audio

Realtek High definition audio

Thnx for the support :)

Petersson wrote on 5/31/2023, 8:45 AM

@Mara-Martnez

Okay, that's the option I was referring about.

For me (and others) VST2 / VST3 plug-ins became very sluggish, slow and freezing the GUI when this option was enabled in build 370.

Turning the option off in build 370 was the solution.

In build 403 the slowdown is extreme, almost unworkable and this option doesn't do anything against it.

So I still work with build 370, because 403 broke almost all VST plugins I had to use.

vkmast wrote on 5/31/2023, 9:21 AM

For me (and others) VST2 / VST3 plug-ins became very sluggish, slow and freezing the GUI when this option was enabled in build 360.

Turning the option off in build 360 was the solution.

In build 430 the slowdown is extreme, almost unworkable and this option doesn't do anything against it.

So I still work with build 360, because 430 broke almost all VST plugins I had to use.

@Petersson is it possible that you actually mean builds 370 and 403?

Petersson wrote on 5/31/2023, 9:56 AM

For me (and others) VST2 / VST3 plug-ins became very sluggish, slow and freezing the GUI when this option was enabled in build 360.

Turning the option off in build 360 was the solution.

In build 430 the slowdown is extreme, almost unworkable and this option doesn't do anything against it.

So I still work with build 360, because 430 broke almost all VST plugins I had to use.

@Petersson is it possible that you actually mean builds 370 and 403?

Yes, you are right.

I am mixing things up, sorry.

Mara-Martnez wrote on 5/31/2023, 11:21 AM

So, what am i supposed to do in this case? Is it something that vegas or sound forge should solve? It's horrible to have to edit like this, and I have a lot of work left. I am Spanish and my English is not entirely good, I would ask you to specify if I could really resolve the situation "temporarily" or should I resign myself and edit what remains of the audio in this way.
Thank you very much for your help

Petersson wrote on 5/31/2023, 3:05 PM

@Mara-Martnez

Vegas is totally not usable for audio professionals since build 430.

It crashes and freezes several times a day and changing the VST-parameters results in destroying your audio and an extreme sluggish GUI as well; you can not work with it like that.

So I decided for myself to revert back to build 370, which is "somehow" usable (bugs, crash, freeze... but workable because we all know how bad Vegas performs since version 20 for audio).

You can use 370 by unplugging the internet, startup 370, enabling the internet.

Vegas developers say they are aware of (most) audio problems and try to fix it (when it's done...).

Mara-Martnez wrote on 6/2/2023, 1:19 AM

Thank you. I will try to do It.

Mara-Martnez wrote on 6/2/2023, 11:22 AM

Hi Petersson :)

I have installed build 370 as you said, before opening it, I disconnected the internet and I try to open it. Vegas loads, but the problem does not open, let's say that the bar loads completely, but the program does not open. Do you know what it is due to? What I can do? Thanks again for your help and sorry for the inconvenience.

Mara-Martnez wrote on 6/2/2023, 12:03 PM

I have found another solution, once all the effects are added split the audio into several tracks, this makes editing easier. It has helped me, it no longer freezes when cutting, separating... etc. In case it can help you. And the effects look good on my audio, they don't break down. Greetings and thanks for your attention and help.

****EDIT: This solution worked fine until it stopped working. I don't understand what can happen. I am very tired of this, I have paid a lot of money for a program that I cannot use.

Petersson wrote on 6/3/2023, 4:55 AM

You can only start build 370 when disconnected from the internet (until the interface is shown).

Or / and you can set the clock back to 2nd May 2023 (and set it back once the program is ready).

BUT THIS IS FORBIDDEN BY VEGAS

So I don't think it will help you, like you already mentioned.

Build 403 is a complete and 100% disaster for audio professionals; it broke all VST 2 / 3 effects (besides the RX ones) and build 370 crashes at startup.

I can work with 370 because I did some programming enabling it, but for most of the professional audio users Vegas is dead like dead can be.

They said they will fix it, 'though...