backing into zero

I'm currently working with 5 playlists. The problem I'm running into is that when I back into zero on one of those qlists it takes everything to black; even channels not owned by that playlist?

 Can I stop this?

Parents
  • If you back into zero on a cue stack, it should take any channels owned by the cue stack, plus any manual values that are not overrides of channels owned by another cue list out.    It should not impact channels that are owned by another cue stack.  Keep in mind, though, as an LTP system, if you "back" through your cue stack, and if some of those cues had stolen control from a second cue list, you are not going to be returning control to that second cue list as you back up.     Does that make any sense?  If this is confusing, you can drop the show file to me, with an explanation of what's happening (specifically), and I'll explain why the desk doing what its doing. 

    Thanks!

  • thank you. i discovered my problem was that I had a bunch of channels captured at zero, and was looking in blind at only active channels. So I couldn't see that I had taken control of them. operator error. your explanation does indeed make sense. thanks.

Reply Children
  • Ah, good.  Thanks for letting us know.  The action of the back button was actually a hotly contested one earlier in development.  It seemed to us we arrived at the most logical scenario (what happens if.... multiple cue stacks, null/filtered values, tracked, asserted, HTP versus LTP, et al).    There has only been one other inquiry about this feature, so it looks like its making sense to you guys as well :-)  that's good to know!

Related