i see... for our project, we need to send data across network to multiple nodes, so where thinking of using osc-udp, and then for the critical messages like play we don't really like udp so were looking at osc-tcp. Now thinking of making a mix between osc-udp and oscquery for critical commands.
one last question, for the moment at least.. i remember reading somewhere that the python bindings of libossia are somewhat not maintained? is there lots of functionality missing or outdated things? recommendation for a new project like our thats would heavily rely on libossia would be to use C++? or ossia python is ok?
I'd personnally recommend using C++ - the python bindings should be ok in terms of feature support
but it's more, that they aren't tested often
if you have some spare time it would be nice if you can test them and tell us if there are glaring problems
can take some time to look at them
what are you planning to use for software UI ?
(also, did you check the cueing abilities of ossia score =) )
i'm currently trying and testing python bindings
(sure! im using it now for testing our osc receiving :)
(ossia score i mean)
Our plans are to make some custom UI's one of them would be web-based surely, the other one still haven't decided
ah ok :) looks interesting !
in particular oscquery data can be sent from a webpage
so that could be useful to you
yes! i looked at that example! we were already thinking of using websockets so libossia is making itself a very good candidate for a building block