I understand that situation but I don't think it exactly applies to my situation. The situation you're speaking of happened to me as well, in version 11.1 I think, Ableton was messing around with Apple M1 finalizations and somehow broke the ability to scan shortcut vst folders, under Custom Ableton folders. I had a few VSTs that I had installed in directories out of my home VST directory which I just made a shortcut to and placed in my home directory. Version 11.1 broke that ability. 11.1.1 fixed that, which was cool. Maybe this is what u are speaking of? Still, it wouldn't explain why in version 10 and such since I've been using TBPRo VST3 64 bit, everything worked fine. And of course, when I downgraded back to 11.1.1, all was good as well. Then I updated to 11.1.5 (Happy now @Alpha0ne? ), which is CRAZY fast at loading my long-ass processing chains, (Like seriously fast!) Everything was loading BUT TBPro shit. But all is good now, I found a good workaround. Ableton always has something.

 

System requirements
Minimum system requirements

• Windows 7 - 11 (x32/x64), OpenGL 2.1 GFX card
• Mac OS X 10.11 - 12.2 (Intel , Arm), Metal GFX card
• SSE2 capable CPU

Plugins are provided in the following formats:



Windows: VST2/VST3/AAX, 32/64 bit
The windows plugins need VC2019 redistributables installed. In case they are missing please download here.

Mac OS X: VST2/VST3/AU/AAX, 64 bit
Mac OS X universal binaries are provided for all plugin formats except AAX. AAX can run on M1 with Rosetta.

Please update your graphics driver to the latest version, otherwise graphics errors may occur in the GUI.

Tested with

• Cockos Reaper
• Steinberg Cubase/Nuendo/Wavelab/SpectraLayers
• FL Studio
• ProTools 12/20xx
• Reason (VST2)
• Studio One
• Ableton Live
• Logic Pro X
• Garageband
• Digital Performer
• Cakewalk/Bandlab
• Samplitude
• Adobe Audition
• Bitwig Studio
• Traktion
• nTrack Studio
• Audacity
• iZotope RX
• BlueCats VST Host
• Sadie
• Acoustica
• Goldwave
• Ardour
• Saw Studio
• Samplitude/Sequoia

 

Did u install under the C:\Program Files\Common Files\VST3 folder?

 

It automatically reinstalls:
C:\Program Files\Common Files\VST3\TBProAudio

Ableton recommends using these folders for VST plugin installation:

• C:\Program Files\VSTPlugins - 64-bit VST2 plug-ins.
• C:\Program Files\Common Files\VST3 - 64-bit VST3 plug-ins. (Live 10.1 and later).
• C:\Program Files (x86)\VSTPlugins - 32-bit plug-ins.

 

Ummm... okay?

 

Yes, there, it's the default location. I like to keep them at default location and just organize the folder inside the VST3 folder so it would appear nicely on Live's Browser.

 

organize inside the vst3 folder? you move the default installs in the "common files\vst3" around? and then live shows your maked-up folder structure?

 

Read my comment above ;)

 

Yes for the VST2 version and jbridged 32bit as well. I always pay attention to the installation process so the dll/vst3 files will be installed properly in a correctly named folder so all of them would appear beautifully on the list. If the installer didn't provide the custom location, I would manually move them and check if it's work. Some need registry edit (only minor) some need modification to their configuration files. 90% of them, you can just freely move them without doing anything. Just make sure to move them before running them for the first time. Up until today only 1 VST3 that I have outside the folder, it is Steinberg SpectraLayers. It's tricky because of the ARA integration and all so I just leave it there.