Automation…, Delete Global Time, Insert Global Time, Delete Events, and Modify Levels… commands are logged as single list items. Each of these actions is available for Undo, as long as they remain on the History List.

•Using this list, it is possible to regress to any point in the mix. If at some point things went in the wrong direction, it’s easy to go back to where the mix was on the right track.

•Highlight any item in the list to deactivate all forthcoming listed actions. When the mix is played, no actions listed below the selected event will occur.

•If an event is selected in the list, then a change is made in the Mix Editor, all events following the selection will be replaced by the new event.

•Use the Undo command from the Edit Menu (Ctrl+Z) or the control surface to regress through the History List steps one at a time.

•Use the Clear Edit History command from the Edit Menu to remove all events from the History List. This action cannot be undone.

The MIDI Map Window (Ctrl + –)

The MIDI Map window offers setup options for bidirectional MIDI control of practically the

entire console’s parameter set. The MIDI Map provides complete parameter access to almost all channel functions, master fader, channel strip, and Aux master controls, and all plug-in parameters. In addition, the Master section and Transport controls are assignable to MIDI messages. Additionally, a ‘roving ’ Fat channel map routing may be added, so that MIDI control may follow the selected Fat Channel, which is great for external devices such as a joy stick or X-Y pad controlling (for example) a channel’s Surround Pan without hard mapping (and subsequent remapping). MIDI Maps may be created and saved to disk for subsequent recall.

MIDI continuous controller, polyphonic aftertouch, and note on messages are assigned to the various parameters via the MIDI Map, in a linear approach of one controller type per param- eter. Any variable controller may be a continuous control message or a poly aftertouch message, and any switch message (on/off or assignment switches) can be assigned to a note on (or note off as note on of velocity 0) message.

Messaging may be bidirectional. This means you can control the console from a sequencer or control a sequencer from the console. Note that MIDI program changes may also be used to trigger D8B snapshots. Snapshot program change messages may occur simultaneously with MIDI Map control messaging. The shorter length MIDI program change messages allow for much greater MIDI bandwidth utilization, and in some cases can accomplish the required control without totally mapping the console via the MIDI Map. Snapshot triggering via MIDI is not enabled in the MIDI Map, but is set via the GUI Setup>Mix Options window, by checking the MIDI Snapshot box.

A listing of D8B console parameters is found in the MIDI Implementation Chart at the end of this document. The off, minimum, and maximum values are listed with the associated MIDI controller values to aid in setting up a remote control map. Note that many of the console’s values are

8-bit resolution (255 values). Since MIDI conventionally sends only 128 values (two byte MSB/LSB precision is not supported by the D8B), intermediate steps will be interpolated by the D8B.

Applications for the MIDI Map include remote transport control from MIDI applications that don’t support MMC or the HUI protocol (but do allow their own internal parameter mapping), surround joystick control, or any continuous controller or two-state switch application (light- ing, remote mixing, show controls, etc.). Any mapped control information may be transmitted via manual adjustment on the console, snapshot recall, and/or automation playback (which may include snapshot or other Event track playback).

D8B Manual • Chapter 3 • page 93