• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    n9yty
  • Date
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 87 subscribers
  • Views 1488 views
  • Users 0 members are here

What am I doing wrong with OSC subscriptions?

I'm trying to subscribe to some parameter updates....  So many holes in the documentation, and so many versions of the documentation floating around...

It looked like, from the v3.1.0 User Manual that you could just send it as an OSC command:

/eos/subscribe/param/Intens=1

I get a message that "enable/disable" is missing. So I passed it in not as part of the path but as a separate argument, 1, and that didn't return an error, but it also doesn't send me updates when intensity changes.

Without being able to find any good examples, I have to ask what I am doing wrong.

The docs seemed to say that I should be seeing this in the output:

/eos/out/param/intens

Unknown what values it returns since that isn't documented and I can't get it to send anything. Slight smile

Parents
  • +1

    What software are you using currently?  I would suggest something like touchosc to use and better understand the OSC language that Eos speaks.  Each OSC message is an address "/eos/something/blah" and an argument which is often a 0 or 1 but sometimes a string of text like "Cyan".  and example message would be

    /eos/subscribe/param/red (this is the part that is confusing because depending on what software you use it is defined differently) 1

    the = sign is just what eos uses to differentiate between the address and the message if you are creating the message in eos software.

    This is an example of in Tab 99 of and Eos console of it receiving a subscription and the usual response when it has at least one channel with that parameter.  

    And the message setup in touchosc 

    I hope this helps you understand how OSC works with Eos a bit better.

Reply
  • +1

    What software are you using currently?  I would suggest something like touchosc to use and better understand the OSC language that Eos speaks.  Each OSC message is an address "/eos/something/blah" and an argument which is often a 0 or 1 but sometimes a string of text like "Cyan".  and example message would be

    /eos/subscribe/param/red (this is the part that is confusing because depending on what software you use it is defined differently) 1

    the = sign is just what eos uses to differentiate between the address and the message if you are creating the message in eos software.

    This is an example of in Tab 99 of and Eos console of it receiving a subscription and the usual response when it has at least one channel with that parameter.  

    And the message setup in touchosc 

    I hope this helps you understand how OSC works with Eos a bit better.

Children
No Data
Related

www.etcconnect.com