where to put preset (tricky)

[tester]

I have a tricky schematic in which editbox everything works fine when is no need to put preset inside (part is just refreshed on gui). Where and how to pud preset module in order to get right readings when using preset manager?

[DigitalWhiteByte]

[tester]

1. Set editbox to 1 (editbox = 1, output = 0.5).
2. Save program.
3. Use editbox arrows to switch right (user value 0.990, output value 0.505).
4. Load program.
5: Result: editbox value = 1, output value = 0.505 = not center

As I said - it's tricky. Somewhere a trigger is missing or one too much.

[stw]

maybe now...

[DigitalWhiteByte]

I had forgotten that the edit box did not generate trig in some circumstances.

[Mo]

Better make the preset range 0-1. Also fixed the editbox arrows when you click and hold then drag the pointer out of the area, a mouse click up message was not sent.

tricky-where-preset_fix.osm

(11.31 KiB) Downloaded 56 times

[tester]

Okay, thanks for that.

Now there is one another issue I just found, "zero crossing" related. I short terms, plus zero in editbox should be equal to output = 1 (and it should express maximum range when right arrows arrows are in action) and minus zero should be equal to output = 0 (and it should express range when left arrows are in action).

I know this is weird a little bit, but this is ratio based approach for L/R panning (of slow modulator frequencies). I guess the whole design should be remade somehow, but I'm lacking ideas.

[Mo]

Not sure how it should work but here is a way to detect if it is -0 or 0.

negative-or-positive.png (5.54 KiB) Viewed 408 times

[tester]

Maybe it's better with 0-1 ranges, but these presets are also thought for manual edit. WYSIWYG so to speak; thus - all preset values must be user friendly. From what I saw, for my needs (no outside automation) - hosts like audacity, reaper and wavelab - accept these presets "as is". Second reason is accuracy policy and SM float policy. Conversion to 0-1 and back - produces inaccuracy large enough to cause problems - for example in wide frequency ranges and small frequency differences (for precise/synced spatial manipulations - processed digitally via VST).

I see what I can do with that ratio controller, thanks for tip on splitter and for fixes. I check tonight how it works. Probably this the last night on this apllication, because it's almost done.