UDP syntax (control) - specifically EOL

[KlankOntwerp]

Hi,

I would like KiOSC to control certain devices, but I am running into an issue with the implementation of UDP within KiOSC.

Firstly, I understand that (right now)  I cannot fully control the syntax (so I cannot send a fader message like "volume -60" where -60 is the variable sent by the fader). That is why all I can and will use is buttons which can send fixed strings. Anything else is a 'nice to have'.

The real pressing issue is that messages are closed with NULL ( \00) in stead of EOL (\0a) which means that the other program never registers the sent message. Could there be a way to define the control characters so it can be changed to \0a (or maybe even customized for devices listening to ETX)?

[Julien Levaufre]

For now it is not possible to select in Kiosc editor what kind of character you wan to use for the separation between the tag and the data, and for the end of message.
The /00 we are using now is compatible with a lot's of the 3rd party controllers that our customer are using, and this is the first time we have a feedback with this kind of problem.

Could you tell me what device you are trying to control with Kiosc, to let me see if I can find a solution for you?

I will add your remarks to our wish list and see how we could improve KIOSC about those features.

[KlankOntwerp]

I am using 3rd party software that needs the line feed. The UDP string input field is interpreted as 100% ASCII, right? I've tried using \n but that is also directly converted to ASCII. If I can put the newline character in front of the \00 I am probably saved for now too (have to check but I think I would).

[Julien Levaufre]

Yes, it's right anything typed is interpreted as ASCII, so even if you type the "\0a" in the input field it will convert each characters to its individual HEX value.
In the future KIOSC will be able to directly send HEX characters but for now it will only be available with TCP.