All releases are fine here... Im on win10 x64 latest release... The problem are the daws themself... At first in Studio One got same error... Same in Ableton... But not in FL Studio... I fixed both with win8 compatibility mode... AudioUTOPiA are legends!!!!

 

For audio effects, VST3 is unloaded from RAM when unused/idle and free CPU resources. However, for some virtual instruments, often I prefer VST instead VST3, because VST3 protocol filters ALL MIDI "Program Change" & "Bank Select" messages, it's a Steinberg stupidity (IMO) - but it's another debate.

 

Last edited: Jan 16, 2016

Edit: vote was changed to... "Disagree"

Yes Daniel, and of course I'll try to explain the reason: AudioUTOPiA's nfo file (for Virtual Buss Compressors plugin) indicates clearly both VST2 and VST3 formats are available inside his distribution, as I've already said in other posts in this topic.

Of course, using actual AudioUTOPiA's installer doesn't install VST3 anymore (but VST2 instead), as I've already said here - again - so please read carefully published posts/replies first! it seems to be a "bug" in the AudioUTOPiA's VBC installer, and nothing else (I've sent a comment about this issue), despite the related installer have both VST2 x86/x64 and VST3 x86/x64 checkboxes (they're act as "package selectors", for custom installation). Also I precise this plugin is existing as both VST2 and VST3 specifications, exactly as indicated on the official Slate's website, it's not my imagination => http://www.slatedigital.com/products/virtual-buss-compressors/ (click "SYSTEM REQS" tab, near middle/bottom of page)... This is a simple issue in AudioUTOPiA's installer (this issue isn't related in their nfo), BTW noboby can't install REAL .vst3 files provided by AudioUTOPiA installer, unfortunately. Remaining unfixed for all of us at this day.

I'll hope my explanation is clear such crystal? and a "dislike" vote isn't a drama, IMHO (I've got some "Dislike" or "Disagree" on this topic too, but I don't make my cinema about them, I don't lose money or life because I've collected some of these). However, maybe a "Disagree" vote was more appropriate? (EDIT: it was changed to "Disagree"). I can assume you're a bit agressive by saying "what is your problem?". Be sure I don't have any problem, and really, I don't care, dude! Simply never forget this: here is a C.M. forum, and not a battlefield! Perhaps it's only a simple misunderstanding (language barrier?), it's always possible, aren't? I'm 52 years old French guy, not a kid.

@All of us want to rename .dll files to .vst3: the best way (until possible fixed "setup.exe" published by AudioUTOPiA) is to use Slate's Virtual Buss Compressors as VST2 plugin (VST 2.4 .dll), it works fine! I repeat: renaming ".dll" to ".vst3" files is a stupid idea (on your PC, rename "C:\Windows" folder to "C:\MacOS X" and you've got an Apple Macintosh computer instead, believe me!).

 

Last edited: Jan 16, 2016

you have not understood my irony !

 

One more for me, I win!
(I've voted "Creative", it's also my irony).

 

Last edited: Jan 25, 2016

I have tested this one with Win7 32/64 and Cubase 4! Working!

 

I suppose it works fine too on Windows 98 (OSR2 edition, it's important) + Cubase Score for Windows...
Okay don't worry floppy, it's another chained irony on this topic (probably a FX chain?).

How can you test on Win7 32/64? multiple PCs? mutliboot? virtual machines?

I'm not Cubase specialist, but I'm not sure Cubase 4 exists as 64-bit (perhaps I'm wrong, however)... btw, except if your post is a joke, plugins are running in x86 mode, even on x64 OS.

Also I'm sure Cubase 4 doesn't support VST3 plugins (but don't worry, ".vst3" VBC plugins aren't installed due to a bug inside AudioUTOPiA's installer, unfortunately, and never fixed too bad).

 

Last edited: Jan 25, 2016

My bad MEL!

Cubase4 is indeed 32bit, but you´re able to run it on a 64bit system! And vst3 isnt an option in Cubase4 - period!

I didn´t pay enough attention to the "vst3" part of the threads heading ...... just wanted to say it was posseble to run this plug in Win 32/64bit in Cubase4 - Thats all!

 

According to change extension on Vst2 to Vst3 files
I have noticed that it is only possible to do so on plugins that are already ported for Vst3
It cant be done on Vst2 plugins that dont have been ported for Vst3

Aslo as "MozartEstLa" mention he had CRC checked the Mixbus and it dont match i also CRC matched them and they did not match..

BUT i have CRC checked other plugin i changed from Vst2 to Vst3 with the "real" if we can call it so anymore? Vst3 "i.e "Aptrigga 3" and they matched.

I am no expert but i can believe that AudioUTOPIA guys could have made a mistake when they named the plugins i dont know how they do when they crack BUT since they have released plugins with cracked (patched) dll;s
It might be that they simply can have named the Vst wrong and that the VBC dll is really a Vst3 what is odd and speak against my thoughts is that it is NOT installed in the Vst3 folder isntead it is installed in the Vst 2 folder..

But who knows anyway?

What is clear though is that CRC matching renamed Vst2 to Vst3 with "real" Vst3 is not really proof..
If so how could some "real" Vst3 and renamed Vst2 to Vst3 match when i CRC matched them?
So is Aptrigga a real Vst3 or is it a false Vst3?