mididocs:seq:configuringtracks
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mididocs:seq:configuringtracks [2014/09/18 13:15] – [Trigger Layer Assignments] borfo | mididocs:seq:configuringtracks [2016/03/22 21:20] (current) – ↷ Links adapted because of a move operation admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | **[[mididocs: | + | This page is obsolete, most information |
- | ======Configuring Tracks====== | + | |
- | [[http:// | + | |
- | + | ||
- | Some information about track provisioning, | + | |
- | =====Track Memory Requirements===== | + | |
- | The SEQ is a 16 track sequencer, but each track is basically a collection of [[layersintro|Trigger and Parameter Layers]] - each step in a track records several layers of information. The more layers of information that are recorded, the more memory will be required to store each step. | + | |
- | + | ||
- | Each step in a Parameter Layer can store 128 values. | + | |
- | + | ||
- | Each step in a Trigger Layer only contains an on or off value. | + | |
- | + | ||
- | The SEQ allots a certain amount of memory to each track - 1024 bytes (or 8192 bits) dedicated to storing Parameter Layer information, | + | |
- | + | ||
- | Note that the instruments in a drum track are basically the same thing as Trigger Layers - they have an on and off value for each step (eg: is the snare drum played here? yes/no) | + | |
- | + | ||
- | The SEQ conveniently provides predefined track types which divide up the available memory in various ways. | + | |
- | {{layers.png}} | + | |
- | + | ||
- | If you do the math on that chart, it looks like there must be some memory overhead that I didn't take into account that makes each step of a Parameter Layer require 1 full byte of memory rather than just 7 bits. But whether the above is 100% accurate or not, it's probably way more than you need to know in order to operate the SEQ anyway. | + | |
- | + | ||
- | =====Who Cares? | + | |
- | Fine. | + | |
- | + | ||
- | Press MENU + GP Button #2 to enter the TRACK EVENT Page, which looks like this: | + | |
- | {{trkevent1.gif}} | + | |
- | + | ||
- | Turning Encoder #1 selects which track you're working with. Turn Encoder #2 to choose one of the track types from the table above. | + | |
- | + | ||
- | =====Port and MIDI Channel Assignment===== | + | |
- | + | ||
- | Self explanatory. | + | |
- | + | ||
- | =====Parameter Layer Assignments===== | + | |
- | + | ||
- | After you've initialized the track, the options displayed on the right side LCD on the TRACK EVENT Page will vary depending on what track type you chose. | + | |
- | + | ||
- | ====NOTE, CHORD, and CC Tracks==== | + | |
- | Parameter Layers (including the chord layer type) can be assigned on the right LCD. These three track types are essentially the same, the only difference is the Parameter Layers that are assigned by default. | + | |
- | + | ||
- | ====DRUM Tracks==== | + | |
- | Drum Tracks are different. | + | |
- | + | ||
- | On the right LCD, you can assign the 1 or 2 Parameter Layers that are provisioned for the selected Drum Track Type. You can also set up the track' | + | |
- | + | ||
- | * set a midi note - the SEQ will send this note out the selected Port/ | + | |
- | + | ||
- | * assign a name (press GP#8 to edit the name, or just accept the default name provided). | + | |
- | + | ||
- | If the Track has an Accent trigger layer, you can also set the VelA and VelN values - these represent the Normal Velocity (VelN) of the instrument, and the Velocity at which the instrument will play if an Accent is triggered (VelA). | + | |
- | + | ||
- | **Shorter Parameter Layers in some drum tracks**: | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | =====Track Length (LEN)===== | + | |
- | Press MENU + GP Button #6 to enter the TRACK LENGTH Page | + | |
- | {{trklen1.gif}} | + | |
- | + | ||
- | Look at the track types table above again for a second. | + | |
- | + | ||
- | You can choose a track length manually with Encoder #2 (this is good for selecting non-standard phrase lengths), or you can press one of the quickselect buttons on the right LCD to choose from a list of predefined lengths: 4, 8, 16, 32, 64, 128, or 256 steps. | + | |
- | + | ||
- | + | ||
- | + | ||
- | =====Track Timebase (DIV)===== | + | |
- | Pressing MENU + GP Button #5 opens the TRACK DIVISION (DIV) Page. | + | |
- | {{trkdiv1.gif}} | + | |
- | + | ||
- | This page allows you to change the resolution of the track (change the number of beats each step in the track represents) by dividing the midi clock. | + | |
- | =====Trigger Layer Assignments===== | + | |
- | + | ||
- | MENU + GP Button #9 takes you to the Trigger Layer Assignments page. | + | |
- | {{trgasg1.gif}} | + | |
- | See the MIDIdocs article on [[layersintro|Trigger Layers]] or the [[http:// | + | |
- | + | ||
- | Remember that you can assign more than one trigger to a single Trigger Layer, making it a " | + | |
- | + | ||
- | Most track types include all 8 types of Trigger Layers, so you really don't need to worry about reassigning them. But the ability to assign trigger layers can be useful for drum tracks, which don't have many trigger layers. | + | |
- | + | ||
- | =====The TRACK MODE Page===== | + | |
- | MENU + GP#3 opens the TRACK MODE Page. | + | |
- | {{trkmode1.gif}} | + | |
- | Read the [[http:// | + | |
mididocs/seq/configuringtracks.1411046110.txt.gz · Last modified: 2014/09/18 13:15 by borfo