OSC In/Out DAT & OSC Out CHOP bugs (?)

Bugs
1

Hello,

TD Version 2023.12230
W11 Pro 24H2

OSC DAT:
I feel like the OSC In DAT and OSC Out DAT ops are the wrong way round?

The OSC In DAT has a wire input, which doesn’t make sense as it is a “source” of data. Surely it should be able to produce a table of received messages.

The OSC Out DAT only has a wire output, which doesn’t make sense as it is a “sink” of data, and I don’t know why it would be a “source” of data. Surely I should be able to wire in a table of messages and have it send them? It also has a “Received Messaged” tab in the parameters, which is confusing.

I also recently managed to crash TD by wiring a table into the OSC In DAT, however I haven’t managed to recreate this. If I can make it happen, I’ll try and provide a minimal reproduce-able TOE file

OSC Chop Out
The OSC Out does not respect “Cook Every Frame: Off” and “Send Events Every Cook: Off” when in “Data Format: Transpose”.

I have a CHOP of data that I am trying to only send as a bundle (ie “/led/A 1 0 1 0”).
Transpose does exactly what I want, but it is transmitting every frame. As the receiving end is ESP32 - and the value changes aren’t very often - I don’t want/need to be bombarding it with 60 packets a second.

Attached is a minimal reproduction.
MVE_CHOP_Transpose.toe (101.8 KB)
Clicking any of the buttons shows that it is continually sending messages.
I would expect it to send 1 event with all the data when you click the button.

As it stands, I’ll just set up a CHOP Execute, and send the data that way. No big deal.

2

Hi @towerful,

thanks for testing this so thoroughly.

the input to the OSC In DAT was used for parsing OSC messages coming from for example serial connections - testing this feature revealed the issue of the crash - it’s repeatable by attaching a Table DAT and inserting an integer…

For the Output of the OSC Out CHOP - we just don’t have a provision for operators without outputs.

For the OSC Out CHOP, the issue with cooking seems to be that it is always Timesliced without the ability to turn Timeslicing off on the Common page. Will have a look at this as well as the issue of it sending every frame despite the Send Events Every Cook parameter being turned off.

cheers
Markus

1 Like
3

the input to the OSC In DAT was used for parsing OSC messages coming from for example serial connections - testing this feature revealed the issue of the crash - it’s repeatable by attaching a Table DAT and inserting an integer…

Before I even get a chance to circle back and provide a test case, amazing.
That sounds about right, I was dealing with integers in a table.

we just don’t have a provision for operators without outputs.

Fair enough, makes sense.

Will have a look at this as well as the issue of it sending every frame despite the Send Events Every Cook parameter being turned off.

Magic, thanks. I’m glad it wasn’t something I was misunderstanding.
Like I said, I have a workaround. But I look forward to being able to refactor that workaround out in some future update :slight_smile: