How to send multiple Midi presets on song select

[JerryK]

I've been sending the patches for by guitar floorboard for a long time.  I think that's done with Send Midi 1 on Song Selection.
I now want to add to that, sending a chosen 'capo' preset for the song as well.

I'm a bit baffled by Send Midi -vs- Send Midi 1, and
Send Pinned Midi [blank] -vs- Send Pinned Midi 2 and/or 3.

I presume Midi 1 is the first preset in the list on a song.  That's my guitar patch.
So what does 'Send Midi' send?
Others currently attached to a song are for my use during Automation - but I need my proposed 'capo' to happen on Song Select.

Is there an article somewhere, revealing what I'm missing?

[arlo]

Send MIDI sends the default MIDI preset, which is usually the first one but you could override that with Settings > General > Defaults > MIDI Preset, OR it sends all the MIDI presets if Settings > Audio & MIDI > Send MIDI Presets Together is on.

Send MIDI 1 always sends the first MIDI preset.

The Send Pinned MIDI actions work similarly, but with the presets that you've pinned to all songs, rather than the presets you've attached directly to specific songs.

Note that you can put an additional MIDI message into an existing preset, or create a separate preset and attach it to the same song as an existing preset, or create a separate preset and attach it to the existing preset. The first option is simplest, while the second and third options can reduce duplication if you want to use some of the same MIDI messages with multiple songs.

[JerryK]

Thanks for that illumination, which I may need to read several times.

So what's the right way to send my guitar patch, as I currently do, hopefully the first preset on every song, followed by one of currently 8 'capo' presets, 1 to 8, if present?  Both of them at Song Select, whether auto or not?  There is also a Capo zero happening at every Song End.
Only songs with a 'full' capo and not Drop-E or whatever will want one.
Or do I need to add a Capo0 to all the others?  I guess that would work.  Then I would send Midi 1 and 2, for example.  I'd prefer an easier way but it's achievable.

[arlo]

Maybe the most intuitive way to set this up is to make a separate MIDI preset for each capo setting. Then for each song where you use a capo, attach the desired capo preset to the existing MIDI preset for that song. Then when you add more songs and MIDI presets later, you won't have to remember the MIDI code for capo settings; you can just keep reusing the capo presets you already created.

You might have to adjust Settings > Audio & MIDI > MIDI Preset Order to send your capo preset ("Attached Presets") before or after the existing preset data, depending on how your guitar processor needs to receive that.

[JerryK]

So I think that's a preset per patch-capo combination?
I was kind of hoping to avoid multiplying them together (somewhat) but it does save editing a lot of songs unnecessarily if they don't want a virtual capo.

Thanks again Arlo

[Insider0203]

I have a similar situation with my presets.

I basically have midi presets for all the core functions of my guitar fx processor and then I make the combination presets as needed.

It works fine but it can be a lot to manage. You end up getting a lot of duplicates and presets nested in other presets.

I made a post a while back where I patched the idea of having "batch presets".

When editing a song, the user can choose to attach presets in batches, which would just be a group of presets. They can create multiple batches and then there would be new app control options "send batch midi" etc

[arlo]

"I was kind of hoping to avoid multiplying them together..."

If you prefer, you can just put the MIDI messages for the capo directly into the existing song presets. I think my suggestion would be easier to maintain, but the best approach depends on the nature of your data and how much of it is shared across songs versus unique for each song.