midi_device.event = function(data)
local d = midi.to_msg(data)
if d.type == 'note_on' then
transpose = d.note - 60
end
end

I don't think we need this section anymore (Actually I don't think we ever did). It looks for a root note as midi input and then transposes everything accordingly.

I know you suggested adding a separate device for each track. I'm not sure I know that would work yet. And currently the MIDI channel is just assigned by track number (e.g. Track 1 = Channel 1, Track 2 = Channel 2, etc.). So until we implement something more complicated, should we comment out midi out device and midi out channel from the parameter menu? Right now, they don't do anything.

R8C9 currently clears all tracks of notes. I think that button should reset the playheads back to zero (start) and also reset the playhead directions all back to forward. Essentially resetting everything back to default.

Second of some ideas to give us a UX a little more like FM.

As $subject, e.g. pressing and holding key 2 causes the grid to use all eight rows to display all four tracks as they appear on their individual pages.

Alternately (or maybe stretch goal? ;p), assign a grid key toggle and make this a new page, i.e. sequences are playable/editable the same as on their own individual pages.

I know that we're in that realm of "happy accident", and we have MIDI out to capture sequences in case something really nice pops out, but it'd be kind of cool to be able to save and load the whole "deck" as a preset.

We should have all the leds on the settings page light up when pressed to indicate a change has been made.

@millxing

Similar to #2, but this one refers to different MIDI devices connected to norns.

This is undesirable.

pause = 1 is executed at the module level and in init(), so I'm not sure what I've done

When pausing the sequencer with MIDI output, the last MIDI note played fails to turn off (stuck note).

Third of some ideas to give us a UX a little more like FM.

UX thought: Use the "reverse" button - first tap reverses, second ping-pongs, third goes back to forward.

I really like to use the scalar transposition feature, but one thing that bugs me is when you transpose above/below the limits of the scale vector, it loops around and shits the note to the bottom/top of the scale. This sounds bad (I think), but the nice thing is that it preserves the shape of the sequence. It sounds better to just limit the sequence to the bottom or top of the scale, but then you lose the relative positioning of the notes within the scale.

Nice to be able to output each track to a separate channel for output to e.g. a DAW, or maybe multiple outboard gear.

Upon starting the sequencer, the transport is playing, but the pause grid button (southwest-most led) is already lit up.

I set up 4 different sounds in VCV Rack sequenced by 4 MIDI channels coming from Quence. I was just listening to these sequences slowly evolve (randomness parameters = 3-5) and started thinking it would be cool if the Randomness and RestFrequency parameter slowly modulated themselves. Either from some internal LFO or random source, or from some external source like RACK or Ableton.

NOT IT 😝

I don't have a crow, so I won't be implementing this, but I can't think of why this wouldn't be a good idea and reasonably straightforward to implement.

As it stands currently, choosing or even just scrolling past the crow jf output option will put JF into Synthesis mode. The problem is that it never leaves synthesis mode. So a users JF module will be stuck in Synth mode until a power cycle.

I've had a couple drinks, so I'm not going to fix tonight :) My thoughts at the moment are to change setup_jf() to something like...

if track1 or track2 or track3 or track4 are outputting to "crow jf" then
    jf mode = 1
    crow pullup = true
else
    jf mode = 0
    crow pullup = false
end

(pseudo code obvs :) )

putting this here to make sure I remember to fix it tomorrow :)

The block of leds on the settings page (R5-C6, C13-C16) currently sync all tracks by setting all the playheads back to zero (start). I think we should formally define which button does this and add it to the instruction graphics. What other functions could we add to this block of less?

While I have completely failed to figure out how to use Cheat Codes (despite reading the manual and watching a couple of videos), I do really like the help mode it uses.

When in help mode, pressing a led indicates on the screen what the function of the led is. I think we could implement something like this.

First of a few ideas to give us a UX a little more like FM.

Instead of literally reversing a track's sequence, play it backwards, e.g. from right to left.