Hello MG,

I'm now pretty certain what the problem is with MidiDev.cfg and should be able to fix it in a 2.0.4 release today or tomorrow. It will be a very high priority to get this fixed. I'm surprised there are not more reports of the problem, but perhaps I don't fully understand it yet.

For now, stay back on 2.0.2.

If I hear more reports of this problem, I'll temporarily remove the 2.0.3 patch from the www.notation.com/ComposerUpdate.htm and www.notation.com/MusicianUpdate.htm pages.

Cheers
-- Mark