You can either use OSC (OpenSourceControl) for this or use our Net Broadcaster / Listener actors.
OSC will need a dedicated IP. Yes, in performance/installation environments we typically set static IPs in the DHCP lease of the Router, that way when we connect a device with a specific MAC address it will always link up with that IP address.
Net Broadcaster is great because you simply set the ID of the computer in the Isadora preferences menu. You don't have to set the Network IP address. Just plug all your devices in with the same router and you are ready to go, set your Network ID in the Isadora preferences so that they all have a unique ID and you are ready to go!
Net Broadcaster requires a router with Multicast support.
@dusx Thanks for the lightning fast reply! I missed that CPU to GPU converter actor, sounds like the right solution for me. I'll try and let you know how it goes in case the solution interests someone else.
@benju Didn't you do something similar for the large spinning imagery spanning multiple beamers for Hexploitation? I think I remember you saying you used Virtual Stages. Do you think your approach would be applicable here?
this is a very interesting observation - thank you for sharing it.
so far I am still working in 3.0.7 but I should come to a decision in this week and I have the tendency to follow the first suggestion of Woland (even if the internal hardrive of the old macpro is only 500 gb) and try the bootable partition with a newer os. as I jumpt from high sierra with a new M1Max-macbookpro directly to monterey - which works ok for me apart from the incredibly annoying orange dot - I'd be be very curious to know if you have a clear recommendation for mojave, catalina or big sur?
I just have a project, where I need to receive ArtNet, to trigger cues from a GrandMA and I had similar issues like @jiw.
The PC I use for the Project does have several Network Ports. I use two of it. One for VNC and regular Networking and one for the ArtNet Network.
I have a 'Master scene', which is always on in the background, receiving ArtNet on one channel, triggering the cues. In one of those 30ish cues, I have a second receiver actor, which listens on a different channel but on the same Universe and IP, to trigger some special actions. I had both running fine (probably separate, as the 'Master cue' might not be on, while testing this specific cue). In the show, all cues where triggered, but the 'special' ones not. I could see the actor didn't show any rcv while the other did it's job. (No worries, I was prepared, and triggert those specials manualy, so nobody got hurt. ;-) ).
As I do not have access alot to the PC, I tried some things with recieving and sending actors on two different devices connected directly. I mainly tried alot with different Ethernet devices, changing the IP adresses in the actors setting, or using the default settings. Results where very confusing, so will be the text coming from here, probably. So I say sorry allready for the longiness.
Some thoughts/feelings I got about the results:
1. Different softwares receiving ArtNet on the same PC (I used ArtNetNominator as well), block the Ports for other ones, some not. Some does that only, if you select the corresponding IP (ANN does that).
2. I had the impression, that it doesn't always work like expected, if you want to use a different IP address, which isn't the default, shown in the Isadora preferences. And I found that the default Address (empty intf addr value, only shown in the output value) of the actor, sometimes isnt' the same to the default of Isadora itself, shown in the preferences. E.g, when I leave the node selection empty, but set a manual IP, which isn't the default of the actor, the receiver stays silent (even when using the default address, which is corresponding to the set network of the sender actor). Setting the node to it, the receiver awakens right on.
The scheme is like following: If the isadora default isn't corresponding to the actors default on the same machine, the receiver only works, if you choose the node explicitly on the senders side, despite the IP shown in the actors, are in the corresponding network. If you don't set a node in the sender, the reciever is only responding if the sender is using an IP which is corresponding to the default of isadoras preferences, ignoring the default adress for the actor. It even seams, that sometimes the right address isn't one of those default adresses, but a third, if you have more than two IP's on the same machine. In this case only this "hidden" IP works for the reciever, and then as expected with AND without node set.
3. Is it maybe possible, that two ArtNet actors block them selfs, like the two different softwares on the same machine?
4. I sometimes had the issue, while choosing the right IP Address, the node wasn't shown. On the other hand, I could not send to a chosen specific node, when I chose the IP, where it showed up.
5. Does two recieving actors using the same engine? I gave two receivers, two different IP adresses, corresponding to two different Ethernet ports. On one Port there was an ArtNet signal, on the other there wasn't.
When I gave the first actor the IP without the ArtNet Data, it didn't receive anything, like expected. But when I gave the other the right address for the Data, the first one started recieving (which should not), while the second one didn't. Killing the first actor, sometime helped instantly, sometimes I had to switch some thing on the sender actor like the node select.
In general, it doesn't seem to be a good Idea to use more than one receiving actor at the same time, even on different IP settings.
Systems: Windows 10 MacOS BigSur MacOS High Sierra
PS: While testing, I had some other issues with the matrix value actors. Several times I could not manage to get the reciever actor to show values. The left one in the screenshot has been put first. As I couldn't get it to work, I compared it to the ones from the ArtNet tutorial patch, which ran immediatly, even the sender beeing in the other patch. I just copy and paste it into my patch then, which worked fine. I then put another from the toolbox, which worked immediatly, too.
edit: If you look closely, the first receiver shows new msgs, but doesn't change the output.