Hi List and Lucas,
Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console.
The alternative is to use the 192.x.x.255 broadcast address, and simply send everything to all nodes, is this the preferred way for every situation with more then one node?
Thanks for any insights,
Simon
Hi Simon,
Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console.
strange i don't get the "socket bind failed.“ with 2 [artnetudp]. tested on Windows11 and Debian13.
eventually you can use [trigger] objects to address multiple ips or universes. see attached .pd file.
also if needed (and if you have an github account) you can open an issue on the repo:
https://github.com/Lucarda/pd-artnetlib
Thanks Lucas,
I will check that out. I am on MacOs 15.7.2 with PD 0.56.1
Am 13.12.2025 um 17:06 schrieb Lucas Cordiviola lucarda27@hotmail.com:
Hi Simon,
Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console.
strange i don't get the "socket bind failed.“ with 2 [artnetudp]. tested on Windows11 and Debian13.
eventually you can use [trigger] objects to address multiple ips or universes. see attached .pd file.
also if needed (and if you have an github account) you can open an issue on the repo:
https://github.com/Lucarda/pd-artnetlib
-- Mensaje telepatico asistido por maquinas
On 13/12/2025 04:56, Simon Iten wrote:
Hi List and Lucas,
Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console.
The alternative is to use the 192.x.x.255 broadcast address, and simply send everything to all nodes, is this the preferred way for every situation with more then one node?
Thanks for any insights,
Simon
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/CD2H6UZZ2X...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
<arnetlib-multiple-ip.pd>--- pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/MHV4O3BKZO...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
I have created an issue
https://github.com/Lucarda/pd-artnetlib/issues/1
and will try to investigate further.
hello, If this is a show stopper for you, you can send artnet data with netsent. (CF my very basic art_net lib in deken : it's not optimized, but vanilla) Cheers c
Le 13/12/2025 à 08:56, Simon Iten a écrit :
Hi List and Lucas,
Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console.
The alternative is to use the 192.x.x.255 broadcast address, and simply send everything to all nodes, is this the preferred way for every situation with more then one node?
Thanks for any insights,
Simon
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/CD2H6UZZ2X...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
Thanks for this.
Still wondering what is best practice actually in a Network/WIFI situation, if I only have ArtNet devices in a network would it not be more efficient to just send everything via the broadcast address? Less traffic, less latency I would assume. (Assuming that there is some overlap in DMX data that affects more than one device..
Or is there an advantage in sending only to the device that needs the data? Parsing at the receiver end for example, which could take longer if all the data is sent to all devices…
Am 15.12.2025 um 08:17 schrieb cyrille henry via Pd-list pd-list@lists.iem.at:
hello, If this is a show stopper for you, you can send artnet data with netsent. (CF my very basic art_net lib in deken : it's not optimized, but vanilla) Cheers c
Le 13/12/2025 à 08:56, Simon Iten a écrit :
Hi List and Lucas, Is there a way to send different universes (or even the same) to multiple IPs with artnetlib? If I simply create another artnetudp object I get an "artnetudp: socket bind failed.“ error in the console. The alternative is to use the 192.x.x.255 broadcast address, and simply send everything to all nodes, is this the preferred way for every situation with more then one node? Thanks for any insights, Simon
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/CD2H6UZZ2X... To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/TKGZX2BCWL...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
Thanks for this.
Still wondering what is best practice actually in a Network/WIFI situation, if I only have ArtNet devices in a network would it not be more efficient to just send everything via the broadcast address? Less traffic, less latency I would assume. (Assuming that there is some overlap in DMX data that affects more than one device..
Or is there an advantage in sending only to the device that needs the data? Parsing at the receiver end for example, which could take longer if all the data is sent to all devices…
No experience with artnet here, but one advantage of broadcasting is that the sender does not need to know, nor worry, about the addresses and presenece of the receivers on the network.
One disadvantage of broadcasting is that the sender does not necessarily know about the addresses and presenece of the receivers unless you implement some pinging for diagnostics.
:)
I would not worry about parsing and associated CPU consumption until this problem actually arises.
best, P