No M1 support's forced me use products from *other* music software makers

13»

Comments

  • Kubrak
    Kubrak Member Posts: 3,144 Expert

    I fully agree. Just one thing, notebooks with new AMD Ryzen do well. The only problem is that many manufactures of notebooks still prefer Intel, and if they make AMD notebook, they often put there inferior display (than on comparable Intel one) or too low amount of memory, too small SSD.... And so on....

    But things slowly change....

  • Kubrak
    Kubrak Member Posts: 3,144 Expert

    @Mutis

    Move code from iPad (ARM) to M1 (just a biger brother of that iPad's ARM) is something pretty different from moving code from x86....

  • Maciej Repetowski
    Maciej Repetowski Member Posts: 707 Guru
    edited June 2022

    Yeah, but NI didn’t do anything for mobile, except for iMaschine happy (and later abandoned) experiment, which was yet another strategic error, IMHO.

    So for them, whether it was A series or M series - the same exotic animal they’ve heard rumours about but never seen one in person 🤣🤣🤣

  • Kubrak
    Kubrak Member Posts: 3,144 Expert

    Apple supports developers, well? Developer Transition Kit (DTK), HW to test M1 code was available only five months (June 22, 2020) before M1 computers came (Nov 17, 2020). And it was not even M1, but iPad chip, and it had betaversion of macOS....

    And folks wonder, why transition to AS takes so long.... The thing is that Apple has not helped transition much...

  • Kubrak
    Kubrak Member Posts: 3,144 Expert
    edited June 2022

    I just say, that the support was not that great and if DTK came much sooner transition would be more seamless. Such a thing takes several years, so providing DTK, that even was not real M1 system and completed OS, five months ahead is not suffitient at all... It has helped transition, but if it came year sooner, things would be much better.

  • nightjar
    nightjar Member Posts: 1,325 Guru

    The timing of Apple's release of materials for AS compatibly is not a primary or secondary reason for NI's slowness.

    NI's own poor decisions caused their lack of competitive development speed.

  • Kubrak
    Kubrak Member Posts: 3,144 Expert

    Again, different companies face different technical problems. NI has its own antipiracy system, for example.

    To develop this one needs final version of OS and real CPU, not something like that.

    And NI is not so much delayed comparing to iZotope, for example... And iZotope does not have to deal with its own antipiracy, like NI....

  • fictional character
    fictional character Member Posts: 1 Member

    Hi NI,

    Any update on Maschine M1 support please? The UI is really bad and the performance is worse on my Mac Studio with M1 max than my old 10 year i5 iMac which I've just had to get rid of due to a degradation in performance. A rough idea on timescales would be really helpful as it will stop me obsessively checking almost every day and feeling disappointed :-) I know u guys are working hard to resolve and it's appreciated but be good to know if we can expect in the coming months or will it be later? Thanks

  • More Or Les
    More Or Les Member Posts: 3 Member

    HEADS-UP: NI just released this "Roadmap" of Traktor features... Too bad for us M1/M2 users that native support still isn't in the latest version, but at least they've said "it's on the way". Hopefully, it'll happen before the end of the year (only putting them a year behind other Audio software/hardware makers... #justsayin):

    https://community.native-instruments.com/discussion/5305/traktor-pro-3-feature-roadmap-q3

This discussion has been closed.
Back To Top