http://bugs.winehq.org/show_bug.cgi?id=14052
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.ne | |t, ken@codeweavers.com
--- Comment #13 from Jörg Höhle hoehle@users.sourceforge.net 2009-09-16 11:04:39 --- Was Ken Thomases, the author of the offending commit, informed of this regression (he's not in the CC list today)?
I see 2 issues here: a) MIDI fails to initialize for some people (?) - The original poster must find out if MIDI is missing entirely on the machine or if the failure is due to Wine.
Alas, I cannot reproduce this. MIDI works fine on my "early 2009" Mac Mini.
b) If a) is not Wine's fault, acknowledge the fact that MIDI may not be available. b1) Partially revert Ken Thomases' patch, e.g. ret = CoreAudio_WaveInit() /* must have */ if (ret=SUCCESS) { MIDI_Init; WaveInit; } return ret; BTW, I don't know why the patch was written that way. ALSA and OSS simply initialize the 2-4 components and return SUCCESS. Why different behaviours among audio drivers?
b2) Rework winecfg so that it does not crash if part of audio is not present. Comment #9 shows that winecfg still behaves badly in wine-1.1.21. On Linux, presence of MIDI in winecfg depends on Timidity or similar being installed, so the view is already dynamic and can accommodate missing MIDI.