EOS and the VL 1000

Hi, are you using a show file that was created in an earlier version than 1.4? If so the problem is possibly that the console is using the old VL1000 fixture profile embedded in the show file, rather than the new VL1000 fixture profile that fixes this and other issues, and provides normalised shutter controls. If this is the problem, then to update the show file to use the new fixture profile, go to Patch, Fixtures, User, Edit, scroll down the fixture list to your VL1000 fixture, and click Update Lib - this will apply the fixture profile to the show file.

However be aware that applying the new fixture profile on an existing show file may well cause you problems, so I'd only do it on a well backed-up file. Taking Zoom parameter as an example, in the old fixture library the range was 19 to 36 - this meant that an attribute value of '29' in cues & palettes would result in a DMX value of 143. However as soon as you Update Lib, the range becomes 19 to 70, meaning that the value of '29' now give a DMX output of 48 - consequently all the VL1000s in your show will have much narrower beams than they did previously! 

In addition the parameter for gobo indexing also had a range change in the newer VL1000 library - so if you do Update Lib on an existing show file be prepared to spend some time going through the show to update beam palettes and / or cues. :)

David

Hi, are you using a show file that was created in an earlier version than 1.4? If so the problem is possibly that the console is using the old VL1000 fixture profile embedded in the show file, rather than the new VL1000 fixture profile that fixes this and other issues, and provides normalised shutter controls. If this is the problem, then to update the show file to use the new fixture profile, go to Patch, Fixtures, User, Edit, scroll down the fixture list to your VL1000 fixture, and click Update Lib - this will apply the fixture profile to the show file.

However be aware that applying the new fixture profile on an existing show file may well cause you problems, so I'd only do it on a well backed-up file. Taking Zoom parameter as an example, in the old fixture library the range was 19 to 36 - this meant that an attribute value of '29' in cues & palettes would result in a DMX value of 143. However as soon as you Update Lib, the range becomes 19 to 70, meaning that the value of '29' now give a DMX output of 48 - consequently all the VL1000s in your show will have much narrower beams than they did previously! 

In addition the parameter for gobo indexing also had a range change in the newer VL1000 library - so if you do Update Lib on an existing show file be prepared to spend some time going through the show to update beam palettes and / or cues. :)

David

Anne and Company,

This brings up another question.  When you program a show, does the lightboard record DMX values or does it record the "end result"? Meaning does it memorize that you want the fixture to be 29 deg or does it record that the DMX value is 143?  How is this value affected when swapping fixtures to a different fixture than originally programmed, i.e. swapping a VL1000 for a MAC2K?  Thanks

Jay 

Hi Jay-

I'm not sure what it does for Zoom...I'd have to check by doing a fixture swap. For Pan and Tilt and colour mixing, it records in degrees and Hue/Saturation (if HS was used to store in the first place, eg from the color picker).

I'm sure someone more clever will chime in to confirm!

-luke-