I can run most midi apps in wine through timidity with no problem but there are quite a few apps which don't allow you to assign the midi output to timidity such as Media Player Classic or WM player 6. They try to use the windows default which is of course MS synth or Emu10k1. There must be a way of mapping the midi output in wine from such apps to timidity but I just can't get it to work. I have tried all the suggested registry tweeks I have found online but most are several years out of date so none of them work any more. Interestingly I get midi sound output from MS synth using the dxdiag music test but nothing else which is puzzling because it is shown as the win default in dxdiag so in theory apps like WM player should use it and work?. Any help getting this one final remaining wine issue solved would be great. I am working with wine versions 1.1.3.5 and 1.2 on PCLinuxOS Minime 2009 and 2010 respectively. DirectX 9.0c installed with no errors .
> They try to use the windows default which is of course MS synth or Emu10k1.They would use the standard MIDI output... MIDI through the softsynth works for me if I start out with a clean wineprefix, start Timidity as an ALSA server in the background, run winecfg, open the audio tab once, and press OK. It'll pick up on Timidity at that point (or in my case, Fluidsynth, but I used Timidity in the past so I know it works). If this didn't work, do you have a sound card that already has its own MIDI support? Wine will prefer that over default MIDI if that's the case. Lastly, if none of this work, check out aconnect (or was it alsaconnect? Hm). It lets you bind MIDI ports to other ones (like the standard 14:0 to Timidity).
I have an older SB live soundcard which supports midi but with soundfonts I tried using aconnect using the default client 14:0 and timidity 128:0 and aconnect said the connection was already subscribed !?. So why no sound output I wonder?.