Avoiding unwanted NIP moves

Paul,

I definitely can relate to the "blind noise" issue that arises when programming, especially when you are in a hurry...which is practically all the time. A typical practice I try to maintain while programming is to mentally (and visually by looking on the screen) keep tabs on what my fixtures are doing, even when they are not on. If I spend a lot of time working on a moving light focus and eventually not use it, I always press [Sneak] [Enter] to bring those units back to their original state. Sometimes this can get you caught up with previous errors, so it also doesnt hurt to send everything [Home] [Enter] at the end of big cueing sequences and then build again from there. For instance, at the end of a big musical number, I try and send everything home in the restore cue, then re-assign whatever palettes I am using for the coming cue.

As far as "Cue Only" vs. "Track", I tend to work in "Cue Only", but use [Update] [Track] a lot. Helps to clear out unwanted moves, but keeps the designer able to work in the "Cue Only" mindset.

I realize this is not ground breaking information, but unfortuantely I think it comes down to the programmer :/ I tend to come in at least once before final dress and sit in the quiet theatre for a few hours and listen to every cue to avoid such issues. Especially depending on the space, unwanted moving light noise won't bring smiles from anyone. Spreadsheet is a great clean-up tool though :)

-Nick

Sneak would be how I would get around it.  Some other possible options would be:

-using [Select Active] or [Select Manual] before a record or update.  You have to be careful though - if you have chans at 0 that you want to be recorded at 0, then you can't use select active.

-you can always use [make null] to exclude channels, or parameters from a record or update command. (use sneak or make null to make them un-null)

-Use selective record.  Say for example you don't want chans 1 thru 5 you can use the syntax [- 1 thru 5 records x]

-use a combination of [select manual] and [query].  I just tried this in the offline editor and it seemed to work a treat:

[select manual query {fixture type} VL1000AS {is in} @0 enter] will select all the VL1k's that have had manual changes and are at 0.  From there you can make null, or sneak, or use selective record.

I found that writing a macro with the [select manual query] worked a treat.  You can write a few macros - 1 for all fixtures, another for scrollers, another for VLs, another for Studio Spots... have a play with query as there are many options

Hope that helps

Cheers - BFJ

Nick and Brent,

Thanks for your helpful replies.  I may play with the macros once I have time to set up the X-Keys pad.  Until then, we'll just be Sneaky.

Paul Court

Humber College

Toronto

Hey guys.  There are a couple of things that are happening in 1.5 that will aid in this.

First, we are putting a flag in the PSD (playback status display) for each cue that has a dark move instruction stored in it (excluding lights that are in a marked state).     So, if you are trying to clean up your show, this will be an indication of where you need to look. 

Also, double hitting the sneak key will sneak your NPS, but not your intensity.  So, if you see a light with a manual zero, and also manual FCB data, sometimes you are not sure if you should sneak it (because maybe it was on, and now it needs to be out), but you want to be sure to remove the NPS.   This will make that possible, without having to select FCB or - Intensity before the sneak command is issued.  

About channel provides a list of cues with dark moves.  (does that now).

The .pdf also has a dark moves report.

When we get around to rewriting About Cue, that will provide a list of channels in the cue with dark move instructions.  

Hope this helps.

a