[BUG] what happend to osc/max

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

Parents
  • 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.

Reply
  • 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.

Children
No Data
Related