cues programming

Part 20 is commonly used to mark channels when AutoMark is disabled and parts can be used to influence the speed of the marking. This is part of what's called Referenced Marking. It doesn't have to be part 20, or any part at all, but it is considered best practice in bigger shows by a lot of programmers.

I don't think there can be any sort of efficient workflow where you try to convert absolute data into presets after the fact. You should definitely look into creating a preset right away, even before recording the cue this position will be used in.

At our school, we have an Element 60. I want to learn good practises for programming theatre shows. Because we have multiple people work with the lighting console, I put the console in cue-only, so that people starting out have an easier time. But I found myself hating cue-only later in the process when I can to select multiple cues to copy an edit to after I changed something, something tracking would have avoided.

So I am now reading information about tracking vs. cue-only, because I am considering switching to tracking (I have heard that once you understand it and you incorporate it into your though process, it is much more efficient than using cue-only).

I feel like cue-only requires a simpler mindset, but more work to fix things later (so initially easy, then hard). And tracking is harder to grasp at first (and requires actual practise), but less work to fix things (so initially hard, then easier). Is this thought correct?

But while thinking about this, some questions come up. For example, when you edit in cue-only and you have 5 cues in a row doing the same thing (except a few lights that change between the 5 cues) you can choose to edit any of the cues (first one, last one, or even one in the middle) and then copy it carefully to the rest. But with tracking, do you always need to trace back to the place where the light got the parameter information that you are now editing (so the first cue)?

Also, with cue-only you always know that if you do Go To Cue 10, then the complete cue 10 will the put on stage. If the console is now in tracking, does it also put on the tracked values into cue 10 (which would be expected behavior) or will it only do the move instructions that are stored in cue 10?

With cue-only you just have completely independent cues, and two contiguous cues that are two different scenes are just two cues and that's that. But with tracking, is it maybe a good idea to put a Block on the first cue of a scene, so that the new scene is completely independent of the previous scene?

At our school, we have an Element 60. I want to learn good practises for programming theatre shows. Because we have multiple people work with the lighting console, I put the console in cue-only, so that people starting out have an easier time. But I found myself hating cue-only later in the process when I can to select multiple cues to copy an edit to after I changed something, something tracking would have avoided.

So I am now reading information about tracking vs. cue-only, because I am considering switching to tracking (I have heard that once you understand it and you incorporate it into your though process, it is much more efficient than using cue-only).

I feel like cue-only requires a simpler mindset, but more work to fix things later (so initially easy, then hard). And tracking is harder to grasp at first (and requires actual practise), but less work to fix things (so initially hard, then easier). Is this thought correct?

But while thinking about this, some questions come up. For example, when you edit in cue-only and you have 5 cues in a row doing the same thing (except a few lights that change between the 5 cues) you can choose to edit any of the cues (first one, last one, or even one in the middle) and then copy it carefully to the rest. But with tracking, do you always need to trace back to the place where the light got the parameter information that you are now editing (so the first cue)?

Also, with cue-only you always know that if you do Go To Cue 10, then the complete cue 10 will the put on stage. If the console is now in tracking, does it also put on the tracked values into cue 10 (which would be expected behavior) or will it only do the move instructions that are stored in cue 10?

With cue-only you just have completely independent cues, and two contiguous cues that are two different scenes are just two cues and that's that. But with tracking, is it maybe a good idea to put a Block on the first cue of a scene, so that the new scene is completely independent of the previous scene?