after locking the rack state the effect doesn’t show up again (for the moment ). To be serious: could be the reason but it can also happen 2 hours later as the effect occours randomly.
Out of curiosity: if locking a rack state is able to fix the problem, what would be reason behind? I don’t really understand why locking is necessary at all to keep things stable. For me locking a state always was more of a “safety lock” to handle “misbehavior” of the user.
Edit: I’m pretty sure I got it (and as in many cases the problem was sitting in front of the laotop ).
After locking the states the effect unfortunately occoured again. Listening to it I didn’t have a single idea which of the other sounds stored in states could fit to what I heard.
So my only clue was: it can only be the stored sound but in some way manipulated - f.e. by external controllers - and this was exactly what happened.
Hives filter had a mapping to CC#01 but no mapping of an external controller to CC#01 and even though I generally predefine not used controller channels by binding a defined value on song load I didn’t have CC#01 in mind in this case.
So when I called a song before that had a binding from controllers to CC#01 cantabile remembered last value and as songs are not completely restored Hive reacted in the described way. This can also explain the fact that even calling up the sound in Hive again didn’t change anything.
@dave_dore: many thanks for “cross-thinking” - even though it wasn’t exactly the problem in the end it helped very much changing the way of thinking. At least it helped solving a problem in a few hours I couln’t get rid of during last two weeks!
Kind regards, Volker