Tracking Apple Silicon Native Hosts, Plugins, Effects

[dix]

Orchestral Tools emailed today to say that their Sine Player is now M1 native.

"Apple M1 compatibility: SINEplayer is now natively supported on Apple's M1 architecture."

https://www.orchestraltools.com/store/get-sine

[eagle007]

oeksound soothe2 and spiff have both just been updated for M1 native!

Yes! Both Soothe2 and Melodyne on the same day!

[Gammon2004]

Yup, those two were the last irreplaceable plugins I'd been waiting on to make the transition. I've spent the past few hours in Studio One running in Native M1 mode and so far things are going quite well. Old mixes with Melodyne running ARA seem to be opening and playing just fine, as well.

oeksound soothe2 and spiff have both just been updated for M1 native!

Yes! Both Soothe2 and Melodyne on the same day!

[sQeetz]

And as you know Reason works well with Rosetta on M1 Mac computers.

Every time I read that a little bit of vomit tries to come out.

[machinesworking]

And as you know Reason works well with Rosetta on M1 Mac computers.

Every time I read that a little bit of vomit tries to come out.

Yeah tell me about it, I mostly use it as a plug in and AU doesn't do MIDI out in anything but Logic, so using all the great chord, arp, and sequencers with other plug ins is not happening unless you run DP11 or Live in Rosetta which I have little interest in doing.

[jamcat]

I mostly use it as a plug in and AU doesn't do MIDI out in anything but Logic

I have discovered this is not exactly true. AU plugins send raw MIDI out directly to the host in a way that works with Logic's inserts, but other DAWs can't easily access, because the MIDI stream lacks a container.

You can tap into that MIDI stream by creating a MIDI port for the plugin. I have done it in Studio One with the AU version of EZplayer.

Here's what I did:
I loaded EZplayer into my Instruments list, then I added a new Device in Preferences > External Devices. EZplayer was available to select under "Receive From." After that, I was able to select this new EZplayer MIDI Device as my MIDI input on an Instrument channel and send EZplayer's MIDI output to it. AU support is built into Rosetta2, so Intel-coded AU plugins will be recompiled and show up in native Studio One 5.

Disclaimer: this might not be possible on a lesser DAW.

[machinesworking]

I mostly use it as a plug in and AU doesn't do MIDI out in anything but Logic

I have discovered this is not exactly true. AU plugins send raw MIDI out directly to the host in a way that works with Logic's inserts, but other DAWs can't easily access, because the MIDI stream lacks a container.

You can tap into that MIDI stream by creating a MIDI port for the plugin. I have done it in Studio One with the AU version of EZplayer. What I did was I created a new MIDI Device, and EZplayer was available as one of the MIDI Input options. From there, I was able to select the MIDI Device I created as my MIDI input on an Instrument channel. AU support is built into Rosetta2, so Intel-coded AU plugins will show up in native Studio One 5.

You're not really arguing against what I'm saying here though, it's just that you're able to use Studio One this way, but it all seems to depend on how the DAW publishes MIDI ports? DP automatically publishes VSTi's that have MIDI out as possible input sources, so typically it just works with VSTi's anyway. There's two ways this can fail, the AUi plug in doesn't publish the MIDI out, or the DAW itself hasn't updated the AU spec to allow for plug ins to publish MIDI out.

It seems that the way Studio One engages this allows for AUi's to publish MIDI out if you "create" a port for it, I'll check out Live, it's possible Live can also get around this, but I would be curious if Reason Rack also was capable in Studio One? Oh, and pretty much every DAW can use AU plug ins in Rosetta while running native.

[jamcat]

Yeah, I don't know about Reason specifically, and I have no way to test it out. Just saying it is possible to work around AU's MIDI limitations. I updated my post above for more clarity on precisely how to do it in Studio One.

[machinesworking]

Yeah, I don't know about Reason specifically, and I have no way to test it out. Just saying it is possible to work around AU's MIDI limitations. I updated my post above for more clarity on precisely how to do it in Studio One.

Hmm, your new information points to EZ Player publishing itself as a MIDI port outside of Studio One, that's if the external device in Studio One works like it does in Live and other DAWs.

[Anonym32339]

Just downloaded Melodyne 5.2.0 and it’s native AU

You mean it runs via Rosetta… that’s not native at all…

98BC463D-D657-48FE-A35B-9ECA6EBC472A.jpeg

Edit: Strange is that it is mentioned in the change log of 5.2 but it should work Native then not only in AU.

833AE12F-CC0A-4401-A4C8-B79F4F136540.jpeg

Maybe we found a bug, will check that later in the Studio.

[rhye999]

It is running natively both in AU and vst3

[jamcat]

Any news on those Lindell Audio updates?

[sprnva]

SuperFlyDSP have released native builds of:

Stereo automatic Flying Wahwah (1.7a)
Flying Delay (0.9.9)
Flying Chorus (1.3a)
Stereo Flying Tremolo (1.4a)
Flying Phaser stereo (1.3a)

[Atlatnesiti]

It is running natively both in AU and vst3

Confirmed, that is correct.

[teilo]

Just downloaded Melodyne 5.2.0 and it’s native AU

You mean it runs via Rosetta… that’s not native at all…

This is not a Celemony issue. It's an Apple issue. ARA does not work on M1 with AU plugins because of the AU plugin hosting service. This is true of any DAW running native that uses Apple's AU hosting service, and it is true whether the plugin itself is native or Intel. When running Logic under Rosetta, the AU hosting service is not used. Therefore to use ARA, you must run Logic under Rosetta.

Celemony has a note about this: https://helpcenter.celemony.com/M5/doc/ ... ?env=logic