Machine 3 on M+

AdelV

https://community.native-instruments.com/discussion/comment/227114#Comment_227114

Dual booting most likely requires an unlocked bootloader, and I'm pretty sure that’s never going to happen because of safety and legal reasons.

PK The DJ

There may not even be room to have effectively two separate OS on the internal storage.

D-One

Not an expert… but I dont think it would be as complicated as dual booting… Yocto can do version switching of the SW at runtime, but even if possible, why go to all that trouble? What's the benefit of switching around? Having two SD's, switching them around and managing / keeping track of all that sounds like a nightmare even on a normal computer, let alone in a Standalone.

If development is already slow, something like this would make it even slower…

tetsuneko

Well, the other option is to buy another M+ for using 3.0 with - not exactly ideal either now is it?

PK The DJ

NI should take a leaf out of Akai's book and make it possible to revert easily to a previous OS/firmware. Ableton's Push can also do this. Ditto Denon DJ with their Engine OS.

tetsuneko

You can do this with the offline M+ OS installers I think? But IIRC there is something in the upcoming 3.0 which will prevent rolling back to 2.x OS versions..

ozon

Why worry about things that don’t even exist yet?!

tetsuneko

It will exist by the end of this year aka within the next 6 or so months.. And by then, if you upgrade and 3.0 turns out to be a hot mess, you've already pooped your pants (and messed up potential gigs etc). Better to prepare for it now than not to

I wonder if even resetting the whole device will help..

AdelV

You don't know it for sure, so saying it will be a "messed up" is a bit dramatic. There are a lot of smart people working at NI, and I believe they're doing their best to deliver a great product. Of course, it's not easy, and the business side of things can affect the stability of updates. But since 2020, Maschine+ has improved a lot in a good way, so there's no real reason not to trust the Maschine team.

djadidai

It all depends how M3 will affect the cpu. If it doesn’t require more, than I prolly will update, but I’ll stick to M2 on my M+ if M3 is glitchy and eats cpu.

tetsuneko

https://community.native-instruments.com/discussion/comment/227610#Comment_227610

I still got PTSD from the M+ launch, dont want to experience something like that ever again.. I dont doubt NI's capability to deliver a solid 3.x version "eventually".. but its the amount of time that it might take which worries me here. I've gotten used to my M+ just working yknow

Astralbeats_225

https://community.native-instruments.com/discussion/comment/227641#Comment_227641

Same, I welcome the extra features that 3.0 will bring but I CAN NOT go back to the instability that the M+ had at launch. I'll be lurking in the background watching everyone who updated until I'm satisfied that it's stable. 😅😅😅

Flexi

There is a paradox here, nobody really trusts NI anymore, so who tests the V3 update on M+, I suspect quite a few will bypass that test entirely, V3 ends up being a bit of a mess when released because it has had such little testing.
Moral of the story, NI need to make the M+ downgradable to V2 if they want people to test V3 (for free, generally in the music world beta testing is free)

tetsuneko

There will still be plenty of testers.. but they will not be people who are thinking of using their M+ for playing gigs

ozon

If the M+ is such a vital part of your live performance setup, you should have at least one backup unit.