Comment # 2
on bug 9837
from Hanspeter Portner
>>However, I don't see any code in the OSC dissector to specifically handle OSC over TCP with the packet size at the beginning of each "OSC packet".
>>(Using dissect_osc_heur() won't work for OSC over tcp).
Good catch, I've never used OSC via TCP and totally forgot about handling it
seperately. OSC is mostly used via UDP (but not exclusively).
However, there are two different ways out there of packetizing OSC for
streaming protocols (whether it is for TCP or for a serial line). The one
mentioned above (prepend packet size as uint32) works well for TCP and USB
serial. But this method is discouraged nowadays in favour of SLIP encoding of
the packet which is more robust and applicable for e.g. noisy lines like RS232.
Some apps and libraries only support the first, others only the second and only
few support both.
As long as both methods are out there, I guess we need to check/handle both of
them?
>>Is OSC over TCP used in the real world?
Yes, there are apps and libraries out there that support OSC over TCP, USB
serial, raw serial lines.
>>Is there an official IANA TCP port assignment for OSC ? (and/or for UDP ?)
No, usually each app uses its own custom port, thus the heuristics is needed.
The only thing related to OSC registered with IANA is oscit (a
configuration/query protocol on top of OSC)
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=132
>>Can you provide a capture with OSC over TCP ?
Yes, will try to record capture files for both methods in the next days and add
them here.
You are receiving this mail because:
- You are watching all bug changes.