Overview of Pattern & Table Commands
This page is intended as an overview of the Commands available to use in Patterns and Tables. Many of these will be familiar to LSDJ users as generally, where appropriate, I've tried to match the command letter to the same/similar function that appears in LSDJ. However, there are some that I've left out (where not appropriate) and others that I've added.
Commands For Tracks A to D
|
run Table xx |
| select Vibrato program xx |
| play arpeggio chord, x = 1st note, y = 2nd note |
| delay note by xx ticks |
| select ADSR Envelope xx |
| play MultiFX, x = speed, y = MultiFX number |
| select Speed Table xx |
| random (pre) jump in Table/Pattern or terminate Pattern |
| set audio engine interval (number of times per frame that audio is refreshed) |
| random (post) jump in Table/Pattern or terminate Pattern |
| kill note after xx ticks |
| slide to note, speed xx |
| set Gate Time xx for note |
| set Hard Freq amount xx |
| scale output level of note |
| linear Pitch Sweep, xx = speed, 01 to 7F for up, 80 to FF for down |
| set step resolution/speed for Pitch Sweep. Chord and Vibrato |
| retrigger note at speed xx |
| non-linear Pitch Sweep, xx = speed, 01 to 7F for up, 80 to FF for down |
| set fine tune (detune) of xx |
| set probability of note playing |
| |
| set Duty or select Duty Table xx |
| |
| select Echo program xx |
| set Table speed, xx |
Commands For Tracks E (DCM)
Some of the Commands are reused to provide unique functions for Track E only.
| set sample End Offset |
| set sample looping on/off, 00 = off |
| set playback speed of sample |
| set sample Start Offset |
Some Notes About Commands
Something to bear in mind is that there is no range checking on the parameter value for any of the Commands. Please refer to the section "Command Details" for details on limits for each command.
Having said that, it's not likely that you could cause anything to go (too) drastically wrong as although the editor will allow you to pretty much enter any value, there are some internal checks in place to sensibly limit the parameters. This will manifest itself generally as values "wrapping around" e.g if a parameter's range is 00 to 1F and you enter 2F, the value that gets sent to Pulsar's engine will likely be 0F. If you understand about binary operations on numbers this will make sense. If not, don't worry about it.
Also, it might be apparent that some of the Commands don't apply to certain voices. For example, there is no Pitch Bend for Track D (noise). Pulsar ignores Commands where they are not appropriate.