After sending /replyFormat “#address# #data#”, there is no reply from the Qlab on UDP 53001 port.

[Tian Milo]

I'm using the max, I just want to get the data of the reply, the instructions tells me when I want to specify the reply, I have to use the replyFormat, but after I send the /replyFormat “#address# #data#” to 53000, I could not get any message from the 53001.

The udp log of the Qlab workspace status shows:
unknown client getting OSC reply: (null)

I just want to know why and what happened.

Anyone knows what happened? How I can get only one string?

Thanks

[Chris Ashworth]

Hi Tian,

I’ve attached a sample QLab 4 workspace where QLab is “talking to itself” to set the reply format.  The example output I get in the Status Window —> “Logs” tab when I run it with OSC input and OSC output both logged is:

2018-05-27 14:45:48 (483.840): UDP 127.0.0.1:53001 sent OSC message: /replyFormat "#address# #data#"

2018-05-27 14:45:49 (485.146): UDP 127.0.0.1:53001 sent OSC message: /thump

2018-05-27 14:45:49 (485.147): UDP 127.0.0.1:53001 getting OSC reply: /workspace/8E5E443B-E2A9-4B86-A8FA-61162BD845D6/thump "thump"

2018-05-27 14:45:51 (487.080): UDP 127.0.0.1:53001 sent OSC message: /cue/3/listName

2018-05-27 14:45:51 (487.081): UDP 127.0.0.1:53001 getting OSC reply: /cue/3/listName "/cue/3/listName"

2018-05-27 14:45:53 (488.539): UDP 127.0.0.1:53001 sent OSC message: /cue/4/colorName

2018-05-27 14:45:53 (488.541): UDP 127.0.0.1:53001 getting OSC reply: /cue/4/colorName "red"

Do you get the same results when you run it?

Best,

Chris

[Максим Вараксин]

Hi! 

I have the same problem. I need to receive cueNotes & displayName on my Ipad. When i send /cue/selected/notes i receive a very very very LONG message reply (a lot of text). But i need to receive only "data". Using command /replyFormat “#address# #data#” an then sending /cue/selected/notes i receive the same long_read. 

How did you solve the problem?

понедельник, 28 мая 2018 г. в 01:47:09 UTC+7, ch...@figure53.com:

[Brent Lord]

Hello --

Since the text in your notes field likely contains spaces, your /replyFormat command should have quotation marks around the #data# token so that your data payload ends up as a single argument in your reply message. Also you'll need to escape those quotation marks in your /replyFormat message with the backslash character, so that they become literal characters in your reply message rather than getting interpreted as argument delimiters when handling your /replyFormat message. For example:

/replyFormat "/myReply \"#data#\""

Brent

[Максим Вараксин]

Hello!

Thanks for replying. 

After sending these message i have the result (screenshot).

This is the one only message, which contains "status":"error"

Then when i send /cue/selected/dispalyName i receive a long_read which contains status, workspace id and other. 

Max

ср, 19 июн. 2024 г. в 02:34, Brent Lord <br...@figure53.com>:

--
Contact support anytime: sup...@figure53.com
Follow QLab on Threads: https://threads.net/@QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/cRnyeuFYGwk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/45a9b965-dc78-4f42-8977-a4c3f6599d83n%40googlegroups.com.

[Brent Lord]

I'm not certain, but it looks like your message might be arriving with everything in the "address" of your OSC message.

Be sure that the "address" portion is only /replyFormat.

The message should have a single argument, which in my example above was "/myReply \"#data#\"".

The way a Network cue in QLab parses a message string requires that you put quotation marks around the format so that it will be interpreted as a single argument. If the app you are using to send your message already lets you specify the address and the argument separately, then try without enclosing your format in quotation marks, which also means you won't need to escape your inner quotes, like /myReply "#data#"

Brent