On doing more tests on 5.5B1 here's what I see:
power on the unit and have it set like this:
OMNI: off
MIDI maps : none
MIDI ch: 1
press PROGRAM to look at presets list, on DSP A
send CC #0 with value 17 on MIDI ch 1 > the display goes to preset
1710 – DSP A, pointing at the correct bank
send Prog Change 10 on MIDI ch 1 > display shows "Preset 1710 is
already loaded"…and it's actually not! Any other program is loaded,
depending on how the unit was left before doing this test.
send Prog Change 11 on MIDI ch 1 > DSP A correctly loads preset 1711
in DSP A, as expected
send Prog Change 10 on MIDI ch 1 AGAIN> DSP A correctly loads preset
1710 now
send CC #0 with value 20 on MIDI ch 2 > the display goes to preset
2010 – DSP B, pointing at the correct bank
send Prog Change 10 on MIDI ch 2 > display shows "Preset 2010 is
already loaded"…and it's actually not! Any other program is loaded,
depending on how the unit was left before doing this test.
send Prog Change 11 on MIDI ch 2 > DSP B correctly loads preset 2010
in DSP B, as expected
send Prog Change 10 on MIDI ch 2 AGAIN > DSP B correctly loads preset
2010 now or you may also get "preset 2010 is alredy loaded"
Looks like there is a problem when pointing to a bank AND to its first
preset xx10…then you get the message that preset is already loaded
even if it's not.
can you replicate this on 5.3?
Can anybody replicate this on OS V5.5B1?
thanks
Italo
