Export to MIDI, prologue events -- can they be disabled for export?
When I export MIDI from MuseScore for use in a DAW (Reaper to be specific) I often encounter strangeness in the playback depending on the particular VSTi I'm using. I notice that the exported MIDI often adds a MIDI Reset (CC 121 ??) at the same event time as the first note but after the note event in the stream. For example:
| Index | Position | Type | Parameter | Value |
|---|---|---|---|---|
| 1 | 1.1.00 | PC | 121-0-0 | 0 |
| 2 | 1.1.00 | CC | Volume MSB (7) | 100 |
| 3 | 1.1.00 | CC | Pan Position MSB (10) | 64 |
| 4 | 1.1.00 | CC | Effects Level (91) | 0 |
| 5 | 1.1.00 | CC | Chorus Level (93) | 0 |
| 6 | 1.1.00 | Note | A3 | 80 |
| 7 | 1.1.00 | Reset | 0 | |
| 8 | 1.2.50 | Note | E3 | 80 |
That reset ends up causing the VSTi plugin to cut off that first note on playback so I've been manually removing that event every time I use exported MIDI from MuseScore. Further, my understanding of Reset is that it should be doing what the prior CC events are individually doing (setting default volume, pan, effects, chorus, as well as things like pitch wheel, mod wheel, etc).
I don't (or haven't yet) used non-default bank and programs in my VSTi plugins, but if I were to do so, wouldn't the forced bank/program select added here muck with that too?
I will note, too, that those CC messages for volume, pan, effects, and chorus, do interfere with any "static" settings in the VSTi interface that I've made before I begin playback. E.g. if I set a knob in the UI for volume or pan, it will get reset at the start of playback given this MIDI prologue thus I often strip those out as well.
I'm just wondering if there isn't some way to disable (or customize) this prologue to exported MIDI.
=========================
OS: Windows 10 (1909)
MuseScore: v3.5.0