Version 3.3.0.189
the osc "max" syntax is lost
"/eos/chan/<number>/max" or "/eos/at/max" or "/eos/param/<parameter>/max" doesn't work anymore
workaround: use full instead
Version 3.3.0.189
the osc "max" syntax is lost
"/eos/chan/<number>/max" or "/eos/at/max" or "/eos/param/<parameter>/max" doesn't work anymore
workaround: use full instead
I can confirm. Their new(ish) manual and OSC dictionary is a big improvement over the former. But I send this:
OSC: -Address: /eos/user/1/at/max -Argument:
While "Chan 1 Pan" is currently on the console, and when I send it, it just puts up an Enter diamond. All the current verbiage indicates this should work and I can't find any verbiage stating this is an intended breakage.
I can also confirm replacing "max" with "full" works as expected.
I have also been having issues with max, specifically in the IRFR app. I imagine the functionalities are linked. Pressing max on parameters under ML controls no longer works. RFR 4.1.6
Thank you for reaching out. We can see this as well and are currently investigating. As soon as we know more I'll update here.
Thera are also many other bugs and feature requests with OSC which should solved.
This is written up as:
[EOS-57473]
OSC: /max broke to set channel levels & parameters, impacting RFR control
This was fixed in Eos 3.3.2.
www.etcconnect.com