search

ossia / score

ossia score, an interactive sequencer for the intermedia arts
https://ossia.io
Other
1.45k stars 101 forks source link

sending impulses doesn’t seem to work to MadMapper #1464

Open bltzr opened 1 year ago

bltzr commented 1 year ago

I don’t know if this is ossia’s or MadMapper’s fault, but nothing happens when trying to send an address @type impulse from within a state to MadMapper sending [FIRE] from OSCQueryBrowser, or just the address as an OSC message from Max works, though

jcelerier commented 1 year ago

hmm so checking the OSCQuery data that madmapper sends, things that sound like impulses use the OSC "N" type which from the spec: https://opensoundcontrol.stanford.edu/files/2009-NIME-OSC-1.1.pdf means "Null" : Null: (aka nil, None, etc). No bytes are allocated in the argument data

in score I had assumed that this means that there's no actual message in there but I can easily make it so that OSC "N" is mapped to an impulse

jcelerier commented 1 year ago

hmm and sending "nil" OSC messages seems to work for madmapper indeed.. I guess we have to add some metadata in the ossia objects that tell if the "impulse" will map to "I" or to "N"...

also just sending nothing in the type tag seems to work

jcelerier commented 1 year ago

what do you think of just sending a message with no data at all for the ossia::impulse case (instead of the current I) ? this should not break ossia afaik but maybe needs testing with Vezer and others

jcelerier commented 1 year ago

@bltzr what does it give with current builds?