Obsession II to EOS translation problem.

I am having issues with an OBS2 export into EOS. The issue that I am seeing is that my moving light color values are somehow being reversed in the translation. I.E. 73% on OBS2 becomes 27% on EOS. This makes things difficult when there are 0% values being recorded in places where that fixture's color value should really be at 100%.

Any suggestions would be appreciated.

OBS Offline v 5.2.3
EOS Offline v 1.9.0

Thanks
Kalen S

 



[edited by: nelakluwos at 9:26 AM (GMT -6) on Mon, Aug 9 2010]
Parents
  • Hi Kalen,

    This sounds like the personality in Eos does not perfectly match the one you used in Obsession.  You might try selecting the "Import as Custom Fixtures" option from Eos and see if that gets you the correct levels.  Alternately, you could create a custom fixture in Eos which reverses the ranges for the color parameters, and patch the affected channels to that fixture instead.  For this you would open the fixture editor, make a copy of the current fixture, then go to the ranges of the color parameters and switch the DMX values.

    Thanks,

    Ann

  • Ann,

    Thank you for the speedy reply. I have tried to import both as library fixtures and as custom, both yielding the same results. I have also created a custom fixture by copying the current one and reversed the ranges for the color parameters which still did not produce the desired results on stage. Which leads me to my next question...

    How does the EOS handle the translation from "Focus Group" to "Preset"? In my screenshot, when calling up FG 193 for fixture 1, it selects all parameters as if there is data stored for each. However looking at EOS in the background, I am missing data for cyan and magenta for the same fixture. Which makes me believe whenever Preset 193 is called up in EOS, the color values from the previous cue will track through into a place where I thought I already had values. Please correct me if my thinking is wrong.

    Thanks!
    Kalen

Reply
  • Ann,

    Thank you for the speedy reply. I have tried to import both as library fixtures and as custom, both yielding the same results. I have also created a custom fixture by copying the current one and reversed the ranges for the color parameters which still did not produce the desired results on stage. Which leads me to my next question...

    How does the EOS handle the translation from "Focus Group" to "Preset"? In my screenshot, when calling up FG 193 for fixture 1, it selects all parameters as if there is data stored for each. However looking at EOS in the background, I am missing data for cyan and magenta for the same fixture. Which makes me believe whenever Preset 193 is called up in EOS, the color values from the previous cue will track through into a place where I thought I already had values. Please correct me if my thinking is wrong.

    Thanks!
    Kalen

Children
  • Ok so upon further investigation, I found that values not used in a focus group are not stored in a focus group. However if you tell fixture 1 to go to focus group 193, it will add 0's to parameters which have no data stored.

    The workaround by creating a new fixture and modifying the ranges of the color parameters would work except that...

    In my example... OBS channels 1113+1114 (cyan and magenta) have 0 values as they were not included in the focus group. Channel 116 (yellow) is at full. Now when this same cue is opened up in EOS cyan and magenta are STILL at 0 whereas yellow has been reversed from FL to 0. So this is why creating a new fixture and modifying its ranges doesn't work.

    What makes the translation not take the 0% channels to 100%?

  • Hi Kalen,

    Why don't you email your Obsession show file to me and I'll take a look at it? 

    Ann

Related