2004b and mac and external keyboard woes

[appyface]

Good Morning,

My church has been using 2003a on Mac OS 9 with OMS and external Yamaha SY55 keyboard, and having some midi patch change problems. We just upgraded to 2004b last night and have same problems.

We used OMS Easy Setup and believe the external MIDISport 2x2 and SY55 keyboard were detected correctly -- we can input from the keyboard and all output plays back to the keyboard as we would expect. (We have turned off internal speaker playback). This keyboard only has 16 channels. In midi setup, input 1-16 and output 1-16 are mapped to the SY55. All other channels are 'none'. MIDI sync is 'none'.

The problem is this: The keyboard patch gets changed to patch 57 as soon as a document is opened. The patch does not change from 57 when playback is started, regardless of the patch selected in Instument List instrument definition.

We can manually change the patch on the keyboard and then Finale changes it back to 57.

Now here's the really odd part. The problem behavior is totally consistent for a given document with the problem. However, the problem is inconsistent from document to document!

We can create another document, new or from same template as one with the problem, in this document the keyboard patch is NOT changed to 57 when the document is opened (whatever is selected on the keyboard is left alone), and when playback is initiated the Instrument List definition is correctly sent and the keyboard plays the desired patch!!!

We can then create yet another document, just like the one that works, and it might (or might not) have the problem!!! If it has the problem, it will ALWAYS have the problem, even after rebooting. But if the document doesn't have the problem, it always works correctly.

Where to start looking to solve this annoying problem? Just can't seem to find what is different between a document with the problem, and one that is working correctly. We cannot figure out where patch 57 is coming from.

Thanks in advance for any help or suggestions on how to fix this, or at least troubleshoot and narrow it down to the cause.

--appyface