Collaborative project!

[ustk]

@hisefilo Just pushed the "More" panel and interface code cleaning

[ustk]

@hisefilo Do you want the drawbars to be stepped?

[hisefilo]

@ustk mmmm never thought about it. ..... what do you think??

[lalalandsynth]

@hisefilo They are stepped. Rendered as 9 steps . 0-8

[ustk]

@hisefilo both are good, it could be a custom setting later in a pro version so let say this one can be stepped

[lalalandsynth]

@ustk Also saves bit of memory :)

[ustk]

@lalalandsynth @hisefilo Ok so I doing the stepping code...

[ustk]

@lalalandsynth Don't forget to stitch the strip in reverse order

[lalalandsynth]

@ustk Ok, so what is the rule here , why in reverse order ?
Also , for switches ?

[ustk]

@lalalandsynth Because when a drawbar is fully opened (at 8), the knob is at 0
So the first image in the strip is 8, and the last image is 0

[ustk]

@hisefilo @lalalandsynth Drawbars are ready to receive the filmstrips

[lalalandsynth]

@ustk Yep, should be a way to flip value of a slider easily , but yes , will make sure of that .

[ustk]

@lalalandsynth It's not because of the values in fact but because of the mouse.
With a knob, the value is going up and down when the mouse goes up and down, so both the value and the filmstrip have to be inverted.
If we were using script panels, I could have made the code the way we want independently from the mouse movement.
So if it's a problem, tell me and I can change the knobs for script panels ;)

[lalalandsynth]

@ustk Bt sheer luck it is rendered in the correct way :)

[lalalandsynth]

@ustk Yes, At some point i expected to just be able to invert the values in min max properties , felt intuitive.

[hisefilo]

@ustk @lalalandsynth sliders are already inverted. So just inverting the strip as @ustk said will do the trick

inline function onKnobDrawbar4Control(component, value)
{
	SimpleGainMain4.setAttribute(SimpleGainMain4.Gain, 100 * (1 - value) - 100);
};

[ustk]

@hisefilo I simplified the code and made it compatible for step behavior.
Pull the git if you wanna have a look :)

[ustk]

@hisefilo Also the skew factor is fucked up because the knob doesn't respect a log curve. The result is that we hear the sound only between pos 5 and 8, nothing before. Will check if a valueNormalized can help...

[hisefilo]

@ustk shoul be linear. not logarithmic as gain is...... I guess

[ustk]

@hisefilo The issue is that the knobs are necessarily linear. But if you just apply a factor 100 to it and map it as gain, the dB scale is not respected.
If you test your code above (mine has the same issue), we begin to hear a tone only from the midpoint

We need to use a valueNormalized applied to a dummy knob set in decibel, so it will convert to the right scale for us. I remember having this issue and that's what Christoph suggested.