Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OSC commands with numbers
(11-02-2019, 02:39 AM)davidbaxter Wrote: A byte array might be better if we had control of both ends of the communication. As it is, I can't change the X32 and it wants to get a padded string (in Hex: 2F 63 68 2F 30 31 2F 6D 69 78 2F 66 61 64 65 72 00 00 00 00 2C 66 00 00 3E CC CC CD)  for the text string "/ch/01/mix/fader ,f .4". The documentation of messages the X32 responds to is a long table of similar messages with different parameters. e.g. "/ch/01/mix/mute on", "/bus/1/dyn/ratio ,i 2", etc. This is all in accordance with the Open Sound Control protocol.

UDP operates on bytes only, not on strings. Strings are transmitted as bytes. You don't need to change anything on the X32 to use byte arrays in your own code (case in point, your ToBytes() example). I think you need to read up on the correlation between 8bit strings and 8bit bytes. They are the same data. You can use byte arrays to build up your OSC messages, especially for the portions that don't involve human-readable characters. Just something to consider.

(11-02-2019, 02:39 AM)davidbaxter Wrote: 1) Is one send construct preferred over the other?

Not really. It just really depends on what you are sending - strings, or byte arrays.

(11-02-2019, 02:39 AM)davidbaxter Wrote: 2) Where should I have read/learned more about these details of Indy?

Experience, online tutorials that are floating around, maybe documentation too (though the docs are quite old - for instance, it predates the introduction of the IIdTextEncoding interface).


Messages In This Thread
OSC commands with numbers - by davidbaxter - 11-01-2019, 03:04 PM
RE: OSC commands with numbers - by rlebeau - 11-01-2019, 10:37 PM
RE: OSC commands with numbers - by davidbaxter - 11-02-2019, 02:39 AM
RE: OSC commands with numbers - by rlebeau - 11-04-2019, 05:13 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)