How to trigger by osc "scenes" on ableton live from eos nomad?

I tried getting that type of thing working myself a while ago and was never successful. I was never able to get Eos to output arbitrary OSC strings for Qlab. At the time I did not have wireshark, but I spent an entire evening on it with no luck. All I ever got was either no result whatsoever or syntax errors. 

eos moderator I have never once in my entire life gotten a single OSC message using the "=" to work as expected with Eos. All the documentation on that appears to be patently false (so every single page of the OSC documentation is flat out wrong). Eos uses a space " " to separate incoming address and argument, not "=". Yes, I know I'm directly contradicting the documentation. The documentation is wrong. Try it yourself. The space " " works and "=" does not. Maybe there's a really specific scenario where the "=" does in fact work, but it most certainly is not reliable in any regard. The space " " works 100% of the time.

I tried getting that type of thing working myself a while ago and was never successful. I was never able to get Eos to output arbitrary OSC strings for Qlab. At the time I did not have wireshark, but I spent an entire evening on it with no luck. All I ever got was either no result whatsoever or syntax errors. 

eos moderator I have never once in my entire life gotten a single OSC message using the "=" to work as expected with Eos. All the documentation on that appears to be patently false (so every single page of the OSC documentation is flat out wrong). Eos uses a space " " to separate incoming address and argument, not "=". Yes, I know I'm directly contradicting the documentation. The documentation is wrong. Try it yourself. The space " " works and "=" does not. Maybe there's a really specific scenario where the "=" does in fact work, but it most certainly is not reliable in any regard. The space " " works 100% of the time.

The Eos manual states at the beginning of the OSC chapter:

Arguments

OSC arguments are additional data for a command that can be appended to the string
following the method.

Eos uses the = character in OSC strings to separate the method from any subsequent
arguments. Third-party OSC software often requires a different character, and may not
be able to interpret incoming strings that use =. Consult the documentation for your
OSC software to determine the appropriate character to append arguments.

And that's exactly how it behaves. When sending OSC from Eos you use a = to separate the address from the argument. What other software uses to signify that separation is not in the realm of Eos or its documentation.

I'm talking about OSC inputs into Eos. In other words the documentation that instructs me how to form OSC messages to be sent to Eos to control Eos parameters.

Documentation states that "/eos/chan/1=100" should bring channel 100 to full. It doesn't. However, "/eos/chan/1 100" does work. That's consistent for all other types of commands. Domentation instructs me to separate address/argument with "=" but it never works. " " always works.

The documentation instructs to use /eos/chan/1=100 where = is the character your 3rd party software uses to separate the OSC address from the argument.

If that's what it says, it should say that. It doesn't.

Like I can programmatically send Eos a perfect string of "/eoschan/1=100" and I can verify that Eos is receiving that verbatim, and it doesn't work. I have never once read anything in the documentation ever that states the "=" is just a placeholder and is not meant to be part of the string. For crying out loud, most people don't even understand that OSC consists of address/argument. The documentation is seriously broken.

With the = as a spaceholder It worked perfectly fine. I used the command which ableton needs but instead of using the space I used =. But I agree that this information was crucial for it to work and before I wrote in the forum I nowhere found this information. Would be great to mention it. Thanks anyway for the help, the show runs now perfectly.

Thank you for keeping us up to date.