Hi Camille,
It would be invaluable for integration with QLab to be able to decode their JSON-strings that is their default reply format: http://docs.figure53.com/qlab/osc-api-v3/#reply-format
encoded in these strings are 1-n fieldname:data value tuples/datasets, and if those could be automatically decoded and split like for example the MIDI Notes (where you look at pitch, velocity, and trigger for every note received), then the contents could be re-routed sensibly to other applications !
I would be so stoked (but I am sure I would not be the only one )! This would allow i.e. to set motorised faders to assume the positions as you select i.e. and audio cue, so would allow for bi-directional integration of control surfaces...
Cheers,
Freddy
It would be invaluable for integration with QLab to be able to decode their JSON-strings that is their default reply format: http://docs.figure53.com/qlab/osc-api-v3/#reply-format
encoded in these strings are 1-n fieldname:data value tuples/datasets, and if those could be automatically decoded and split like for example the MIDI Notes (where you look at pitch, velocity, and trigger for every note received), then the contents could be re-routed sensibly to other applications !
I would be so stoked (but I am sure I would not be the only one )! This would allow i.e. to set motorised faders to assume the positions as you select i.e. and audio cue, so would allow for bi-directional integration of control surfaces...
Cheers,
Freddy
Comment