more HTP problems, or RTFM event?

loebusloebus Registered User
I had a designer that wanted three handles per fixture type, each with fixture intensity and a position, so that she could bring up any handle to control level and execute a position. I set each cuelist to go off zero, thinking this would be easy.
Simple enough, except that whenever a fader was up and she would raise another controlling the same group, the intensity for that group would bump out as soon as the new fader engaged the new cue. So essentially it was treating intensity as an LTP parameter. It seems to me intensity should always default to an HTP parameter, but what was more disconcerting was that even setting the cuelist to use HTP had no effect. Seems to me with all the faders set to use HTP, the faders should use HTP.
Or am I missing something.
Forgive if this has been discussed, I can't imagine something this obvious has gone unnoticed.

Comments

  • Marty PostmaMarty Postma Registered User
    edited May 2009
    Hey Brooke,

    Out of curiosity......what did you set the Release and Assert times to in those lists?
  • loebusloebus Registered User
    edited May 2009
    Release and asset times were set to defaults, 2s.
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited May 2009
    As you discovered, unless explicitly set to HTP, all control of intensity is LTP. With that said, we do have an known issue where HTP values can be temorarily overridden when an LTP cuelist controlling intensity for the same fixtures is played back. This is logged as bug #9746. Right now your best bet is to set your intensity on a seperate HTP handle and have your positions without intensity setup on their seperate handles.
Sign In or Register to comment.