Plugin-alliance VST plugins not visible from DAWs on Windows 10 machine

[Virgiauskas]

I noticed a more particular issue with PA plugins - I use Windows machine as my main one, but installed same plugins to my Mac laptop, and when I open Ableton projects with VST3 plugins added, on the Mac they are not recognised and shows as missing. If I replace them on the Mac with same PA plugins, then Windows doesn't recognise them.
First time I noticed such behaviour, re-install of plugins on Mac didn't help.

[mcbpete]

Unless I'm completely misreading your post - PC VSTs and Mac VSTs (as in the .vst3 file) are not cross-compatible, as are compiled libraries for the respective device/cpu. You can't just copy a windows .vst3 file to a mac and it work on that device - you'd need a vst3 that has been compiled for the target architecture

EDIT: I think I am misreading your post - You're talking about a DAW project made on a Mac/Windows loading into the other device claiming the plugins are missing even though they're installed on both devices right ?

[deegonbeats]

Lots of PA plugins aren't working. Tested in Reaper too, they do not show up.

I’m having this exact problem here. Have u solved it?

[Averia]

PA bx_oberhousen only works correctly using roland gokeys 5 or minilab with Reaper or Studio One. If I use Keystage it only works with Ableton and it did right away with no additional configuration. Native Instruments is also hit and miss with Studio One but not with Reaper and Ableton. Some combos only work with certain sound output configurations (driver, BT vs direct connect monitors) - Studio One 7 hangs with Mic output to Monitors but other DAWs do not. Lot of software incompatibility across the board with Ableton the only one I haven't had any issues with. Just started out with recording and once I have a stable reliable product think I will just settle on that - so far it is Ableton as the DAW as it works flawlessly with all my hardware and software.