Hi!
Me and a friend of mine have a problem with the volumen Knob after updating to CorOS 2.1.0
The range of the volume knob has changed. We have dead zone at 0% and at 100%. When you srtart turning the knob, the first part is at 0, then goes normal until the last part of the knob, that’s at 100%.
My friend tell me that his volume jiggles all the time when the volume is notat 100.
Please ensure that you are on the latest firmware update (2.2.0 as of 10/9/23). Also, NDSP recommends to keep the main volume at 100% at that is actually unity and gives the best SNR. If you still continue to experience issues with the volume knob after updating, please email support@neuraldsp.com so that the issue can be logged and resolution can be provided.
Yes, i Have CorOS 2.2.0. I use at 100 % all the time, but I have a problem that with CorOS versions before 2.1.0 i have’nt. MY friend’s QC, the volumen jiggles too.
I am having the exact same problem 
When the volume is all the way down (fully counterclockwise), I need to turn the knob for a bit before my QC sees the rotation and starts counting the volume up from zero.
Similarly, when the volume is at 100 (fully clockwise), I need to turn the knob for a bit before my QC sees the rotation and starts counting down from 100. When I am turning up the volume, it reaches 100 and stops incrementing well before the knob completes its full rotation.
I only noticed this after upgrading from 3.0.0 to 3.1.0, but I can’t say for sure that the problem was not present before the firmware update.
I always assumed that the dead zones at 0 and 100% are intentional to make sure you stay at 0 or 100 even with vibrations, small accidental movements on stage etc.
Or do you refer to something else?
Agreed, having a bit of a dead zone is a good thing. I actually calibrate my expression pedal so that I can get to 100% without accidentally pressing the toe switch.
However, in this case, with the QC volume knob, the amount of dead space is well beyond what you would expect. For me, approximately 25% of the motion range is now dead space. I am pretty sure that was not the behavior prior to the firmware update. I’m hoping there is some way to recalibrate. I have not yet reached out to NDSP support.