has anyone done any osc control of the xr series mixers from behringer with PD? i am attempting this and a starting point would make it easier :)
cheers
Hello
On 2020-03-29 18:47, Simon Iten wrote:
has anyone done any osc control of the xr series mixers from
behringer with PD?
i did play around with the x32, which behaves rather similar. the main point being, that using pairs of [udpsend] [udpreceive] objects wont give you any success in bi-directional communication.
a good starting point to solve this is in using [udpsndrcv] from iemnet.
apart from that: https://community.musictribe.com/t5/Recording/X-AIR-OSC-Documentation-Releas...
there you will find the OSC-documentation for the XR series
enjoy, peter
Pd vanilla's [netsend] actually allows bi-directional communication: the second outlet outputs messages sent back from the receiver.
On 30.03.2020 23:31, Peter Venus wrote:
Hello
On 2020-03-29 18:47, Simon Iten wrote:
has anyone done any osc control of the xr series mixers from
behringer with PD?
i did play around with the x32, which behaves rather similar. the main point being, that using pairs of [udpsend] [udpreceive] objects wont give you any success in bi-directional communication.
a good starting point to solve this is in using [udpsndrcv] from iemnet.
apart from that: https://community.musictribe.com/t5/Recording/X-AIR-OSC-Documentation-Releas...
there you will find the OSC-documentation for the XR series
enjoy, peter
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 3/31/20 12:06 AM, Christof Ressi wrote:
On 30.03.2020 23:31, Peter Venus wrote:
a good starting point to solve this is in using [udpsndrcv] from iemnet.
actually [udpsndrcv] is just an abstraction around [udpclient] to implement the object of the same name from mrpeach.
Pd vanilla's [netsend] actually allows bi-directional communication: the second outlet outputs messages sent back from the receiver.
right. with recent Pd's you can implement the [udpsndrcv] abstraction using [netsend -u -b].
gfmdsar IOhannes
On Tue, 2020-03-31 at 09:16 +0200, IOhannes m zmölnig wrote:
right. with recent Pd's you can implement the [udpsndrcv] abstraction using [netsend -u -b].
Hm. I see bidirectional connections with [netsend]/[netreceive] working only for TCP. Also, the help-file says 'send' for [netreceive] works only for TCP.
At least, in the current master branch.
Roman
Hm. I see bidirectional connections with [netsend]/[netreceive] working only for TCP. Also, the help-file says 'send' for [netreceive] works only for TCP.
Yes, but the problem is only about [netreceive -u]: it doesn't store a list of clients, so [send( can't work.
Actually, the implementation would be not so trivial because UDP has no real notion of connection, so [netreceive -u] wouldn't really know when to remove a client from the list... Or should it just keep clients until explicitly removed by the user? For a real server, I think we also need something like a [sendto( message, so we can reply to specific clients, since we don't always want to broadcast - also for TCP mode!
But pairwise bidirectional communication does work for [netsend -u], ist just that you need two pairs of [netsend -u] and bind them to specific ports:
[connect localhost 9999 9998( -> [netsend -u]
[connect localhost 9998 9999( -> [netsend -u]
Now you can send messages between the two sockets. See attached patch.
Christof
On 31.03.2020 11:15, Roman Haefeli wrote:
On Tue, 2020-03-31 at 09:16 +0200, IOhannes m zmölnig wrote:
right. with recent Pd's you can implement the [udpsndrcv] abstraction using [netsend -u -b].
Hm. I see bidirectional connections with [netsend]/[netreceive] working only for TCP. Also, the help-file says 'send' for [netreceive] works only for TCP.
At least, in the current master branch.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 3/31/20 12:40 PM, Christof Ressi wrote:
Now you can send messages between the two sockets. See attached patch.
incidentally (well not so much i guess), this topic has also been covered by a few other threads on this mailinglist and on pd-dev and on github: https://github.com/pure-data/pure-data/issues/917
gfamdsr IOhannes
On Tue, 2020-03-31 at 13:19 +0200, IOhannes m zmölnig wrote:
On 3/31/20 12:40 PM, Christof Ressi wrote:
Now you can send messages between the two sockets. See attached patch.
incidentally (well not so much i guess), this topic has also been covered by a few other threads on this mailinglist and on pd-dev and on github: https://github.com/pure-data/pure-data/issues/917
Yeah, right. I wasn't sure if was already in master, but my fault was that I tried that between [netreceive -u] and [netsend -u]. As Christof's patch illustrates, one should use two [netsend]s.
Nice!
Roman
-
Christof Ressi -
IOhannes m zmölnig -
Peter Venus -
Roman Haefeli -
Simon Iten