The definitive Knob

[unkargherth]

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]

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]

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]

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]

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]

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

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

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]

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]

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]

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

question: When ? when? when?

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

[Tom7777]

Cool jorge, that looks great

[Nu Audio Science]

Niiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiice

[Shifrin]

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

Shif.

[jorge]

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:
http://www.synthmaker.com/docs/uploads/2005/may/15/customParser2.osm
For this schematic you need the latest version of SM:
http://www.synthmaker.com/setupSynthmaker_0_9_3k.zip
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]

Thanks jorge, amazing as always

[skOre]

This is _so_ amazing!