DSP Robotics Support

Hi Guys,

Before I post a sample schematic, I've a question on a design regarding knobs.

Specifically ... BitMap knobs.

I'm looking to provide an option in the way a knob is 'programmed' to provide a determined number of steps AND the ability to switch to step-less or continuous mode.

I design all my bitmap knobs using KnobMan, and there I define the number of steps to render. This has worked fine [although, it is tedious that several knobs with varying number of steps are needed for a given project].

I prefer the 'look' of bitmap knobs over vector designs. But I wonder if there is a way around locking a knob to only work within the number of steps designed in Knobman

Since all my knobs are general linked to MIDI, there is a limit to the GM spec of 128 steps. [I don't know the limits of the hi-rez controls].

Anyway ... as a general question here ... I could use some thoughts/ideas on how to design for this, and what I should consider.

Thanks for letting me ramble this thought out. Still ... would be most interested hearing some ideas.

Thanks!

It does not matter how many frames you use in knobman the values output by the knob rely on a) stepped mode number of steps and b) unstepped mode the sensitivity value.
I tend to use a minimum of 32 frames but still get 128 values you just don't always see the knob move as you get 4 values between each frame, though on a small knob even with 128 frames I doubt you would be able to pick out individual movements.
Also if you don't need the look use the static bitmap knob as its easy to add the start and end angles to its properties saves a lot of time in knob man when you don't need a full range knob.

Hi Xtinct,

OK ... I'm re-reading your post to get a better understand.

And now I need to re-check how my knob is working [or not]. I had thought I tested with a knob that had some 21 steps [frames] from the KnobMan app. I thought I had tested turning OFF steps in the knob property, and the knob still kept the stepped movement, rather than a smooth continuous travel ... I'll re-check again.

This is kinda what brought me to this question ... but maybe I over-looked something ... not quite sure what, but I'll check again.

I'll also look into the 'static' bitmap knob you mention. I don't think I ever used that module.

Could you explain what makes a knob 'static' by design ???

Thanks again !

Yes the movement will be stepped with just 21 frames but check the output you will have more than 21 values.
I suppose the best practice would be to increase the number of frames till you cannot notice the jumps and that will be the minimum number you need and the smallest file size.

As for the static knob its just one frame so small file size and the dot or line indicator is produced separately or you can even remove that frame if your gui is an image and have the knobs as part of that image with the empty knobs over laying it with just the indicators.

Hope that makes sense just woke up

Quick example clearer more than my words it is

Dividing a square into steps always results in more steps. So all you need to do is have more steps.
Visibly the last frontier would be one pixel of movement, to be fucking ants about pi to half the number of pixels on the width.

Xtinct wrote:Quick example clearer more than my words it is

ahhh ... now I understand 'static' knob design.

Thanks for the example Xtinct ... very much illustrated the style of that design.

The way you did the switch from stepped to continuous was exactly what I was going to try with the knobs I was using.
I had really hoped it was just needing to toggle the 'STEPS' in Properties in order to allow both methods.

Still need to ponder how I'd do this using my 'NON-static' knobs in the most efficient manner ... I'll look closer when I get back tonite.

Big Thanks!