Pressing any of the highlighted letters in the variable headings will move the cursor directly to the indicated variable. You can then press Enter to edit the highlighted variable or simply type the new value. Numeric variables can also be changed by pressing the Page-Up (+1), Page-Down (-1), Ctrl-Page-Up (maximum) and Ctrl-Page-Down (minimum) keys.

If a mouse is installed, you can move the cursor directly to a variable by clicking on it. A second click selects the variable for updating. Click on the arrows in the bottom left and right corners of the screen to increment and decrement the values of numeric variables.

CHANNEL VARIABLES VIEW

This view contains data which relate to the MIDI channel used by each track. These variables are referred to as the 'initial controllers' as they are MIDI controller messages that are sent before playing a sequence. You can also send them manually by using the Initialize option on the Event menu.

Events in a track (eg. a system-reset sysex) can be transmitted before the initial controllers. See the dly+ (delay) variable in TRACK VARIABLES VIEW.

Since the settings for a channel apply to all tracks which are using that channel, the variables for all tracks on the same channel are automatically updated when one of them is changed.

The first few variables in this view are the same as those in GLOBAL VIEW. The following variables are specific to CHANNEL VARIABLES VIEW:

 vol       The initial volume controller


 bal       The initial balance (pan) controller


 mod       The initial modulation (vibrato) controller


 fx1-5     The initial effects controllers


 msb/lsb   The initial bank-select controllers

TRACK VARIABLES VIEW

This view contains settings which apply specifically to each individual track. These settings affect the way that each track and the MIDI data it contains is played. Changing the settings of track variables has no effect on the actual MIDI data stored in the track.

The following variables are specific to this view:

 key+      The key-transposition offset (in semitones) for all notes.  Notes
           transposed to values outside the range 0..127 will not be played.


 vel+      The key-velocity offset for all velocities in the track.  Values
           outside the allowable range will be bounded to minimum or maximum.


 dly+      The tick-offset (delay) for all events in the track.  Events
           delayed before tick #0 (ie. using a negative delay) will be sent
           before the initial controllers when the sequence is played.  This
           allows special events (such as the XG On sysex for the DB50XG) to
           be sent before the MIDI channels are initialized.


 goto      The first beat of the looped section of a track.


 x         The number of times to play the track's looped section (1 to 99).
           A setting of zero causes the track to be looped indefinitely.


 f         The global on/off status of the MIDI filters (see below).  This
           setting allows all filters to be enabled and disabled without
           changing the status of each individual filter.  The status flag
           is a minus sign (-) if filters are disabled (the default) and a
           plus sign (+) if filters are enabled.


           When filters are disabled, setting this variable prompts you to
           confirm by pressing 'f' for 'filter-on'.  When filters are enabled,
           a list of the types of events which can be filtered is displayed in
           the INPUT/OUTPUT LINE.  Press 'f' for 'no filter' to disable the
           event filters.  Otherwise, select the type of event you wish to
           filter by pressing its highlighted key.  If the filter is currently
           disabled it will be enabled, and vice versa.  You can also use the
           cursor to enable and disable the individual filters directly by
           highlighting them and pressing 'Enter'.


 npcmkbtsx The individual on/off status of each MIDI filter for the track.
           These allow selected types of events to be filtered out of a track
           while it is playing.  If a filter is set for a particular type of
           event, no events of that type will be sent from the track to the
           MIDI-OUT port.  This does not affect the actual events stored in
           the track.  When the filters are disabled by the global on/off
           setting (above), each filter is marked with an asterisk.  If
           filters are enabled, event types which will be played are marked
           with a plus sign and types which will be filtered are marked with
           a minus sign (the default).


 size      The number of bytes of memory used by the track.  Most events use
           four bytes, though some use more and some less.  Each beat used by
           the track also requires two bytes, as does the end-of-track marker.
           In this shareware version of BeatMaster the maximum size of each
           track is 65516 bytes.

Go to BeatMaster : Info : Views