submaster non-linearity with color parameters

I first noticed this a while back and posted about it somewhere (perhaps one of the EOS beta forums) but it reared its head again recently.  When using the faders to control subs that contain color parameters, the parameter level is not matching the fader level.  Furthermore, the parameter levels at a particular fader level are different if they are the result of a fade down vs. a fade up.  This makes it hard to match color values based on fader positions when busking a live show using the faders for individual CMY parameter control.

EOS 1.9.8- starting from scratch with a new show.

  • Patch ch 1-10 as Seachanger XG 4 channel fixtures.
  • Patch ch 11-20 as Studio Command 1200 fixtures.
  • In blind,  record sub 1 as Cyan parameter only at Full for all fixtures (1-20)
  • In blind, record sub 2 as Magenta parameter only at Full for all fixtures
  • In blind, record sub 3 as Yellow parameter only at Full for all fixtures
  • All submaster attributes stay as default: Additive, Proportional, HTP
  • Assign subs 1-3 to faders 1-3
  • In Live, bring faders 1-3 from 0 to Full- parameter levels read at Full
  • Bring faders 1-3 down to 50%, parameter levels read 57, 62, 57
  • Bring faders to zero and then up to 50%, parameter levels read 41, 38, 38

If the command line is used to set the faders at a level, (i.e. SUB 1 THRU 3 @ 50) then the fader level and parameter levels match the level on the command line.  The non-linearity only occurs when using the physical or virtual faders to set the sub levels.

I can't think of a reason for this to be a feature... thoughts?

-Todd

 

 

Parents
  • Hi Todd.... in trying out exactly the scenario above, I do see a small rounding error - sometimes.  But it is never greater than 1%.  (Still needs to be addressed).  But am not seeing anything as far off as you are reporting.   Stand by please while we ponder some troubleshooting.

    Thanks much!

    a

     

  • Anne,

    I just tried this offline in 1.9.9 build 10 and the same thing happens. I can send my show file if that helps.

    -Todd

     

     

  • Todd, thanks.  We are seeing a difference from a client/backup/offline.  We are on it.

    Thanks much!

    a

     

  • I noticed the same problem with 1.9.8 offline with intensity parameters if the sub is proportional/LTP

    Also there are some strange interactions if an intensity channel is in a LTP sub and a HTP sub.  if I put channel 1 in a HTP sub at  full and bring the fader to 50%, then bring up the same channel in a LTP sub, the channel level in Live begins increasing as soon as the sub moves off zero.  If I continue to move the fader up and down, the output seem to have no correlation to the fader position.

    If a sub is created with NP's only, does it become LTP by default?  It would explain why the color parameters were affected.  When I added intensity to a color sub, it was affected as well. When I removed all NPs and toggled the mode to HTP,  the sub acted normally.

    All these behaviors were observed using a NEW show, and virtual faders

Reply
  • I noticed the same problem with 1.9.8 offline with intensity parameters if the sub is proportional/LTP

    Also there are some strange interactions if an intensity channel is in a LTP sub and a HTP sub.  if I put channel 1 in a HTP sub at  full and bring the fader to 50%, then bring up the same channel in a LTP sub, the channel level in Live begins increasing as soon as the sub moves off zero.  If I continue to move the fader up and down, the output seem to have no correlation to the fader position.

    If a sub is created with NP's only, does it become LTP by default?  It would explain why the color parameters were affected.  When I added intensity to a color sub, it was affected as well. When I removed all NPs and toggled the mode to HTP,  the sub acted normally.

    All these behaviors were observed using a NEW show, and virtual faders

Children
  • Yes, an LTP override begins its transition from the moment the fader begins moving - that is the basic nature of LTP fades.    It doesn't have to wait to match the current level - that wouldn't work at all if you intent is to use the LTP fader to reduce the level.    The fader is a proportional master between the level control is grabbed at and its stored end state.  Therefore the current output and the sub value (% of completion) are highly unlikely to have any numeric relationship.  

    HTP/LTP for subs or cues is only applied to intensity.  NPs are always LTP.  Because the LTP/HTP attribute of a submaster is never applied to NPs, storing only NPs to a submaster does not automatically change this attribute of the sub.  That would be a bit confusing, since it would be unclear to you if you added intensity parameters to such a submaster what the behavior of the intensity was to be.

    Thanks much!

    a

     

  • My observation has been that with an LTP sub with a stored value of full and a background value of zero, moving the fader up and down and back to 50% produces a different value every time, with speed of movement affecting the deviation, as much as 30% off. 

    BTW, if I use the command 'SUB 1 @ 50 Time 5'  or 'SUB 1 @ 50 SNEAK' , the virtual fader moves to 50% but the LTP sub output jumps to its stored value at the end of the fade, with the exception of 'TIME 0', which functions as expected.  I didn't see this in the 'Known issues remaining' section.



    [edited by: 33boardop at 4:09 PM (GMT -6) on Fri, Nov 25 2011]
  • Yes, the rounding error is contributed to by the speed of the fader movement.  We are on it.

    When you are referring to LTP output, are you referring to NPs (which are always LTP) or to LTP intensity?  These are not the same thing.

    The results of a submaster not at full (either by setting the handle or via a command line call) will be different based on the setting of proportional or I-Master for the submaster.  Setting a proportional sub at 50 (by either method) will cause all content to be replayed at 50% of their stored settings.    (This is assuming a start of home - see next point below).  Setting an I-master sub in the same manner will cause the intensity parameters to be recalled at 50% of their stored values (or 50% of their transition from where ever they are to the end state of the submaster - based on the background level and the LTP/HTP nature of the intensity).  All other parameters are set to their completed state on a bump.  The trigger for NPs on an I-Master sub are the following:

    Pressing the bump button to mark.

    Moving the I-Master fader off of zero.

    Setting the submaster value to any value other than zero, by all possible means.

    In all instances, the NPs will go to their end state upon activation of the submaster. This is expected behavior.

    Thanks,

    a



    [edited by: Anne Valentino at 1:43 PM (GMT -6) on Mon, Nov 28 2011]
Related