Status on m1/m2 update?

I think it's pretty old. Most other products that are still around and as old as Reaktor are true flagships that are significant to the income and potentially the survival of their developers. I don't think Reaktor really fits into that bracket.

I wish Reaktor was more actively enveloped, but I think it is something of a niche product owned by a company that is actively trying to dominate the mainstream of their market sector. There are lots of Reaktor 'users', but I would guess that many of them are really only Reaktor users as a consequence of being Komplete users, and are unlikely to have bought Reaktor as a stand alone product.

In that context, the languishing state of Reaktor makes complete sense, even though I don't like it. I'm happy that it still exists, and is still valued by NI.

I could be completely wrong about this. It's just my view as a result of the way development and maintenance has been over the years.

How much optimised native machine code do your business apps and game support stuff have to generate?

Yes, Apple used to produce slow junk notebooks. It is better now.

As a SW developer you should understand that there is rather big difference between bussiness aplication and highly optimized multithread SW that must do its job in time. Maybe even with parts of x86 assembly code...

And that it is not possible to test plugins well untill there are DAWs running in AS native mode. And not only one DAW. Plugins have to be tested and run well in all major DAWs...

And there is difference between CPU in development kit and M1. Running on platform and running well are two quite different things. And code that runs OK on M1, does not have to run OK on M1 Pro/Max/Ultra. And that there are some problems in M1 Ultra....

Simply, even in one family of Apple CPUs there are incompatibilities. Now M2 came, but M2 Pro/Max/Ultra/.... will be on different node. Generaly they will be quite different CPUs than M2...

That is real mess and madness...

Concerning laptops I was refering to Mindspan's statement that M1 laptops are way better than last generation. So, last generation was clearly junk....

Well, in x86 world code that runs on i3, will run without problems on i7 or AMD. It is not so with M1 and M1 Pro/Max/Ultra.

M2 and M2 Pro/Max are on different nodes and so being different CPUs. It may be OK, but there also may be differences and compatibility problems.

Not speaking about the fact M1 CPUs have security problem that cannot be patched/repaired as it is fully hardware thing....

My guess is that NI has AS compatibility and VST3 for few months, but waits for K14 release. Otherwise NI could release updated plugins one by one or in logical groups. But if they release all in one batch, many of them have to be completed long time ago...

And also, if K14 comes in several weeks, everything has to be completed so that physical media may be created and so on.... With delivery problems and so on, everything has to be finished for release on NI side.

Well, Traktor runs fine on M1 and has problems on M1 Pro/Max. And not only Traktor, also other programs of other companies.

M1 and M1 Pro/Max are different. Apple has changed something in M1 Pro/Max comparing M1 and so they are not fully compatible... And M1 Ultra has yet another anomalies as it is two CPUs soldered together.... It may seem to you they are the same type CPUs, but they are not and they have to be treated separately.... If one needs things are computed in time.

It is not one code fits all CPUs....

5-10 weeks to go. :-DDD

Traktor is not AS native. It is probably problem in Rosetta 2 or OS (memory management, thread management, ...).

Simply, what runs OK on M1, does not run on M1 Pro/Max. That is reality. NI has solved it somehow. But before that he hit some kind of incompatibilities....

I do not say, there is problem M1/M2, just that there might be problem between M2 and M2 Pro/Max.

And SW problems with M1 Pro/Max. Maybe it was/is due to OS problem, but still it is related to differences between M1 and M1 Pro/Max. And I have read about other programs having problems, but do not remember what programs. In case of Traktor user had to switch off multithreading and make Traktor run just in one thread.

When one needs do things in real time even subtle differences in behaviour of CPUs may matter....

But memory leak is compatibility problem. Sandboxing is compatibility problem.

Opera has/has problems. Do not know if was or was not native.

And if certain program works OK on M1 using Rosetta, but does not work OK on M1 Pro/Max/Ultra it is compatibility problem. Just changing CPU for higher model should not make things not working. (If that happened other direction - would work on higher model, but not on lower - it could be understandable....)

But OK, things will settle down in a year, two and things might work.... But I still doubt Apple will be able to keep pace with x86 and maintain price in acceptable margins. Apple's chips are big and so expensive to produce. Also four different chips (Ax/Mx/Mx Pro/Mx Max) make production and development costly. And it seems that Apple has some problems with "chiplet" concept - M1 Ultra (two glued M1 Maxs) performs worse than it should....

We will see in few years....

Rosetta is just band-aid. It’s a temporary measure until most/all apps are rewritten as native M1 code. What matters to Mac users, is if native apps work on all M1 and M2 processors and they do.

Apple has created the best binary translator so far, incomparably better than Microsoft’s x86 to ARM translator for Windows on ARM. But it is still just emulation which will not translate everything (for example AVX code) and in case of Reaktor, which compiles x86 code on the fly - it just cannot work.

Kubrak’s post implied that there is incompatibility between M1 processors when working with native apps, so I was relieved that it was just Rosetta problems. BECAUSE WHAT MATTERS ARE NATIVE M1 APPS, everything else is just temporary band-aid, as I said.