Quote:
Originally Posted by philait
+ OSC: support for binding messages to FX learn
+ OSC: support for multiparameter messages
+ OSC multiparameter example: /track/1/fx/3/fxparam/1,4 (with 2 arguments) sets 2 FX parameters at once
# OSC: various fixes for controller feedback, preventing flooding, etc
[...]
|
Thanks for the additions and fixes!
With regard to flooding, I'm beginning to think it doesn't make much sense to expect messages corresponding to all effect parameter names and values at every refresh.
Schwa, could you please also explain a bit what messages are supposed to work bidirectionally, which are only supposed to be sent out, and which are only supposed to be received? Initially I thought that all messages in the config are supposed to work bidirectionally, but after thinking a bit more about it, I'm starting to have second thoughts. It would make more sense to e.g. send a track + slot number to REAPER, and then get the effect's name / parameters / values back.
Maybe it would be useful to make the direction of messaging user configurable, by means of flags or something similar? (e.g. -S: send only / -R: receive only / -B: bidirectional)