Quote:

(I' m a bit miffed with the site: I've just drafted quite a long and careful reply to the thread, and when I clicked to load it, I got an error message that 'my form is no longer valid', and the whole thing is lost. I wasn't that long !)

Sometimes I'll ctrl-C what I've typed, in case I've gone over time limit.
Quote:

except maybe what Ron meant by the overrides (no reference to Thru in opt.pref.overrides ?)

Sorry Ian, you're quite right. (I've had numerous patch change issues, and I generally check that window for conflicts.) Sorry.

You might try using the midi monitor to confirm whether events are actually generating on the thru channel. Start monitoring just before hitting play. Use the filter so as not to get overwhelmed with data. If the thru channel goes dry as the song starts, see if any strange message(s) were sent just before that. You might also try changing the thru channel (with concordance on the synth of course, just in case you're using a master channel that sends a mess of controller msgs to the synth). If there's a midi monitor on the synth, you might check that the data are returning to it.

But chances are it's a sound card/driver issue. You might describe the sound card and name the midi driver. Others may have deeper insight than I. There are one or two faqs that address related problems - not exactly yours, but they might provide insight as well. Search on "thru".

I know how frustrating these things are. The good side: once you solve them, they're solved for life. I hope someone here can help. Please post when it's resolved. Even if it was simple thing, the insight helps us all.

-Ron

EDIT - A wild thought: You don't happen to have the keyboard wizard on? It says in the helpfile there's a setting for it relating to the thru channel. I'm wondering if it could be competing with the external controller?

Last edited by rkl122; 03/21/09 04:42 AM.