Quirks and Known Bugs

This is just a collection of information for any strange or experimental behaviour. As such, they might get changed, removed or fixed(!) in subsequent releases of Pulsar so don't rely on them unless I move them to the main part of the manual.

Using Pitch Slide Command (Lxx) in Tables

This works but is a bit weird. What happens is that the destination note for the slide is calculated from the current note PLUS the Pitch Offset on the step of the Table where the Slide Command is placed e.g.

0F 0C L08 -00

would slide to a note that is an octave (0C semitones) above the note in the Pattern with a speed of 08.

You can also have multiple Slide commands in a table but the results will be very unpredictable.

Playing Individual Patterns That Are Transposed in Chain

Normally the Transpose value for a Pattern is obtained from a Chain but despite the Transpose value being reset to 0 when the editor is initialised, an indeterminate value for Transpose will be set if you haven't first played the Song or a Chain before playing a Pattern (starting playback from within the Pattern editor).

Editing Notes After Reset/Boot-up Before Song Has Been Played

The Instrument sound for Tracks A, B, C and D will have been 'reset' so only a very basic sound will be played. For the sample channel, Track E, all notes will play the first sample (sample number 00). This will persist until an Instrument has been set on each Track (by playing the Song) at which point the prelisten sound should reflect the Instrument settings on each Track.

Tables For Track E (DCM)

It is possible to use the Run Table command (Axx) on Track E though it has limited use. The biggest difference is that the function of the VL and PT columns are mapped to different functions:

The other quirk with using Tables on Track E is that samples will be retriggered on every step of the Table. This is because changing any sample playback parameters (in the NES's hardware registers) has no effect until you trigger a sample again.