• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    n9yty
  • Date
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 92 subscribers
  • Views 3238 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

  • 0

    /eos/subscribe/param/Intens=1 is misleading you must send /eos/subscribe/param/<parameter> with an int32 argument / value (0 or 1).
    And yes the documentation is not the best, many things are missing / added and configuration on EOS is     complete new with 3.2.

  • 0

    Are there no examples of how to actually make this work?   commented, but I did exactly that. After trying it in the path, I did it by using the path as was mentioned with a boolean parameter of 1. Still it caused no new messages to come in upon changes.

  • 0 in reply to n9yty

    This depends from the application you use.

  • 0 in reply to sstaub

    I am literally sending OSC directly to EOS, no application except me and the one I want to build.

  • 0 in reply to n9yty

    Which software did you use for sending?

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

  • 0

    Ok, I can see I won't get an answer here, but I guess this is not an official support forum.  I have sent the command, so it doesn't even matter what software, and I see it RECV in the EOS debug window, but it doesn't send any matching out commands related to it or when values change. Never mind, time to move on.

  • 0 in reply to n9yty

    We want to help but without knowing how whatever software you are using defines the address separate from the argument we can not assist.  I tried to give examples of how I have done it on one piece of software.  If you could supply some additional info we could help.  If you include images of the incoming message from tab 99 in the eos software that may help us diagnose what is happening.

  • 0 in reply to Druuka

    Here is a pic of tab 99 where I subscribed to the intensity parameter maybe this will be helpful.  It may be that you don't have some other setup option turned on... knowing what software you are using will help figure that part out as well because there are multiple methods of connecting to the console with osc.

  • 0 in reply to n9yty

    If you are writing your own software then other questions come to mind.  What connection method are you using? UDP or TCP? Have you tried sending to a piece of software that you can have bounce messages back or log so you can see the exact message?  Diagnosing your IDE and personal software is very difficult since it its still unclear if you understand OSC in its methods and practices. If you are looking for coding examples of how to make this work we need to know what IDE and software/hardware you are developing on.  What does your packet look like in Wireshark?  What does the Diagnostic tab in Eos show.  Pictures might be helpful.

www.etcconnect.com