osc
osc copied to clipboard
pq
Any plan to support OSC bundles?
Do you have any plan to implement the support for OSC Bundles?
I was testing your library with Bitwig Studio and it failed immediately because the lib doesn't accespt addresses starting with the "#" char, as in #bundle
Thanks for the interest!
Do you have any plan to implement the support for OSC Bundles?
I'm not looking at it currently but would be very open to external contributions!
Is the Bitwig Studio address scheme documented anywhere? Is the issue just with # prefixes?
Thanks for your reply @pq. I would like to have the time to contribute, but I fear it won't happen soon...
Unfortunately Bitwig doesn't provide an online documentation of its API. I can only share a screenshot from the local copy bundles with Bitwig, showing the OSCConnection and the OSCBundle interfaces.
The most popular (and the ony as far as I know) concrete implementation of the OSC control is the one from Jürgen Moßgraber. It provides and implementation of the interfaces and expose them as a Bitwig controller.
It works perfectly with many OSC clients (including the great Open Stage Control).
In any case, the OSC Bundle is part of the OSC 1.0 specification, it's not something specific from Bitwig.
FYI @pq I'm starting the implementation of OSC packet and bundle. I'm doing it in my little free time, so no deadlines. I've started with the refactoring of the folders as in the following picture:
It might change during the implementation. It's just to let you know....
FYI @pq I'm starting the implementation of OSC packet and bundle. I'm doing it in my little free time, so no deadlines. I've started with the refactoring of the folders as in the following picture:
It might change during the implementation. It's just to let you know.... how can see your code？
Hi @giohappy and @pq, my team and I are using this package for a project and we'd be happy to contribute to this issue as our hardware emits bundles. We don't need support per se, we currently just skip 20 bytes and parse the rest, but it would be nice to not have to document and explain that workaround. We also recently had an issue with our clock, which this feature could have notified us of.
@giohappy, can you share your last version of the code as a branch, maybe in a fork, and that way my team can branch off and submit a PR when we're ready. In the meantime I may dig around to see how simple or difficult this would be, because I notice you mentioned a refactor
hey @Levi-Lesches I didn't work on this further. Actually I'm not using Dart anymore and I even don't remember if I still have this code somewhere. If I find something I will share it np.
Hey @Levi-Lesches! Sorry fort the slow reply. I've been pretty preoccupied elsewhere but would be happy to see contributions!