I refer to McDSP FutzBox v6.1.0.8 for windows from AudioUTOPiA....wonderful plug indeed, but I'm not able to let it working under win10/64 and Studio One 4.5. Vst2/64 not relevated, Vst3/64 seen but freezing the daw......
Is anybody able to make it running under above conditions? Help appreciated......

 

I have same issues with Softube AudioUtopia release, I use Reason 11 and latest SO1 version, in Reason vst2 work normally, in SO1 vst2 are blacklisted, and vst3 freeze strangly the software music is working but nothing work, I need to go to the task manager to stop SO1.
So I think it's a related problem only with SO1 on Win10 system. The only way I find to get these plugins work, it's to use in metaplugin.

 

thanks for replaying...same exact issues....and in metaplugin (never used...) vst2/64 works...

 

Did you try running studio one in compatibility Mode for win 7/8 and/or run it with Administrator rights? If Not, try that and let us know if it works then. Of course you have to Reset your Blacklist.

Good luck

 

Thanks, I'll try compatibility, it's already running with Administrator rights.
About resetting S1 Blacklist it's always a problem (I still don't know exactly how to do in a proper way), vst2/64 it's not blacklisted, it simply doesn't appear even if the dll is inside the folder...not recognized

 

Last edited: Jun 18, 2020

Could you please tell me how to do?

 

i can run it in SO4 with jbridge using vst2 x86 version of the plugin, but buggy.. presets not working. i think i've tested it in SO3 x86 with same plugin version too, it can load but buggy too. no problem in reaper vst2/vst3. if really need, you can try slave reaper w/ SO4 and load futzbox from there..

ps: futzbox is one of many reason i slowly shifted to reaper from SO4.. essential plugin yes.

 

unbelievable.... working in a daw and not in another......

 

The problem is that I dont use studio one that much and i have no Access to my System at the Moment, so I cant take a look for you but

Open your studio one preferences and go to the locations Icon, then the vst plugins tab.

CHeck the scan at startup Box.

Click Reset Blacklist and Restart studio one.

If that still doesnt work for you, you could try to delete the x64 folder in

C:\Users<username>\AppData\Roaming\PreSonus\Studio One 4

And dont forget to Set up the compatibility Mode as I Said before.
As @Citrik Acid said it could be related to w10, so this could be the Trick cause this also works for other plugin bundles like soundtoys and softube if I recall correctly

 

Thanks, I think this is the best way

 

Compatibility mode + admin running: not recognized (vst2/64)
DDF metaplugin: not recognized after its plugs scan (always vst2/64), so, not possible to load it (I don't know how CytriK Acid
could do so)

Ok, ok, now I'll give up

 

Last edited: Jun 18, 2020

try to copy all the plugin DLL to new folder in different locations
then start the daw and point the new locations of the plugin , then rescan it and try it if it work !

 

Thanks for he advice, tried, nothing to do, it doesn't wont to cooperate....there must be something in conflict with win 10.
Let's hope that some skilled guy will be able to have the magic touch

 

FIX TO AUDIOUTOPIA MCDSP and SOFTUBE PLUGINS IN STUDIO ONE 4.5 UNDER WIN 10

@Pereira Here is the fix. Install Soundtoys BY AUDIOUTOPIA . Then, whenever you want to use McDSP in Studdio One with Windows 10 all you need to do is insert one Soundtoy plugin on any unused channel BEFORE opening MCDSP. Voila! There are other things you can do but they will affect the way that S1 works.

 

Last edited: Jun 18, 2020

The fix to your OFF TOPIC problem is the same one as it is for @Pereira

 

Download on sister site DDMF metaplugin, and use it as a vst2/3 wrapper, open it on SO1, and in metaplugin open plugins you want, both x32 and x64 plugins as vst2 & vst3

 

I can't because I use legit Soundtoys plugins, but I will try now with legit, thanks for the help man

 

Don't work with legit so I will continue to use as I used before

 

Thanks for the suggestion, but the problem is that S1 doesn't see the VST2/64 dll (so I can't upload anything) and vst3 makes it unstable...

 

More or less the same here, metaplugin sees Vst2/64 (after a replacing into a separate folder and a newscan), but doesn't load it (error.....)