Ruby Double Slider

[billv]

A ruby double slider.

Test_Ruby Double Slider.fsm

(288.02 KiB) Downloaded 1307 times

In this fsm it uses the FS Preset Manager
Slider works ok but preset solution still buggy..
EDIT:
UPDATED VERSION FURTHER IN ...
http://www.dsprobotics.com/support/viewtopic.php?f=3&t=2668&start=10#p13682

[RJHollins]

Very interesting Billv.

I also noticed the knob design .... bitmap and ruby ...

hmmm ... somehow you have a design that can be vari-stepped ... using the same bitmap.

I would like to understand how this was done. I've been working on a vector-based design to do this.

Maybe at some point you find time to share some background info on the design technique. I could sure use some more learning on this [and all things GUI].

Thanks !!!
look to test this example schematic

[billv]

I also noticed the knob design .... bitmap and ruby ...

the bitmap is jay and the Knob is Trog...
http://www.dsprobotics.com/support/viewtopic.php?f=3&t=1692#p7804

I would like to understand how this was done.

No idea..pass...see Trog...

look to test this example schematic

the preset setup is still buggy...

[billv]

This uses my preset manager...same slider...seems to be faultless.
no traces of bug that appears in first fsm using the FS PM..
Dosn't need that extra trigger from pm either...

Test_Ruby Double Slider_v2.fsm

(290.33 KiB) Downloaded 1142 times

i think I'm gonna stop building to FS PM spec altogether.

So the slider works...but you'll have to find your own preset solution.

[trogluddite]

hmmm ... somehow you have a design that can be vari-stepped ... using the same bitmap.
I would like to understand how this was done.

Cheating!
IIRC, the knob always stores the current, unstepped float value internally. The stepped output and the frame number of the bitmap are rounded independently of each other.
If you have sufficient animation frames, the pointer will look about right for most small step counts - anywhere within a few degrees will be close enough for the typical size of a control. Or you could load an animation that has the same number of frames as you have steps (can save memory if the count is small).

Jay's gorgeousl graphic has 128 frames, so is exceptionally smooth.
With the stock knob you have to be careful with that, as more frame transitions = more redraws = bigger CPU load when dragging the control. But the Ruby code in this one uses an internal timer which restricts the redraw rate to prevent that problem. The output value remains unrestricted, so that the actual value can move more smoothly.

If you tried, say, having three steps, but used a four frame animation, you probably wouldn't get what you expected - a frame would be skipped somewhere in the middle!

[Nubeat7]

about the pm issue, i had some similar issues with my xy pad, i think the problem is when you get more then one preset parameters from different presetmodules into one ruby module, further in your schematic it is updating double time - because you also get a trigger from the knobs...

i solved the PM issue in my xy pad with using a preset parameter array with 2 values, you can output it like this

Code: Select all

output 'presetvalues', [@rvalue,@lvalue]

maybe i would go another way here and update the knobs from the doubleslider module to have them updated and also set them on presetchange, this are 2 pm values less and you avoid doubletriggering on presetchange

[billv]

using a preset parameter array with 2 values

i thought about that at one stage, but went the other way.
i will try this, and give the FS PM one more go..after all,
i shouldn't have to need 'about close', 'afterload' and 'trigger delay's' to make this happen.

i think the problem is when you get more then one preset parameters from different presetmodules into one ruby module

i thought that too but changed my thinking, cause there's no bug with my PM.

[Nubeat7]

here is the link for the xy pad, the last version uses preset parameter array..
viewtopic.php?f=3&t=1121&start=20

[billv]

I did find one piece of bad code, where the interact is turned on during
external input. Seem to make no difference though.
Most attempts today went via array preset method...none worked
I'm starting to be convinced its just bad coding/design somewhere.
I just saw your post now nubeat7, and downloaded.
But I noticed in yours there's one slight difference.
Your keeping the array intact...today i was breaking array down into the two inputs.
I tried it for a while...still no good here...same buggy result.....
At a loss ATM...
I got a module with correct inputs/outputs.....and still can't make it work with FS PM.

[Nubeat7]

i investigated some time into your doubleslider, to find a solution which also includes the external setting with the knobs, which btw complicated the things, it seems i had found some way to make it work with the stock PM,

finally i also overworked some parts of the code, which i wanted to avoid to keep it as original as possible, but i could't resist it was too interesting for me, its basically the same i just did a couple of methodes to avoid repeting the same code a few times and simplyfied some parts.. hope you also like it, and don't feel highjacked!

anyway if you load the schematic it seems that there is still some issue on loading, for a short time it shows a ruby error which i think is gone after the pm parameters are loaded ( to better see this save the project when you are inside the ruby module and reload it), the error is happening in the event methode (looks like it asks for the Preset input array which is nil) which i don't completely understand because there should only happen things when a trigger comes from the PM parameter array which shouldn't be nil when it comes from the Pm!?

i couldn't find a solution for this, i also tried to use the save and load state methodes and init methodes butnothing changed this, some guru skills are needed here..