iirc you can send it any value
but there is a specific ossia::impulse type
I think which is translated to Impulse in python ?
before I go modifying the library, is it currently possible to add an OSC destination without a new local port?
I'm using OSCQuery which already provides a UDP port, but I want clients to identify remote endpoints that should OSC messages when parameters change and there is no need for an additional local port
I'm using OSCQuery which already provides a UDP port, but I want clients to identify remote endpoints that should OSC messages when parameters change and there is no need for an additional local port
it looked like the osc_protocol tries to setup both and will throw an error if the receive fails.. but maybe something else exists
on another topic. it looks like i'm going to want to move from ossia-cpp (the "safe" bindings) to the "fast" c++ bindings so i can take advantage of the multi protocol protocol. I'm not seeing a way to build the dylib and package those headers. do most projects simply include libossia as a submodule and build the c++ directly in or am I just not seeing a cmake configuration option for the fast c++ ?
before I go modifying the library, is it currently possible to add an OSC destination without a new local port?
I think that for this one would have to make another implementation of the "osc" class. In the branch i've been working on the last few months it should not be very hard:
the osc class looks like https://github.com/ossia/libossia/blob/feature/async_protocols/src/ossia/protocols/osc/osc_generic_protocol.hpp
and is parametrized like https://github.com/ossia/libossia/blob/feature/async_protocols/src/ossia/protocols/osc/osc_factory.cpp
so to send to multiple clients, what I'd do is :
- change that template to have different socket types for sending & receiving
- putting the multiplexing in the "sending" socket type, e.g. instead of udp_socket it'd be something like
class multiple_sockets {
std::vector<upd_socket> m_sockets;
void open() { for(auto& socket : m_sockets) { socket.open(); } }
void write(const char* data, std::size_t sz) { for(auto& socket : m_sockets) { socket.write(data, sz); } }
};am I just not seeing a cmake configuration option for the fast c++ ?
well, "fast C++" is basically the default API that it builds when nothing is specified
but there hasn't been more testing than that
(and it's missing a port of the oscquery server protocol)
likely the api is going to change a bit more, for instance with that multi-client thing, that would be a very useful feature and I want to make sure that it works
(or at least that it's very easy for an user of the lib to make it work by combining a few building blocks)
@jcelerier it looks like the
I'm wondering if you have any advice? I'm trying to get both oscquery AND a list of outbound UDP, all echoing incoming changes as well as local changes.
I see that the oscquery client has this thing
the
multi_protocol setup isn't actually going to solve my problem because if one of its children is oscquery, and another is osc, I don't get the echos (set_echo(true)) i need from oscquery -> osc, the UDP osc protocol only gets the changes that are triggered via local operators, push_valueI'm wondering if you have any advice? I'm trying to get both oscquery AND a list of outbound UDP, all echoing incoming changes as well as local changes.
I see that the oscquery client has this thing
open_osc_sender which looks like it might actually do what i'm talking about.. but i don't actually see how to initiate it.the
json_query_parser parses a message StartOscStreaming that looks like maybe it initiates it? So maybe there is a WS data command I can send that actually achieves what i'm trying to do already? Or, am I on the wrong path?
i'm forked from a recent master FYI
hey all. So tried to dive into https://github.com/OSSIA/ossia-sclang but hit a wall quite quickly with
WebSocketServer not found.
I cannot locate such class and no official quark turns up anything similar.
any clue?
to use oscquerry you will need a spescial build
but the sclang quarck also suports plain osc
simply replace
exposeOSCQueryServer() by exposeOSC()
if you are interested in the build that includes both HTTP and Websocket primitives, you can find it here
I think I was interested in the OSCQuery, but will try exposeOSC() first
we have discussed it on the supercollider page
but i am starting to wonder if merging it is feasible in the near future
for a quick demo of the quarck using OSC, you can have a look at https://www.youtube.com/watch?v=6a01Ij_sYNc
what's unclear now, is how to use the "learn" feature
like you do on that video
you can change the name of the device. The ports have the same defaults as the quarcks so you don't have to change them
once the device is created, right click and select learn (the window appears)