maybites

I just looked at it as a unit that stands for itself and not in relation to others. like pixels: you cant really set it in relation to the other...

I guess the term 'remotely' is a bit vague: it could mean: 1. setting the parameter via [ossia.remote] 2. or/and setting the parameter via OSCQuery or Minuit or OSC. I...

I had another closer read of the docs: `Defines the way the value of ossia.parameter will be accessible : when set at GET, the value can only be retrieved, when...

``` One thing we could then add to @mode set's doc is maybe, e.g.: Defines the way the value of ossia.parameter will be accessible : when set at GET, the...

the topic of 'remoteness' is not resolved. does it apply only to remote apps that communicate via protocols like OSC, OSCQuery or Minuit. or does it also apply to 'local'...

well, I think this should be decided by those that have the practical experience. and understand the implications on the implementation. > So I would say it applies to both...

I think the definition explains the agreed behaviour: ``` Defines the way the value of ossia.parameter will be accessible : when set at GET, the value can only be retrieved,...

we should forbid * to modify a parameter's value with mode 'get' from ossia.remote * to receive a parameter's value with mode 'set' from ossia.remote, except on creation time of...

@avilleret I wonder if [ossia.monitor] would already cover some of this functionality? (I cant test it since its help file says its currently defunct).

the question is if [ossia.monitor] or [ossia.remote] can cover some of the above mentioned functionality. [ossia.remote //*] seems to capture all changes to parameters, so it covers @outputmode 1. [ossia.monitor]...