Re: 10.6 Tutorial: POST2 - Record Cue
Posted: Thu Jul 16, 2009 6:10 am
jgoss wrote:Fantastic job Bobby. The tutorial's are really great. If only the manual was written in the same easy to understand fashion...
Maybe start the tutorial with the fact that the console needs to be in a certain personality and state that people should experiment with the settings to find you own favorites. Settings are well explained in the tutorial.
Maybe mention first that [SHIFT] and all the actions you will discuss bring up a window that contains extra help with that function.
p. 7-8 If you dedicate a considerable amount of space to tracking, you should do the same for This Cue Only. e.g.:
p. 10 Maybe you could explain the word "assert" a bit more.This Cue Only comes from the preset boards, that replaced the manually operated resistance dimmers backstage. On these boards you could set up multiple cues (or looks) in advance. (Pre-set) Because of it's nature you'd have to set the entire look for every single bank of faders. You could then fade between those banks of faders.
The advantage of this is that if something changes in one cue (or look) it will never affect others. And, while it can seem quicker to only program the lights that change, don't forget that with Cue Only lights that go to zero don't have to be recorded. So if you have lighting states that change a lot it can actualy be quicker to work in Cue Only mode. It is also less difficult to record cues in a different order than they will be played. If you'd have to record a show where cue 3, 7, 9, 11, 15 and 21 are the same and everything else is different, you don't have to worry about tracking channels in Cue Only.
p. 11 "Show checkpoint time" The menu item itself is unclear. You could easily think that the checkpoint time is shown somewhere. "Autosave checkpoint file (in minutes)" would be much clearer (Although this is not a point for your tutorial)
p. 12 I would not give your readers the idea that the console is so unstable that you'd better save after every keypress. (They will find out themselves after a while )
p. 20 "Deleting a range of cues is no different that deleting a single cue. It just applies to multiple
This paragraph also has the first mention of the infamous Blue Box. Maybe you should mention earlier or tell a bit more what it is here. I would prefer to talk about 'selected cel', rather than blue box. I know it is another part of Horizon history that I am talking about. It might be sensitive, but it must make sense (and sensibility!)
p. 22 Remove Redundant Data is already mentioned on page 18. Why split the information. I think the parts on p. 18 and 22 should swap or be joined to one.
p. 26 Warn for the fact that people should try to navigate in blind with the Step forward/Step back keys for the cuelist. They always control your live cuelist! (Made that mistake!)
p. 27 Moving Around the Cue List. You'd like to have this information much earlier.
p. 29 "The logic is that it is always DELAY / FADE since that’s the way time works in the universe." What universe? Explain. This doesn't make it easier for me to understand.
p. 30 I would explain the independent timing first and then go to cue parts. Because the concept of independent timing makes partcues obsolete. The only use for them is to graphically show what happens when and to be able to label what is going on when.
p. 31 Maybe mention the labeling of normal cues earlier.
p. 39 Follow (time) will start counting from the moment the cue that is to be followed on starts. So in your example there is 4 seconds between the completion of the cue, till the next cue is following.
p. 41 It would make sense to explain deleting cues here. If you delete cues that were skipped with a link before you'd have to delete preserving the cuestate. (I forgot the precise terminology here)
p. 48 see posts above! Please change for sake of clarity.
p. 53 and before. In these cases it could be useful to mention the default values or the values you used for the examples in the tutorial.
p. 55 Maybe you could explain 'external SMPTE' it refers to a physical connector on the console?
I miss releasing the cue, cuelist or all cuelists in an early part of the tutorial (only the mouse action is explained on p. 58)
Pfff. That was a long one!