http://bugs.winehq.org/show_bug.cgi?id=20426
--- Comment #5 from David Rogers ezekiel000@lavabit.com 2010-03-10 11:14:26 --- (In reply to comment #4)
What does aconnect -o (or -l or -lo, or -lx, I forget the exact options) report?
ezekiel@alice:~/Desktop$ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'TiMidity' [type=user] 0 'TiMidity port 0 ' 1 'TiMidity port 1 ' 2 'TiMidity port 2 ' 3 'TiMidity port 3 '
When either FluidSynth or Timidity are started in server mode, additional ports are seen both in winecfg and aconnect. If your aconnect shows nothing or solely that MIDI through port, then this is not a Wine bug, and you need to google to find out how to setup MIDI software synthesizer (do you have HW?) for your machine.
When I checked winecfg with Timidity started in server mode 4 timidity output appear. I don't have a hardware synthesizer. I don't have any problems with FLuidsynth and ScummVM games that use midi but I think that's irrelevant.
/dev/dsp: Device or resource busy
What other SW is using it? (lsof)
Nothing seems to be using /dev/dsp according to lsof (although I've never interpreted the output of that command before so I could be wrong) and there is nothing else using any sound output open.