Wul wrote:I had to try this, because I couldn’t believe a credible developer would let this slip through the net, and then again after a major update , and yes it’s still there in 2.10.1 .
It only happens when the same note is pressed on another channel.
Checked the midi monitor and that only registers a note off on the second channel.
This software is seriously flawed, users are continually having to find workarounds, for what are basic errors.
I have the midi hub. So that would be my workaround , actually on second thoughts it wouldn’t solve it . There is no workaround.
Yeah that's crazy.
There is something not working right with beta testing I guess.
Also Track mute, after 2.8, works differently, as you unmute a track it starts playing only when a new note is triggered. Before 2.8, it started immediately, because the sample or track was kept playing but silenced.
That changes my way of using track mute, not nice.
I wonder if there is a connection with this behaviour and the midi note off bug of this thread. Maybe with 2.8 they messed up midi protocol.
And also I found another bug, qlink project mode forgets qlink assignment of subgroups and outputs, which is a big shame because I route different tracks to a subgroup to apply an effect to all of them and now I cannot do it anymore.
Bugs, bugs, bugs.
What are beta testers doing?