What is the compliment to Mark?

I'm feeling dumb asking this, but I'm not seeing an answer in the documentation. Maybe I don't know what to look for?

I've been using workarounds while digging, but I just gave up searching. . . .

 

Mark pre-loads the NPs into the previous cue so your moves happen in the dark, not during the fade in. . . . . simple.

. . . . . but how do you Mark the NPs to avoid movement on the fade out?

Mark doesn't seem to work going forward in the list.

What I've been doing is going back & editing all of my cues in Blind and inserting the appropriate Palettes into the following cue or part 2.

but that's a lot of labour on the back end whereas the front end is a few keys.

 

There has to be a simple way to Mark the fade outs, right?

Parents
  • sorry for this answer, but clean fade outs are the result of clean programming. however you don't have to manually insert the palettes into the fade out cue, just remeber that At Enter removes a move instruction which will result in a tracked value. (this will of course also remove your intensity move instruction so either you type [-] {Intensity} [At] [Enter] or [At] [Enter]
    [Out] )
  • No offence taken.
    If I were starting from scratch it'd be one thing, but usually I'm adapting a road show's show disk to our house.
    So my cues are already built and I'm having to interject our fixtures into their design.
    (but also, I work with one LD who usually likes to start by programming every BlackOut cue first.)

    Thank you for @ [Enter], I wasn't thinking about it that way.
    I just assumed if you could Mark on the fade in, you could Mark on the fade out.
  • If you want to program blackout cues first, use Intensity Blocks (not full blocks) on those cues. Shift-Block is the keystroke. That will block intensity data from tracking into a blackout, but it will let non-intensity data track through. You won’t get live moves on the fade out that way.
Reply Children
Related