nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can’t believe Native Access is still Old Code

25Kyz

I am running MacOs 27 beta 2 so I take responsibility for that. I haven’t ran Native Access so long but today I said let me see if there are any updates to my programs. Everything has been fine and no problems at all. Native Access says it has an update that will install after restart. I click restart. Now NA isn’t opening because the code is for intel hardware??? All programs are in demo mode. No amount of trouble shooting will allow that stupid NTK Daemon to install. Even right click and try to open in Rosetta 2 for some reason isn’t giving me the Open in Rosetta box. Come one Native people who are still there. Even Arturia code is working…

Find more posts tagged with

Native Access

Native Access 2

Maschine 2 SW

Comments

Vocalpoint

That OS is unsupported. Expect odd things to happen

And Rosetta is gone in MacOS 27

Ni will have to whip up some new installers but I wouldn’t expect them to support this OS until early 2027

Matthew_NI

We don't yet support macOS 27.

Native Access (at least for now) requires Rosetta only because it supports an enormous range of content installations, including some older legacy instruments that require Rosetta.

Such instruments will either have to be updated or retired, come the time.

25Kyz

@vocalpoint Rosetta isn’t gone in MacOS 27. It will be leaving but not yet. I can still open Logic in Rosetta.

Vocalpoint

https://community.native-instruments.com/discussion/comment/264403#Comment_264403

Apologies. My bad. It’s Intel that is dropped in OS 27.

Rosetta to go in OS 28

PoorFellow

https://community.native-instruments.com/discussion/51133/can-t-believe-native-access-is-still-old-code

I am running MacOs 27 beta 2 so I take responsibility for that.

From what I can see than N.I. haven't even officially started any compatibility testing for MacOS 27 :

Compatibility of Native Instruments Products on macOS

Come one Native people who are still there. Even Arturia code is working…

But while this is not meant as an invitation to a discussion on the topic here, then I actually agree with you on this. But as seen in context to what is already written here (ref. Matthew_NI) then I see the problem as being two fold. One is the N.A. tech used , another is the Rosetta requirement needed for other apps as mentioned by Matthew_NI.

So even if say NI one day (e.g. under new ownership) decided to change their DRM scheme/installer tech then that would not help as long as a lot other stuff require e.g. Rosetta. So IMO then in the end then the right place to complain is at Apple since they are those that more or less directly are creating the problems by changing third party program code requirements. N.I. is just another 'victim' of the changes in the computer industry. But since these changes are (IMO obviously) going too fast then Apple ought to stop spitting out a new OS/OS update breaking programs at a rate that seen from amount of trouble created for users in between would appear to be every other day or so.

25Kyz

Well, in case some other souls dare to brave MacOS 27 prior to official support I was able to get back up and running by downloading and install Native Access 1. Straightforward too. Which boggles my mind that the newest Access 2 (3.25.0) will not install.

Dubalab

NI has to do a lot of work. Let’s hope iNMusic puts the resources to make it happen.

It’s clear the old owners didn’t or almost, properly.

PoorFellow

https://community.native-instruments.com/discussion/comment/264417#Comment_264417

I was able to get back up and running by downloading and install Native Access 1

Really great that you got it working. General problem however is that if you are not using latest version of N.A. then often it will not show some products or will not install (or activate ?) some products.

Jeremy_NI

@25Kyz As mentioned already here, MacOS 27 is not supported yet. Rosetta is needed for a few older installers for older third party products. For NI products we migrated almost every product to new installer technology. The Native Access team is totally aware that Rosetta will be obsolete at some point and are preparing for that. No timeline yet.

Someone with a similar issue posted their solution on Reddit, maybe this can help: https://www.reddit.com/r/NativeInstruments/comments/1u4x3xl/native_access_issues_under_macos_27golden_gate/

25Kyz

@Jeremy_NI Thanks for that reddit link. That worked!! And it updated to 3.25.1…

Rick-C-137

when will Native Instruments finally ditch the Rosetta requirement to make use of Native Access?! Afaik the NTKDeamon is the culprit ..

Wish they would give a native installer for those of us that do not care about ever installing legacy products (what the NTKDeamon is supposedly for) and want to keep Rosetta off their system because they run a full Apple Silicon native system.

Vocalpoint

https://community.native-instruments.com/discussion/comment/265719#Comment_265719

This - really say it all - direct from NI - just two posts above yours:

25Kyz

Well just want to say it took hours of utilizing google gemini but i got the NA 3.2 up and running within Mac OS 27. 6 days later i opened it up to purchase SuperSaw. DANG IT!!! New Native Access update so i'm force to leave Native Access running in the background or start this process all over again.
Dear Native Instruments/In Music;
Give us a way to turn off this program's auto-updating.
This is frustrating.
Signed, User :(

PoorFellow

https://community.native-instruments.com/discussion/comment/266105#Comment_266105

Give us a way to turn off this program's auto-updating.

Ni consider it a security risk if we turn off N.A. auto-updating so N.I. do not allow forum discussions about how to turn off auto-updating.

Vocalpoint

https://community.native-instruments.com/discussion/comment/266105#Comment_266105

NA is not supported under MacOS 27. So any "work" or effort you put into it - is at your own risk.

And Auto-Update? Never going away - so that is a non-starter.

Quick links

Unanswered questions