Thanks for your suggestion.. this fixed the issue with the plugins not showing up in ableton 10, on windows 10 ver 20h2 clean install.. peace & blessings enjoy the "wave"

 

Anyone try run DAW as Admin, before install tons of libraries ?

 

anyone having issues with ableton live 10? They load fine on FL Studio but they crash on Ableton, it has anything to do with the redistributables?

 

Softube plugins still not working after installing all mentioned redistributables (win 20h1)

 

Does this apply on all SOftube plugins for you?

 

yes on all none are working

 

Ableton crashes when scanning the Softube vst2 plugins, so i deleted those. Now it scans the VST3 nevertheless when i try to load them ableton crashes inmediatly showing this

 

Even tho the C++ download from above made some vst2 show up in ableton the GUI are messed up & vst3 still not being recognized, ??

Fixed issue with GUI by changing the settings on the gui to openGL Graphics & restarted DAW.

still no VST3 at present but geting there x

 

Last edited: Jan 4, 2021

Having issues in Pro Tools 12 as well. I got a mix template so I made a new one replacing the plugs by the softube. CLA-76 for FET Compressor, for instance.They all worked ok while the session was openned. When I tried to close it PT crashed. I tried in my real sessions too with the same issue when I closed.
I removed them all from the sessions and then PT is now working fine again. No crashes. So I removed them all from my computer too.
Got C++ installed by thw way.
In Repaer they dind't crash...same with Studio One. Just the AXX files didn't worked for me.
Same issue with others releases too...Stratum, Lexicon, UVI Spark and TiCO. The last two have been fixed already.
I know they will fix them all...We just need to wait.
Posting just to let them know.

 

Last edited: Jan 4, 2021

Not sure

 

Last edited: Jan 4, 2021

So you have the console for doing this?

 

I had the same problem one year ago with AudioUtopia releases. After searching in some forums, here's how I fixed:
- Open a clean session in your DAW
- Insert SoundToys Microshift in any track
- If the "A serious program..." window pops up, just click OK and ingore it
- Bypass Microshift (I mean, turn it off, not just bypass)
- Save session template
- Restart the DAW

This worked for me in legit Cubase Pro 10.0.6, I have Microshift off in the Control Room in all my sessions, and both AudioUtopia and new R2R releases work like a charm.

Hope it works for you...

 

How in the world could soundtoys microshift solve the issue of a plugin from a completely different vendor?

 

possibly due to those other vendors sharing similar/same protection coding.

 

well my friend, i just did that and solved the problem, this goes beyond comprehension haha

 

I have no idea, all I know is that if I quit Microshift from the Control Room, Cubase crashes with that window when I insert any plugin from Softube, Slate Digital, SoundToys, Empirical Labs, Relab, Waves... It's a fact.

 

I'm glad you solved! I know... I said "... WTF, why?" first time I did it hahaha

Saludos desde España, compadre!

 

sfill no luck seems as if vst3 are not responding at scan no luck in either reaper,fl studio, cubase 10 x 11 & ableton

 

Similar to what Rockefeller31395 described I have solved it with the following methods... this is a paste from a OneNote entry I made back then...:

The Softube release from AudioUTOPiA (and possibly other iLok plugins) has problems with Windows 10. The VST2 versions of the plugins crash hosts when scanning them (start) and the VST3 versions result in crash on song load.

To get the VST2 versions to work use jBridge with them!

For the VST3 versions do one of these:

• set the host to Windows 8 compatibility mode (& admin start)
  • terrible compromise. It slows down all DAWs in loading and performing
  • "Omnisphere 2.5 is completely unusable when win 8 compatibility mode is on"
• load a SoundToys plugin before it.

Full Walkthrough
1. For first scanning and validation you need to run in win 8 compatibility mode
2. Put a SoundToys Plugin on the first slot of the master bus*
3. You can now use every softube/relab/SSL duende plugin
4. Maybe create template
5. You can now disable compatibility mode

* For Ableton you need to put the SoundToys Plugin on the first slot of FIRST Track (not master track). Because Ableton starts to load plugins from first track and you need SoundToys Plugin to load before any other Softube and etc. plugs. Studio One starts to load master chain before every other stuff, that's why for Studio One you need SoundToys Plugin on the master (opening saved project). Cheers.

 

Last edited: Jan 4, 2021