Native Instruments Apple Silicon M1 Compatibility

1121315171828

Comments

  • Damn
    Damn Member Posts: 10 Member

    🤣🤣🤣

    if you mean "anti reverse engineering" don't say antidebugging or other fantasy words!

    I'm writing code for over 25 years and never heard of that - all my collegues had to lough this morning!

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

    Desktop market (towers) is mostly gaming and graphics workstations now. Nvidia GeForce RTX 3090 needs about 400W alone. Same with hi end AMD cards in workstations and gaming computers. This is just not sustainable in the long term.

    To Kubrak: I agree with all your other points in general, though. Also about AMD processors.

  • Kubrak
    Kubrak Member Posts: 3,145 Expert

    "anti reverse engineering" is just broader expression for "antidebugging", at least in my language. It is shorter. We also use debugging in the meaning reverse engineer using low level debugger....

    So, now you know, what I meant... Protection against piracy and anti reverse engineering code probably has to be rewritten for M1.... And it diffentiates NI from others.

    I am writting code for 40+ years, if that matters.

    @Maciej Repetowski

    Yes, graphic cards world is crazy.... I do not need them, it passes me... But iGPU of AMD Zen4 APU will equal to low end discrete GPUs. And in Zen5, it will be yet considerably stronger. Majority of folks will not need discrete GPU even for decent quality gaming...

    I agree that 800-1000 W PC setups are just crazy.

  • Kubrak
    Kubrak Member Posts: 3,145 Expert

    Even secondary market may have priority at given time. If it were primary market, M1 native compatibility would be ready months before M1 release. ;-)

  • Calagan
    Calagan Member Posts: 189 Advisor

    It's strange : it seems that Apple is not a secondary market for 90% of plugins devs (that already released Apple Silicon versions of their plugins)...

    I think it's not honest to find technical or strategic justifications to NI. They just didn't care about updating their products since years. You can't say for exemple that VST3 users are a secondary market.

  • Maciej Repetowski
    Maciej Repetowski Member Posts: 707 Guru

    VST 2 still worked so why bother - I guess that was NI’s strategy for last 16 years 🤣

    When Steinberg finally lost patience and pulled the plug from VST2 - the horror was palpable…

    I had lots of fun reading developers cries on KVR, some just couldn’t even compile VST3 plugins. It’s not that they didn’t want to, they didn’t know how to make it work AFTER 16 YEARS.

    Unbelievable 🤪

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

    Why unbelievable? They did nothing during those 16 years. Maybe they even tried from time to time, and it did not work. So, why to bother, if everything has worked fine in VST2? Why to risk that things will go wrong, why to spend money on something 98% of users do require? Just to please Steinberg?

    And they would have to support VST2 and VST3 for many years. It is reasonable and economical to switch as late as possible, not as fast as possible.

  • Kubrak
    Kubrak Member Posts: 3,145 Expert

    @Calagan

    They just didn't care about updating their products since years.

    Why should they? Products have worked and they still work on target CPU. NI made bugfixes, improvements and maintenance that was implied mainly by neverending changes in MacOS...

  • mezzurias
    mezzurias Member Posts: 27 Helper
    edited June 2022

    Because that's how companies get left behind. How many companies are no longer here because they could't keep up with the times. It's not rocket science, customers are fickle and if they find something new and convenient they will move, there is no loyalty. It's up to the company/developer/provider to move where the customers are going. This is like business 101.

    By not providing what the customers want, when they want it they leave room for more nimble competitors to come and eat their lunch. That's why a lot of large software (like Adobe) companies are moving to subscription models, less chance customers will move elsewhere if they have to keep paying rent just open their projects.

  • Kubrak
    Kubrak Member Posts: 3,145 Expert

    Most of companies did not hurry with VST3. The demand from users has started quite recently... And NI has most plugins VST3 already.... Not being AS and COVID, it would be probably sooner....

    I guess it is easier to move to another product, if one uses subscription. No financial investment is needed to switch to another product.

  • Filip Hoško
    Filip Hoško Member Posts: 8 Member

    I'm a programmer but also a co-owner of a software company and I usually do a lot of management/planning. From my point of view relying on something to be working while the technology is moving on is incredibly short-sighted. I'm totally aware of the fact that you have to plan your resources (people-power) wisely since you'll spend time and money. But if you look across the landscape you see that NI is sticking out in this "problem area" (M1 compatibility) like a sore thumb. There are other major companies who already have native M1 compatibility for all or substantial amount of their products for quite some time. Apple provided M1 development machines from summer 2020 if I'm not mistaken. That will be almost 2 years now. The company I co-own has only <10 developers but the (very small) teams built several applications during those 2 years from the ground up - this also encompasses business analysis, analysis of technical requirements, UI design, testing and deployment apart from the actual coding. These were web and mobile apps but the projects were non-trivial. I can't believe that company such as NI couldn't do better as it did with this. I don't see behind the curtain and I don't want to be judgemental (there's really no point in doing that) but to me it seems like a poor management decision or they really underestimated this. Now they're being roasted by musicians who work on Macs and want to upgrade (or already did) and use a lot of NI stuff. They look incompetent and I bet that's something they're not very much proud of and it wasn't part of their marketing plan (at least I hope so). It's pretty sad to read the comments here and I hope NI will be able to deliver the updated apps soon without burning out the developers.

  • mezzurias
    mezzurias Member Posts: 27 Helper

    The demand didn't just happen recently as you put it. Ableton of all companies was one of the last of the major DAWs to support VST3, but once that was in users started to expect it to be there. So it's been at least 4 years at this point. The only other major DAW that doesn't have VST3 support is Reason and their financial situation was in such dire straits that they needed a new CEO to come shake things up. Like NI they rested on their laurels and basically invited customers to look elsewhere.

  • nightjar
    nightjar Member Posts: 1,325 Guru

    Soundwide partners Plugin Alliance & Brainworx certainly love their Macs.

    Brand new MEGA Sampler (just released today with content from NI) is currently Mac-only.

  • Calagan
    Calagan Member Posts: 189 Advisor

    This is an insane comment. To be dedicated to what you do means spending your time creating new products and improving the old ones. To be honest means fixing what's broken in your products.

    The heaviest stuff on CPU I use are from NI, just because they don't care about optimization and long term maintenance. I can't remember how much issues and troubles I had because of bugs with Reaktor, Kontakt or other NI plugins (on my old laptop and right now on my new one). For exemple, I just discovered recently that my brand new Guitar Rig 6 doesn't report its latency to the DAW, so you can't use it in parallel or record with it (after I found it, I did read mention of the issue dated almost from its release, so it's not new and it's still not fixed - it will probably never be fixed). They never improved the GUI of Reaktor and Kontakt in years, despite the massive amount of legit critics. Battery 4 is universally considered as a downgrade from Battery 3. I'm not using Drumlab anymore because of a crashing bug and CPU usage feedback loop that is there since at least 6 years (when I first bought it - I was using Maverick I think at this time) and this issue was never fixed. Form is amazing but is ultra CPU intensive (even compared to the granular engine of Pigments for exemple), doesn't sleep when not used (like 99% of any other vsti I use, and no it's not a problem to implement CPU pause with VST2), it has also issues with using own samples... And so on, and so on, etc. etc. All these issues were there since the first time I used their plugins, so it has nothing to do with OS changes : they just don't fix broken things, and don't improve their products.

    When u-He released Diva it was a cpu hog (but had no bugs), and almost each year they brought various improvements, to the point of today where after a lot of regular updates it's a wonderful piece of code (stable and as CPU efficient as it can). Same with Valhalla, Tokyo Dawn Labs or many other great and respected devs : when you buy from them, you know they will constantly improve their products and add new stuff.

    I love most NI synths and plugins : I don't criticize the sound quality of these tools and they seem to have very creative synth designers (this is the main reason I still buy them stuff). But the maintenance is awful, and it's a shame in terms of business. To me, this is just disrespect for the customers. There's no rationality or justification, this is just "thanks for the money, now good bye"...

  • Dan
    Dan Member Posts: 3 Member
    edited June 2022

    Windows has lots of users in the corporate market, but not so much in the music industry. There are many people who use Windows for music, it's true, and I think it's important to support them. But, how many music professionals do you know, and how many of those use Macs? For me, the answers are (1) many, and (2) every single one of them.

This discussion has been closed.
Back To Top