Thanks Mike, that's encouraging. But the Sonitus plug-ins are DirectX, not VST. I did add the folder where the Sonitus DLLs reside to Vegas' list of VST folders, but that didn't help. Maybe there's an option in SONAR to also install VST versions? I'll check.

--Ethan

I checked by starting to run SONAR 8's Install again, but I saw no option to install VST versions of the Sonitus plug-ins. :-(

Any other advice is greatly appreciated.

--Ethan

Hey Ethan !
Good to see you over here in Vegasville !

I've been having some troublesome stability issues with Vegas Pro 10e-64bit and my rather new i7, Windows 7/64bit, Nvidia GTX470 machine.

I've tried not using any 32 bit plugs, such as UAD2 Duo plugs, and have almost abandoned VST plug-ins altogether to try and nail down why "Vegas has stopped working" messages.....would be curious to here how you make out with the Sonar plugs and if you have any issues with Vegas.

Cheers Ethan.

As a 'stop-gap measure' for old 32-bit plugins Vegas 64 bit will automatically 'wrap' 32-bit [b]VST[/b} plugins to work in a 64-bit environment. But not DX, sadly.

Which is odd because SCS/SF were late to embrace VST, but seemingly early to reduce support for DX. Unless I got that wrong.

You need to push Sonar/Sonitus/Cakewalk to update their VST plugins to 64-bit. Or are Sonitus some Sonar-specific format ? Note the post by 'sdmoore' in this forum about how he had already updated his freely available plugins to 64-bit !

geoff

PS Great to see you here Ethan !

Thanks guys for the welcome. I've been a forum member here for many years, but I stopped posting in almost all forums earlier this summer to work on my upcoming book about audio:

Ethan's Audio Book

I assume the Sonitus plug-ins that come with SONAR are 64-bit since I installed the 64-bit version of SONAR. But here's something else that might give a clue: I just downloaded and installed the 64-bit version of Sonalksis FreeG, a freeware VST volume control plug-in. Vegas doesn't show that as available either. I added the folder where the DLL resides to Vegas' VST folders list, and I confirmed the DLL is present. But after having Vegas re-scan all the VST folders, this plug-in still doesn't show up. So that implies the fault is with Vegas?

--Ethan

Is your book as entertaining as your "Acoustic Treatment Exposed" video from a while back?

Ethan: > I added the folder where the DLL resides to Vegas' VST folders list, and I confirmed the DLL is present. But after having Vegas re-scan all the VST folders, this plug-in still doesn't show up. So that implies the fault is with Vegas?

Sometimes you can just copy the plugin's .dll from where it was installed into a folder that Vegas already uses ....

In general, you can't expect ALL VSTs to work in ALL applications.
There are many reasons for this: badly written is one (which is often the case with the free ones.... :-); incompatible host application is another but important reason, as the underlying paradigm of the application may not pass or provide necessary timing & other critical info etc. etc. E.g. the excellent and expensive Celemony Melodyne Editor VST Plugin wil never work in Vegas and other sample editors like Steinberg Wavelab, Sony Sound Forge, or Bias Peak. Some of the iZotopeRX2 modules will not work in SSL/Soundscape and many other hosts. I have a folder full of 'free' ones which are guaranteed to crash most hosts..... invariably they will work in just one host.
The VST specification is also open to a certain amount of 'interpretation' so not all developers stay strict with the guidelines, or even test their work much in a range of hosts.

... or well-written, but written to work with a soecific app and to not work with others.

See if they work in REAPER x64 .

geoff

Well to add to the evidence here . . . This with the Izotope Mastering Effects Bundle, that came with Sound Forge 9.

I'm trying to get the 32bit Izotope Mastering Effects Bundle to be revealed in 64bit VP10e. It shows ands works in 32bitVP10e nicely.

Here's the thing: When I open 64bitVP10e and go to the VST in Preferences and allow the VST to browse to the exact same position that allows 32bit VP10e to see these VST effects nothing changes and nothing is added to the 64bit - nothing.

So to recap: I've got Izotope Master Effects Bundle 32bit VSTs working in 32bitVegas; I've got the Izotope RX2 32bit VSTs working in both 64bit and 32bit VP - BUT I can't get 64bit VP10e to see the Izotope Mastering Effects Bundle.

Bizarre . . .

Grazie

That would be because the SF IZOs are not VST, but DX plugins, and V10x64 does not auto-wrap DX plugins as it does VSTs ;-(

geoff

Thanks Geoff for the good news..... ugh....

Grazie

The way around is to open and process in 32-bit Vegas (can install alongside Vegas64 -bit in a 64-bit OS).

If you must proceed in V64, once the mastering is done, render to a new audio track(s).

geoff

Sure Geoff, but why?

Grazie

If you for some reason NEED to use those plugins within Vegas !

geoff

Yes Geoff I most certainly realise this.

My question is that this situation is not acceptable and I WANT it to be different. I wish to have these DirectX plugs work DIRECTLY in 64bit VegasPro 10e. Telling me that that is the way it is, doesn't stop me wanting a solution? Having/needing to string together a workaround, and I thank you, isn't the issue here, why we have to have it this way in the first place is what I wish to change. Don't you see that?

Cheers

Grazie

Oh I see where you are coming from. Yes, I agree entirely !

I guess it is because they consider DX rather 'legacy' now, as VST is now very much the mainstream. In which case, release VST versions of the Izo Mastering plugs.

geoff

Good!

DX maybe is too legacy, I don't care, somebody should get over it.

And to follow on from there, as the Izotope Mastering Bundle is brilliant, we need to have Izo and SCS raise the bar to get them available in the NEW 64bit Century.

C'mon guys, sort it!

Grazie