More information on future updates M+

@Matthew_NI …?

If that new hardware would build upon the current software architecture it would definitely make sense to first stabilize / optimize the existing code base. Same goes for expanding version 3 on desktop, and maintaining support for MK3 and M+. Because IF they would release Maschine MK4 hardware without doing so, this would really backfire at NI.

And yes, I also think M+ hardware will become EOL within 2025 or early 2026… well, at least, the standalone part. Not because of what Maschine 3 SW is showing us now, but because of more ’generative tools’ based on LLM-power, that would never run within acceptable ranges on the current hardware.

That’s why I’m so interested in the answer to: will Maschine 3 on desktop support the M+ running on version 2 software…?

If I would have to choose and/ prioritize development, with respect to resources and customers:

1. Update and stabilize version 2 of the M+ software / firmware.
   1. Everything that’s announced to be currently in beta for Q1.
   2. Including support for the latest version 2 projects from / on desktop.
2. As the development of desktop OSs (Mac, Win) moves much much much faster, I would then first improve the support of M+ version 2 projects within Maschine 3 SW on desktop.
   1. Offer the import / export of standalone projects from M+ into the desktop software from the UI. So without going through the file system hassle.
   2. Preferably, by making use of (local) WiFi. But, this would require an update to the M+ software, too.
3. Bring over K8 player support to M+.
   1. Focus on K8 and Sampler / Audio updates and upgrades to support version 3 desktop projects.
   2. At this point all other on-device MIDI and UI improvements should be considered nice-to-haves.
4. Support of exporting version 3 projects to the M+ (using the improved transfer workflow).
   1. When exporting from desktop offer a ‘bounce to Audio’ for non-compatible parts, without loosing its source data on desktop (like Ableton Live 12.2 offers: bounce to new track, keeping the original MIDI data, instrument and settings within a muted / hidden track).
   2. All other should be covered by K8 player or other on-device plugins + MIDI.
5. Bounce to audio should also be used as a basis to export to an Ableton Live 12+ project on desktop.
   1. Bring over MIDI, convert instruments to Kontakt, bounce tracks to audio (dry or EQ / FX applied).
   2. Stop the development of Maschine as a plugin.
   3. Focus on plugins for Kontakt, Reaktor, and their Player-versions (without editing capabilities).
   4. This should also function as an exit strategy, not only for customers. Because this feature could also keep users within the NI ecosystem, continuing to use the other instruments and libraries.

At this point you could gently announce version 2 on desktop EOL, without the need to upgrade M+ standalone to version 3 just yet… or ever.

Now there’s the option to tighten the integration with Kontrol hardware and/or release a new Maschine MK4 controller. The new controller hardware could reflect some new features of the desktop software.

If a ‘Maschine Plus MKII’ would ever see daylight, use its powers for on-device usage of (3P) plugins, more complex FX processing, MPE, STEMS, other so-called AI features, and last but not least: a much better GUI, offering much more usable information and feedback instead of eye-candy.

Every update could and should include at least one MIDI and/or workflow based improvement for Maschine Plus and MK3, too. These could all be minor improvements, and because of the desktop importer / exporter be kept or isolated within the ‘version 2’ realm.