Modulation, also confusingly called AUTO/Automation - even though it is not Automation, as many have pointed out - basically the automated changes of parameter you can record with the AUTO button, is a mess to manage, IMO.
As far as I can gather from the Maschine Manual and from user experience, modulation is stored within the pattern. So far that makes sense.
However one of the biggest pitfalls is that when using the ERASE+Encoder shortcut to erase Modulation of a single parameter it apparantly straight away removes it from all the patterns. Thats definitely not what I would expect in a typical workflow and has confused me many times in the past when I didn't understand why my carefully recorded modulations had disappeared from patterns that I hadn't even touched.
There is certainly room for improvement in the area of modluations in general, however I acknolegde that this functionality is particularily challanging to do in a way that is both intutive and enabling to creative expression.
But destroying recorded modulation in other patterns without warning, when the obvious expecation should be editing on the selected pattern only, seems lika a no brainer, and an easy fix to improve user experience.
Or am I the only one annoyed by this?
I really love Maschine for how close it gets to an all-in-on hands on feeling. But small unneccessary flaws that make one feel like progress will randomly get destroyed hurt the overal experience 😉