Hog in a theater

Easy way to block cue is to only activate the cue you want to block than

To block fixtures that are in the cue :
open the cue
edit
touch
update

Or

To block all fixtures :
Open the cue
edit
select all
touch
update

But a blocking cues function could be useful

Steph,

I know that stuff...also copy with state to programmer and merging back is an easy way to make a blocking cue.
But like I said, the usual problem with blocking cue is that fixtures are added before blocking cue and they get tracked trough.
This could be solved by recording the whole theater rig to cue...but there's no point in doing that.
From a console like Hog3 I expect a bit more clever solution...

What you're describing is the Lightpalette style blocking cue. In theater shows, it's standard to put a blocking cue at the end of each scene to make sure you don't inadvertently track a dimmer into the next scene.

But the Lightpalette series (and similar consoles like the Obsession) are all single cuelist, intensity only, consoles. The "Hog way" of accomplishing the same thing is to use a different cuelist for each scene. If you need a LP style blocking cue, it's easy enough to create one by touching all of your intensity parameters in a cue. It's a slightly different model, but gets the job done.

Once again...

I don't know anything about Lightpalette (or Obsession)...during last 15 years I've used only Hogs, GMAs and Compulite Vector.

I know putting your scenes in different list is a way to prevent tracking from scene to another.

But, we tend you use a single list for a play...it is just much more simple to run and rehearse. Other lists are used mainly for videos, chases and some FX.

A scene usually starts with a blocking cue and it has the main elements of what the scene is going to be and its purpose is to take care that scene doesn't take tracked data from earlier scenes. If the blocking cue is a BO...then there's a possibility that a scene ends there...
But when the play is in a rehearse state, there's some unsure things.
What are the fixtures we are going to use? Is there fixtures that are supposed to track from scene to another?
The reason why I'm asking an automatic blocking cue is because
Many times several fixtures are added before blocking cue and they are tracked through cause they are not recorded there.
Why they are not recorded there? Because it was impossible to know the final amount of fixtures and there's no point to record hundreds of unnecessary dimmer channels and fixtures to a blocking cue.
An example:
My scene starts with one fixture on and the fixtures from the play that I know are off. Automatic blocking takes care, when more fixtures are added in cues before, they stay off in the blocking cue.

But after all this is not a big issue...

The top request is still the search function.

If memory serves.....there used to be a Blocking function (it was a column in the Cuelist spreadsheet).

I think it was removed for stability reasons, but maybe it will re-appear someday. :dunno:

Marty,

Yeah, I remember that too and I've been wondering how it was designed to work.
What great ideas were hiding behind that button...

Doesn't the state button do that? (select lights, record, cue, x, STATE (from record toolbar), enter

[QUOTE=stephenwyker;47270]Doesn't the state button do that? (select lights, record, cue, x, STATE (from record toolbar), enter

It does, but if you add a fixture(s) into patch, then data for those fixtures will track though.

The automatic blocking could be very usefull.
I work in a theatre where the main console is a Roadhog.
I also think the fixture tracking sheet could is very handy.

Greetings

Wouter

You can open a cue window. It allows you to see current and tracked values. Select a master, then [Cue], [Cue] to open the window. Values in Red are active, Blue is tracked. If you click the follow current, any master you select will then be displayed.

...black are hard values, off is a "released" value and source button gives you the origin of the value.
But, that is not what I'm asking for.
The idea of the tracksheet is to show multiple cues for certain fixtures at the same time. It kind of shows the tracking through all the cues in a list. If I remember right tracksheet is logged as an enhancement.
Though in this case, it is kind of workround for good search function, but it would make things easier and is a good start.

Hi,
My background is theatre style lighting desks all the way back to the AVAB 201. The AVAB Expert had a tracksheet of the style you are mentioning and it was a breakthru toghether with time groups at that time. These where then implemented into the Strand 500.
I agree that this would be a great function for theatre style programming for the Hog OS.

Any news for the tracksheet function?

... i just finished analyzing the effective use of deskchannels in a show with lots of cues in a single cuelist.
The Show State does not help because of all the blocking cues in this cuelist.:sad: