• State Suggested Answer
  • Date
    sschiesser
  • Date
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 87 subscribers
  • Views 978 views
  • Users 0 members are here

Use manual commands while OSC input is active

Good morning

I'm experimenting with OSC input for receiving intensity or color values for specific fixtures from external sources (e.g. RGB values from video or audio level). That works pretty good!

But I noticed that every time an OSC command is coming in, it clears my manual prompt. For example: with OSC coming every 2 s, I'm currently typing Chan 2 @... and if the input has arrived before I press Enter, the prompt gets deleted. Not saying of course when my OSC stream is much faster.

Is there here a workaround to work with both inputs in parallel or should I start building an external command line that controls EOS over OSC? :-(

Thanks for your advices!

Sébastien

  • 0

    I guess you're sending /eos/cmd or /eos/newcmd commands to your console?

    The two measures that would improve your experience are:

    • Try using /eos/chan syntax. Not all commands are possible but this syntax would perform better because it doesn't have to write to the command line.
    • Look into sending your OSC messages to a different user. By default you'll be using the same user ID as your console. When sending to a different user ID you'll automatically get a separate command line.
  • 0 in reply to eos moderator

    I'm actually sending /eos/chan/x.y val since I have cells in my fixtures.

    Just tried to send to user 2 (/eos/2/chan/x.y val) while have user 1 activated. No change is noticeable: values flow in from user 2 correctly and I still can't get my command line. Should I make some changes in the User Settings?

  • 0 in reply to sschiesser

    You can either send /eos/user with an argument of 2 when connecting and all subsequent OSC commands will be sent to this user, until the connection is closed and a new one is established.

    Or you can do what you tried and preface each OSC command: /eos/user/2/chan/... You seem to have been missing the word user in your OSC address.

  • 0 in reply to eos moderator

    Indeed! Now I really send OSC commands to user 2... and receive nothing when user 1 is online. Thus how do I get access to my separate command line?

  • 0 in reply to sschiesser

    Are you attempting to have the user 1 channel selection mirrored to user 2 so that the osc commands feed user 2 while basing the channel selection on user 1?  It is a bit unclear what you are hoping to have on your command line.  

    Each user has their own command line that feeds changed into the manual values and stage that all users can see.  Each user gets their own channel selection.

    Please elaborate on what you want it to do so we can help advise.

  • 0 in reply to Druuka

    Yes somehow like that. I have standard manual channel selection & settings (for now while rehearsing), while intensity & colors of some fixtures are controlled by an external app sending OSC.

    Currently I always have to first stop the OSC flow to make manual changes. I can imagine that on production, everything will be controlled by OSC, but we are far from that yet ;-)

    Do you mean I should assign the OSC-fixtures to user 2 and keep the others for user 1? Or can I share channels?

  • 0 in reply to sschiesser

    you can "share" channels but user 2 won't follow your channel selection.  If you are doing channel selection and action over osc then the osc stuff will all happen without user intervention.  If you need to choose the channel for osc to interact with then the separate user is more complicated.

    I would suggest having osc controlling channel selection and action for those lights it will affect. 

    This will allow you to select and control any fixture you want while user 2 takes care of the osc fixture control.  

Related

www.etcconnect.com