24.08.2013 Views

ETC Ion - Theatre Uwinnipeg

ETC Ion - Theatre Uwinnipeg

ETC Ion - Theatre Uwinnipeg

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using [Undo]<br />

Undo is a method to reverse or “undo” certain operations performed in the software.You can use<br />

[Undo] to reverse any command that results in a change to data that would be saved to the show<br />

file or any command that changes manual levels in live. Commands that can be reversed using<br />

[Undo] are:<br />

• Record and update operations<br />

• Delete commands<br />

• Manual level changes<br />

If there are any commands in the command line, pressing [Undo] once clears the command line.<br />

Once the command line is empty, pressing [Undo] will start the undo process.<br />

When [Undo] is pressed from an empty command line, the command history display will open in<br />

the CIA and the most recent completed command is highlighted in gold. If you press [Enter], you<br />

will undo your last command.<br />

You may use the page arrow keys to select multiple commands. When [Enter] is pressed an<br />

advisory is posted. When [Undo] is pressed again, all highlighted commands will be undone and<br />

subsequently removed from the command history. When removing more than one command, a<br />

confirmation is required.<br />

After an Undo has been performed, a {Redo} button will appear in the command history. You may<br />

press this button followed by [Enter] and the last undo will be “redone” to reinstate the removed<br />

commands.<br />

In a multiple user environment, each user is only able to undo the changes that they made. In the<br />

undo command history, the user will only see the commands that they used.<br />

Note:<br />

Command History<br />

Commands to be<br />

undone<br />

Not all commands can be undone including playback actions and manual<br />

attributes placed on channels or encoder actions.<br />

Command histories are kept for each editing session which begins when the console logs on to the<br />

network or when you load a new show file. Each user builds an individual command history, specific<br />

to the commands they have entered.<br />

You can open the command history at any time by pressing {Cmd History}.<br />

Commands that do not affect manual input or record targets (loading a cue, running a cue, or<br />

moving a submaster) are not included in the command history.<br />

15 Advanced Manual Control 201

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!