Hi,
Sorry for the late answer. The MIDI driver is very rudimentary : (by memory) it doesn't handle SysEx, doesn't handle notification from MIDIServer, and poorly tested : just testing by reading few MIDI files, and few In/ Out tests with 2 virtuals application.
I think you first need is to add MIDINotifyProc, in MIDIClientCreate to track your MIDI setup changes.
Cheers Emmanuel
Le 7 mai 09 à 06:20, Dewdman42 a écrit :
Does anyone know if Darwine can be fixed to handle virtual midi ports correctly? They work very sporadically right now. It seems to be related to getting the ports flushed or initialized or something. When there is a virtual midi port present (under OSX), Wine seems to see it and lists it as an available midi port, but I have not been able to consistently get that port to function correctly. Sometimes it does and sometimes it doesn't and it seems to related to switching it on and off in some fashion makes it work, though I can't seem to find a pattern that will work consistently.
All I can figure is that somehow Wine is not handling midi ports in a way that is compatible with OSX virtual midi ports.
Anyone have any experience or knowledge in this area?
Thanks
View this message in context: http://www.nabble.com/Does-wine-handle-virtual-midi-ports-correct-on-OSX--tp... Sent from the Wine - Devel mailing list archive at Nabble.com.