allow recording events in stopstate #multitimbral #hardware #soundfont #parameterlocks

[coderofsalvation]

I really like the concept of being able to export a midi-file which includes program-change + MSB + LSB bank select for each midi-channel.
This ensures correct playback of the exported midi-file on multitimbral devices/soundfonts (MT).

The problem

I don't know a convenient way of doing this.

When the transport is stopped..sending midi-notes to a pattern does record it to the pattern.
However, it does not capture programchange+MSB+LSB or CC events (send from my MT device):

seq66-2025-06-18_18.52.22.mp4

Per-pattern Instrument-definition workaround

Right now I'm doing:

• MT: transmits notes on midichannel 1 to seq66
• MT: I select the previous instrument (on the physical device oro midi-controller)
• seq66: I press 'play' and 'record' on a pattern
• MT: I select the next instrument (so MT triggers a program-change + MSB + LSB bank select of the desired instrument to seq66)
• seq66: profit! the values have been captured in the pattern (not ideal though, the values never end up exactly in the beginning of the pattern)
• seq66 I have to manually move the events to beginning of the patterm
• rinse and repeat: I do this for every pattern

question: is there an easier way to do this?

Brainstorm

Can we maybe allow recording midi-events in the pattern editor (during stop-state?).

This would make the above mentioned ~64 manual steps redundant.
One could hit record (without pressing play), receive some midi data, which would (over)write the values to the current patternposition.
This more modern workflow, allows hardware to augment the seq66 pattern-editor cursor.

bigger picture: synths/keyboards/grooveboxes emit program change + LSB + MSB-events when switching patterns or instruments. Many of them also send midi CC snapshots (reverb/chorus/delay send values) when switching instruments. For example, here's my CASIO CTS-1000v synth when switching an instrument:

How awesome would it be if these events would be captured at the pattern cursor-position?
Such a speedy workflow...
Elektron calls this 'recording parameter locks'..and Korg calls it step edit.

Closing thoughts

The good news is that recording notes during stopmode, increases the pattern-position for each note.
Via this exact same mechanism, NRPN data would become possible (which re-uses CC 6 to send a value`).
Many midi-devices transmit NRPN data for device-specific settings, so recording it (during stopstate) starting from a specific patternposition would really allow exciting control without external dependencies/drivers/definition-files.

Seq66 is unique in that it treats the .mid file as a first-class citizen for project-metadata too.
In other words, the midi-file is completely selfcontained.
Having an easy & modern 'capture' way to get the program change + LSB + MSB into the midifile would be awesome.

All other (older) midi editors either lack this, or require you to create (very timeconsuming) instrument-bank-definition files (which is an anti-pattern imho, as they usually never exist for your preferred device/soundfont/software combination).

[ahlstromcj]

I will soon study your email, to understand it, and will get back with you soon. Thank you again!

[coderofsalvation]

Awesome, and sorry for the lengthy issue!
(btw. I've updated/simplified it so the github version might be better)

[ahlstromcj]

I basically have all your other issues fixed in the 'wip' branch. Now working on this one, and just want to be clear. First, I think the usual way to set up a synth channel is to send the following, where n is the channel, b is the desired bank, and p is the desired patch: (1) Send the bank select CC command: "0xBn 0x00 b" ; (2) send the program change command: "0xCn p". But it looks like you are saying that (some of) your equipment sends just a special program change: "0xCn pb" where p and b are just nybbles. I think the best thing to do clear up my confusion is open a pattern containing your bank/program change data in Edit / Events in Tab, then click the "Dump" button and post the relevant lines of data here. Thanks! Also, looking around, it seems some equipement does it differently: <https://www.reddit.com/r/synthesizers/comments/tfsfvj/midi_program_changes_a_quick_reference_guide_and/>

[ahlstromcj]

Ah, I see in the link above: You'd think that'd be enough for anyone, but in the rare case that a synth needed MORE than 16384 patches (!) MIDI set up an informal convention where CC 0 would be the MSB and CC 32 would be the LSB of a bank change message. Let's say you sent A for your value of CC 0 and B for your value of CC 32. Then the bank specified would be A * 128 + B. This plus the PC would allow you to reference over 2 million patches. I shall plan for both the one above and the more normal CC 0 b + PC p.