jimDicken I had already tried the method you suggested in the lyrics area without success, but I did not use the SX characters in the code. I gave your idea a go and I'm pretty sure it worked, but only once! I have no idea why this would be, but the keyboard definitely changed to the desired song.
Well, that's a start!! 🙂
Yeah, the 'SX' thing is something @peter pointed out to me as I worked through my own SYSEX testing. It's undocumented, but only because the ST4 documentation hasn't been written yet!
Anyway, good thing is that we now know that (1) we have formatting correct, and (2) we have the MIDI connectivity correct.
Do make sure you are using a current ST4 Beta build (1937 as of writing) as Peter did fix a SYSEX issue a few builds ago relating to really large SYSEX commands that someone else encountered.
My first thought, much like your own, was that we needed to possibly increase the time between the first and second SYSEX commands to allow time for the Genos to receive, process, execute them, and then be ready for the next command.
As a test, try putting a few seconds between the commands, e.g.
; First command to load the song on the Genos2
[midi@00:00.10: SXF0 43 73 01 52 26 03 00 00 00 55 73 65 72 3A 2F 48 41 52 4D 4F 4E 59 20 47 55 59 53 20 53 4F 55 4E 44 53 2F 41 72 6D 73 20 4F 66 20 4D 61 72 79 5F 47 2D 41 5F 48 47 2E 54 31 37 34 2E 72 67 74 00 F7]
; Now we'll wait 10 seconds before sending the next command to select the first sound
[midi@00:10.10: SXF0 43 73 01 52 25 11 00 02 00 02 F7]
If that works, then play with the timing of the 2nd command until you get a feel for the minimum safe time you need to leave between song load and sound select commands.
If it doesn't work... more thinking (and coffee) required 🙂
