I'm using ELC node8 and you can do HTP merge or LTP merge in each output, same as Luminex.
I'm using ELC node8 and you can do HTP merge or LTP merge in each output, same as Luminex.
you need an htp merge- to control from 2 different devices-
you will have to check whether your box will do an HTP merge-
artnet is just a ethernet protocol its doesnt do any merging - it depends on the interface box
LTP merging wont work - as both devices are going to be sending information at the same time-
Awesome, thanks guys, this was exactly what I was looking for. I couldnt find any of this online. I was really surprised by the lack of info on Artnet, well, at least what I could find. Thanks everyone.
Wayne at Artistic Licence invented artnet... check out the Artistic Licence website for details and info.
I can recommend his book: Rock Solid Ethernet
http://www.artisticlicence.com/index..._id=&order_id=
Also check out the DMX workshop software to understand more about how it all works...
http://www.artisticlicence.com/index..._id=&order_id=
the first 5 pages of this manual is usefull to give an explanation:
http://www.artisticlicence.com/WebSi...es/art-net.pdf
(p5 onwards is compex..>!!)
If you need more specific info - let me know
Simon
Simon Pugsley
SNP Productions Ltd. (UK)
Lighting & Video Control Solutions
Catalyst|Sales|Hire|Training|Support
Catalyst Dealer UK Europe & Worldwide...
Office: +44 (0)1908 410129
Mobile: +44 (0)7958 390034
simon@snp-productions.co.uk
www.snp-productions.co.uk
by definition - an HTP merge wont work for a colour device!... an LTP merge would be more usefull on a colour device.
However, as previously stated - a switch function between 2 ports would be of more use as there are 2 controllers connected.
Merging usually requires hardware - ie: an Artnet box (node)
However, it is also possible with some software:
http://www.artisticlicence.com/index..._id=&order_id=
Art-Net II Protocol Release V1.4 Document Revision 1.4ak 9/11/09 (extract)
Data Merging:
The Art-Net protocol allows multiple nodes or servers to transmit ArtDmx data to the same universe.
A node can detect this situation by comparing the IP addresses of received ArtDmx packets. If ArtDmx packets addressed to the same Universe are received from different IP addresses, a potential conflict exists.
Merge is implemented in either LTP or HTP mode as specified by the ArtAddress packet.
When a node provides multiple DMX512 inputs, it is the responsibility of the Node to handle merging of data. This is because the Node will have only one IP address. If this were not handled at the Node, ArtDmx packets with identical IP addresses and identical universe numbers, but conflicting level data would be transmitted to the network.
Simon Pugsley
SNP Productions Ltd. (UK)
Lighting & Video Control Solutions
Catalyst|Sales|Hire|Training|Support
Catalyst Dealer UK Europe & Worldwide...
Office: +44 (0)1908 410129
Mobile: +44 (0)7958 390034
simon@snp-productions.co.uk
www.snp-productions.co.uk
why you say " by definition HTP merge doesnt work on colour device!"?
I think you have not got something right in your understanding of LTP and HTP?
this is the scenario-
two consoles or devices transmitting continuous information- at the same time-
you know how LTP works? ( last takes precedence ... )
For example-
On console A - transmit channel 1 as say 50 -
On console B - transite channel 1 as 25 -
with LTP data flips between 25 and 50- continuously- this is not very useful - particularily on a colour channel - your colour flips constantly between 2 values- breaking scrollers - or flickering LED products-
With HTP ( highest takes precedence ) output is 50 - data doesnt flip- it stays constant-
How you work with HTP is when you have 2 consoles outputting at the same time - you set the output channels to 0 ( fader down ) when you want the other device to have precedence.
The 0 zero value works as an implicit channel by channel switch between the two data streams-
When you set one controller to 0 values - whatever channels - the other devices channels with any greater value than zero has the output-
you do not have to do any additional switching of devices or configuration-
?
I fully understand the difference... a switching method would be better and safer. HTP method relies on the values staying at zero on the other desk... not necessarily guaranteed on an existing show which is what Matt is trying to do... However - if the values do stay at zero - then its a valid method.
Simon Pugsley
SNP Productions Ltd. (UK)
Lighting & Video Control Solutions
Catalyst|Sales|Hire|Training|Support
Catalyst Dealer UK Europe & Worldwide...
Office: +44 (0)1908 410129
Mobile: +44 (0)7958 390034
simon@snp-productions.co.uk
www.snp-productions.co.uk
what reasons you say then that
?by definition - an HTP merge wont work for a colour device!... an LTP merge would be more usefull on a colour device
when actually the opposite true- htp merge works - ltp merge doesnt.
it is easy to ensure that values stay at zero- you pull the cue fader down-
LTP would not work under any circumstances - as the outputs fight each other-
it is not feasible in most circumstance to change the configuration of devices - and i would suggest that changing device configuration in any live show - is much less safe than htp priority-
you skip a song for example which might have a config cue - and you have no idea what state the device is in?
htp priority is stateless and easily reversible - changing device configuration is hidden and not easily observed.
and htp priority works on each and every single channel on every universe - and is totally controlled by the lighting console on every single channel- on every universe-
you can only switch entire universes in bulk?
unless there is a super complex per channel priority system somewhere that i dont know about-
Well, once I get the rig all set up and playing nice, ill try both ways and post the results.
i think you misunderstand the concept of the ArtAddress packet within the artnet spec-
Merging is not implemented in either LTP or HTP mode as specified by the ArtAddress packet.
this is a configuration packet not an implementation -
this is a packet that tells a device to do configure something - if it wants to - not an implementation-
it is a configuration specifically for an artistic licence box - usually because they lack any kindof user interface - buttons or web interface -
typically these packets are only used by artistic licence - as other manufacturers have different functionality- that does not fit into 'the artnet spec' as artistic licence sees it-
the confusing come about because artistic licence manufactures its own products to do these things- and it is talking about configuring its own products-
and in particular you should never assume that any other device other than an artistic licence device will actually be reconfigured by this or any other packet-
there is no requirement for an ELC product to respond to - or be reconfigured by the ArtAddress packet- it is not an implementation.