How do I know if a plugin is M1-compatible?

Tesgin · 07-03-2022, 10:57 AM

I'm trying to update my plugins for REAPER to be all M1-compatible. Loading REAPER as full ARM64, not Rosetta mode.

For some plugins that I load it's obvious that it's not compatible: an icon appears in the task bar that says "reaper_host_x86_64". If it's a VST3 I'll also get a message in the FX window warning me that a bridged plugin may be open. That is clear to me.

If I load a plugin and it doesn't say that, and I do not get the ugly blue and white "reaper_host_x86_64" icon, may I then assume that it is M1-compatible?

I ask 'cuz I have, for example, a plugin that loads in bridge mode for the VST3 version, but if I load it as AU I do not get the "reaper_host_x86_64" icon in the task bar, and I do not get the "bridged plugin may be open" message in the FX window. Looks like it'd be M1-compatible, but the manufacturer has communicated to me in private email that it is not. I'm so confused.

EpicSounds · 07-03-2022, 12:36 PM

you're close. With the AU version there is some other kind of bridging happening which makes it seem more like native M1, but these always end up crashing the project IME. AU plugins are bridged separate from reaper but you'll see the bridge in Activity Monitor as an Intel process.

Basically you'll know if the company has said its been updated for Apple Silicon / ARM64/ M1 in the past 18 months.

Stella645 · 07-03-2022, 12:37 PM

AU doesn't support Reaper bridging so a lack of bridging notification is not telling you anything.

You might try this:

https://www.thinkersnacks.com/as-pluginfo.html

Tesgin · 07-03-2022, 01:38 PM

I love the REAPER forums.

This is absolutely awesome. I would never have known that!

Loaded that Pluginfo app. PERFECT!

Do helpful. THANK YOU!

EpicSounds · 07-03-2022, 03:03 PM

that's a great little utility!

DThompson55 · 07-03-2022, 03:20 PM

Quote:

Originally Posted by EpicSounds

...the AU version there is some other kind of bridging happening which makes it seem more like native M1, but these always end up crashing the project ...

I've always used AU for no particular reason. But you're saying maybe stop doing that on the M1, correct? I have noticed some funky funky, but didn't realize it might be the AU doing whatever kind of bridging it's bridging. I'm between projects at the moment. Might be a good time to update my templates to not use intel based AUs wherever possible?

EpicSounds · 07-03-2022, 07:18 PM

Quote:

Originally Posted by DThompson55

I've always used AU for no particular reason. But you're saying maybe stop doing that on the M1, correct? I have noticed some funky funky, but didn't realize it might be the AU doing whatever kind of bridging it's bridging. I'm between projects at the moment. Might be a good time to update my templates to not use intel based AUs wherever possible?

I use VST3 when possible. Makes my projects compatible with Windows as well.