Controlling a HES' DL3. from an ion

It's a media server, and by definition those take up huge numbers of DMX addresses as they have large numbers of controllable attributes, many of which are 16-bit.

To make it more interesting, this particular media server is also a moving yoke fixture!

You'll patch it across several desk channels, much the same way as you patch the Eos Pixelmapping virtual media server:

• One desk channel for the movement
• Another for the "Global"/'Master' control of the media server
• Plus a desk channel for each 'Layer'/'Object' in the media server

Selectively-stored Palettes and Presets are your friends, use them extensively (and carefully). You really don't want to build each state from scratch.

Expect to spend a lot more time on the media server than on the rest of the rig combined. Most shows that make extensive use of media servers have a programming team dedicated to them.
- If you've never used a media server before, they are often quite confusing until you get your mental model of the 'virtual' internals sorted out, as they are quite different to most of the other types of fixture that you might have used.

Richard said:

It's a media server, and by definition those take up huge numbers of DMX addresses as they have large numbers of controllable attributes, many of which are 16-bit.

To make it more interesting, this particular media server is also a moving yoke fixture!

You'll patch it across several desk channels, much the same way as you patch the Eos Pixelmapping virtual media server:

• One desk channel for the movement
• Another for the "Global"/'Master' control of the media server
• Plus a desk channel for each 'Layer'/'Object' in the media server

Selectively-stored Palettes and Presets are your friends, use them extensively (and carefully). You really don't want to build each state from scratch.

Expect to spend a lot more time on the media server than on the rest of the rig combined. Most shows that make extensive use of media servers have a programming team dedicated to them.
- If you've never used a media server before, they are often quite confusing until you get your mental model of the 'virtual' internals sorted out, as they are quite different to most of the other types of fixture that you might have used.

Aww, I see!

Also, I found that this chart helped me alot when trying to break down this massive instrument:

http://www.highend.com/pub/products/digital_lighting/DL3AxonDMXProtocol_V2.pdf

So for example, I would have:

1.) 1 chanel dedicated for the "mechincal controls," and this would cover DMX channel's 1-21?

2.) 1 channel dedicated for the Global controls, and this would cover DMX channel's 22-76(Pg. 2 in the doc!)?  

3.) 1 channel per object - And each channel would have all of those attributes under the ML controls screen(while in a tab..)?

 So, I'm assuming their is already a profile of the fixture in the current release? How can the console handle all of those parameters???

Thanks guys! This seems like a big programming project! Woohoo for overtime!!

Richard said:

It's a media server, and by definition those take up huge numbers of DMX addresses as they have large numbers of controllable attributes, many of which are 16-bit.

To make it more interesting, this particular media server is also a moving yoke fixture!

You'll patch it across several desk channels, much the same way as you patch the Eos Pixelmapping virtual media server:

• One desk channel for the movement
• Another for the "Global"/'Master' control of the media server
• Plus a desk channel for each 'Layer'/'Object' in the media server

Selectively-stored Palettes and Presets are your friends, use them extensively (and carefully). You really don't want to build each state from scratch.

Expect to spend a lot more time on the media server than on the rest of the rig combined. Most shows that make extensive use of media servers have a programming team dedicated to them.
- If you've never used a media server before, they are often quite confusing until you get your mental model of the 'virtual' internals sorted out, as they are quite different to most of the other types of fixture that you might have used.

Aww, I see!

Also, I found that this chart helped me alot when trying to break down this massive instrument:

http://www.highend.com/pub/products/digital_lighting/DL3AxonDMXProtocol_V2.pdf

So for example, I would have:

1.) 1 chanel dedicated for the "mechincal controls," and this would cover DMX channel's 1-21?

2.) 1 channel dedicated for the Global controls, and this would cover DMX channel's 22-76(Pg. 2 in the doc!)?  

3.) 1 channel per object - And each channel would have all of those attributes under the ML controls screen(while in a tab..)?

 So, I'm assuming their is already a profile of the fixture in the current release? How can the console handle all of those parameters???

Thanks guys! This seems like a big programming project! Woohoo for overtime!!