Dorico is exporting PC 2 messages at some note offs into my MIDI file exports.
I triple checked and PC 2 is not being used by the expression map for the instruments that are exporting this bug. I checked all slots, note on and note off expression messages.
If this was an XML or MIDI import, check the source. If you just manually entered those notes then we’ll need to see the project (cut-down is fine as long as the problem is visible).
Can you please attach a minimal Dorico project that reproduces this problem, so we can investigate, Craig?
Here is a cut down version:
6M4 Clown Attack edited down to show PC2 issue.dorico (1.3 MB)
The PC 2 messages are being generated after the “arco” playing techniques in the score.
Exporting a MIDI file form Dorico and importing it into Reaper and Nuendo are both showing these PC 2 messages.
The expression map for the strings is long, but none of the slots use PC 2.
Notice that Reaper is seeing PC 2 in the above screenshot, not PC 1.
It is later followed by PC 21 (which is correct, as I intended as used in the exp map for pizzicato).
Wondering if Reaper has mis-labeled the PC#.
Yes, it looks like Reaper is indeed mislabeling the program change. Dorico’s MIDI output contains program change 1 and program change 21, but not program change 2.
It’s quite strange! Cubase/Nuendo has all of the PC #s wrong because they started at 1 instead of 0, so all of their PCs are off by +1. Reaper on the other hand only has one of the PC #s wrong (PC 1 reading as PC 2). So this is bungled by both Nuendo and Reaper, but not Dorico.
As an FR: it would be nice to be able to view the PCs that Dorico is generating from the expression maps in the key editor. The key editor seems to have the capability of showing all of the other modifications/message generation: CC values, transposition, velocity, note length, delay etc.
It would be nice to see what PCs are being sent so as not to have to export a MIDI file to find out.