sending Strings over Ethernet, Bug, Question

1. I can't send strings when they start with a slash e.g. "/ard/pin9"

2. Is there a way to send any ascii char, that means none printable chars or hex bytes like 0x00?

Parents

0 sstaub over 10 years ago

to 1. "/" will interpret as an OSC-Cmd
0 ueliriegg over 10 years ago in reply to sstaub

in some program languages you would have to escape the character, i.e. mark the following character as something special. try "\/ard/pin9" (backslash forward slash). just a guess, no idea what will happen ;)
0 sstaub over 10 years ago in reply to ueliriegg

Hi Ueli,
I have tried the "\", but it doesn't work. Only the slash at the beginning will recognized as a special control char for OSC.
0 ueliriegg over 10 years ago in reply to sstaub

ah, but just to clarify: are you trying UDP strings or OSC?
0 sstaub over 10 years ago in reply to ueliriegg

first i tried to do an udp string, but with a slash at the beginning the udp string becomes an osc message
0 miz over 10 years ago in reply to sstaub

Hello,

Yep, this was an oversight - thanks for the report :) Will be fixed in the next 2.3.2 beta build...

RND 0032588: Magic Sheets - commands with "udp:" prefix should never be sent as OSC

Reply

Children

0 miz over 10 years ago in reply to miz

Oh, and there is currently not a way to specify a raw packet. Added to the list:

RND 0032589: OSC/UDP - add functionality for specifying a raw packet in hex (like "0x00,0x32,0x65")
0 ueliriegg over 10 years ago in reply to miz

chris, how would i force UPD or OSC when executing from a cue?
0 miz over 10 years ago in reply to ueliriegg

I could add the same "udp:" qualifier there too...?
0 ueliriegg over 10 years ago in reply to miz

great! for me OSC is the default anyway, so i would hate to add more keystrokes to OSC strings...
0 sstaub over 10 years ago in reply to miz

good idea, may you can extend the qualifiers with methods for sending OSC over TCP1.0 or TCP1.1, that would help to control programs like lab with safety, or to change the destination when using more than one OSC-machines.
0 Paul Toben over 10 years ago in reply to sstaub

It would definitely be great to be able to specify an IP address. something like "<protocol>:<ip address>:<payload>"
0 sstaub over 10 years ago in reply to Paul Toben

+1
what you mean with payload, port? e.g. osctcp11:10.101.90.100:53000 (osctcp11 for SLIP, 53000 port for qlab)
maybe "lloopback", "localhost", "broadcast", instead of the IP-Adress
0 Paul Toben over 10 years ago in reply to sstaub

Sorry... that should have been "<protocol>:<ip address>:<port>:<payload>" where "payload" is the string you want to send.