[Solved] Preset Bug in Trogs ruby Bitmap knob

[Walter Sommerfeld]

Hi guys,

found this nice knob in my toolbox...

If i save the actual program i see the actual knob value -
but when i switch to the next preset it's back 2 it's previous value

someone has a clue for me?!

[tulamide]

Wow, this is a tough one!

Scenario:
Preset 1, I changed the value from 0.14 to 0.7. Switched to preset 2, then back to preset 1. Shows 0.14. Now investigating code/routings

RubyEdit works correctly. I "watched" all variables Trog used, and they all say 0.7 . Just the input "from_preset" is at 0.14, which is strange. It becomes even weirder.
Since Ruby works I look at the VST preset module. The "Preset Value" input is at 0.7, the "Display String" input is at "0.14 blobs" and the Param-Prim's "current value"-output is at 0.14

I suspect the Param-Prim not working correctly, but I don't know why.

[Nubeat7]

try to set the lock flag in the presetmanager on and off again, it looks like that the presetmanager primitive doesn't recognise this flag correctly...

[Spogg]

try to set the lock flag in the presetmanager on and off again, it looks like that the presetmanager primitive doesn't recognise this flag correctly...

This is interesting to me because I found the Lock flag doesn't do what I expect in any of my projects.

[Walter Sommerfeld]

Nope Rene,

forgot 2 add another 'normal' knob - this works so the lock isn't the problem here - i think...

like tulamide mentioned - it seems 2 be really a tough one this time... i could live w/o it's working in my actual project but you know: we are curious

btw:
Another effect if added in my never ending big master controller emulation project is
that if i control it remotely (Midi or set value) i get a very low redraw rate w/o smoothness

[Nubeat7]

@walter just worked here.. fs 3.06

[tulamide]

@walter just worked here.. fs 3.06

That makes it even more tough. I'm on 3.0.6 as well. Did you change anything?

[Nubeat7]

as described above, just set the lock flag on and off again... nothing else.

[tulamide]

as described above, just set the lock flag on and off again... nothing else.

Sorry, but I thought of that as well - it didn't change the behaviour. So, either you are a special case, or there is more to it than just toggling on/off.

[Nubeat7]

no, just that on my machine, i also doublechecked it with downloading the original fsm from the first post, tried it - error confirmed - toggled the lock on / off - and it works as it should!