Status on m1/m2 update?

Subscription service cost is not tiered by the device a user may choose to utilize within the service. There can be tiers for users of different budget levels, but the cost basis is level of content/services.

As an example, video streaming services charge the same whether you access their content with a desktop or a smart phone.

And it's perhaps the most pivotal period in NI's history... the acquisition into Soundwide has blurred the whole vision of where things may head. I had more confidence when it was just iZotope and NI. A recent exodus of iZotope brainy people has me thinking it's all gonna be just a race to the bottom with Plugin Alliance.

A leader needs to articulate a fairly detailed vision for Soundwide and all its elements pronto.

Please go and re-read the thread!

For reasons already explained 'in reality nearly everyone' has a product that is much easier to port to Apple Silicon than Reaktor, so Reaktor will take longer to port. If you don't like that take it up with Apple, don't blame NI because they have unique and amazing products. Instead celebrate them, and hassle Apple for making NIs life difficult, and for creating a situation that slows down development in other areas that would benefit all users, not just Apple users!

I guess VST3 and AS native is already ready. Maybe for months. Just NI has decided to release it in Komplete 14 and not sooner.

My bet is that delay does not have technological roots, but economical. AS transition is costly. Developers must reduce costs (VST, AS and K14 in single release).... And maybe somehow motivate users to buy K14 ASAP, e.g. for full upgrade price. My guess is there will be major releases of some products and the older versions will not get AS and maybe even VST3....

Reaktor might be different story. It may take longer....

We will see, hopefully, more in 5-10 weeks....

NI has huge technical debt because NI has some very old products with very old codebases. It comes with the territory. That means they have some old products that can only be profitable with small maintenance teams, but at the same time changes take more work and cost more resources... the result is updates are infrequent, and it takes much longer to react to things like AS. It's just the nature of a 'mature' product like Reaktor.

I guess over the years, they could have spent more money on Reaktor to keep the codebase in better order, but then that would have been more expensive and might have resulted in Reaktor being cancelled many years ago due to unprofitability.

Sadly, transitioning to a completely new platform forced upon the industry by Apple probably means that stuff like HiDPI and VST3 will take even longer... unless they decided to incorporate those and other changes at the same time in the context of a large re-write... I seriously doubt it, but fingers crossed!

If what I've said here makes me anti Apple, then what you've said must make you anti Native Instruments, at least I'm on the right forum ;)

I don't think NI have made any excuses. Just their usual response - they want to do it, and hopefully will do at some point in the future, but no promises.

NI have problems with a very old codebase on a very old application. I haven't 'omitted' this. It doesn't change the facts of this debate. You are just trying to steer the discussion away from the relevant facts towards a different argument that nobody disagrees with.

You seem to be implying that I am blaming all problems with NI and Reaktor on Apple, which is patently ridiculous. please stick to the discussion we are actually having :)

Point is that Apple have introduced a new hardware platform, and NI for various legitimate reasons are taking longer to port Reaktor than some of their competitors have taken to port their quite different applications.

I don't really blame anyone for this. I don't think that's a sensible way to look at it. I've already stated that I think a move to ARM is probably a good thing, and that Apple are one of the few companies big enough to make it stick.

The problem here is that there are folk who do clearly need someone to blame, they believe they are entitled to the thing they want, right now, and if that's not happening, someone needs to be blamed, and they have decided that NI are guilty in some way. I'm saying to them that _they_ should go blame Apple.

If this makes me an Apple hater - so be it ;)

There's yet another straw man

There should be no 'blame' here. It's the Apple users that are demanding to blame someone (If they must, then they they should blame Apple). I'm sure, given the circumstances, that the AS native port of Reaktor will arrive in a timely fashion. They will get it out as soon as possible. Everything else is on hold Reaktor wise, AS is the number one priority. It will be as timely possible.

The facts:

*Apple have introduced a new hardware Platform

*NI have an old product with a large and ancient code base. It is also particularly difficult to port, due to being compiler based

*NI are throwing all their Reaktor resources at getting it done ASAP

*it will be ready as soon as possible

*this is not good enough for some Apple users

Apple users are 'calling out' NI, being negative on the NI forum, and generally being unwilling to accept that this is an (hopefully short term) Apple problem. It's also an NI problem, but not one of their own making (they had enough of those already).

Apple users need to accept that Apple's decision to change the hardware means that some applications will take longer to be ported. This is an inevitable consequence of a new hardware platform... it's not about 'blame' it's just the way it is. It was a decision by Apple, their roadmap is the 'reason' for the problem, without their decision, there would be no problem. Now it's time for their users to be patient, and thankful that NI and other third parties are choosing to support the new platform.

The problem might (we can't know) have been lessened if NI had a more modern codebase, younger applications, and less interesting technologies, but that's hardly a reason to start blaming them for something that they had no control over.

It doesn't matter how you try and frame this or what narrative you try and spin around it, all of this is a direct consequence of Apple introducing a new hardware platform. If *you* must apportion blame *you* cannot legitimately absolve Apple.