This has already discussed and this would result in strange display glitches when several knobs are turned at the same time.
Other synths seem to do it. But then they were probably designed to do it from day one and resourced accordingly :)
Rather than change category could it not just display the parameter being edited with its value?
If multiple knobs are turned you simply show the value of the first one turned and then don’t display the value of any other knobs for a few seconds? It seems to do this on my Novation Nova.
Obviously CPU time is severely limited as it is.
Would be cool if it were doable…
You have misunderstood me. I’m not saying that there’s a technical limitation or bug that prevents this to be done. It’s just that you’re asking me something that has no obvious specs. If you turn filter resonance and oscillator waveform at the same time, what should the display show?
First line of LCD shows the first knob value and parameter name (name would need to be abbreviated).
Second line of the LCD shows the second knob value and parameter name?
Then if another knob is turned the line for the knob that has been idle longest gets replaced?
Someone may try to turn three knobs at once to be a nuisance of course.
Display would timeout after 1 or 2 seconds?
Should this change the current page? Should it change the active parameter for the encoder?
I’ve found that I am kind of working blindly twiddling knobs and listening more than looking. So I would be happy if the LAST knob touched caused the display to move to that page. If you move two at once maybe blank the screen out if there isn’t enough resources to flash back/forth (it would look bad anyway). Maybe just put a “(* – * )” or something until one of the knobs stops sending, then switch to the active knob page.
Anything would be better than being non-responsive. IMHO.
Yes!
Your proposals make it hard to reuse the existing code, so it’ll take more time than planned. Very, very low on my priority list – I don’t even have a programmer to test it, and I am not interested in building one since this is not a product I want to actively support myself.
Well my thinking was to continue to use the existing pages so it’s not a shitload of new programming. The existing pages are fine. If you could just switch to the last active knob’s page. Either use a delay or ignore simultaneous input. Wouldn’t matter. It would still be a huge improvement.
Incidentally, I’m not sure if it is the OLED but the knob feedback is lightning fast! I had expected a lag and there is absolutely zero. The OLED values just fly as fast as I can turn the knobs.
Yup.
Actually I think there might be even an advantage to not seeing what you tweak on the display… trust your ears! :)
but my programmer still does not work so I don’t know what I’m talking about :D
When do we get to “try” the new build?
I would really like to try this. If you prefer you can email me a copy at titusraindrops ( the at sign ) gmail ( the dot) com.
I will be your beta tester guinea pig.
It looks like you're new here. If you want to get involved, click one of these buttons!