1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Apple M1 Native Access Registration Trick

Dieses Thema im Forum "Computer Technology and Setup" wurde erstellt von scertic, 26. November 2020.

  1. scertic

    scertic New Member

    Beiträge:
    4
    Hi boys and girlz,

    Just wanted to share a solution I used to get away from the problem of "Your platform not being supported" with native access.

    Considering you moved to apple silicone / M1 from an old computer / time machine etc, facing the 'demo' mode of all applications, and inability to run Native Access, here's a workaround.

    Open Terminal:

    cd /Applications/Native Access.app/Contents/MacOS
    execute:
    arch -x86_64 -c ./Native\ Access

    NOTE:

    It will still complain after a while, but the registration will go through and software installed will not be in demo mode anymore.

    Note that this solution will work only if you migrated from an old computer / time capsule and similar - not sure about other scenarios facing the "Activation issue" and inability to run Native Access. Other scenarios are not tested.

    Hope it helps if moving existing products to M1.

    Stefan

    [​IMG]
     
    • Like Like x 2
    • Informative Informative x 1
  2. kokernutz

    kokernutz Active Member

    Beiträge:
    446
    Hmm, doesn't work for me. I used Migration Assistant when setting up my new MBA. Native Access launches and still says my computer is unsupported. Console output shows the app still queries NI's servers and lists all the products registered to my email.

    ➜ MacOS arch -x86_64 -c ./Native\ Access
    [20201126 7:08:18.993 D] 1057268 ========================= Starting Native Access =========================
    [20201126 7:08:18.993 D] 1057268 version: 1.13.1 (R134)
    [20201126 7:08:18.993 D] 1057268 using endpoint: "api.native-instruments.com" 443
    [20201126 7:08:19.024 W] 1057268 Result: 1, Is running in rosetta: true
     
  3. scertic

    scertic New Member

    Beiträge:
    4
    As noted, this is applicable to exit the demo mode only if you migrated from old computer, further:

    Quote:
    It will still complain after a while, but the registration will go through and software installed will not be in demo mode anymore.

    Also, did you go into the application itself with:

    cd /Applications/Native Access.app/Contents/MacOS ?
     
  4. kokernutz

    kokernutz Active Member

    Beiträge:
    446
    I used Migration Assistant and yes, I am in the right dir:

    ➜ MacOS pwd
    /Applications/Native Access.app/Contents/MacOS
    ➜ MacOS arch -x86_64 -c ./Native\ Access
    [20201126 7:20:15.060 D] 1067455 ========================= Starting Native Access =========================
    [20201126 7:20:15.060 D] 1067455 version: 1.13.1 (R134)
    [20201126 7:20:15.060 D] 1067455 using endpoint: "api.native-instruments.com" 443
    [20201126 7:20:15.090 W] 1067455 Result: 1, Is running in rosetta: true


    I'll keep playing around with this, thanks.
     
  5. scertic

    scertic New Member

    Beiträge:
    4
    Ok and when you run the app is it a demo or registered now? Given this is not a solution to run Native Access rather trick it into registering app that are otherwise in demo mode.
     
  6. kokernutz

    kokernutz Active Member

    Beiträge:
    446
    Still in demo.

    Screen Shot 2020-11-26 at 7.46.35 AM.png
     
  7. scertic

    scertic New Member

    Beiträge:
    4
    Strange, it's the actual moment when it drop a list of products when it performs registration, message should be like "Setting Owner for product XY" in console. I guess this is key is cached username / password. Maybe try to run it on old computer, login to native access and copy it. Not sure if this is going to work if it does not send authentication. Anyway play a bit and get back with results.

    Not touching mine after it enabled products, given it's possible something is changed server side. :)
     
    • Like Like x 1
  8. Rick Baumhauer

    Rick Baumhauer New Member

    Beiträge:
    5
    scertic This did work for me for both Komplete Kontrol and Kontakt, but not Maschine (got the same "Your hardware has changed" message as kokernutz). Thanks!
     
  9. mloupe

    mloupe New Member

    Beiträge:
    3
    I got it to work by copying the key in keychain access from my old computer. It's the com.native-instruments.Native Access API key.
     
    • Like Like x 1
  10. Rick Baumhauer

    Rick Baumhauer New Member

    Beiträge:
    5
    I assume it worked for me because I migrated my data from my Intel Mac mini to my M1 Mac mini, and that brought the keychain along.
     
  11. Paul Gottsch

    Paul Gottsch New Member

    Beiträge:
    5
    This worked like gang busters for me as well. I also migrated from an Intel machine and brought my Keychain over.

    Only issue I had was initially navigating Terminal to the correct .app content folder. The path in the OP didn't work for me. I eventually accomplished this by actually going into the Native Access.app, "Content", then "MacOS", then right/ctrl+clicking the folder, going to Services in the context menu, and selecting "New Terminal at Folder". Just in case anyone else has brain problems like me with Terminal lol.

    Game = Changed. THANK YOU FOR THIS
     
  12. Rick Baumhauer

    Rick Baumhauer New Member

    Beiträge:
    5
    Paul - glad you got it working. Not being able to run Kontakt or Komplete Kontrol for the first several days after my M1 mini arrived was quite limiting.

    That said, I want to be sure that you're aware that there is now a working Native Access beta for Apple Silicon, available from https://support.native-instruments.com/hc/en-us/articles/360014683497
     
    • Informative Informative x 2
  13. Paul Gottsch

    Paul Gottsch New Member

    Beiträge:
    5
    I actually did see that almost right after I discovered and implemented this workaround lol. I'm not 100% about the switching process though. Would I just uninstall the old NA, install the new, sign in and (re)authorize like normal?

    Edit: thank you for sharing that info!!
     
  14. Rick Baumhauer

    Rick Baumhauer New Member

    Beiträge:
    5
    Paul - download the file linked in that update and run the installer (or copy the app from the DMG - don't remember off the top of my head). It will replace the version of Native Access that won't start up on an M1 Mac. Once you sign in, if you migrated your data from another Mac, it will see your installed products; if you didn't migrate, it will let you download your registered products as normal.
     
    • Informative Informative x 1
  15. Paul Gottsch

    Paul Gottsch New Member

    Beiträge:
    5
    Fantastic, thank you Rick!!
     
  16. Icaras

    Icaras NI Product Owner

    Beiträge:
    80
    This is excellent news and thanks for sharing. However I migrated my Mac but it's showing all my products as uninstalled. I just tried installing one product and it simply replaced the same folder on my Mac. No biggie but looks like I'll still have to redownload everything.
     
  17. Paul Gottsch

    Paul Gottsch New Member

    Beiträge:
    5
    I had to go through and use “Relocate” in the NA app for almost all my previous installs, most worked but not all. Is that option available for you?
     
  18. Icaras

    Icaras NI Product Owner

    Beiträge:
    80
    Hmmm....I don't see that option in my NA. Where does it pop up?

    At least NI's servers are super fast. Downloaded Damage 2 in a matter of minutes!
     
  19. Paul Gottsch

    Paul Gottsch New Member

    Beiträge:
    5
    It popped up as an option along side "Reinstall" when first clicking on the yellow/orange "Repair" button on the right side of NA. I should have probably asked first if you had those yellow/orange "Repair" options next to various products in NA? It sounds like it's not giving you the Repair option and just "Install", is that right?

    Fast servers are a solid consolation at least! The libraries were the long installs for me. Hopefully those came over for you without incidence.
     
  20. Icaras

    Icaras NI Product Owner

    Beiträge:
    80
    Yea, didn't get the "repair" buttons for me. Weird. I'm just happy that the libraries are working again. Just waiting for Massive X now :)