You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CC48> works great and steps with every tick of the encoder.
CC48< starts spamming and because of that chokes up input until midizap can catch up
Back has a high value at ~126-127. Could this be causing it? I tried different operators after the CC48 but didn't get any better results
The raw messages look like
32:0 Control change 0, controller 48, value 1
32:0 Control change 0, controller 48, value 1
32:0 Control change 0, controller 48, value 1
32:0 Control change 0, controller 48, value 1
32:0 Control change 0, controller 48, value 126
32:0 Control change 0, controller 48, value 127
32:0 Control change 0, controller 48, value 127
32:0 Control change 0, controller 48, value 127
32:0 Control change 0, controller 48, value 127
The text was updated successfully, but these errors were encountered:
Midi debug output is the same. The messages themselves are very consistent so I believe is the 127 value being interpreted as VERY fast when that's the slowest speed.
1 is slow 2 and 3 are faster and faster
127 is slow reverse and 126/165 are faster reverse. So going backwards.
[0] CC48-1 value = 1
[0] CC48-1 value = 1
[0] CC48-1 value = 1
[0] CC48-1 value = 1
[0] CC48-1 value = 126
[0] CC48-1 value = 127
[0] CC48-1 value = 127
[0] CC48-1 value = 127
[0] CC48-1 value = 127
DJControl Compact USB
Pipewire Jack with QJackctl
CC48> works great and steps with every tick of the encoder.
CC48< starts spamming and because of that chokes up input until midizap can catch up
Back has a high value at ~126-127. Could this be causing it? I tried different operators after the CC48 but didn't get any better results
The raw messages look like
The text was updated successfully, but these errors were encountered: