Use manual commands while OSC input is active

Question

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&eacute;bastien

eos moderator · Answer

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.

eos moderator · Answer

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.