Vegas hangs if you apply - VST3 spectral denoise (izotope 10 or 9).
Hangs every time from the moment you apply that particular VST plugin, so it is unusable.
It should be easy to reproduce. See my signature for my system.
Media is coming from Sony RX10 III camera:
Video: 00:00:11,040, 25,000 fps progressive, 3840x2160x32, XAVC-S
Audio: 00:00:11,040, 48 000 Hz; Stereo, PCM
Vegas hangs if you apply - VST3 spectral denoise (izotope 10 or 9).
Hangs every time from the moment you apply that particular VST plugin, so it is unusable.
It should be easy to reproduce. See my signature for my system.
Media is coming from Sony RX10 III camera:
Video: 00:00:11,040, 25,000 fps progressive, 3840x2160x32, XAVC-S
Audio: 00:00:11,040, 48 000 Hz; Stereo, PCM
It's not only VST3 or VST2, not only Spectral Denoise and certainly not only iZotope.
Almost all plugins from both iZotope, Melda and other third parties do crash Vegas (from version 20 onwards).
De-ess, de-plosive, EQ, etc... they all do crash, freeze, destroy and mutilate both Vegas, the project and your timeline.
I did report many of those bugs, even in close contact with the devs - but Magix itself didn't answer.
They send me 10 (!) e-mails before answering with random stuff like "is your copy hacked" and "do you have a serial" and "send us the credentials" (over plain e-mail, yeah).
Finally they were willing to answer me (I did even de-compile their own codebase, required .DLL's and library enhancements) and told me "they were aware of the problem".
To list up the extreme issues with audio again and again;
So for everyone using audio in Vegas on a professional base; don't do it until those issues are fixed.
I narrowed down all the errors to the GUI / canvas / history-stack and redraw classes, but they refuse to answer to my findings.
There's something really totally f*cked up in the core of the codebase, since all those issues are 100% related to the same (and single) weakest point in the repo's.
Off-topic : somehow this forum keeps resetting my profile and session cookies.
On-topic : lol, after working about 16 hours for an edit of one minute long, Vegas did crash more than 50 times today.
Luckily I do hit "save incremental" every freaking minute and have auto-save set-up to save it every five minutes.
Just check the screenshot to see what happens if you "just" enable an FX like iZotope or Melda (VST2, VST3, etc... in Vegas 20).
Freeze, GUI interrupt, canvas redraw, buffer overflow, crash.
As you can see the embedded interface of the plugin "stops" being drawed at the borders (right and bottom).
Indicating an overflow in the parent software (Vegas), causing a white screen "flickering" every single time you "undo" or "redo" anything (which is completely useless, since it doesn't happen when you "rightclick and toggle enable state".
This makes working almost impossible (why am I even trying to stick with this software?).
Vegas hangs if you apply - VST3 spectral denoise (izotope 10 or 9).
Hangs every time from the moment you apply that particular VST plugin, so it is unusable.
It should be easy to reproduce. See my signature for my system.
Media is coming from Sony RX10 III camera:
Video: 00:00:11,040, 25,000 fps progressive, 3840x2160x32, XAVC-S
Audio: 00:00:11,040, 48 000 Hz; Stereo, PCM
It's not a solution for your problem (VST3 from Melda / iZotope / etc... simply doesn't work in Vegas 20), but when a random (GUI) freeze happens, you can try to bypass it as follow;
It's a real pain in the *ss that we have to work like this, but Vegas 20 isn't usable for audioprofessionals; it will crash and freeze whatever you do using a dedicated third party plugin.
@Touchette @Peterson I cannot comment on your issues as you describe as above, which could be very real, and indeed an issue; but for now I want to point the focus on one VST3 plugin in particular as the post title suggest:
VST3 spectral denoise (Izotope). For me, it is the only one which does not work. It is the only one which lets my system hang from the very moment I add this plugin. No other Izotope RX10 plugins exhibit this behavior. All other plugins do not lead to a hang of Vegas when applied. I even updated the RX10 to v10.4.0) , but the issue still remains. I tried running Vegas 20 in administrator mode; I tried to change the audio device to all possible types in Vegas preference. Note that the spectral denoise works in sound forge pro...
@Touchette @Peterson I cannot comment on your issues as you describe as above, which could be very real, and indeed an issue; but for now I want to point the focus on one VST3 plugin in particular as the post title suggest:
VST3 spectral denoise (Izotope). For me, it is the only one which does not work. It is the only one which lets my system hang from the very moment I add this plugin. No other Izotope RX10 plugins exhibit this behavior. All other plugins do not lead to a hang of Vegas when applied. I even updated the RX10 to v10.4.0) , but the issue still remains. I tried running Vegas 20 in administrator mode; I tried to change the audio device to all possible types in Vegas preference. Note that the spectral denoise works in sound forge pro...
I can confirm.
For me, I downgraded to RX09 (from RX10).
It did cost me another $ 1.500,- for the license, but RX09 does "work" (it still crashes / freezes about 15 times a day, but there are moments it works).
I also use Sound Forge, Studio One, Reaper and RX Editor - those work 100% without any limit, freeze or bug.
Sidenote : this is about iZotope only. Other plug-ins like from Melda (and iZotope) immediately do crash Vegas in less than one second when you "undo" a parameter from a plug-in (doesn't matter which plug-in or which parameter).
Looks like it has never been tested.
PLEASE, DO NOT UPDATE TO THE NEWEST VEGAS 20
It makes the software even more unworkable and corrupt.
Please, see this thread;
All the errors are even made worse now.
@Peterson the new Vegas 403 build does not hang anymore when applying VST3 spectral denoise. I also tried Voice de-noise, and spectral denoise + voice denoise in any combination...
It also renders OK.
Obviously there are a lot of different render possibilities, source material differences and VST parameters you could set, but having a quick check it looks OK now.
So for me (on my PC at least) my original post stating "Vegas hangs if you apply - VST3 spectral denoise (Izotope)" seems fixed with version 403...
I see a slow redraw period when Spectral Denoise is activated and deactivated but no crash nor excessive number of undo states. It's the RX9 VST 2.
I'm not able to get RX 9 De-Ess or Declick to crash toggling it on and off while playing and adjusting settings. I'm testing on a AVC mp4 file with AAC audio if it matters.
@Peterson the new Vegas 403 build does not hang anymore when applying VST3 spectral denoise. I also tried Voice de-noise, and spectral denoise + voice denoise in any combination...
It also renders OK.
Obviously there are a lot of different render possibilities, source material differences and VST parameters you could set, but having a quick check it looks OK now.
So for me (on my PC at least) my original post stating "Vegas hangs if you apply - VST3 spectral denoise (Izotope)" seems fixed with version 403...
Really glad to hear that the update works for you.
But "other" plugins still triggers a lot of issues.
It looks like they solve each incident per plugin, in stead of writing a solid library for all the plugins.
Build 403 is totally unworkable for me, because;
I had to revert back to build 360 and freaking disable / enable my network every time Vegas launches (which I have to do very often, because even 360 crashes and freezes several times a day).
All problems are related to VST and memory / GUI management.
More info in this single tread; https://www.vegascreativesoftware.info/us/forum/bugs-vegas-20-403-has-serious-workflow-bugs-for-audio-professional--140900/
Are some of the plug-in's automation parameters enabled, even if one parameter is active, that could write many changes within a few milliseconds.
Are some of the plug-in's automation parameters enabled, even if one parameter is active, that could write many changes within a few milliseconds.
Sorry for the late response.
No, it has nothing to do with automation.
See this thread with more details and screen captures from other programs;
It's the exact same plugin, exact same settings, but only in Vegas 20 / build 403 it becomes unusable.
And it is with other 3rd party plugins as wel.
______________________________________________________________
Also, see the capture below.
I change one parameter (slider) and Vegas records hundreds of unusable undo-states (crashing and freezing the program).
In Vegas 20 / build 403 those states are now only "hidden" from view (when you choose "don't record undo states for FX") but still captured in memory (freezing the GUI as shown in the other post I mention here).
Are many undo states created for all VSTs you are testing or just a few? Trying to replicate here.
Please create a separate post about the VST undo state issue (or use one of Petersons threads).
My original post issue "Vegas hangs if you apply - VST3 spectral denoise (Izotope)" which was very reproducible, is solved by V20 build 403.
Please create a separate post about the VST undo state issue (or use one of Petersons threads).
My original post issue "Vegas hangs if you apply - VST3 spectral denoise (Izotope)" which was very reproducible, is solved by V20 build 403.
+1
@Peterson
I'm just a fellow reader here and also think it's better to stay in your own thread and not confuse other threads - and thus fellow readers.
You surely have a different system environment than bitman - so please stay in your own thread.
Honestly it's very confusing which thread is which given the basically identical text in each. I thought this was a Peterson thread just reading the most recent entries.
FWIW, I also tested spectral denoise in 20.403 and haven't been able to get it to crash. I also don't see excessive states being created here.
I created separate threads for it.
But to be honest, I created tons of tickets and threads for the same issues months ago.
And nobody listens, in build 403 things are worse than ever.
Sorry for inconvenience.
@Peterson You're not helping yourself by repeating the same thing at length in multiple threads. Rather than gain attention, the sheer volume of words and repetition creates confusion and makes your points an unnecessary effort to follow and digest. The repetition is also against community rule #3. You have 2 other "parent threads" on the go, and have more or less hijacked this thread to turn into a 3rd. Please keep threads concise and specific to the issue. Link back to a parent thread where necessary rather than repeat everything and, please, no more new threads unless it's about an issue not already covered by your existing threads.
I understand and already said "sorry".
Also I have "bundled" the issues by setting the subjects to 1#2 and 2#2.
Finally I did not haijack this by purpose, but some others were referring to the same (like) issues (which are all connected to the memory overflow, by the way).
But I understand your concerns, so I will not reply in this thread.
Last thing : I created tons of tickets, issues, phoned to Magix, spoke with devs and litterly no-one is listening (which is why I keep repeating these bugs - I do it for the best of us and future of Vegas).
👍