block + unblock

unblock is a function which removes the parameters already present in the preceding memory.

exemple: cue 1 is 1 thru 8 @full
cue 2 is 1 thru 7 @full + 8 @ 50
if you unblock cue 2 it will became 8@50, as 1 thru 7 @full is already in the cue hog 3 don't need it in tracking mode.

from manual P204:
To unblock cues, use the Unblock button in the Main Toolbar:
• Cue 3 Unblock, Enter : unblock cue 3 on the currently chosen master.
• List 1 Cue 3 Unblock, Enter : unblock cue 3 of cuelist 1.
• Cue 1 Thru 10 Colour Unblock, Enter : unblock only colour parameters
in cues 1 through 10 of the cuelist on the currently chosen master.
• List 1 Cue 3 Group 10 Colour Unblock, Enter : unblock only the colour
parameters of fixtures in Group 3, in cue 3 of cuelist 1.
To unblock complete cuelists:
• List 1 Unblock, Enter

manual page 203
to turn Cue 4 into a blocking cue, you copy it to itself ‘with state’:
1. Cue 4 Copy State Cue 4 Enter : the State button is on the Record Options
Toolbar that appears when you press Copy.
2. Select Replace.

so you will have a full cue. on hog 2 it was: load cue 4, pig+active, update

O.k. thanks Steph
So the unblock remove the tracking info, but i still don't know for what i need a blocking cue. and when i record it the same way as the manual say and the same intensity velues, the time i do a "copy to itself" this is not the same result like the menual.

Thanks again Steph
Amir

Amir,

Often times, you will want to block intensity in a blackout cue. That way, even if you add a new fixture into the cues before it wont track through in a cue that's supposed to be black.

I'll also block cues at the beginning of each scene when I'm working on a more traditional theater show. This is so that if I make a color change in scene 1 it won't track through into scene 2.

Tom,

I understand now, very good tool.
But both, block and unblock, don't work in my Hog, i try Cue 3 Unblock Enter, nothing happen, tracking values still in the cue. i try to block some cue's but again, nothing happen, the cue dont act the same like the manual.

So...maybe my Hog have some bugs...?

Thanks
Amir

Yeah, unblock is a little bit broken right now...and they know about it.

FYI, the fastest way I've found to create a block cue is the following syntax:

Cue XXX Merge State Cue XXX Enter. You can also use masking with this syntax if you want to, for example, only block intensity in a cue.

Amir,

Hillary is correct that there are a couple of scenarios where unblock doesn't work properly, but you should see it unblocking. Try creating a new cuelist with some fixture data in cue 1. Copy cue 1 to cue 2, then type Cue 2 Unblock Enter. This should remove all of the hard values in cue 2. If you open cue 2 in an editor and turn off Show State, it shouldn't have any data. You should also see that it doesn't have a fade time in the cuelist window since it doesn't have any parameters.

I hope this helps.

Oh yeah, I don't know if I've mentioned this before or not, and it may already be in the pipeline independently of me, but if would be really cool to have a syntax like:

Cue 12 Pig+Unblock (changes to the masking toolbar and you can set masking) Enter (toolbar returns to normal). So, as you might imagine, in my little scenario, Pig+Unblock = Block.

Hillary,

I've opened enhancement #9400 for this request and I've added your comments to the enhancement.

Thanks.

Using blocking cues will be much easier once the "Blocking" cells in the cuelist are working properly. So turning blocking on and off on a cue by cue basis will be very easy.:D

Next software release perhaps?:confused:

Marty,

Enhancement #6057 discusses implementing blocking functionality, but this probably won't happen in the immediate future. Right now we're very focused on some patch releases with important bug fixes and releasing console software that will communicate with Hog 3PC.

Thanks for the update Tom:)

I agree that there are much bigger priorities right now!
Keep up the good work down there as we all very much appreciate it!:headbang:

Yeah, if I remember correctly, several years back, in talking with some of the original developers, the idea for the blocking cells in the cuelist window was to toggle a complete block for that entire cue...a "blocking for dummies", if you will, that would be unaffected by and supercede any kind of Merge Remove or toolbar Unblock function. Then, if you needed more specific blocking, you would do it via the command line & toolbar.

That's how it was explained to me also, Hillary. One thing that would be kind of cool about that implementation is that you don't have to worry about updating all of your block cues when you have to add fixtures to your show.

It might be cool if the blocking column either showed Off or some combination of IPCBE. Then you could use this functionality on a per-parameter group basis.

OK, how about this idea:

1. It shows "On" only if the cue is blocked on a "cuelist priority" basis...i.e. blocked using the Block cell in the cuelist window
2. It shows "Off" when the cue is completely unblocked and not blocked on a "cuelist priority" basis
3. It shows some combination of IPCBE in dark grey text if one or more of these parameters is blocked.
4. It shows some combination of IPCBE in black text if one of those parameters is completely blocked.

Some examples:

if you had a cue where only the color & intensity was partially blocked, you'd get: I-C--.

If you had a cue where the intensity was completely blocked, you'd get: I----

Intensity & Color completely blocked, some Position blocked: IPC--

I can't even begin to tell you how useful this kind of functionality would be to me.