Status on m1/m2 update?

Two years is early adaption in case of total changing the CPU platform. MS has started with ARM on Win many years ago, five, eight.... And almost zerro market penetration... There is not sound reason for change. Disadvantages outweight the profits in most scenarios.

M1 is OK CPU, but not miracle. It is just marketing hype created by Apple. AMD may perform similar results if on the same node like AS CPU. Soon it will be possible to compare M2 and Zen4 CPUs....

To be honest this is an issue with most software companies. Most user gripes are usually met with silence. Most companies rarely tell you what they are working on.

I think also the larger the company, the more likely you will get the silent treatment. To be fair though in a large company, who should reply to posts, the programmers (who might not be socially adept, or might give out too much information), marketing (who might not be able to answer much of the technical questions), management (should their work be monitoring user forums).

I've seen some companies become more vocal and it still can pose problems when goals are not met.

My guess is too software programming is pretty complicated and is met with various successes and failures, and probably some of the stuff they are working on is probably pretty boring too at times because they are probably in the weeds alot. And M1 support is obviously a very technical matter. Reaktor is most likely using very old code base and even if they knew 3 months prior M1 support was coming out, they probably needed like 3 years. But yes there is a price of using old code base as it often can be harder to adapt to future technologies. I doubt in 1996 anyone knew Apple would come up with an M1 processor. Just like in 25 years from now, it would be almost impossible to try to guess what will be going on in the future CPU market.

The answer would be to try to stay current but that is a challenge with a company as diverse as NI. I think to Reaktor is such a popular program, if they tried to change it too much, it would most likely make many users upset as well, so they also have to make their changes with care (not breaking backwards compatibility, changing stuff in a way it will throw veteran users off too much).

NI isn't the only company though with issues porting to M1, Reason (another program with an old codebase) is probably having similar issues. Ableton (which seems to be further along compared to the other two as they have a beta version) has been in beta mode for awhile. Some companies will support these things faster than others and alot probably has to do with the Availability/resources of company, codebase, skill of programmer, documentation, luck.

After (silently) reading the past few pages of this thread, I strongly wonder what warrants the thread to remain open? Serious question because I feel like all we do is just spinning around in circles since... dunno... page 3?

What else does need to be said (apart from the usual blame games and "what could've been")?

Well, AMD proclaimed they are prepared to make ARM CPUs, if there is demand.... So, far there is demand mainly in server sector, as power consumption plays role and there is heaps of money there.... But it runs Linux, I guess, so no real transition cost....

There are Win ARM 2in1 PCs for years. I guess Surface X. Not much success, so far. Maybe one day. MS cannot make severe disruptions like inforce ARM. People and most of industry would stay on older Win versions.

It took many years effort to make people convert from Win7 to Win10. Most serious users have ignored W8 and W8.1. And now, 7 years after release of Win10, there are still 11% Win users on Win7, which is several years EOL (without support and security patches). And new Win11 (1 year old) has only 11%.

Win market is rather conservative and things that does Apple are not absolutely possible....

Maybe that ARM or similar CPU will penetrate to Winworld more than homeopatically one day. But there is not real reason for something like that to happen. Nobody is probably eager to rewrite/recompile milions of proprietary applications worth multitrilions USD.... And at least AMDs are not much more power hungry than ARMs. And now, when there is real competition with ARM platform, x86 will focus more on efficiency...

AS native and VST3 for most of NI SW is comming in 6-11 weeks. Hopefully also Reaktor....

Nice that the Traktor area provides so much more roadmap vs Komplete.

However, that graphic was a bit oddly constructed, with timeline flow "backwards" to my expectations.

Nice to see stem separation on the map... but shame that browser improvements are in the "last" column.

It's a nice idea, but I'm not sure if it's a realistic proposition.

It seems to me that for some years now, Reaktors development path has been mostly reactive (as opposed to proactive). Front panel patching looked a lot like a reaction to the big splash made by arrival and popularity of VCVRack. More recently of course, the thread topic of porting to AS... Any existing roadmap would have to be torn up and thrown out in the context of those events. And we all know how customers react when companies announce features and make promises, then scrap them - it's not pretty.

It makes sense that Reaktor is reactive at this point in it's life - it's very old/mature. The idea that NI have a small Reaktor team providing maintenance, that can slowly add features and make updates at times when there is less external pressure, and then switch to 100% firefighting when new OS versions are released, or a new hardware platform is dropped on them from a great height. That makes total sense to me. Just enough to keep it ticking over. So the product can continue to be financially viable. The downside is that big changes will take longer than they would for a younger product that still has a larger dev team with more resources, because it is being actively developed at a much faster pace.

If NI did give us a road map, it's quite possible that they would just end up dropping things from it or changing the time-line as much anticipated milestones approached.

Edit:If anybody wants to read these threads i am talking about on the old forums...2-3 developers chimed in to say interesting stuff here and there about the team,developement. That was 3 years ago though...

And maybe they didn't like the brouhaha very much and decided after that to never intervene again...hehe.

https://www.native-instruments.com/forum/threads/6-3-released.355009/page-7

And the second one...

https://www.native-instruments.com/forum/threads/why-and-why-not-yet-racks-user-blocks-etc.355161/