• Date
    itscorydon
  • Date
  • Replies 1 reply
  • Subscribers 184 subscribers
  • Views 2458 views
  • Users 0 members are here

Haze parameters on submaster issue caused by stop/back or go to Q.

Hello!

I've got an issue that I assume someone knows the answer to.

I have two Radiance hazers with two parameters each that I am wanting to control via submasters routed to faders. In my instance I have four faders: two submasters controlling the haze parameters of the fixtures, and two submasters controlling the fan parameters. These faders are all fine and dandy and working well until I decided to stop/back or go to a cue. In that instance, all of my active submasters that contain my individual haze parameters reset to 0.

Is there an easy way that I can set it so that my parameter faders maintain their values when I go back/go to Q instead of resetting to 0? This makes it difficult during rehearsals when we are trying to fill the room with haze and make changes to our cues at the same time. 

I also notice that this is only an issue with individual parameters. If I have a submaster containing only intensity for my work lights and I want to stop/back/go to Q, it stays at it's fader-ed level, and does not reset to zero.

Thanks in advance!

(FYI: this is on ION running V2.6.0.9)

Parents
  • you can make the sub a higher priority. by default both the cujelist and the sub have a priority of 4. make the sub at least 5 and everything's fine.

    it has nothing to do with having one more more parameters on it. it's about Intensity or something else. by default Intensity is handled on an HTP basis, while all Non-Intensity-Parameters are always LTP.

    when going back or using GotoCue the console Asserts the cue, turning your hazers tracked values into move instructions and thus takes over your values. actually having haze move instructions in your cues and simply using Go would take over your haze values as well, unless you that priority thing.
Reply
  • you can make the sub a higher priority. by default both the cujelist and the sub have a priority of 4. make the sub at least 5 and everything's fine.

    it has nothing to do with having one more more parameters on it. it's about Intensity or something else. by default Intensity is handled on an HTP basis, while all Non-Intensity-Parameters are always LTP.

    when going back or using GotoCue the console Asserts the cue, turning your hazers tracked values into move instructions and thus takes over your values. actually having haze move instructions in your cues and simply using Go would take over your haze values as well, unless you that priority thing.
Children
No Data
Related

www.etcconnect.com