If this is the case, then why even have a conductor - the condutor's purpose is to replace the pc. That is why it plays the show sequences, plays the mp3s, and has its own scheduler to setup/play the show. It sends out sync packets across the network to keep the slaves (2nd, 3rd, 4th ethernet dongle) in sync. RJ has never said it was designed to display video, operate electro mech devices (fogger for halloween etc) - this is going to have to be from external devices.
The conductor plays its own sequence data, and sends out sync packets for any slaves to use to maintain synchronization. From what I have been told it has/is never been designed at this stage to replace anything but a standard show computer running sequences, music and a scheduler.
My assumption was one way to get external 3rd party control of non light (incan, led, rbg led etc) in a show. You take away the conductor and then you have what we have now - a E131 device sending over ethernet directly controlled by a pc ....
btw, if you go over the video again, a slave controllers the ethernet dongle its attached to, just like the conductor controls the dongle that it is attached to.
one the files/songs/schedule is loaded on the conductors memory card, a PC is not required to be connected anymore - hence RJs demonstration - both the conductor unit and slave unit in the video were talking thru each other via wireless bridges - not to his laptop...
Anyways, this is off topic this is about if LSP 2.5 will have this capability - it will - as far as what information RJ has released the conductor will not.
Myk
Another assumption about how things do/might work...
After listening to RJs video, it is my assumption that the conductor is removed and the PC serves this purpose. The PC (running xLights, LSP, Vixen, etc.) will send its regular sequence data over all LOR, DMX, or whatever networks it is configured to do. AND it also can drive video in a LSP configuration -- like any other LSP setup is capable of doing. What is 'new' is that the LSP software (and any other slave-aware software) is that it sends out (transmits) its own multicast sync packet, and the slaves receive that packet and play their own local sequences to the connected hubs and controllers.
PC Software replaces the conductor.
BTW, the slave is a receiver and therefore "listens" for the sync packets. It does not transmit anything.
It is my suposition that the PC-based sequencers do not 'listen' for packets... that would be to disruptive to their normal behavior.
