"Record live sequence changes" functionality

[slightlynasty]

First off, thanks for being so responsive with these issues/suggestions, it's really great!

Currently the "record live sequence changes" only adds patterns into the song timeline as whole loops, starting at the last pattern loop and ending at the next, and ignoring queueing completely (queueing a pattern just adds it to the song immediately). It seems to me that a live-oriented sequencer like Seq66 should have the ability to record a live performance as accurately as possible, so that a user can simply hit the record enable and do their live performance, knowing that can then go back and replay it exactly (if they want to do a recording session for example, or perform the same track while focussing entirely on knob tweaking etc.)

The song timeline already supports arbitrary start/end points for pattern "chunks", so it seems like this should already be possible. Thoughts?

[ahlstromcj]

That sounds reasonable. I will have to think it through. Currently working on fixing variable-PPQN issues and those dang QComboBoxes.

…

-------- slightlynasty 01:01 Sat 20 Mar --------

First off, thanks for being so responsive with these issues/suggestions, it's really great! Currently the "record live sequence changes" only adds patterns into the song timeline as whole loops, starting at the last pattern loop and ending at the next, and ignoring queueing completely (queueing a pattern just adds it to the song immediately). It seems to me that a live-oriented sequencer like Seq66 should have the ability to record a live performance as accurately as possible, so that a user can simply hit the record enable and do their live performance, knowing that can then go back and replay it exactly (if they want to do a recording session for example, or perform the same track while focussing entirely on knob tweaking etc.) The song timeline already supports arbitrary start/end points for pattern "chunks", so it seems like this should already be possible. Thoughts? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #44

-- Knocked, you weren't in. -- Opportunity

[slightlynasty]

Hi! Just looking at this again after a bit of a gap, and there's a few bugs (using 0.99 currently) worth looking into:

1. When recording live sequence changes in song mode, turning "snap" mode off makes the pattern block start exactly when you press the button on the Launchpad, like you expect, but the end point always extends out to the next multiple of the pattern length when you mute it again.

2. With "snap" mode enabled, live sequence changes always snap to pattern length regardless of the snap size setting in the drop-down box. The snap size does work when dragging and resizing pattern blocks in the timeline - except...

3. ...there's an off-by-one error in the snap size drop-down. 1/1 and 1/2 are both 1/1, 1/3 is actually 1/2, 1/4 is actually 1/3 etc.

Again thanks for all your work on this, I know what a pain it is trying to fit these sort of big projects around daily life!

[ahlstromcj]

For 2), do you mean the end of the trigger (when you mute the pattern) is always set so the end - beginngin = sequence length)? In other words, do you want the end of the trigger to snap, like the beginning does? Thanks for any clarification you can provide.

…

-------- slightlynasty 18:42 Sun 02 Oct --------

2) With "snap" mode enabled, live sequence changes always snap to pattern length regardless of the snap size setting in the drop-down box. The snap size does work when dragging and resizing pattern blocks in the timeline - except...

[slightlynasty]

Sorry, completely forgot to respond here! Yes, I think the snap should work for both the start and end points of the clip. There's lots of times when performing where you want to punch a pattern in for a beat or a couple of notes and then mute it again, and the snap mode should let you capture a cleaned-up version of that.

I think the guiding principle for song-mode sequence changes in general should be that it records faithfully whatever the user is doing on-the-fly.