Maschine 3.7 — I’d really like this one to be about stability
I’ve been using Maschine for many years, and despite all the ups and downs of the platform, I still genuinely love it. There is something about the Maschine workflow that I simply don’t get from a traditional DAW.
That’s also why I think Maschine 3.7 could be a very important release.
Personally, I’m not looking for another huge feature drop. I would much rather see 3.7 focus on making the existing Maschine 3 ecosystem more solid, predictable and trustworthy.
There are still a number of areas that keep coming up in the community:
Plugin hosting and VST3 stability
Plugin scanning, loading and unloading still seem to be a recurring source of problems for some users. There are reports of Maschine hanging during plugin scans, crashes when plugins are unloaded or projects are switched, and VST3-related issues that don’t necessarily happen in other hosts.
There have also been cases where buffer handling with VST3 plugins caused pops, crackles and unexpected CPU behaviour.
I think the goal should be simple: if a VST3 plugin works correctly in a modern DAW, Maschine should host it as predictably as possible too.
CPU efficiency and regressions
Performance has clearly improved in several Maschine 3 updates, but CPU behaviour can still vary considerably depending on the project, plugins and version.
One of the most valuable improvements would simply be:
Please make “no performance regression” a priority.
A project that worked comfortably in one version should not suddenly become significantly heavier after an update.
Project saving and project integrity
This is probably the most important one for me.
There are still reports of projects not saving correctly, changes apparently disappearing after reopening, and problems with saving projects together with their samples.
For a music-production application, I think this should be considered a fundamental reliability issue rather than a quality-of-life feature.
If Maschine says the project was saved, I should be able to trust that it was saved.
That includes the project state, samples, plugin states and everything necessary to reproduce the session.
Reliable plugin state recall
There have also been reports of plugin states not being recalled correctly after reopening projects, as well as plugin windows and parameters contributing to crashes.
Again, this is less about adding functionality and more about confidence:
Open the project tomorrow and it should sound exactly like it did when I saved it today.
I know software development is complicated, and I also understand that Maschine is not meant to become another traditional DAW. I’m not asking for that.
Maschine is already an incredibly powerful creative environment.
Cheers,
