boogiemonsta / quantumtracker Goto Github PK

While sequencer is playing, punching steps in only works if done very slowly.

Otherwise, the loop plays the steps in unpredictable spots of the sequence. When that happens, stopping and starting playback fixes the issue, the sequence itself is not where the bug resides.

Punching in steps while the sequencer is playing also generates clicks and pops, potentially linked to issue #4.

When activating/deactivating steps by clicking them in the interface, it updates the sequence accordingly, but the reverse isn't true

If I hard code a sequence to be [1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0] it plays it back correctly as 1/8th notes, but on the interface I don't see the steps.

The binding between the steps displayed in the interface and their 1 or 0 counterpart inside their sequence must be made to go both ways.

As a user, when playing a sequence, I wish to instantaneously hear the changes I make when I move the BPM slider.

Right now, a change to the BPM slider is only heard once a new cycle begins (as if the modification was quantized to the whole cycle length).

Inside of Tracker.vue, the variable bpm is reactive, but the issue must be with the gate variable, calculated from the BPM to be exactly the length of the cycle, and used to trigger the sequences.

When the samples play through QuickTracker, they don't sound as good as when playing them in any audio editor.

In QuickTracker, the transients sound dull and smeared off, and it generally sounds much more "lofi", as if run through a bit reducer, or at a lower sample rate.

There's also random cracks and pops when activating/deactivating steps while the sequencer is playing.

Switching the mp3 files for their original wav file counterparts instead doesn't change the issue.

After punching in a sequence, when pressing the QuickTracker logo or the 'space' bar, there is a delay before the sequence starts playing

This delay before playback is related to the BPM: the slower the BPM, the longer the delay. This issue must be related to #3.

-> Look into the reset value for setInterval.