this is my first post in this forum, but I’ve been following the conversations in here for a while and found them to be very productive and I am glad there are many people active here who really know their stuff.
My problem concerns inverted buttons and sliders. Inverted in this context means, that the Invert Value Checkbox in the tab Value of the widget properties is checked:
When using such buttons with the current Lemur template, I noticed that if i activate an inverted button in Lemur, the corresponding GP button widget is activated too (as would be expected) whereas if I activate the button in GP, it is deactivated for Lemur and vice versa. I have uploaded a minimal rackspace which shows the problem: https://www.dropbox.com/s/5uaukk0ob7vdo79/Inverted-Buttons-OSC.gig
I have further investigated the issue and found the following:
By looking at the “raw” OSC messages between GP and Lemur it was clear to see that GP sends out inverted values for the buttons (in the example rackspace consider the adress
/Button3/SetValue) so it is likely for this to be a bug in GP rather than the Lemur template.
Aside from buttons, sliders and knobs are affected as well.
The inversion occurs not only when moving the widgets “live” in GP, but on (variation) recall too.
Interestingly, when pressing Refresh in the Lemur template, the Lemur buttons/sliders/knobs receive the “correct” values (as in: as I expected).
Did I overlook something? Should this be expected behavior? (And if so: Why?) Or is this just a bug in GP?
Thanks in Advance
This was tested using Gig Performer 3.2.7 on Windows 10.