1.9.5 Using channels for pixel-mapping and also as standard channels

Hi,

Yes this is possible as you describe.

You can effectively patch the physical fixtures twice, once in patch as per usual and also as part of a pixelmap.

A bit of further reading (if you haven't found it already) is available in the 1.9.5 manual supplement here - http://www.etcconnect.com/docs/docs_downloads/manuals/Eos_Family_v1.9.5_Operations_Manual_Supplement_revA.pdf

Happy pixelmapping!

Graham

just a small off-topic note: if you're still in 1.9.5 like the thread title suggests, you should update to 1.9.6

Ueli

Click,

To expand on Graham's answer.  Once you have the fixtures patched both in the pixel mapper and normally in the patch screen, you then can control them in two places.

You can bring them up in the normal channel and in the pixel mapper.  Within the ML Controls for the pixel mapper there is an encoder which lets you switch priority between the "pixel mapper" and the "normal channel".  I do not have a show setup to be able to tell you exactly what the encoder is labeled.

Hope that helps,

I had a chance to use the VMS on a project in February with an array of Mac 301s that I used primarily for backlight.  The pixel mapper allowed for creating effects in a really visual way, as well as providing a nifty tool for matching color in the video content.  I even see a lot of potential just mapping to intensities for conventional fixtures.

I have to admit we missed the above mentioned Crossfade parameter, so we had to figure out the HTP relationship.  For the VMS to take precedence, in the fixture parameters, the intensity had to be full while the RGB parameters had to be at 0.  In other words, the intensity channel worked like a sort of i-master for the fixture (regardless of whether RGB came from the VMS or the fixture itself), while the fixture's RGB channels would be HTP with the VMS's RGB channels.

-Josh

The parameter that you are looking for in the server layer is called crossfade.  

:-)

a