You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem when integrating with REAPER's OSC implementation: they define a t trigger type (from this mirror of their default config):
# t: trigger or toggle message. The device triggers the action, or toggles the
# state, when the pattern is sent with no arguments, or with an argument of 1.
# The feedback values REAPER sends are identical to those sent for binary
# arguments.
So: I can send the first trigger with no problem, but any subsequent triggering "1" values are never sent by osc.c.
(The workaround, at least for REAPER, is to send a 0 value before sending the trigger value: REAPER ignores any value but "1", but doing so invalidates the "cached" value in osc.c. It would be good to be able to avoid the extra messages over the wire.)
The text was updated successfully, but these errors were encountered:
Hi @OddBloke, thanks for this well-researched issue! Unfortunately it seems like Reaper is re-using the t OSC tag here, which is already defined by the OSC specification as time-tag - otherwise a solution might have been to simply implement these additional tags.
I'll need to think about a way to indicate that the event-deduplication should be disabled for specific OSC paths. I would not like to disable the deduplication globally, as that would cause a lot of events to be output when translating from backends that might not do their own event deduplication.
osc_set
inosc.c
doesn't send output on a channel if the value is unchanged:midimonster/backends/osc.c
Lines 735 to 746 in 1f31bc7
This is a problem when integrating with REAPER's OSC implementation: they define a
t
trigger type (from this mirror of their default config):So: I can send the first trigger with no problem, but any subsequent triggering "1" values are never sent by
osc.c
.(The workaround, at least for REAPER, is to send a 0 value before sending the trigger value: REAPER ignores any value but "1", but doing so invalidates the "cached" value in
osc.c
. It would be good to be able to avoid the extra messages over the wire.)The text was updated successfully, but these errors were encountered: