Native Instruments Apple Silicon M1 Compatibility

Lol just bought Komplete at full price. Allready owning massive x and maschine, but hey. Thought it would be a good idear. Seems battery isnt compatible with cubase 12 in silicon mode. Lol and eh in rosetta its a dissaster. Hope Native solves this fast. Because paying 600 euros is crazy this doesnt work. Isnt informed good. Because Komplete says its compatible with vst3. But If you look at battery....Its not. Wow spend 600 euro's for half working software. Thanks Native!

I am not the guy you responded to, but I would really love to beta test Battery 4.

It's the only non native VST that I am using so I would really like to test it in full native projects.

@Jeremy_NI

I would like to beta test Battery 4. Also having problems installing. Keeps hanging on bite vst. Had permissons on read and enabled full disk access. No idea what the problem is. Have multiple software vst's installed. Like maschine and Massive X. Would like some help. Thanks.

I'll try tonight to make things work. If not i'll contact support. Thanks for the help.

I've got a question regarding the last Apple Silicon native version of Battery 4 (that was uploaded maybe 2h ago) : is it normal that when I launch the Audio Unit version of it, it triggers the AUHostingCompatibilityService process ?

It's like if the Audio unit version of Battery 4 is not Apple Silicon Native !

I tested, and it's not like that with Massive and Phasis (two recently updated plugins), so I guess it's not the policy of NI, and it must be a bug or just the first version of the update...

EDIT : I removed the faulty AU version of Battery4 and reinstalled the whole package. Everything is ok right now. The AU version of Battery 4 is now definitely Apple Silicon native, dated from 2023 and has the good version number. Strangely, the faulty AU was marked as version 4.3.0 but dated from 2017. PlugInfo was telling me it was AS native but it was not, and was telling me 2023 when the "get info" feature was telling me 2017 as creation date. I guess it was a glitch in the NI installation files, or a bug in my system. It's ok right now.

EDIT 2 : it seems to be a glitch in the NI installation files, because I'm not the only one to have the issue (I had some talk about it in a gearspace thread). Whatever you can read in the pluginfo app for exemple, the updated AU plugin IS NOT A.S. NATIVE. You definitely need to remove it before installing the update. Then it's ok... (for any strange reason)

I'm 100% with you on this.

Catalina was released in october 2019, and it's the last step for many old Macs (that still run perfectly fine). It's pure madness from Native Instruments, because their product only run officially on 3 Mac OS : Big Sur, Monterey and Ventura. And they even didn't port the entire range on Apple Silicon.

It's the only plugin brand I use with such a small window of operation : none of the other plugins I use droped Catalina, and 95% of them are Apple Silicon native since months (Reason, Sonimus and Kush being the last ones in my collection to be stuck in the Intel world).

I don't think it's the way to manage professional audio tools. Or maybe they are not intended to be professional... It's been months I started to avoid using NI products in my music (when possible, because sadly a lot of them, especially in Reaktor, sound truly unique), because I know it's only long time troubles. I've experienced these troubles in the past (when updating Reaktor and Kontakt), and the transition to Apple Silicon is the worst I experienced, so since months I try to use u-He or Arturia synths instead of NI ones.

When I open old sessions from maybe 3-4 years ago on my brand new Apple Silicon mac, the only plugins that make trouble are the NI ones : I lost hours in the past trying to replace Kontakt 5 instances by K6 ones, Reaktor 5 instances by R6 ones, and now I loose hours of my precious time replacing Intel Vst Reaktor 6 instances by AU Reaktor ones (because I need to work in an Apple Silicon native session and can't use Live eternally in Rosetta mode just because of NI products). Next step will be to switch to vst3 when vst2 will no longer be supported. I mean, what other dev waited so long to offer vst3 while immediatly droping vst2 at the same time ?

99% of my other plugins just offered me updates with no change in the name of the plugin and no absurd way of saving presets (check my complain in the Reaktor 6 beta thread).

Anyway, I hope this transition will end soon because it's truly a huge pain in the ass...