;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; CAKEWALK ASCII FILE FORMAT -- EXAMPLE FILE ;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Lines that begin with a semi-colon are comments. You can put ; anything on a comment line; it will be ignored by the Asc2Cake ; processor. ;;; The ASCII file is made up of three sections: ;;; VARIABLES, TRACKS, and EVENTS ;;; ;;; These are described below. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; This is the VARIABLES section. You can set Cakewalk variables ;;; like the Tempos here. ;;; ;;; Any variables you omit will be assigned default values, which ;;; are the same as the defaults Cakewalk itself uses. For instance, ;;; if you omit the Timesig variable, 4/4 will be used, which is the ;;; default time signature in Cakewalk. ;;; ;;; It must be the first section of the file, and it must begin with ;;; the following line (even if you list no variables at all): [VARIABLES] Tempo=120 Tempo1=60 Tempo2=120 Tempo3=240 Timesig=4/4 Keysig=0 ; Note that the Keysig variable is a value from 0..11, for C..B. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; The TRACKS section follows the VARIABLES section. It contains ;;; information very similar to that found in the Track View. Each ;;; line is like a line of the Track View. ;;; ;;; Each line is of the format: ;;; ;;; "" [*] ;;; ;;; is the number of the track (since you can omit tracks) ;;; is the name enclosed in a pair of double-quotes ;;; is the active status "PLAY" or "mute" ;;; is the pitch transposition (-127..127) ;;; is the velocity transposition (-127..127) ;;; is the forced MIDI channel, (1..16, or 0 for none forced) ;;; An asterisk (*) is appended if the track is selected. ;;; ;;; The ASCII==>WORKFILE conversion program will supply default values ;;; for tracks you omit. These are the same as used in an empty work ;;; in Cakewalk. ;;; ;;; The section must begin with the following line (even if you ;;; list no track information at all): [TRACKS] 1 "Bass Line" PLAY 0 0 0 * 2 "Solo" mute 12 0 0 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; The third section is the EVENTS section. It contains a list of ;;; events, in temporal (time) order. The format of each line is ;;; similar to that of the Event View: ;;; ;; [:][:] [[] ] ;;; ;;; The semi-colon (:) or bar (|) MAY be used to separate the , ;;; and fields, but a space is okay, too. ;;; ;;; different from the Event View. A single letter is used to denote ;;; the event kind (rather than spelling out its name) to save space: ;;; 'N' -- Note ;;; 'K' -- Key (note) pressure/aftertouch ;;; 'M' -- Monophonic (channel) pressure/aftertouch ;;; 'C' -- Controller ;;; 'P' -- Patch/program change ;;; 'W' -- pitch Wheel position ;;; 'T' -- Tempo change ;;; 'A' -- track Active status ;;; ;;; , , and depend on what kind of event it is. ;;; In contrast to the Event View, these are all raw numbers. For instance, ;;; MIDI key numbers are given for note events, rather than the converted ;;; pitch string format of the Event View. The other notable exception ;;; is the pitch wheel event ('W'), whose two bytes are converted to a ;;; single signed number in the Event View. In short, all data fields ;;; are given in raw numbers as defined in the MIDI spec. ;;; ;;; This section must begin with the following line (even if you ;;; do not define any events): [EVENTS] ; ; Here is a C major scale, in quarter-notes (durations=120, and 120 ticks ; equals a quarter-note), on track 1, MIDI channel 1: ; 1 1 1:1:0 N 60 64 120 1 1 1:2:0 N 62 64 120 1 1 1:3:0 N 64 64 120 1 1 1:4:0 N 65 64 120 1 1 2:1:0 N 67 64 120 1 1 2:2:0 N 69 64 120 1 1 2:3:0 N 71 64 120 1 1 2:4:0 N 72 64 120 ; Note that MIDI key numbers, not pitch strings, are used. ;;; The following section header should be included at the end of ;;; the file: [END]