Home | News | Products | Support | Download | Sales | library | Guests | Contact | WebCam | Links
CDS Logo LanBox-Talk mail archive
 

By date: Prev | Next | Index By thread: Prev | Next | Index

SubjectRe: [LCtalk] Feature request...?
FromFokko van Duin
DateSat, 10 Jan 2004 14:59:59 +0100


At 21:20 +0000 09-01-2004, David Raison wrote:
This could be limited to an address within the LCX subnet, then you only need 1 byte :-)

Yak, we don't do that ;-)



On the other hand we have planned new firmware for this year which supports UDP broadcasts and point to point (for DMX distribution, Capture 3D visualization, etc ), and also UDP receive. This way you can also pickup e.g. the analog inputs of a LCX via Ethernet, or certain layers.
Sounds like fun, any firmer specs/dates on this?

Before summer.



I was hoping to use the LCX as the "Master" controller/sequencer, thus these messages would be for other non-DMX but sychronised events such as 'play sound track x' on the PC. This would allow a sequence of reasonably complex cues to be manually sync'd to a sound track in, say, 5 minuite chunks.
Now I currently plan to use a script that starts the sound & light cues together from the PC, but that now means I have two "controllers" :-/

Well, with distributed DMX that's easy; use a few (say 4) light channels for sound control messages. Use 1 byte as command # and 3 params bytes. As -ALL- (up to 3072) light channels of a LCX will be broadcasted on Ethernet, your cumputer can pick them from the network easily, and use them for whatever is needed.


With UDP broadcasting the LCX can be used for many distributed show control applications, and it also opens the way for very fast direct lighting control via network. Video or other realtime data depending DMX is then easy to built ;-)

--
Fokko van Duin,                     Creators of the LanBox-LC
CDS advanced technology bv,         DMX lighting controller.
http://www.cds.nl/                  http://www.lanbox.com/

We are member of MIDI Manufacturers Association, MMA

By date: Prev | Next | Index By thread: Prev | Next | Index