Color matching issues on VMS (Pixel Mapping)

Paul,

What version of software are you running on the Ion? 

I am not seeing any issues between the output values of pixel maps and conventional patch (these are the fixtures patched in the standard patch)  for the ChromaQ Color Force 72 fixtures. 

For VMS, there won't be an Amber parameter.  We use RGB and/or HS to calculate the color output for all different color configurations.  For the Color Force fixtures we convert RGB to HS and then HS to RGBA to output.  The output values are exactly the same for the VMS and conventional for me.

Several things to look try:
- When using the VMS, you can set the CrossFade parameter of the Virtual Server to -100 to set the output priority of 100% to VMS and then no values from the fixtures patched conventionally are being output.
- Do you have an intensity level of the Color Force fixtures patched conventionally when you are using the VMS?  The output of VMS and conventionals HTP when CrossFade is set to 0% (Home).

If you are still having problems, please send me your show file and I can take a look at your show.  Email is eos (at) etcconnect (dot) com.  Please put Attn: Steven Peterson and reference this forum.

Please let me know if you have any other questions.

I "worked around" the issue by setting both the Ion (running 1.9.6) and the Color Force 72 to three color RBG and let the fixtures do the heavy lifting in regards to AMBER values . . . that seems to work as expected . .

what it looked to me was that it was sending RED data to RED address, BLUE data to AMBER address and GREEN data to BLUE Address . . . but since I "fixed it" I am leery of going back just to check my suspicions . . when things slow down again I may set them up and test that theory . . .

I "worked around" the issue by setting both the Ion (running 1.9.6) and the Color Force 72 to three color RBG and let the fixtures do the heavy lifting in regards to AMBER values . . . that seems to work as expected . .

what it looked to me was that it was sending RED data to RED address, BLUE data to AMBER address and GREEN data to BLUE Address . . . but since I "fixed it" I am leery of going back just to check my suspicions . . when things slow down again I may set them up and test that theory . . .

You are correct and you have also found the work around.  It is a bug in 1.9.6 that was fixed in 1.9.8. 

so if I update to 1.9.8 then it will work properly the way I had it set up originally?

Yes, that is correct.  We fixed the issue in 1.9.8.

But you will want to install 1.9.9 - which is the latest software on the downloads page.

:-)

Thanks,

a

Anne .. 

I saw that as soon as I went to download 1.9.8 .. so I just skipped it ..and downloaded 1.9.9 . . .

I noticed that the offline editor now just says EOS Family .. and that the VIRTUAL KEYBOARD looks different .. (is that what the EOS keyboard looks like?)

will this be the same on the RVI? it would be nice to have the RVI have the same keyboard layout as the Ion .. but if not we'll manage . .

Thanks . ..

Paul

Yes, we needed to standardize the offline editor and client.  With the introduction of Gio there were 8 different options if we maintained each product in the family separately.  And we did decide to go with the Eos virtual keyboard.   

:-)

a