Yes. Export a whole Song Book, individual songs, or your custom hardware profiles from the "…" menu as a file, then AirDrop or email it — the recipient taps the file and it imports straight into their copy of MIDIPerformer.

Turn on "Learn triggers from MIDI in" once, in Setup → App. After that, while any trigger field is open for editing, hit the real pad or move the real control on your gear — the message is captured and the fields fill themselves in, including automatic wildcards when the hit matches a known hardware profile control.

It marks that field as a wildcard — "any channel," "any velocity," etc. — so a trigger still fires even if that particular value varies hit to hit.

Set a response's Duration above zero, then choose a start value, end value, and curve (Linear or S-Curve). MIDIPerformer steps the output value across that time span instead of jumping instantly — handy for slow fades.

Automatic responses fire as soon as their part activates, optionally after a delay, optionally ramping to an end value over time. Manual responses wait for their own separate MIDI hit before firing — useful for an ad-lib cue that shouldn't happen every time the part plays.

The song-level trigger (or banter-level) jumps straight to that item from anywhere — e.g. a dedicated program change per tune from a footswitch. A part's trigger only matters while that song is active, and advances it to the next part.