Hi @peter
Yes the DAW (Ableton) is definitely sending the LSB, see screenshot.

In Ableton, the Bank is MSB, the Sub is LSB and PGM is the PC Value. NOTE, Ableton doesn't use Base 0 MIDI but uses BASE 1. So the 0 LSB is achieved by setting it to 1 in Ableton. Likewise, the PC value of 37 is achieved by sending 38. Why they do that I don't know.....
Anyway, I send that same command to ST3 and it results in the learn process placing "PC37.0@8" into the song select command. And when I run the song in Ableton, the song selects perfectly (In ST3)
When I did the backup Restore to ST4. it placed the same command into Midi Trigger field (PC37.0@8). Which does not work in ST4 (song is not selected).
However, If I 're-learn' in the song, ST4 appears to ignore the LSB command (Sub in Ableton) and places just the PC command (PC37@8)into the MIDI Trigger field. That then works and selects the song as expected.
So my initial problem is that I have about 200 songs with Midi Trigger values transferred over from ST3 that do not work. I can re-learn them all but that will be a pain.
But my 'longer term' concern is about what ST4 is doing with bank commands for the MIDI trigger function in general.
I tried manually typing back in the .0 after doing a re-learn and ST4 stopped selecting the song. So it seems the '.n' syntax on a PC message is not working in ST4.
Thanks of looking at it.