Maschine+ 1.5 = OUT NOW

Since you mention the "bitcrusher" effect, what kind of audio interface are you using? I've had the same effect, but without the crashes, since I've been using an Ultralite MK5. I've never had that with my Focusrite 18i6, for example, no matter which version I had on the M+. I think this is due to the sample rate or whatever is interfering with the communication with the audio interface. 

@Kai_NI good to see your separate post in which you share your thoughts and focus for a development roadmap / (new) product planning.

Maybe you could also write a post and open a structured section on bug fixes, like compatibility or integration with Maschine desktop or Stability improvements. That way we can address things like lost connections with class compliant audio interfaces, etc.

For me personally the M+ doesn’t lack functionality. Yes the GUI could use some improvements based on experience and the integration (lift and shift) with the desktop is suboptimal. But my biggest concerns are with the way authorization is handled and the overall stability, for instance when using an audio interface.

Hopefully you and your team are open for this kind of communication and input.

Motu 8A

I don't remember how I did it, but I remember looking through one of the crash logs a long time ago. There were references about losing connection (or communication or something) with the audio engine followed by an entry stating it restarted.

The thing that really gets me curious is how midi behaves when this occurs. I generally have a keyboard sending into maschine. That stops working. I often have maschine sending midi back out to the keyboard AND I monitor through the audio interface (as opposed to monitoring through maschine). My keyboard is still getting midi and playing normally (so the audio interface sounds fine); but the tempo is much slower.

I haven't attempted to replicate the midi stuff with the new update, but I'd bet it's still doing the same.

For what it's worth, I've had it running for the last few hours. Yesterday, I couldn't get it to keep running for more than an hour.

Looking forward for @Kai_NI or @Kaiwan_NI to respond to my suggestion. Thanks.

I 've learned that there are 3 sorts of "class-compliant": Windows-, Apple- and Linux class-compliant devices.

And of course in most cases no one knows exactly what compliance is meant in a concrete usecase. In forums they talk about the fact that Linux class compliance is still no standard. IIRC our M+ is Linux based...

You know what, you're right. I shouldn't blame NI for the promises in the other resources I've pointed out and just accept that a 'soon' from 2021 can't be kept.