Apple announces new Mac Mini, Air + 13" MBP featuring their own M1 chip.

[UltraJv]

This review is quite good the battery life isnt anywhere near predicted though

"My actual results? I’m getting between eight and 10 hours of real, sustained work depending on how hard I am pushing it. That’s not quite 50 percent better than the last MacBook Air, but it’s very close."

https://www.theverge.com/21569603/apple ... rm-silicon

[whyterabbyt]

Yeah, but what do you call "older"? I mean, I'd love to see Form traslated. I guess it's from 2016.

Form runs inside Reaktor. And since Reaktor is their flagship synth, I imagine getting it working has a higher-than-average priority.

[Sinisterbr]

Just found this

https://support.native-instruments.com/ ... b1k4_ir6ok

[Sinisterbr]

Yeah, but what do you call "older"? I mean, I'd love to see Form traslated. I guess it's from 2016.

Form runs inside Reaktor. And since Reaktor is their flagship synth, I imagine getting it working has a higher-than-average priority.

Right, but I'm not a programmer. If Reaktor itself runs flawlessly on M1, does it automatically mean any emsemble will?

[Ploki]

Tal too are on board.

rsp

You know... it seems much less of an issue than I initially though. Most devs seem to be on a good way.

I upgraded my laptop today (to big sur) and big sur is non-issue. pretty much everything works.

but not M1, intel.

didn't audiothing or someone say Arm port is a matter of build flags, if you use up to date frameworks?

[whyterabbyt]

Yeah, but what do you call "older"? I mean, I'd love to see Form traslated. I guess it's from 2016.

Form runs inside Reaktor. And since Reaktor is their flagship synth, I imagine getting it working has a higher-than-average priority.

Right, but I'm not a programmer. If Reaktor itself runs flawlessly on M1, does it automatically mean any emsemble will?

Basically yes, if Reaktor is 100% implemented as well as running flawlessly(*). The ensemble is a recipe for Reaktor to do things, but it doesnt do them, Reaktor does.

(* Technically, it could be running flawlessly, but not implement absolutely everything that the x86/x64 version has. I'd assume NI would make it feature-identical, though)

[Sinisterbr]

Yeah, but what do you call "older"? I mean, I'd love to see Form traslated. I guess it's from 2016.

Form runs inside Reaktor. And since Reaktor is their flagship synth, I imagine getting it working has a higher-than-average priority.

Right, but I'm not a programmer. If Reaktor itself runs flawlessly on M1, does it automatically mean any emsemble will?

Basically yes, if Reaktor is 100% implemented as well as running flawlessly(*). The ensemble is a recipe for Reaktor to do things, but it doesnt do them, Reaktor does.

(* Technically, it could be running flawlessly, but not implement absolutely everything that the x86/x64 version has. I'd assume NI would make it feature-identical, though)

Nice, thank you. And great news for NI, I suppose, very practical. They only have to translate Reaktor, and not worry about every single ensemble already made for it.

[whyterabbyt]

Nice, thank you. And great news for NI, I suppose, very practical. They only have to translate Reaktor, and not worry about every single ensemble already made for it.

Indeed.

[spacepluk]

I'm a bit worried about older Native Instruments' stuff, especially Massive.

Yeah, but what do you call "older"? I mean, I'd love to see Form traslated. I guess it's from 2016.

Stuff that is old enough to have a lot of cpu-specific optimizations will be harder to port... I'm crossing my fingers it's not a lot... but Maschine+ being intel-based hints otherwise... all speculation of course.

[Sascha Franck]

I'm a bit worried about older Native Instruments' stuff, especially Massive.

So far my understanding is that anything you manage to run under Big Sur will at least sort of run on on an ARM machine. Whether you'll be able to freshly install it might however become an issue (which started with Catalina due to traces of 32bit in the installers or a failed notarization).
Of course, many things will ever only run in Rosetta 2 mode - which might not only cause a (possibly acceptable) CPU hit but might as well be completely abandoned once Apple declares the transistion period to be over. But I expect this to take at least another 2-3 years.

[audiothing]

didn't audiothing or someone say Arm port is a matter of build flags, if you use up to date frameworks?

Not us. We ordered an M1 MacBook Pro, but it looks like it's coming next month (they must be pretty busy). I'm going to test Big Sur on Intel really soon anyway.

From my own tests, I managed to compile some of my plugins for iOS. I had to switch my FFT routines over to vDSP (and now they are actually faster!). It took me just one afternoon of work. I couldn't really test them properly as the plugins are not meant to be used with iOS/iPads. But, anyway, since Xcode didn't complain, I guess I'm not going to see major issues. Plus, we use JUCE, so I'm counting on the JUCE team as well.

Now, compiling is one thing, heavily testing and updating 24+ plugins on a new system (and new versions of DAWs) is definitely going to take some time, but that's going to be our top priority.

[Ploki]

Thank you for chiming in!
I was weighting whether to get Wires or Echocat, but i guess it's gonna be both (not exclusively for your conduct here - but it certainly helped the decision)

[Sascha Franck]

More reviews, for the Mac Mini as well.
Mini:
https://www.theverge.com/2020/11/17/215 ... -m1-review
Air:
https://www.theverge.com/21569603/apple ... rm-silicon
MBP:
https://www.theverge.com/21570497/apple ... -m1-review

So far, most of these reviews seem to be coming from Apple fanboys, yet, the numbers of the various benchmarks don't seem to be faked at all. So, all in all, as much axes as I may have to grind with Apple, they seem to be doing pretty well this time.

[Cinebient]

Looks not bad so far. I have still a week to wait for my M1 macbook pro (16GB RAM seems to take a week longer).
Oh i will also support all developers early on board and buy the music tools i have not yet

Are you using Logic?

Yes and i will do a Logic benchmark of course and will see if i finally can run some plug-ins (even under Rosetta) which brings my current i7 quadcore down, like P900 with 8X oversampling or things like Kaleidoscope or B2 reverb with 4X oversampling in real-time.
Not needed but interesting to know how it performs under longer heavy loads.
A reason i do not wanted the macbook air since i think it will throttle much more after a while.
But early tests and benchmarks looks really great if you think this are the entree apple silicon. So i wonder what they put inside maxed out 16" pro or in their larger desktops.
Normally i never would buy a first generation thing and also not first charge(es) but i thought f....it.
I hope Logic works nice for me on a 13.3" since i´m used to my 15.4" and even always wanted the 16". But i thought i go the more cheap and mobile way this time sine the 16" was way too much money for me to spend and see how it goes. 2 Ports are enough for me and 1 extern monitor is O.K. for me too.

[Sascha Franck]

Yes and i will do a Logic benchmark of course

Great. We could perhaps try to come up with something new, the current benchmarks usually are only focusing on multithread performance. I'd like to have 3 different ones:
1) Singlethread performance.
2) Multithread performance.
3) Combined performance.

I'd happily think about how to set them up as meaningful as it gets using just Logics plugins. I would also happily create appropriate projects including description and upload them somewhere.
So, just let me know whether that sounds like a proper plan.