-
Audioon 5/12/2023
Audio drag delay
Okay, but did it start (the issue) in build 403? Or was it already there in 370 (the previous build). When you drag, is the 'event' following your cursor (at a distance, like slow motion) or not moving at all?In my case (and others) knobs and sliders (in audio plugins) are reacting extreme slow on mouse movement, like they follow your cursor in slow motion, stick to the screen, jump back and forth, catches up and slows down again. That's a serious issue, introduced in 370 (bypass was "do not create undo's for FX") and is now unworkable slow in 403 (bypassing doesn't work anymore).
-
Audioon 5/12/2023
Audio drag delay
When I am moving events around, I notice when I click the audio and start to drag it, it will not move for a few seconds and then it catches up. Never had this happen before. Any ideas what is causing that? Thank you. Is it since build 403 (Vegas 20)? Do you use 'any' 3rd party VST2 / VST3 plugins? When it's pure audio related, maybe it has to do something with these (similar) issues (like "tearing" when you try to alter an event / parameter); https://www.vegascreativesoftware.info/us/forum/bug-help-me-out-1-2-very-slow-performance-vst-plugins-tearing--140921/ https://www.vegascreativesoftware.info/us/forum/bug-help-me-out-2-2-vegas-records-extreme-many-undo-s-crash--140933/ In build 370 the speed went up by miles, when I did turn the option off "to create undo's for FX". But in build 403 this option doesn't do anything and the lag / sluggish drag * drop (tearing) is much more worse.
-
Audioon 5/11/2023
Multi-Band Compressor
...Any chance someone could send @NickHope a direct download link for the SFv16 .71 update so he can add it to his direct-download link list? His list only has up to .57. I finally got it through my Magix account but that link is not direct and the DLM hide's the ball, making it difficult to download once, archive it, and then use it to update multiple machines. @Howard-Vigorita 16.1.2.57 is a SOUND FORGE Audio Studio release, and is the latest update of version 16 of that application. That's the application bundled with VP20. I don't include SOUND FORGE Pro 16 in the downloads post as it has never been bundled with VEGAS, as far as I know. FYI, the 'dlm' download managers put installers in Documents\MAGIX Downloads\Installationsmanager\ so you can find them there. I had a quick hunt for a SOUND FORGE Pro 16.1.4.71 download link but couldn't find one. It *might* be the following, followed by the name of the installer .exe file (which I don't know): https://dl04.magix.net/2023/SOUNDFORGEPro16/ If someone gave me a link to download the SOUND FORGE Pro 16 'dlm' download manager, I could find the link using URLSnooper 2. It is on Filehorse - this is a legit site, isn't it?If not please, remove it (or mention me so I can remove it). I got it, using Fiddler (network inspector).
-
Audioon 5/11/2023
Bug? Three problems with Waves plugins only in VP20.
Another issue with Waves plugins: If the Waves audio plugin window is open, the playhead jerks during playback. The plugin may not be active and still cause tearing. I don't own the Waves plugin, but had the same issues with RX denoise using Vegas 19. Playhead did "scratch" and "slow down" as if it was a fancy audio-fx (like a turntable on the wrong speed). Realtime editing was impossible using RX (it was working fine on very low end machines using e.g. Audacity or Sound Forge). Fortunately in Vegas 20 it works smoother now. Als when you did enveloppe an effect, say adjust from 100% to 99.999% the playhead would became extreme slow and unusable for editing. But that was in Vegas 19, not Vegas 20. Another issue with third-party plugins: In VP20, plugin settings are choppy. Even if Vegas isn't playing. Yes, in every 3rd party plugin inside Vegas 20 / build 403 (not 370). It is now impossible to edit audio in Vegas, because of this sluggish / tearing bug in the GUI. You can't simply set a parameter by slider / knob, because the whole mouse "freezes" or "chops" over the screen. ------------------------------- The thing with VST3 is that they should not be active when there is no audio playing (instead of VST2, where processing is always active, even during silence). But Vegas is always processing, even VST3, even without any sound on the speakers / monitors. It's the same bug like those several recorded undo-states that shouldn't be there.
-
Audioon 5/10/2023
[bug] Help me out 2#2 - Vegas records extreme many "undo's" (crash)
Here's a .wav file with Loudmax 64 VST 2 applied. For Izotope RX9 De-ESS I created a new project, I did the same in the video below (LoudMax 64 / VST 2 and Izotope RX9 De-Ess / VST 2). As you can see both did trigger many (hundreds) of undo's where only four of five should be set. This happens with all 3rd party plugins (the native ones from Vegas act like they should). To make things clear; the problem (for me) is not the insane amount of "undo's" and not the (possible) crash / freeze of Vegas (sometimes that happens, sometimes not). But the problem is that in Vegas 20 / 403 the plugins become unresponsive (when you change a parameter with a slider, knob or mouse-movement than Vegas "struggles" to keep in synch with what you are trying to change). I think the many undo's have to do something with this. See this post that is (somehow) linked to the "undo" issue (I think); https://www.vegascreativesoftware.info/us/forum/bug-help-me-out-1-2-very-slow-performance-vst-plugins-tearing--140921/ In Vegas 20 / 370 the GUI of 3rd party plugins became "sluggish" (tearing) when "undo FX for 3rd party plugins" was active (and became fluid, when turned off). In Vegas 20 / 403 the GUI is always sluggish (the same effect as 370 with the option turned on) even when you bypass the undo's. So it looks like there is a link between the many "undo's" and the "tearing" in 3rd party plugins (since Vegas 20 and even worse in the latest build). - edit - there was no automation or anything active. I just made plain changes which results in many undo's. The issue started with the first build of Vegas 20, became worse in 370 and is breaking (for me) the workflow in 403. Turning the option "record undo's for FX" off, doesn't work in 403 (it was in 370) because the GUI of affected plugins is extreme slow now (in 403). It spoke to the devs of DeEss by Airwindows and Lisp / Spitfish (all de-essers) and they all stated that their plugins did not even "record" their own undo's; this is done by the client (Vegas). I also tried those plugins in Audacity, Sound Forge and RX 10 Pro without any issue.
-
Audioon 5/10/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
I first discovered this problem on a quad-core xenon in the first vp20 version and the subsequent Vp20 update. Then I upgraded the pc to 12 core intel and 64gb memory. The problem has not occurred since then. I thought Vegas 20 had higher CPU requirements. The problem appeared again now in version 403. Those are exactly my findings as well. I have a 12th generation i9 with 128GB ram and even than it freezes. In short; Vegas 20 / build 370 - tearing in 3rd party plugins (slow mouse movement) and tons of "undo" in memory.You could workaround this by bypassing "save undo's for 3rd party FX". Vegas 20 / build 403 - tearing has become extreme, almost unworkable now.The workaround is now doing nothing (it doesn't show the undo's in the undo-stack, but it keeps "fetching / recording" them.
-
Audioon 5/10/2023
Vegas hangs if you apply - VST3 spectral denoise (Izotope)
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). 👍
-
Audioon 5/10/2023
Vegas hangs if you apply - VST3 spectral denoise (Izotope)
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. UNDO bug - https://www.vegascreativesoftware.info/us/forum/bug-vegas-records-extreme-amounts-for-undo-s-causes-lag-and-crash--140933/ TEARING bug - https://www.vegascreativesoftware.info/us/forum/bug-help-me-out-very-slow-performance-vst-plugins--140921 Sorry for inconvenience.
-
Audioon 5/10/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
More details about the undo bug - https://www.vegascreativesoftware.info/us/forum/bug-vegas-records-extreme-amounts-for-undo-s-causes-lag-and-crash--140933/
-
Audioon 5/10/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
I confirm. There is a tearing problem even with stopped playback. The problem is with all third party plugins Okay, so it not just me. ----------------------------------- But how on earth is this possible? Vegas is now completely unusable when you use any 3rd party plugin (even the plugins that are bundled with Vegas itself). I mainly use the commercial Melda suite which costs more than $ 2.500,- and is superfluid even in freeware like Audacity. In Vegas 20 / 370 it was 'okayish', but in 403 it's unworkable. The "tearing" (a new term for me) is so extreme that I can not even finetune a parameter. If I want to slide or drag it to 5.25 (for example) it bounces from 4 to 6, back to 3, new to 7 and freezes at 8. It is simply not possible to finetune your settings. You are really "fighting" or "struggling" with your mouse to get the pointer moving (it is more bad than in the recordings, you have to experience yourself). ----------------------------------- Only the RX plugins are looking / working "okay" now, but the release notes said the "fixed some minor and rare bugs for RX" (read : it didn't work at al in 370). So maybe the "fixed" something for RX, which causes all other plugins to totally mallfunction? Once again, it has to do something with those totally unusable undo-states, that freezes and crashes Vegas and causing an internal refresh loop (memory overflow). ----------------------------------- I tried to create a ticket for this, but that is not possible. It was okay in 370, very bad in 403 - where can I / we report this extreme (new) faillure?
-
Audioon 5/9/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
See the reason (I think) of the slow performance in this video. It is Vegas 20 / build 370. When you change a simple parameter, Vegas "fetches" hundreds of undo-states. I have contacted the dev of this (and other) plugins and they clearly state that the plugin itself is not firing those states to the "parent" (Vegas), but the parent (Vegas) is fetching it from the client / child (plugin). In stead of one undo, Vegas memory overflows with hundreds. In build 403 this becomes so slow, that changing a parameter in a plugin is almost not possible in realtime. As a side effect, undoing one of those complete useless undo's will result in freezes, crashes, etc... In build 370 you can bypass this bug by "don't record undo for FX" in the options, but in build 403 it still saves those (invisible for view) even when changed off.
-
Audioon 5/9/2023
Vegas hangs if you apply - VST3 spectral denoise (Izotope)
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; https://www.vegascreativesoftware.info/us/forum/bug-help-me-out-very-slow-performance-vst-plugins--140921/#ca880192 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).
-
Audioon 5/9/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
This show the exact same plugin in RX10 editor / PRO. It is as fluid as in Vegas 20 / build 360. But in Vegas 20 / build 403 it is extreme sluggish when you move points / knobs and parameters like in the video above. And in Sound Forge Pro 16 also smooth. ________________________________________________________ Also in freeware Audacity it is smooth as hell. ________________________________________________________ But in Vegas 20 / build 403 (not build 370) it is unusable slow and sluggish.
-
Audioon 5/9/2023
[bug] Help me out 1#2 - very slow performance VST plugins (tearing)
I hope this works, because the video-uploader acts weird. It show Vegas 20 / build 370 with the plugin mention above. As you can see (I hope) dragging some points and chancing some parameters is superfluid. In Vegas 20 / build 403 (see animated GIF in first post) it is very sluggish when you try to do the exact same.
-
Audioon 5/9/2023
[bug] Re-enable Vegas 20, build 306
I usually do this kind of revision with Macrium Reflect. With an NVMe disk, one image of a dual boot system can be restored quickly. Sorry, but I don't understand what you are saying. I need to run Vegas 20 / 306 because Vegas 20 / 403 is totally unworkable with most VST plugins. And Vegas 20 / 306 only works until May 2nd 2023, after that it stops working. So I created a .bat file (and compiled it to a 64-bit .exe) that sets the system date in history, fires Vegas 20 / 306 and set the date back to today. It's not possible to work like a professional using Vegas, without writing your own libraries.
-
Audioon 5/9/2023
[bug] Please, fix Vegas so audio-professionals can also use it
@Peterson The new Vegas 403 build does not hang anymore when applying VST3 spectral denoise. I also tried with success Voice de-noise, and spectral denoise + voice denoise in any combination... From my limited testing on my side there seem to be progress on the audio front. There is progress, but Melda is now not workable. When you move a slider (let's say 1dB to 2dB) and that's about 100 pixels movement, every freaking pixel movement triggers hundreds of undo-states in memory. Resulting in a crash when you "undo" that change, but also it's not possible to adjust the slider, because it is so extreme sluggish in movement. This is introduced in build 403. I have contact with the Melda devs and they say their plugin is not shooting those states; it is Vegas that fetches them. Normally you take the start parameter (1dB) and end parameter (2dB) and when you "undo", it goes from 2 to 1. But Vegas records all steps inbetween, like 1.01, 1.03, 1.94, 1.96, until it reaches 2. So the memory is overflown and when you "undo" it, it goes back like 2.00, 1.99, 1.98, etc... That is not how it should work; the inbetweeners are not important.
-
Audioon 5/9/2023
[bugs] Vegas 20 - 403 has serious workflow bugs for audio professional
@Peterson point 1: (toggling the state of a plugin (on/off) with the left mouse button): I cannot reproduce, seems OK to me on my PC point 2: It does seem to track a lot not needed in-between states for undo purposes when turning a a knob for instance from a begin to a final state. Not sure if Vegas is to blame if the plugin insists on sending all changes while turning the knob or slider. It sure is not ideal nor wanted; a beefy PC can probably handle it without crashing, but again, it is not ideal. point 3: Indeed the GUI redraw flickers distractingly. How can this be in this day and age? Are they using an slow interpreting language instead of compiled code? A modern 3D shooter could handle V. refresh rates of 240 Hz... point 4: I do not have Melda... 1. It does not happen every time, it's complete random 2. This bug is 'introduced' in version 20, but you could bypass it by opting "not saving undo states for FX" in the options - in build 403 this option does nothing now (it doesn't save the states, but the states are still shoot into memory) 3. Bad GUI libraries 4. I work 50% with RX and 50% with Melda (I use Vega for audio). Specs : Intel 12th generation i9, 128GB memory, 4TB Samsung Pro SSD, NVIDIA RTX 4090 But it also happens on other machines here (the above is the most powerful I have).
-
Audioon 5/9/2023
Vegas hangs if you apply - VST3 spectral denoise (Izotope)
@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; Undoing a history-state crashes Vegas (there are thousands of entries in the undo-stack) Changing a parameter in a 3rd party plugin (like Melda or LoudMax) is extreme sluggish now The order of the plugins in the chain gets corrupted when you toggle that state of a single plugin 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/
-
Audioon 5/8/2023
Multi-Band Compressor
Not quite multi-band but also a very comprehensive compressor : mCompressor. There's a free version (only show a "warning message" in the GUI) and part of the cheap basic-bundle. Be aware : Vegas V20 build 360 is quite buggy with all Melda plugins and build 403 totally destroys those VST plugins.
-
Audioon 5/8/2023
[bugs] Vegas 20 - 403 has serious workflow bugs for audio professional
Above image show when Vegas 20 crashes or at least disrupts the order of the plugins. Toggle with left-mouse = crash (GUI will freeze) / the ordering becomes corrupt. Toggle with right-mouse = no problem. Above image show in build 403 that moving this EQ point (or a slider) from 3rd party VST is extreme slow / sluggish (GUI freezes because every pixel you move it overflows memory with useless "undo states"). I have reported this months ago, but the problems in newest build only became more worse.
-
Audioon 5/8/2023
Vegas hangs if you apply - VST3 spectral denoise (Izotope)
PLEASE, DO NOT UPDATE TO THE NEWEST VEGAS 20 It makes the software even more unworkable and corrupt. Please, see this thread; https://www.vegascreativesoftware.info/us/forum/bug-please-fix-vegas-so-audio-professionals-can-also-use-it--140335/#ca880023 All the errors are even made worse now.
-
Audioon 5/8/2023
[bug] Please, fix Vegas so audio-professionals can also use it
Set oShell = CreateObject("Shell.Application") oShell.ShellExecute "C:\Users\USERNAME\Desktop\network\disable.bat", , , "runas", 1 WScript.Sleep 1000 oShell.ShellExecute "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe" WScript.Sleep 1000 oShell.ShellExecute "C:\Users\USERNAME\Desktop\network\enable.bat", , , "runas", 1 For those professionals who can not use Vegas anymore (the new one, that freezes all professional plugins), see the VBS above. This will disable-network, start Vegas (the "old" version), enable-network. You also have to include "enable.bat" and "disable.bat" for pinging to your modem. netsh interface set interface "MODEMNAME" admin=disable netsh interface set interface "MODEMNAME" admin=enable Also you have to block Magix servers from HOSTS file; 127.0.0.1 ssl-update.magix.com 127.0.0.1 *.magix.com 127.0.0.1 vegascreativesoftware.com Doing to the "old" Vegas will still work, enabling me to finish the project I have been working on since 2019. I even de-compiled the .exe of Vegas and did find solutions for all those bugs (buffer overflows and GUI mis-performance). But Magix sayed "they were not interested".
-
Audioon 5/8/2023
[bug] Please, fix Vegas so audio-professionals can also use it
Even when I drag a slider from a simple 3rd party plugin like LoudMax (let's say adjust the treshold from 1dB to 1.5dB) there are 250 (!!!) undo-entries in the memory created. Is that VEGAS' fault? If the plugin is passing "changed" information for every minute adjustment, then VEGAS will happily record that a change was made... I am not blaming anyone. But let's keep it simple. Those are (rather) expensive plugins (e.g. more than $ 1.000,- each) and not some illegal kind of crap. They work flawless in other programs and they did "work" very buggy in the "old" Vegas. In the "new" Vegas, they simply stopped working. And since Vegas says "it does support VST 2 and 3 and is for audio professionals" I expect this to work. Also, I did contact support more than 10 times, and they were aware of there problem (they said). I did contact the creators of both Melda and RX, and they do state it's "Vegas fault" (and Magix is aware of it). ------------------------- When I change value 1 to 2, all other software has one undo : revert 2 to 1. But Vegas has hundreds of undo's, and is overflowing it's own memory with values like 1.01 - 1.02 - 1.03 - etc... until it reaches 2. And a single undo does not go from 2 to 1, but from 2 to 1.99 - 1.98 - 1.97 - etc... So you have to undo 1 parameter 500 times to really undo it. That's why it's crashing. Now even when you bypass Vegas' internal "undo system" the events are still fired to the memory and that wasn't the case in the "old" Vegas 20.
-
Audioon 5/8/2023
[bug] Please, fix Vegas so audio-professionals can also use it
https://i.ibb.co/P6xMTPV/new.gif I did uninstall the "new" version V20 of Vegas and installed the "previous" V20 version (while setting the date back to May 2nd, so it doesn't crash at startup). See the image above and compare it to the one in the previous post. The "old" version (in this comment) is smooth, fluid, the mouse and VST-parameters follow the cursor. The "new" version freezes, lags, skips parts, is fighting against the movement. This is so not good for me.
Peterson
Offline, Last login 5/15/2023, Member since 3/23/2023