12-30-2023, 08:05 AM
Hi,
Firmware 2A, two global transpose related misbehaviors:
after update old projects seem to be transposed down severely - Middle C is many octaves down, barely audible. I had to set global transpose to +80-+94 instead of 0 to reach audible range for any note. If this is a default that old projects do not have, the firmware should automatically fix such case on load, as it took me 10 minutes to understand what is happening
.
Second misbehavior is that update passed via new mapping feature to global transpose resets to global default after each cycle of track repeat. It reacts to mapping input correctly, but then reverts back to global value after cycle ends. You get a funny effect of going out of tune and then back to normality if you do not touch anything for a while. It should stay transposed IMHO.
Firmware 2A, two global transpose related misbehaviors:
after update old projects seem to be transposed down severely - Middle C is many octaves down, barely audible. I had to set global transpose to +80-+94 instead of 0 to reach audible range for any note. If this is a default that old projects do not have, the firmware should automatically fix such case on load, as it took me 10 minutes to understand what is happening
. Second misbehavior is that update passed via new mapping feature to global transpose resets to global default after each cycle of track repeat. It reacts to mapping input correctly, but then reverts back to global value after cycle ends. You get a funny effect of going out of tune and then back to normality if you do not touch anything for a while. It should stay transposed IMHO.

