Autoblocks

Greg, Eos will create an autoblock when a move instruction is matched by a move in the preceding cue.  An example might be useful.

Cue 1 - channel 1 at full.

channel 1 tracks at full until cue 10.

In cue 10, channel 1 has a move to 50.

At some point, you set channel 1 to 50 in cue 9.  

Eos will autoblock channel 1 in cue 10.

Essentially, an autoblock preserves the concept of a move instruction, even when the level is now the same as the cue before.   The other option would be to turn channel 1 to a track in cue 10.   By  autoblocking the data,  the "move" is protected.

Does that make any sense?

a

In my theatre, we call them "partial blocks" and have made a macro to get rid of them, which the operator does whenever he has time.

In my theatre, we call them "partial blocks" and have made a macro to get rid of them, which the operator does whenever he has time.

If  you leave auto blocks do they affect anything?

The autoblock will stop a tracked edit, just like a block does.  Autoblocks are noted with an underscore in white (all blocked data is represented in white).

Hope that helps.

a

Anne,

(and others)  I, too, use a "clean up" macro to get rid of those pesky partial blocks in cues as I'm teching.  I was wondering if the "autoblock clean up" feature in the "UTILITIES"  menu of the browser is working yet?  Is this feature supposed to clean up an entire showfile? or just the current cue list? or just a single cue? 

Dan at BAM

EOS programmer at Brooklyn Academy of Music

Dan, it isn't working yet.... our intent is to provide that function to make it easier to clean up auto-blocks without removing deliberately applied blocks.  At some point, in addition to the utility, we will also provide a setup option that disables the auto-block function.  For people who love that feature, as it protects your show data, they can't live without it.  For others, they are, indeed "pesky."  Pretty big jump ball.... 

a