Tracking Apple Silicon Native Hosts, Plugins, Effects

[Kongru]

I just checked with EastWest and they said their OPUS player is M1 Native.

“Opus is M1 Native and subsequently, HW Orchestra Opus edition is as well”

[createADAM8]

IK multimedia Facebook account just claimed that new Syntronik 2 and Sampletank 4 is M1 native in response to comments on the announcement but I can’t seem to find any indication of this on the official website

[teilo]

IK multimedia Facebook account just claimed that new Syntronik 2 and Sampletank 4 is M1 native in response to comments on the announcement but I can’t seem to find any indication of this on the official website

I just tested SampleTank 4.1.5 and Syntronik 2, and yep, both are now native.

[cadiz]

"Preparing to install a couple of DAWS (Reaper & Studio One) and a lot of plugins on an M1 mac. Can anyone share how they are managing native ARM silicon vs Rosetta universal binaries side-by-side. Seems like it could get messy.

In exchange for a remarkably more efficient CPU, seems worth it to be deliberate about this. My belief, and it stands to reason, is that a native DAW compiled for ARM with native ARM plugins will see the best processor performance. I read that running any one plugin in Rosetta mode during a session will mean that all plugins in that session will run performance degraded, at least as compared to running all native. It makes sense. Can anyone confirm all this?"


Reading this I'm not 100% sure that you understand the concept... it's how you start your DAW which decides wether you will use Rosetta (so enable Universal + Intel plugins) or not. When you start your DAW in native mode (default) you can only use native + universal plugins. Universal plugins will not slow down anything as only the ARM code in the plugin is executed...

[Atlatnesiti]

moog has released Animoog-Z iOS and macOS M1 native including free Vst wrapper.
https://www.moogmusic.com/news/introduc ... -ios-macos

[machinesworking]

"Preparing to install a couple of DAWS (Reaper & Studio One) and a lot of plugins on an M1 mac. Can anyone share how they are managing native ARM silicon vs Rosetta universal binaries side-by-side. Seems like it could get messy.

In exchange for a remarkably more efficient CPU, seems worth it to be deliberate about this. My belief, and it stands to reason, is that a native DAW compiled for ARM with native ARM plugins will see the best processor performance. I read that running any one plugin in Rosetta mode during a session will mean that all plugins in that session will run performance degraded, at least as compared to running all native. It makes sense. Can anyone confirm all this?"


Reading this I'm not 100% sure that you understand the concept... it's how you start your DAW which decides wether you will use Rosetta (so enable Universal + Intel plugins) or not. When you start your DAW in native mode (default) you can only use native + universal plugins. Universal plugins will not slow down anything as only the ARM code in the plugin is executed...

So it’s fairly straightforward, you can open up your DAW as Rosetta and all plug ins will open up in Rosetta mode, or you can open of your DAW as native (which is the default), and plug ins that have native versions (are Universal Binary), will open up as native, mostly in all formats with some exceptions. Plus AU plug ins that are not native will mostly open up in your native DAW in with Apples Rosetta AU conversion. This doesn’t work with VST 2 or 3, but both you’re DAWs also support AU so you’re good. There are a small amount of plug ins that do not open up in Rosetta AU.
It’s all pretty cool, I’m choosing to avoid mostly running Rosetta AU versions, but the ones I do run do just fine.

[J0nnyMac78]

Just to add to this, Softube plugins were glitchy as hell using the AU/Native DAW method, but they fixed this a few days ago in their latest update.

[cadiz]

Arturia Software Center is Universal since today... plug-ins not yet...


UPDATE: All the instruments from V Collection 8.2 are M1-native.

[parkerboi]

Arturia Software Center is Universal since today... plug-ins not yet...


UPDATE: All the instruments from V Collection 8.2 are M1-native.

Pigments is Native too

[pdxindy]

Any news about Vital going native?

[cadiz]

Any news about Vital going native?

Latest info here: https://forum.vital.audio/t/vital-on-m1-mac/659/12

[pdxindy]

Any news about Vital going native?

Latest info here: https://forum.vital.audio/t/vital-on-m1-mac/659/12

So no news from Tytel in the past 6 months... not very promising.

[telecharge]

Strange that Arturia says, "Analog Lab V will be updated at the same time as the V Collection for M1-compatibility," but there's no mention of it in the AL5 release notes.

https://www.arturia.com/faq/utilization ... processors

[sprnva]

MIDI Control Center updated here too but it's still Intel-only.

[Funkybot's Evil Twin]

I'd be surprised if many folks in this thread were using Reaper with the Control Surface Integrator (CSI) plugin, but if you are, someone compiled an M1 build for CSI. If you're a Reaper user unfamiliar with CSI, it lets you turn various controllers (MCU, MIDI, OSC surfaces) into an integrated singular control surface that you can customize however you'd like, use for plugins, etc. There's a small learning curve, but once you get up and running with it, it's incredible.

Link to the M1 dylib here (it goes in your Reaper\UserPlugins folder):
https://stash.reaper.fm/v/43340/reaper_ ... .dylib.zip

You'd still need to get the CSI folder from here:
https://stash.reaper.fm/v/42437/CSI%20v1_1.zip

CSI wiki here:
https://github.com/GeoffAWaddington/rea ... rator/wiki