The definitive Knob

Tom7777 · 8 May 2005

Should keep mouse position. What i mean by this is you either see the mouse pointer icon go up down left or right to increase or lower the value. I think it would be great if it would just stay where you hold the left mouse button down within the area.

Shifrin · 8 May 2005

* Modifier+MouseButton to reset the knob to a default position.

* Modifier+LeftClickDrag to fine-tune.

* LeftClickDrag 'left-to-right' for fine-tuning (A la Ohmforce). Assuming knob is a normal linear type knob.

* Switchable to 'circular' type knob? (I don't need this but some may).

Just some ideas!

Shif.

Nu Audio Science · 8 May 2005

You didn't leave me anything to ask for 😠 😀 😀

unkargherth · 9 May 2005

Shifrin wrote: * Modifier+MouseButton to reset the knob to a default position. * Modifier+LeftClickDrag to fine-tune.

Not doable until we get keyboard input

Shifrin wrote: * LeftClickDrag 'left-to-right' for fine-tuning (A la Ohmforce). Assuming knob is a normal linear type knob.

I suspect you mean RightClickDrag. Left clickDrag is the standard drag, true?

Shifrin wrote: * Switchable to 'circular' type knob? (I don't need this but some may).

Could you detail how "circular" knobs behave?

Anyway, by now, I set this suggesions as "Reset" and "Finetuning" on the list. Answer if it isn't ok.

Nu Audio Science · 9 May 2005

Circular knobs are moved by a circular mouse motion, By this i mean the mouse actually has to travel with the rotation of the knob so you are moving in an arc instead of up n down.

unkargherth · 9 May 2005

well. then. I'm having no idea on how to define a ARC mouse area to drag into. Anybody?

Nu Audio Science · 9 May 2005

I haven't got a clue and i dont know anybody who uses it, But it is part of the vst standard 😠

Tom7777 · 9 May 2005

I guess you could define a area or path should i say that the mouse is only allowed to travel in and then connect this to the rotation module somehow but i havent really tried anything like that yet. Im guessing it would need a new module to do so.

You could maybe also make it so the the end of a line is set to the center of the area and the control follows the other end but i have no idea how to do that either.

infuzion · 9 May 2005

Great stuff NAS; looks really sexy!

Nu Audio Science (from previous thread) wrote: Yeah i was getting redraw problems but i used the technique Jorge showed last night whereby you put the redraw component outside of all the modules and it works better, He covers it in a thread last night somewhere 🙂

I was getting the same error; when you swung the knob to the right then quickly left, some LEDs stayed on. NAS got it cleared up 🙂

unkargherth, I think I mentioned #1 & 5, but I'm sure others were thinking it. For #1, it would really be best that the value range be definable, either by giving max & min, or triggering presets (eg 0-10, -10-+10, 0-255, 0-15, 0-F, 00-FF...). I guess a pop-up box can be added to #5, but I was hoping that one can tab between fields so you don't have to reach for the mouse.

cheers

Shifrin · 9 May 2005

Oops... *ignore*

Shif.

Shifrin · 9 May 2005

unkargherth wrote: I suspect you mean RightClickDrag. Left clickDrag is the standard drag, true?

Nope, but you could have it that way! What I mean is when you are draggin the mouse vertically it increments the knob as usual, but dragging the mouse horizontally fine-tunes! There was actually a thread on here about it and malc posted an implementation but I believe there may have been a bug or two!

unkargherth wrote: Could you detail how "circular" knobs behave?

NAS explained how the circular knobs work! As to how to 'code' them, well I've not actually tried that before but you could check the VSTGUI sources here :-

http://sourceforge.net/projects/vstgui

It's not something I ever used (circular knobs) given the choice, but thought it might be useful to have it there for completeness! My guess is that you could calculate the x/y offsets of the mouse position from the knob centre then use simple trigonometry to calculate the angle at which the mouse is relative to the knobs centre, and so update the knob accordingly. I may try to have a go at implementing this, will post back if/when I get the time to try it out 🙂

I also realise there are no keyboard modifiers as yet in SM, but I'm sure they'll pop up soon enough 🙂

Cheers,

Shif.

Shifrin · 9 May 2005

Shifrin wrote: My guess is that you could calculate the x/y offsets of the mouse position from the knob centre then use simple trigonometry to calculate the angle at which the mouse is relative to the knobs centre, and so update the knob accordingly.

And of course, I just forgot there are no trig primitives to use on floats for something like this are there!?!?! Then again maybe you can do it without the trig. Will try to look into it!

Shif.

infuzion · 9 May 2005

http://rapidshare.de/files/1662221/LATK_050509c_infuzion.rar.html (open the link in a new tab/window, scroll to the bottom, then click on {Free}. The link will be on the bottom of the new page.)

tidying up the code...

from the README wrote: LATK_050509c~infuzion.osm Based on NAS’s LATK downloaded 05May08, file size 153,167 bytes. Changes

User-end New

output: Value (float) input: Maxville (float), so the (output) Value will range from 0-MaxValue

Changed knob-LATK interface: Now the LED that the knob is pointing to won’t “turn on” until the pointer is more than half-way of said LED. This is to simulate the “clicks” one feels when turning certain dials.

Programmer-end

cleaned up/organized the code

neatened up stuff by rearranging module placements moved "Vu Dial" up one step Previously, the knob’s output was multiplied to get the desired output value for various modules. Now, Shadow Knob’s Value output is a 0-1 float for the LATK array, & TrueValue float output is for the actual desired output to the text & module output.

LATK’s "click" value is set by subtracting 0.0416667 from the bottom input float

file naming: To prevent confusion, unless a better method is agreed upon, let’s use this: FILENAME_YYMMDDnext-version-letter~you

Release Notes:

As I only did small changes to Nu Audio Science's great module, so nothing is expected in return. However, I still wouldn't mind a linkback, & a free copy of anything you make with this (hook up NAS first).

It's prob best to have the range to be set outside module. Right now, the range starts with 0, but it should be easy to have the range to start in negitives (for bipolar ranges; -1 to 1). I hope others will build on the code!

*phew* hard work... time for a nap.

Nu Audio Science · 9 May 2005

WOAH WOAH WOAH

Too many people keep saying this is a NAS module, Sorry but this needs nipping in the Bud now.

I just did the design (The way it looks) Unkargherth actually invented how the LATKs work.

Cheers Infuzion that looks like a great mod thanks 🙂

unkargherth · 9 May 2005

infuzion wrote: unkargherth, I think I mentioned #1 & 5, but I'm sure others were thinking it. For #1, it would really be best that the value range be definable, either by giving max & min, or triggering presets (eg 0-10, -10-+10, 0-255, 0-15, 0-F, 00-FF...). I guess a pop-up box can be added to #5, but I was hoping that one can tab between fields so you don't have to reach for the mouse.

cheers

Well. Whe i set that requirements the idea was: Have really open knob engine that could be programed with the aid of a "Designer module" to set it up. Polar or bipolar is more a question on how the leds swith on than how the value output is set, In a Bipolar, default value is 0.5 but all ledsa are off if you move to the right leds shwicth on from center to right and invers for left turning. On the value range i think is easy and less confusing to doit outside teh knob itself. (Anyway to build a module with defaults conversions is trivial)

Also, some switchable options ( bitmap or not, color or not,etc) could seem a nsense. But take this way. I could like all the options of a real knob without a knob, ie only leds , readout and output value ( one of my favorite designs), while you could want a colorable stripped bitmap knob, and would be nice that both of us could use the same "knob engine" only with two switches and one bitmap of diference

Nu Audio Science · 9 May 2005

Do you think it would be easy or not to make the designer have a choice for knob or slider ? I was just thinking that this could be used as a single module for any animated control.

unkargherth · 10 May 2005

I think you're thinking in slider standard component of SE

IMHO. I hate sliders. To imprecise if they're small and TOO space consuming if they 're large. Anyway, the diferences in management are so high that making twoin same engine seems, at least, too time consuming ( at worst could be a total nightmare)

anyway, this makes me thing.... another good feature foru the knob would be to be "Quantizable".Some way to tell that it produces only n results instead of a continuous range. This way you can easily convert a knob into a rotating selector frontend

If nobody against, i include this in the list of requirements

infuzion · 10 May 2005

unkargherth wrote: In a Bipolar, default value is 0.5 but all ledsa are off if you move to the right leds shwicth on from center to right and invers for left turning. On the value range i think is easy and less confusing to doit outside teh knob itself. (Anyway to build a module with defaults conversions is trivial)

Ahh, quite right about the bipolar LED thing, forgot about that! I moved the range conversion on the inside of the knob for this version, but now thinking about it, it might be better to have it on the outside, perhaps in a sub-module that could also handle rounding, because you will have the knob, number readout, an input (MIDI In) & presets be able to input values...

BTW, sorry if I didn't give you due credit.

I'm not sure if I'm a fan of an "all-in-one" design; I prefer streamlined code over lots of features. A wizard to help build/choose a particular model is a cool idea though.

Nu Audio Science · 10 May 2005

A slight addendum to the BMP ability The ability to load a single frame BMP or Multi frame vertical strip BMP

cheers

unkargherth · 10 May 2005

Well. Things are going on. I got the last LATK and started some mods

First of all i cleaned up a bit, deleted "debuggin tokens and so on

Modifications:

.- Number of leds changed to 15 .- Now the value is setable externally ( animated modulation, isn't nice? ) .- Made the readout editable .- Also i started a small "Knob designer module. By now you could switch on/off the background, the readout, the knob itself and the leds .- Also started something for Fine Tunning. Use horizontal drag to do it.Still Beta Here is a small "Knob show room"

Notes: If you deactivate all in designer you get a nice INVISIBLE Knob ( although you still can drag and change the value)

Get it here

Waiting for your comments

To Shif: the finetuning is far from perfect, but it's a start

To All: Any idea on how to create mouse hotspots for Min/center/max) without interfering drag funtion?

stefan · 10 May 2005

FWIW, I think this knob looks totally awesome (the gradient one (with the bitmap) does not imo 🙂)

Shifrin · 10 May 2005

unkargherth wrote: To Shif: the finetuning is far from perfect, but it's a start

Here's a link to the thread about horizontal fine-tuning (in case you hadn't seen it) :- Knob with horizontal/vertical control

I'll take a look and see if I can help out with it!

Shif.

unkargherth · 10 May 2005

Thanks Shif. I misse dthis one

Finally i implemented the second sugestion from malc. Horizontal draggin increment or decrements the scalin of vertical dragging

This, and another new features, in the upcoming beta

unkargherth · 10 May 2005

Version 0.2 changelog

.- Changed the alternate drag method for finetuning. Horizontal drag sets the scale for vertical drag

.- Changed type of comunication between designer and knob. Now it use a Bus

.- NEW !! Now you can set the 11 colors used (and its blendings) from the designer

.- Added switch for quantize mode ( still no implemented in knob )

.- More cleaning and reordering

Download Version 0.2 here.

TODO LIST

.- Implement the bitmap mode .- Implement the quantization .- Maybe implement a switchable Caption? .- Find a way to store designer output ( so you don't need a designer for every knob in your synth) .- Still to implement some requirements of the initial list ( bipolarity,etc)

Waiting your feedback.....

infuzion · 10 May 2005

It's getting there unkargherth! The external & click-type value editing works great. Draging the knob with the mouse isn't so great though; it shakes while dragging & when the mouse button is released, the knob (and value) jumps a bit. I had the same problem last night when I was reworking the knob to "click" on certain values; a refresh issue that I couldn't corner. Using the external slider doesn't have such a problem though.

I was thinking of adding the ability to have the knob "click" to certain values, so you can choose say 0-15 MIDI channels, & the knob & values won't move untill you go from 0-1, 1-2, etc...

cheers

unkargherth · 10 May 2005

infuzion wrote: I was thinking of adding the ability to have the knob "click" to certain values, so you can choose say 0-15 MIDI channels, & the knob & values won't move untill you go from 0-1, 1-2, etc... cheers

Thats what i'm trying to achieve with the Quantize option. Make that the knob return only N values equally spaced. Then multiply output by your top range, convert to an int and you have a rotating selector for everything you could needed

Shifrin · 10 May 2005

Unk, couldn't d/l the file was told it was 'Not Found' when I tried to! Good to hear about the quantization. That's something I'd forgotten about although funnily enough had already written for myself! My memory is not good 😉

Shif.

unkargherth · 10 May 2005

Sorry to all. My provider keeps deleting everything bigger than 500 kb Zipped now. Download Version 0.2 here.

infuzion · 11 May 2005

unkargherth wrote: Version 0.2 changelog .- Changed the alternate drag method for finetuning. Horizontal drag sets the scale for vertical drag

So, the further to the left/right to the knob you are, the less the up/down will be? Awsome idea!! Unfortunally, it doesn't seem to work here :/

Changed type of comunication between designer and knob. Now it use a Bus

Aaaahh, now I know how to use the bus! cheers

NEW !! Now you can set the 11 colors used (and its blendings) from the designer

Another awsome idea... LOL the defaults are giving me 80s flashbacks:

Added switch for quantize mode ( still no implemented in knob )

I figured out to do this, the value range needs to be calculated inside the module, which becomes the new value for the knob, readout, & output, but not the LEDs. I'm not sure where to go from there; I think you can have the GUI to update only when there is a calculated value change, or have the value range connect with the knob arc. Here's the schematic for my FloatRounding module:

Ratio=0-1, ValueMax=0-chosen range (eg 16, 255...), ValueRounding=what you want to "Round off" too, (eg 1, .01, .2)

Find a way to store designer output ( so you don't need a designer for every knob in your synth)

Could you have 2 seperately saving preset modules in the same VST, eg 1 presets for GUI, another for synth values? .

Got the smooth knob back, thanks. Keep going; you're on the right path!

lalo · 11 May 2005

wow is goin' marvellous!! i'd suggest to add minimum and maximum value...and resolution ...how many decimal points in the value

lalo

unkargherth · 11 May 2005

lalo wrote: i'd suggest to add minimum and maximum value...and resolution ...how many decimal points in the value lalo

Maximum and minimum has been discuseed before. It's easy to create your own range module and connect the output to it. than including it inside

Also maintaining this range/conversion module outside allows to ccreate bizarre conversion like linear [0..1] to negative exponential [0..-10] and so on.

On Resolution I've been thinking in something more complex: What about 5 position quantized knob that shows Text instead of Dec Value ( for example a quantized knob to select the waveform of a multitype osc )? or a knob ( standard range 0..1) that controls de Cut Off of the filter and shows it in HZ [0..20000] ?

It isn't easy but i'm working on it. POsibly it ends creating the Value to Text module externally and reconnecting it to inside, but still needs studying

Nu Audio Science · 11 May 2005

Holy crap 😮

How dope is this 🙂

Tom7777 · 12 May 2005

Nice, great work everyone 🙂 NAS i like your new avatar 🙂

Nu Audio Science · 12 May 2005

Cheers dude 🙂

Nu Audio Science · 13 May 2005

Just noticed that you changed the order of the links, The shadow looks better in most circumstances below the LATKs, This gives the effect that they are lights because shadow isn't cast onto light 🙂 , If the shadow is a light color this doesn't work as well.

Do you think there is anyway to have a second set of LATKs slghtly larger and blended in a bright color we may be able to replicate glow 🙂

unkargherth · 13 May 2005

Mmmm. no a bad idea, to add glow. In fcat no second set of leeds needed only athird color on existing in a slightly bigger area.I'd take a look

On the shadow issue, the current way is the phisically correct. Shadow should be cast on leds. It's a user decision to sellect the correct color for it so it seems real.

Nu Audio Science · 13 May 2005

Yeah the current way is correct, But to achive the given effect it is wrong, No problems just as long as people know they can change the links Unk 🙂 Dont forget that Shadow cannot cast onto light so when you turn the knob up the LATKs are being covered in shadow.

On the glow issue it really needs to be a seperate LATK i think sothat it can be blended with the original, For instance red would be pink and nearly transparent.

Anyway we'll work it out 🙂

unkargherth · 13 May 2005

Ok. Version 0.3 here

Change Log

0.3 .- Implemented quantization ( up to 16(+1) parts max) .- Implemented ( or tried to) Led Glowing .- NEW: New input Added. cnv. It allows to preconvert the output value. It takes priority over reaodut. Example include a Volume to dB conversion .- Some Household keeping basically cleaning and deleting what's not used) .- Added a version text. If somebody make any changes, please update it

stefan · 13 May 2005

I love this knob. I love it. Now make it resizeable... 🙂

unkargherth · 13 May 2005

Added to list of Requirements as 10.

Nu Audio Science · 13 May 2005

The Glow doesn't work though, It just looks like they are getting bigger and changing color, It really needs a seperate LATK over the top so that the bottom one can change color ie dark red to red and the overlay can be blended in for glow.

You got the size for the glow absolutly perfect though:) , I will try and do a new version with a seperate glowlayer 🙂 , Because you have designed it so well it should be very easy , All i have to dois duplicate the LATK and its design controls then just blend out completly the off color and lighten and blend the on color and then overlay with the original 🙂

Nu Audio Science · 13 May 2005

http://uk.geocities.com/nas_sound/TDKnob2glomod.zip

You may not be able to tell from the picture but the second layer really sorts it out, Now when the leds come on the glow actually is above the shadow , This gives the effect that the light has overpowered the shadow, It also makes it slightly easier to setup a glow.

Now the gap between the LEDs needs to be slightly larger, The OSM here is not a mod just a quick copy and paste job 😉

EDIt* Actually i'll stick that in as a suggestion, Sizeable LEDs 😉

unkargherth · 13 May 2005

Nu Audio Science wrote: The Glow doesn't work though, It just looks like they are getting bigger and changing color, It really needs a seperate LATK over the top so that the bottom one can change color ie dark red to red and the overlay can be blended in for glow.

Thats exactly how has been done a bigger led over the original with lighter color and less alpha blending. The only problem is that we need gradients to make it more realistic. So no real need to duplicate whole LATK, as what i done is to add another transparent lend inside evry litle arc

Nu Audio Science · 13 May 2005

Yeah but my duplicate is above the shadow, Dont worry about it i can always just duplicate anyway to do the glow how i want to, No probs 😉

unkargherth · 13 May 2005

well.We starting have a problem here TKnob3 around 800kb

Waht happends if you disconnect the designer? you loose all your config. Very bad. Becuase on a synth project with said 12 Knobs, seems a bit heavy that 9.6 Mb only for knobs

So we need a decent way to STORE the knob params, and preferably not in the preset, as if some user watch deeply, don't find 12*12=144 Params per knob configuration only.

Any idea? Maybe malc or jorge could suggest something ?

Shifrin · 13 May 2005

unkargherth wrote: Waht happends if you disconnect the designer? you loose all your config.

I've not looked at the schematic in detail, but if the designer is simply sending out a bunch of floats you could use a 'sample and hold' on those floats inside the knob. Then once you've designed the knob and disconnected the designer the values (floats) you chose will be held in the S&H in the knob. Of course if you're using the designer to pass Areas/Colours etc this would be harder as I don't know if there S&H modules for those data types.

Just an idea anyways!

Shif.

stefan · 14 May 2005

Shifrin wrote: unkargherth wrote: Waht happends if you disconnect the designer? you loose all your config.

I've not looked at the schematic in detail, but if the designer is simply sending out a bunch of floats you could use a 'sample and hold' on those floats inside the knob. Then once you've designed the knob and disconnected the designer the values (floats) you chose will be held in the S&H in the knob. Of course if you're using the designer to pass Areas/Colours etc this would be harder as I don't know if there S&H modules for those data types.

Just an idea anyways!

Shif.

Or you could just use one designer for all knobs... Which is what I would've done 🙂

malc · 14 May 2005

Unkargherth wrote: well.We starting have a problem here TKnob3 around 800kb

File size is something we can do alot about. We know of several optimisations already, just a matter of getting them done.

Tom7777 · 14 May 2005

File size will get much lower so just continue as normal i would say and everything will be much better in a future release and filesize should not effect it at all then.

unkargherth · 14 May 2005

Shifrin wrote: I've not looked at the schematic in detail, but if the designer is simply sending out a bunch of floats you could use a 'sample and hold' on those floats inside the knob. Then once you've designed the knob and disconnected the designer the values (floats) you chose will be held in the S&H in the knob. Of course if you're using the designer to pass Areas/Colours etc this would be harder as I don't know if there S&H modules for those data types.

Just an idea anyways!

Shif.

By now, designer is passing ints and colours, but in the future versions is reasonably to think that it could pass another thing (most posibly bitmaps,pens and so on)

There is no SH for colours nor areas, Itried to convert a color to a One Int spec ( you know, blend*167772216+red*65536+green*256+blue) to push it on a sh Int module, but i failed ( though it is teorically posible). Simialr can be done for areas ( first convert to floats, then SH Float), but as far as i know, no way to do it with pens and obviously bitmaps. thats what i asked for and preset independent storage module ion requests/ideas forum

stefancrs wrote: Or you could just use one designer for all knobs... Which is what I would've done

It depends . You can feel ok all knobs in your project looks exactly equals, But other developer not. Seems a nosense having a readout in a quantized knob that selects a waveform that is already drawn in other place. Also No all knobs should be quantized equally or be quantized at all

malc wrote: File size is something we can do alot about. We know of several optimisations already, just a matter of getting them done.

Size is only a measure. What worries me is the indecent ammount of working code we get if we need for example 7 types of diferent knobs for a Synth. is more logical to design every type and save the results as a set of "Consants" in some way. Then, on final stage before Building the VST,connect the module with this "Constants" to the bus input of every knob.

stefan · 14 May 2005

unkargherth wrote: stefancrs wrote: Or you could just use one designer for all knobs... Which is what I would've done

It depends . You can feel ok all knobs in your project looks exactly equals, But other developer not. Seems a nosense having a readout in a quantized knob that selects a waveform that is already drawn in other place. Also No all knobs should be quantized equally or be quantized at all

I did ofcourse mean for all knobs that are supposed to look and behave the same. Not all my knobs in nildon are synced with each other, but all the ones behaving the same are. So I thought it'd be a good idea to let a designer connection for any "knob style" you use stream down your schematic hierarchy. Obviously, there could be better ways to handle it, and no doubt, there will be. Not all data in a knob has to be instanciated per knob instance, so some kind of resource management could be good within SM.

jorge · 15 May 2005

unkargherth wrote: So we need a decent way to STORE the knob params, and preferably not in the preset, as if some user watch deeply, don't find 12*12=144 Params per knob configuration only.

Any idea? Maybe malc or jorge could suggest something ?

I'm working on new components that will allow you to create your own custom parser to extract values from text

Long term it will probably evolve to allow a custom compiler to be created inside SM with syntax colouring etc. The initial version will be ( probably is already ) enough to process text data and extract relevant info from it.

On the other side, you need to generate a text file from the colours, values etc in the front panel of the knob designer but that should already be possible as floats get converted to strings and you can already concatenate strings. So if you transform the values of the knobs, buttons, selections etc to text, you'll be able to use that text instead of the Bus. Or even better would be if you create a BusToText module.

Creating components to save/load the text to/from a text file should be really easy.

unkargherth · 15 May 2005

Wow !!!!. Let me Repeat: Wow !!!!

question: When ? when? when?

(Only joke: take your time....)

Tom7777 · 15 May 2005

Cool jorge, that looks great 🙂

Nu Audio Science · 15 May 2005

Niiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiice 😮

Shifrin · 15 May 2005

That's fascinating stuff there Jorge, so many possibilities!!! 😀

Shif.

jorge · 15 May 2005

Here's an example of a custom parser:

The state of the panel is converted to a string which is then converted back to the state of the panel using a custom parser. Here is the schematic: [old link] For this schematic you need the latest version of SM: [old link] Please note that this is all experimental stuff and the new components are still beta components inside a beta application. The parsing components are not yet prepared for feedback connections.

Tom7777 · 15 May 2005

Thanks jorge, amazing as always 🙂

skOre · 15 May 2005

This is _so_ amazing!

unkargherth · 15 May 2005

Couldn't resist to do it: Custom Parser Atoms

This Is a mini set of Custom Parser Atom converters. Nothing fancy, only toolsfor fast settting and extracting params from a ParamString. They Convert ONE value to ONE pramStr or reverse. Supported types at this moments are Floats Ints, Areas And Colours. Get it here

Jorge. I noticed theres no way to extract strings from ParamStrings. Is this a feature, something you forget, a "Pending to implement issue" or will never be implemented ?

Anyway, Damned good idea, jorge

NothanUmber · 16 May 2005

Hey, now things start to become really interesting. A parser was pretty much on the top of my most wanted features list, that should open many nice new possibilities. 😀

jorge · 16 May 2005

unkargherth wrote: Jorge. I noticed theres no way to extract strings from ParamStrings.

Here is how I'd do a parser for extracting two alphanumeric strings separated by a comma:

[old link] it requires the latest SM: [old link]

Tom7777 · 16 May 2005

This is amazing 😮 🙂

lalo · 16 May 2005

wow jorge!! these days you're goin faster than light-speed 🙂

unbelievable!! nice!!!!

lalo

Shifrin · 16 May 2005

What lalo said 😀

Shif.

malc · 16 May 2005

What Shif said lalo said 😀

Malc.

stefan · 16 May 2005

jorge: fu, those new components (and the simple calculator as well) kick major ass. I have a hard time grasping what is possible and not with SM atm.

unkargherth · 16 May 2005

unkargherth wrote: Get it here

New version. Redownload. SAme link. Changelog on .osm

skOre · 19 May 2005

Lookie what I found 😉

Nu Audio Science · 22 Jun 2005

Unk take a look at my knob designer project i think it may be a natural extension to this and also solve the problems of having too many components 😉

TheAudiophileDutchman · 11 Jan 2006

After testing the great looking TDKnob v0.2 and v0.3 for the first time, I'm reporting the following: under the current SM beta, the knob disappears after a value change; either by mouse dragging directly on the knob's surface or by changing the slider-position (which is used as a [0..1] input for the knob). 😮

Is this perhaps because something changed in the redraw behaviour of SM during the past Months? How to change this in the TDKnob schematic? 😇

infuzion · 11 Jan 2006

TheAudiophileDutchman wrote: After testing the great looking TDKnob v0.2 and v0.3... under the current SM beta, the knob disappears after a value change; either by mouse dragging directly on the knob's surface or by changing the slider-position

Yea, there's something wrong w/the knobdesign (prefs) module or how the knob uses the info. If you turn off all the switches on knobdesign (you won't see the swich change unless you move in/out of the module due to a bug), you'll see the knob come back.

This knob prob should be re-designed; use wireless instead of bus for prefs, simplify code, etc. But it's still a cool knob.

TheAudiophileDutchman · 16 Jan 2006

Hi Infuzion, 🙂

Thanks for helping out!

flamingRedDingo · 19 Oct 2010

I use tons of knobs in my projects. It is not uncommon for me to expose 16 or more knobs in my UI projects.

When I started coding in SM, I too, wanted a knob that was "all things to all people"

Then I got mugged by reality.

SM is not very efficient when it comes to complex UI interaction. Even IF you cleverly section off whole sections of your trigger code when not in use to cut down on CPU, the resulting mess is bloated and very difficult to maintain.

On the other hand, having a SUITE of knobs (bitmap vs. vector) allows the knob control code to remain simple and relatively efficient, even if it's not as flexible...

It would be nice to create knobs with as many features as possible packed into them - so long as bloat and inefficiency can be curtailed, but this isn't possible with some features ...

Take the bitmap vs. vector feature: You need two completely separate display modules to render the thing, and let's not forget how large the property page would get with all of those options!

It would probably be more generally useful to post a complete control suite, (including Midi cc'able momentary pushbuttons, toggles, knobs, radio buttons, horizontal sliders and vertical sliders)

It just so happens that I am working on the vector based versions of the above mentioned components... I'll post them after my multi-loop thing is finished =)