Determine if a plugin is VST or AU in a project

[stereodrive]

Hello,
I'm wondering if there's a way to determine whether a plugin is a VST or Audio Unit in the interface of Ableton Live. I'm experiencing an issue with SSL plugins, specifically the Channel Strip and G Comp, where Ableton crashes if I use both VST3 and AU versions in the same project. To identify which plugin is which, I'm examining existing projects but I find it hard to find out

[scg]

One way is to activate hot swapping for the plugin. This will open the corresponding plugin folder in the browser.

[stereodrive]

Oh this is clever! Thank you very much.

[Tommix]

I just had the same question. With swapping as mentioned below it would not lead to the corresponding folder.
Though another solution was now to open the project with pressing the option [alt] key when opening the project. Then you will find the plugins named als VST or AU. This is a quite secure way to find out which plugins won't work properly.

[cids]

https://sonicbloom.net/list-all-plug-ins/

https://www.youtube.com/watch?v=SzXVPvcyJMU

[Rivanni]

https://sonicbloom.net/list-all-plug-ins/

https://www.youtube.com/watch?v=SzXVPvcyJMU

I was surprised to learn that the device I created was featured in a video.

[Calagan]

https://sonicbloom.net/list-all-plug-ins/

https://www.youtube.com/watch?v=SzXVPvcyJMU

I was surprised to learn that the device I created was featured in a video.

By the way, your device is near perfect and can be very useful.
It could be amazing to make the distinction between vst3 and vst2 (it's a huge mess now with the end of vst2 support when trying to migrate old sessions), but I know it's not possible with the way you did code the device.
Anyway, thanks a lot. A very nice little helper...

[Rivanni]

https://sonicbloom.net/list-all-plug-ins/

https://www.youtube.com/watch?v=SzXVPvcyJMU

I was surprised to learn that the device I created was featured in a video.

By the way, your device is near perfect and can be very useful.
It could be amazing to make the distinction between vst3 and vst2 (it's a huge mess now with the end of vst2 support when trying to migrate old sessions), but I know it's not possible with the way you did code the device.
Anyway, thanks a lot. A very nice little helper...

Thank you. Good to hear it is useful.

You say, 'the way I did code the device.' Is there another way of coding that can distinguish between VST2 and VST3? I would be happy to adjust my device.

[Calagan]

I was surprised to learn that the device I created was featured in a video.

By the way, your device is near perfect and can be very useful.
It could be amazing to make the distinction between vst3 and vst2 (it's a huge mess now with the end of vst2 support when trying to migrate old sessions), but I know it's not possible with the way you did code the device.
Anyway, thanks a lot. A very nice little helper...

Thank you. Good to hear it is useful.

You say, 'the way I did code the device.' Is there another way of coding that can distinguish between VST2 and VST3? I would be happy to adjust my device.

I'm a complete noob regarding M4L coding (and coding in general) so I don't know about a way to distinguish VST2 and VST3.
I know plugview is able to distinguish those formats, but it works differently (it loads a complete Live set from any other Live set, it doesn't explore the Live set it is used in). https://maxforlive.com/library/device/5190/plugview
I bought plugview some months ago, but it's less interesting than your device : it doesn't tell you on what track are the devices, and at some point it doesn't work anymore when the Live set is too big... My main point in this kind of tool is to be able to find where are these bloody vst2 devices I need to replace with vst3 for future proof recall...

But obviously I can't help you in any way in the M4L coding.

[scg]

My main point in this kind of tool is to be able to find where are these bloody vst2 devices I need to replace with vst3 for future proof recall...

Have you tried turning off your VST2 folders in Settings/Preferences->Plug-Ins, and then reloading the project to see what Ableton reports as missing? It's not as convenient as Device Lister, but maybe it would meet your needs.

(And thanks, Rivanni, for creating Device Lister - it's very useful.)