Since the 2.1.9, it’s really hard for me to test the new firmwares because since the 2.1.9, I can only play the lowest octave.
I have already send to Gil a video showing this issue.
The same very low octave is looping on all the keyboard.
I tried different keyboard/midi or usb cables..
Impossible to play all the notes after the 2.1.9…
But after I performed a note calibration. It’s a bit better, now the octave is not the lowest, but with the “000/Panel Settings Preset”,
each B note sounds exactly as the next C…
So, notes 35 36 47 48 59 60 71 72 are exactly the same (but the B 23 and C 24 sounds as they should…)
With others persets, there is problems too. But it is not the same for each…
???
But with 2.1.7, every thing is working good about this issue…
I have checked your videos again, and it seems to me that you are actually sending top octave information from your controller to the MTR, which is why it rolls back to the same octave again and again when you reach the top C. Would you be able to:
Upgrade to 2.1.11
Restore all global settings to default on Editor
Play the MTR from a different controller, or send Midi notes to it from Cubase (or other DAW) on different octaves, and see if it still happens ?
Regarding the second video you sent, showing VCO2 octave changing while rotating VCO2 FREQ, this happens for the same reason - You are at the top octave for VCO2, and it rolls back to the lower octave when trying to go higher.
We’re checking if this is something that can be implemented in a better way.