Thanks rraud, with your techinque is slightly better, even if sometimes I hear glitches.
But if I use a plugin like ozone 8, for example, is a total disaster.
Applaying ozone to the single tracks (11 tracks) is perfect, but I want to use it on the main out.
Anyway, glitches are non present in rendered file, but is almost impossible to choose the right parameters without a clean monitoring.
Even with the siplest reverb (SIR 2), both 32 and 64 there are glitches.
Glitches are there also with Lexicon MPX reverb and with Liquidsonic reverberate.
I have a last generation pc (processor is at 10% and memory at 20%) with a zoom uac-2 audio interface.

Strange that it happens on different PCs. I would look for something in-common to the machines For instance, the Zoom uac-2 audio interface. Try a different converter, even an integrated one would work for test purposes. I have not heard of of many issues with the Ozone Fx which runs ok on my PC as well/the SIR-1.

Otherwise are you using video plug-ins as well? Check for other apps or services running on your PCs. Anti-virus apps in particular have been known to cause problems with DAWs and NLEs. though I have not read of many lately.

same problem with different audio interfaces.
No antivirus or other services.
And the problem is there only if I use the effect on the bus or on the main out, non on the single (mono or stereo) track.

Oh dear this problem STILL exists in VP17? I saw in another post that VST effects were now working as expected when the interface was open. What you describe is the (not so) famous VST fx bug present in all 64 bit versions of Vegas, starting with 11. If you use the VST at the track level, it works decently well. But if you use it anywhere else like on a bus or master out, it will glitch pretty bad. It's much worse when the VST's interface is open.

I refuse to buy any more versions of Vegas until this is fixed. This, plus allowing more than one FX window open at a time... that would be tremendous. It's so stupid that only one FX window can be open at a time.

I had hopes this was fixed given another user's positive results. But if you're experiencing this issue in the version 17 now, I guess it will never be fixed. Sorry to say. If you want to use VST effects without the glitching, switch to version 10 32bit. Good luck finding new 32bit VSTs. 😡

The issue above is why I have moved over to Reaper. Sounds like its not been fixed in VP17 either 👿

Thanks @DiegoC. for mentioning "different audio interfaces". I hadn't used audio effects for a while, but recently added a couple VST effects to an audio-only project, and was surprised to hear severe glitching on VP 17 build 421. I hadn't heard glitching since I upgraded my old Waves Rennaisance 5 plugings to recent versions a couple years ago. I have previously used VST effects in VP, including Ozone 8 on the Master out, with no problems. I had to switch to Acid to get my recording done. But now that you mention audio interfaces, I thought of my new audio interface (Røde AI-1 with Røde AI-1 ASIO driver). So I switched audio device to Realtek ASIO (motherboard audio) -- less glitching, and to Microsoft Sound Mapper or Windows Classic Wave Driver -- no glitching at all! So workaround I will be trying now is to record via Røde AI-1 ASIO with no VST enabled, and switch audio device to Microsoft Sound Mapper for editing/rendering with VSTs enabled. Is VST glitching perhaps a Vegas-ASIO issue?

It seems VSTs work fairly well at the track level but then start presenting the glitching issue when used at the master level and definitely the bus level. I just tested here with VP17 b421 and it does indeed work better when using the on-board Windows audio compared to my interfaces with ASIO drivers. It works for a while, but if VSTs are used at the bus level or even at the master level, eventually it starts glitching with the Windows on-board audio. The glitching correlates to the amount of mouse movement along with other display activity such as realtime displays of VSTs, etc. If I zoom with my mouse scroll wheel, a glitch happens with each click of the wheel.

Using any external interface with an ASIO driver just makes the issue worse, and maxing out the buffer size doesn't help any. I've experienced this on at least a half dozen different systems and installations over the years, and still the only version that works is the last 32bit version, Vegas 10e. I did purchase VP17 because I enjoy the video editing upgrades, and still hoping this VST glitch issue is eventually fixed. :)

I just asked Magix to refund me for 17+18 versions I just bought. This VST problem is unacceptable !!

I agree, its very frustrating not to be able to use VST3, just slows my work flow, by having to use Reaper to process the audio.

So, the infamous VST audio glitch issue STILL exists in Vegas 18? I've seen nothing in their release info about this. I reported this, plus asked for the ability to have more than one plug-in window open at a time (like any DAW or other app, you can have multiple windows open inside). [VEGAS Support representative] replied with the following: "Our development team is discussing a way to resolve both issues you bring up.  We in support cannot provide a guarantee or a time frame for when this will occur, but I can say that your feedback triggered quite a bit of discussion on the topic internally."

Quite a bit of discussion, huh? Perhaps I naively assumed a remedy was coming in the next version. That email exchange was on April 1st, so maybe it was a fool's day joke? Hopefully someone can confirm that this VST glitch issue is finally working now, or still persists. The last Vegas version in which you could use VST fx in any normal fashion was version 10, 32bit. That's over 10 years old now I think.

Too bad, because we'd consider purchasing more licenses for V18 and would share its capabilities within my industry... IF the VST issue was ever fixed.

Yes it certainly does. I just don't know why they have not just got on top of it. I've used Vegas recently for some basic video editing, I miss the efficiency of it, Its still quicker to edit in Vegas than any other editor I have used. But without VST working, I can't use it as my daily editor. I can't imagine how many potential user they have lost because of it. I for 1 don't have the time to contact Vegas support, when I know Reaper works. It's just not as good a Vegas when it comes to editing dialog, which is 90% of my work.

Maybe 1 day they will fix it, I guess we can dream.

Magix has KNOW about this issue for YEARS, not days, weeks or months...YEARS. They have let this once great DAW become useless for doing Pro audio. Video editing is their focus PERIOD.

Yes, there are some on this forum that will swear they do Pro Audio on Vegas but I say BS. You can't do Pro audio on a program that won't work properly with VST plug ins on audio bus's and doesn't support VST3 or bridge 32bit VSTs. shall I go on? Yes I will, MIDI !!! BUT if you liked Vegas for audio production look to Reaper. It was modeled after Vegas and it works flawlessly unlike....

So, until Magix deals with the audio issues of Vegas....it's worthless to me and many others who would love to do Pro audio on Vegas again... but alas 😎

Michael-Schuberth, I can't agree with you more, very frustrating, after all these years.

I loved editing in Vegas, and still do, the other day I needed to put some dialogue to jpeg's, it was quick and easy in Vegas to put together, but had to process it in Reaper because of the VST issue.

Come on Magix, bring me back home.

G.

The other day,on a lark, I asked Magix 'support' about this issue and surprisingly got a reply.

"Hello
Thank you for your message.
​This is indeed a known issue which will be resolved in a future application update/version. Thank you for reporting this issue."

So reassuring, after all it's only been a decade that they've known about this issue. So how many more versions of Vegas will there be before this is finally resolved......? another decade?

Decade, lets not push our luck!!!!

The other day,on a lark, I asked Magix 'support' about this issue and surprisingly got a reply.

"Hello
Thank you for your message.
​This is indeed a known issue which will be resolved in a future application update/version. Thank you for reporting this issue."

So reassuring, after all it's only been a decade that they've known about this issue. So how many more versions of Vegas will there be before this is finally resolved......? another decade?

Well that's fascinating. I sent another message to them too but no reply yet. Just said to level with me once and for all on whether the bug will ever be fixed, and when if so. The reply you got is not very specific and could be just a default reply. I think I got a similar reply with one of the many occasions I've asked about the issue. If/when I get a reply about this, I'll give the news here as well.

The other issue I reported is the problem of allowing only one plug-in window to be open at a time. This is another handicap of Vegas, and I don't remember a time since version 3 that you could ever have more than one plug-in window open at once. This applies to all FX or media generator windows too, not just VST plug-ins. They acknowledged this issue and also said they'd look into it, so we'll see.

LanceMGY, I do wish you the best of luck with this. Yes, you're right, the reply seemed a standard reply to a VERY well known issue..

Who ever heads the Audio engineering wing of the Vegas development team should be ashamed as should Magix as a company. A decade to solve this audio issue...REALLY. ??????

Just so I don't come off as some sort of a complainer, I started with Vegas Audio 2.0...and look where we are today.....

Audio (the bastard step child) is nothing but an annoyance to 99% to 'picture folks and this includes the current developers who are obviously not interested in fixing it or making it more functional. </end rant>

We do admit that very little work has been done on the audio side of the VEGAS code for quite a long time. A lot of issues were introduced with the 64 bit version of the code, but some other bugs have festered for a long time as well.

We very much want to get back into developing the audio side of VEGAS again in the near future. It is embarrassing that some of these issues, whether performance glitches, workflow problems, or just plain modernization, have not been addressed. The audio engine is extremely complex and has some significant flaws in its design which hinder our ability to easily repair the problems. The biggest issue for us is that we simply do not have an engineer on staff right now that has skills needed to address the audio concerns in VEGAS. Our team is quite small for an application that is the size and complexity that VEGAS is, and the expertise of the engineers on staff is in vastly different areas than this.

At this point, since we have not been approved to acquire a new resource to help us with this, we are looking to target one of our current engineers to begin researching and organizing a game plan for addressing the audio concerns in VEGAS. Doing this will sadly mean that other parts of VEGAS will begin to be neglected, but the audio deficiencies are becoming too great to turn a blind eye to. I would like to say that you will see quick improvements in this area, but that is just not realistic. We are not ignoring this, we've heard the complaints and we very much want to address this.

@rraud: don't stop the rant!!! If you (we) do then they (Magix) can keep taking money for a product that is flawed and THEY KNOW IT. which borders on.......

Thank you VEGAS Derek for a reply, that was more than we've ever heard from 'Magix" on this subject.

So, let's wait Vegas 32 in 2056 before the audio update.
This is the first time someone from Vegas admit the problem.
Anyway, stop writing that this is a professional video editor if applying a simple reverb to audio is still a problem without solution!