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
A customer has reported what looks like an issue related to the clock settings per port and we have been able to replicate it in CVThing v1.4.1. Steps on how to reproduce the behavior as follows:
1 - Enter port 1 CV CONFIG menu
2 - Select CLOCK SET
3 - Change Mult. to x32
4 - Enter port 2 CV CONFIG menu
5 - Select CLOCK SET
6 - Change Mult. to x16
7 - Press encoder for 3 seconds
8 - Select SAVE CONF
9 - Save config to USER 1
10 - Reboot CVThing
11 - Enter port 1 CV CONFIG menu
12 - Select CLOCK SET
Result: Port 1 clock is x16 instead of the expected x32
Notes:
In step 9 (Save config to USER 1) same result was obtained if saving to other presets USER 2 to 4
In step 2 and 5 (Select CLOCK SET), same result was obtained if selecting FUNCTION>DIG.FUNC>CLOCK
When CVThing is rebooted, last port selected clock settings are applied to all 8 ports
We will wait for confirmation in order to see if we are facing a bug, and if so, if there are plans to fix it in further firmware versions.
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
A customer has reported what looks like an issue related to the clock settings per port and we have been able to replicate it in CVThing v1.4.1. Steps on how to reproduce the behavior as follows:
1 - Enter port 1 CV CONFIG menu
2 - Select CLOCK SET
3 - Change Mult. to x32
4 - Enter port 2 CV CONFIG menu
5 - Select CLOCK SET
6 - Change Mult. to x16
7 - Press encoder for 3 seconds
8 - Select SAVE CONF
9 - Save config to USER 1
10 - Reboot CVThing
11 - Enter port 1 CV CONFIG menu
12 - Select CLOCK SET
Result: Port 1 clock is x16 instead of the expected x32
Notes:
We will wait for confirmation in order to see if we are facing a bug, and if so, if there are plans to fix it in further firmware versions.
Thanks
The text was updated successfully, but these errors were encountered: