!wow! awesome
Just out of curiosity - can you describe at all what exactly was going wrong code-wise?
I donât think I can describe it exactly without showing the code. At a high level, a shift+fader flag was getting set but not reset.
2 Likes
I also had the problem with fader lock working in reverse a week or two ago. Donât know how I got there but it happend.
In the meantime - before this is fixed in a firmware update, is there a sequence of actions to go through the clear the issue?
Perhaps I am just having bad luck, but within the last day or so I am having a high rate of this happening. Sometimes reloading/re-assigning the sample works, sometimes it doesnât. I havenât found a reliable method to clear the issue besides rebooting.
OofâŚmy bad.
Hi, I have experienced this behaviour a few times too but Iâm only adding sounds to tracks from the internal drive (not SSD) and not a new sample.
Hopefully itâs the same thing that will be fixed with the new OS?
I do have a video of it but itâs basically me being in level mode and moving the fader and the levels not changing. A reboot sorts it.
Doesnât happen everytime and no real pattern to it.