Whenever I try to use this the values just run away like crazy. I think I understand how they intend for it to work, but it seems completely broken.
Let me test mine. I have the V1.2 loaded.
Seems like it only works on numerical values that only show “%” and not those with “KHZ”.
It probably needs an OS correction. All it does is to slow down the speed of advancing the number either positive or negative directions.
Good idea to try to allow fine tuning with shift, however…design/implementation is subpar.
I am referring to the fine tuning while holding the shift button.
Having to hold the shift with one hand while fine tuning with the other hand is awkward.
And still tuning to exacting values is tough if not impossible.
The values seem to “jerk” around quite a bit.
It takes me awhile to even get “close” my hands get tired.
And then the display changes from displaying values back to displaying the patch, before I’m done fine tuning.
It weirds me out a bit to have the knob end up pointing to what it is not, after fine tuning.
Suggestions:
- Allow the shift button to lock–akin to a capslock button.
Also allow fine tuning via the entry encoder (or maybe for ultra fine tuning).
Also allow user to input entries for fine and ultra fine tuning into the appropriate more menus (similar to the LFOs).
Some knobs do not have the fine tune shift functionality that should, for example the delay times.
Try dialing in 600.00 milliseconds. Haven’t checked which other knob would benefit the fine tune shift option.
Using fine tuning shift for the Modulation Oscillator audio rate, display shows xx%.
-
- What does this percentage represent? Seems around 61% (with keyboard tracking on) matches osc1 at 4’ frequency, Why doesn’t it show an user friendly offset similar to how Osc 1 shows its detuning?
- Although it doesn’t show any more accuracy than whole numbers, fine tuning shift is changing the frequency.
The accuracy displayed to the user should be as exact as it actually is, for example 61.01.
3, However, it is still tough to tune it, really needs to have an ultra fine tuning option for a user. I can’t seem to be able to
tune closer than .2 HZ to A440. And somewhat often when I release the knob the tuning suddenly changes.
I agree with the majority of this. I had landed on ‘fine tuning with the encoder’ as my preferred solution, maybe I’m just used to the idea of coarse and fine tune knobs on an osc.
Before I continue I’ll say that I’ve stopped looking at the screen when I’m dialing values that are exposed on a pot. We never needed a screen to dial parameters on a mini, and we still don’t. It really needs to be done by ear, the actual value is kind of irrelevant. That said, I do agree that expressing the tune as a % isn’t the most intuitive. Ultimately we’re not controlling a pitch directly though, we’re controlling a voltage that’s then controlling the pitch. If they expressed this in Hz it wouldn’t make sense either because oscillators drift, and the controller really doesn’t have a way to know precisely what the voice card is outputting. At the very least they should show the actual value down to the internal precision as you recommend, and I suspect it can probably be fixed in about 3 characters in the firmware code. turning a knob and hearing the pitch change without a visual reflection of that change is a little jarring if you’re focussed on the number.