2 Cue Lists, 2 Pages, 1 Fader

Questions or discussions about the Titan and classic consoles and software.

Moderator: Moderators

User avatar
niclights
The eManual
Posts: 4461
Joined: 24 Sep 2004, 01:06
Location: UK

Postby niclights » 19 Oct 2011, 22:59

It isn't quite that simple though. What if, after you have changed page, you still expect the fader to control the original cue-list?
CSmithDesign
Posts: 117
Joined: 25 Jul 2011, 00:45

Postby CSmithDesign » 20 Oct 2011, 05:36

Well, I always try to avoid those issues by locking in the fader so it stays the same cue list on every page. Or, I just let it go and "stomp" on it with a cue list that uses the same attributes on the second page and now that fader is in control until released or the original fader is re-asserted.

The second is most common, even if I don't stomp on the cue, I'll let the colors fade on Fader 1 page 1 while I'm changing gobos on Fader 1 page 2 (or something to that nature, usually better organized than that!) and then go back to fader 1, page 1 when I want to stop the color fade. Or, most likely I'll just forget about fader 1, page 1 and use a different cue or the programmer to change the color. Then later in the show I'll re-assert it when I want to.

This alone would be great. However, I think there could be a couple of ways to implement keeping control of the original cue when you change pages:

- Have a new key profile option: Release Fader. Once a fader is asserted and you change pages, you press the assigned key and the fader is released so you can bring in the new cue (but the old cue is still running in the background until you go back to it)

- Have an option to release the fader (but again, not the cue) when you bring it all the way down (like kill at 0)

- Some combination of the two. ie. Fader at 0 + Flash button = released fader

- Flash and Swop pressed at the same time = fader released (that might be dangerous, though. Easy to fat-finger it)

There's a way to do it, even though it might make things a little awkward. However, I think it's worth it. I think enabling this on non-motorized faders actually gives it an advantage: I just did a show with a Maxxyz Compact and it really sucked waiting for the motorized faders to hit their positions and settle before I could do anything (this Maxxyz took about a second or two before the motor released the fader)

Who is online

Users browsing this forum: Bing [Bot] and 29 guests