More information on future updates M+

LostInFoundation · March 24

And, work on a solution to skip online activation!

I’m afraid this is the only thing we should hope for…and even that it will not be so sure we will get it…

PK The DJ · March 24

"when Akai deliver a timeline"

But they didn't deliver a timeline. When MPC 3 OS was released, they stated that there was no timeline for the desktop software. They had no idea when it would be updated. There's an approximate one now, but that's no different to the NI approximate timeline.

"Comparing the M+ to either of the two Akai machines"

I'm not doing that, and there are more than two MPCs in the Akai range BTW.

"if you want to actually act like"

I'm not "acting like" anything. I'm comparing the situation (that both companies are in) where the desktop software and standalone OS are incompatible.

"They are not in the same situation.. its exactly OPPOSITE"

The situation of the two platforms being incompatible.

Matthew_NI · March 24

@MaikR the plan has not changed since the last time we discussed it publicly here:

https://community.native-instruments.com/discussion/41992/2025-outlook-maschine-kontrol-and-nks-hardware-partnerships

Key points included:

`Maschine 2 on Maschine+ (Q1 Release)`

Maschine 3 on Maschine+ (Q2 Release)

Maschine+ Content Releases (2025)

Also mentioned was a beta sign up link for those interested.

Currently in beta is the Maschine+ update that includes the latest greatest support for Maschine 2, inclusive of many long awaited bug fixes.

Also mentioned in beta is that the next beta releases will focus on the second topic of the list above: Maschine 3 on Maschine+.

You are a participant in that beta so you're well aware of this. In that beta, you also asked about some forthcoming minor fixes, and were informed then that these too were days away.

Nothing is being hidden here. @Chris_NI published a 2025 outlook, and we're in the middle of executing that plan.

MaikR · March 24

https://community.native-instruments.com/discussion/comment/217949#Comment_217949

https://community.native-instruments.com/discussion/comment/216899#Comment_216899

First of all, you’ve stated the delay above… and, this matches the state in which the beta is at this point.

Second, I didn’t expose any information about the ongoing beta, nor being part of it. I see you are allowed to share this kind of information publicly…? Fine.

Still without exposing any details: the current beta has one big flaw that wasn’t solved within the last minor updates. At this point we are still waiting for any information and/or a new fix. No planning or estimates are given, very little communication, no testing tools, and no rollback to a previous stable version.

So no, I’m not expecting polished software. But I do expect decent beta support.

And, maybe you could start by answering another question: why can’t Maschine 3.0 offer support for the M+ on version 2? You know how little progress you’ve made (read: NI) and how long it can take before version 3 on M+ is stable… or in your words, ’polished’ enough for prime time.

And no, I’m not convinced NI will keep its word this time. I’m sorry to say that, but it’s based on my experience with your company during the last couple of years.

Percivale · March 25

Since we are living our lives in quarters in this ecosystem, and Q1 is almost up, let us see if NI can deliver as promised or what some members here have gotten accustomed to becomes validated.

ozon · March 25

@MaikR asked

why can’t Maschine 3.0 offer support for the M+ on version 2?

Maschine is not capable to read files from a newer version. It isn’t even capable of reading considerably older project files.

It’s been like this since forever and must be rooted in the Maschine Project file format. I guess it’s not a real file format (e.g. separate object model suitable for version independent persistence written as XML), but just all the project‘s (version dependent) objects, written as a byte stream. Which is highly dependent on the programming language and the current object model.

Roughly: Reading an older object stream into the current model is often doable (possibly supported by the programming language), but writing an object stream as a different version is much more complicated and requires to keep the old object models in the source code (which has its own implications).

MaikR · March 25

https://community.native-instruments.com/discussion/comment/218116#Comment_218116

Thanks for bringing your knowledge into the discussion 👍🏻

My suggestion would be to use the ‘exporter’ from (the latstest) Maschine 2 on desktop and use it to build an export feature into Maschine 3.

As M+ (after the update) can load those latest Maschine 2 project files / structure, I think this should at least be investigated as an option to support compatibility with the M+ still running Maschine 2 SW.

And, if they don’t want to bloat the Maschine 3 software, an alternative option would be to update the (currently) latest Maschine 2 to support the latest versions of MacOS and Windows.

Of course I would like to see Maschine 3 to get a better import / export feature, and to have it kept on par with the M+ on te latest version 3, too. So probably Maschine 3 SW on M+ will handle this differently.

But…

Well, lets not starting to repeat myself and get into the same frustration over and over again 😉 so we’ll see what NI can bring to the table.

PK The DJ · March 25

I understand what you're asking for @MaikR but………if you need compatibility so that you can transfer projects from the computer software to standalone, why not just use Maschine 2?

ozon · March 25

https://community.native-instruments.com/discussion/comment/218182#Comment_218182

Because it’s not compatible with the latest OS, for example (currently not an issue for me personally, but it’s a problem for new users)

PK The DJ · March 25

You're saying Maschine 2 desktop software is not compatible with the OS on Maschine+?

Cretin Dilettante · March 25

https://community.native-instruments.com/discussion/comment/218225#Comment_218225

Mac, presumably.

MaikR · March 25

Both… Maschine 2 isn’t compatible with the latest MacOS, and project files from the latest version of Maschine 2 aren’t compatible with M+ (yet).

The latter is what the current beta of the ‘final version 2’ for M+ is also about, supporting the final Maschine 2 project files. But as Maschine 2 isn’t upgraded to support later MacOS versions, it’s the end of the line.

That’s why I’m asking for the latest Maschine 2 project format to be added as an export option to Maschine 3 on desktop. To retain backwards compatibility.

PK The DJ · March 25

Oh right, OK. I'm on Windows so not overly familiar with what works on Mac and what doesn't (other than Mac users tend to jump straight on updates then complain when the update breaks compatibility with something).

Also bought my M+ to use standalone, so for me anyway, not done much back/forth with projects. When I did last transfer stuff across, it worked.

[UPDATE] apparently Maschine 2 IS compatible (i.e. it works) on the latest MacOS. It just isn't officially supported. No reason why it can't be used, as suggested.