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

Axx run Table xx
Bxxselect Vibrato program xx
Cxyplay arpeggio chord, x = 1st note, y = 2nd note
Dxxdelay note by xx ticks
Exxselect ADSR Envelope xx
Fxyplay MultiFX, x = speed, y = MultiFX number
Gxxselect Speed Table xx
Hxyrandom (pre) jump in Table/Pattern or terminate Pattern
Ixxset audio engine interval (number of times per frame that audio is refreshed)
Jxyrandom (post) jump in Table/Pattern or terminate Pattern
Kxxkill note after xx ticks
Lxxslide to note, speed xx
Mxxset Gate Time xx for note
Nxxset Hard Freq amount xx
Oxxscale output level of note
Pxxlinear Pitch Sweep, xx = speed, 01 to 7F for up, 80 to FF for down
Qxxset step resolution/speed for Pitch Sweep. Chord and Vibrato
Rxxretrigger note at speed xx
Sxxnon-linear Pitch Sweep, xx = speed, 01 to 7F for up, 80 to FF for down
Txxset fine tune (detune) of xx
Uxxset probability of note playing
Wxxset Duty or select Duty Table xx
Yxxselect Echo program xx
Zxxset Table speed, xx

Commands For Tracks E (DCM)

Some of the Commands are reused to provide unique functions for Track E only.

Exxset sample End Offset
Lxxset sample looping on/off, 00 = off
Pxxset playback speed of sample
Sxxset 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.