Wybron CXI and v 1.7.0

(v 1.7.0 offline editor) fixture CXI_Sroller_Mix

Having gotten used to setting the CXI with DMX values and keeping a percent to dmx chart handy, I now find a bizarre frame strategy has been implemented, with each string having four (FOUR?) frame settings.

Since each CXI string is a never changing arrangement, it should have been no problem to come up with the right number of frames.  Instead the range names seem to be labeled as if they were operating modes. It seems the last standard frame in each string has been given it's own range (F3), as well as the custom frame (F4), but F3 on both strings are labled "color 1 cont", which would better describe a (non existant) mode. 

This false "mode" seems to prevent the color picker from ever using F3, which would map to maximum red using both strings, therefore the accurancy of the color mixing is suspect.

Since a "calibrate" option is available on both strings, this hogde-podge of range sizes and meanings could be horribly corrupted.

Also the range names don't appear on the encoder, only on the new ML page.

The scroller values have been converted to frame values, the only way to find the actual dmx value is with the About screen on the background tab, one channel at a time.  We have one LD who likes to set both strings to 20%, 30% etc, guess I'll need palettes for those.

I could create a custom CXI but I would lose the complex HS conversion required for the color picker to work.

UPDATE: It appears F3 is some gimmic to keep the color picker from going into the custom (non mixing ) frame.  However, according to the wybron manual , the maximum dmx value for the color mix portion of each string should be 242 (95%) , whereas the maximum color picker values (hue = 0, sat = 99) have been 244 and 245,  respectively.

 

 



[edited by: 33boardop at 5:50 PM (GMT -6) on Fri, Jul 31 2009]
Parents Reply Children
  • I would also be interested in controlling certain scrollers with "percent" values.  I have a bunch of Apollo MXR's.  All of the color conversions in their instructions are done by "percent."  (Example: Lee 134 is equivalent to front scroll at 45% and back scroll at 14%)  I am getting around this problem by editing the profile and setting the user range from 0 - 100.  (instead of 0 - 255) It seems to be pretty close, but I am confused at why the encoders display the numbers in "degrees."  I understand the terminology of  "frames" and "percent, " but I'm confused over "degrees."  Is that the same thing as "percent?"

    BTW, I just finished programming my first show with 1.7, and I am really liking all of the changes!

Related