Sending Multi-Line Text with Line Breaks from QLab 5

[Tommy]

Hi,

I want to send a multi-line text (string) from QLab 5's OSC to Resolume's text effect while preserving the line breaks.

For example:

sample text 1

sample text 2

sample text 3

sample text 4

....

Sending a single line works fine.

(e.g., /composition/layers/1/clips/1/video/effects/texteffect/effect/text/params/lines "sample text")

By the way, in QLab 4, it was possible to send text with line breaks by using 'option + return'. However, in QLab 5, an error occurs and the OSC address itself disappears.

Has the specification changed?

Regards,

Tommy

[micpool]

I can confirm your observation about QLab 4

In Qlab 5 the only work around I can find is to put your text in the notes of the cue with line breaks and use do something like this

/composition/layers/2/clips/5/video/effects/textblock/effect/text/params/lines "#/cue/1/notes#"

[Richard Williamson]

Don’t know how resolume would interpret it but you may find success by sending \r or \n in place of the line break (ie /cue/1 “sample text 1\r sample text 2"

--

Richard Williamson
www.richard-williamson.com
ric...@richard-williamson.com
07957 457 362

--
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 the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/d787a61f-f56d-4d4b-8e7e-13376988f526n%40googlegroups.com.

[micpool]

It interprets it literally!

Mic

[Tommy]

Thank you, Mic.

I see, indeed it worked your way! (It feels like there's an extra step involved, though.)

I wonder why something that worked in QLab 4 stopped working...

[Tommy]

Thanks, Richard.

Actually, I had already tried that. But as Mic mentioned, it just gets sent as a long long string without breaking.

[Rich Walsh]

I had a quick look at what was going on at packet level. QLab 4 is parsing a linefeed in the argument to send the 0A byte (correctly). QLab 5 appears to have been tightened up to not allow you to enter a linefeed in an argument, and there seems to be no way of including an escape character to generate 0A instead… (Except indirectly via Mic’s solution.)

You could send it as raw hex, but that would be even more steps!

Rich

[Chris Ashworth]

FWIW, we have some issues tracking this in both the private QLab issue tracker and the public F53OSC issue tracker:

https://github.com/Figure53/F53OSC/issues/45 

--
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 the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5DF32219-3B54-404B-83BD-AFEA911D6B37%40mac.com.

[Tommy]

Hi Rich,

Thank you for your investigation.

It seems that some changes were made to the OSC specifications when updating from QLab 4 to QLab 5, though the reasons are unclear.

Obviously, Mic's suggested method is easier than using raw HEX! (Though it would be great if it could go back to the way it was. Haha.)

Tommy

[Tommy]

Thanks, Chris!

I hope it gets fixed!

Tommy

[Tommy]

Thanks, Richard.

Actually, I had already tried that. But as Mic mentioned, it just gets sent as a long long string without breaking.