Does wine handle virtual midi ports correct on OSX?
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.
On May 6, 2009, at 11:20 PM, Dewdman42 wrote:
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?
As far as I know, only Emmanuel Maillard has touched the MIDI code in the Core Audio driver. I'm CC'ing him, just to be sure he sees this. Cheers, Ken
Thanks a lot for that. Would be nice to get to the bottom of this issue and I am happy to run some tests if he can help me set debug flags or whatever to figure it out. On May 7, 2009, at 1:14 PM, Ken Thomases wrote:
On May 6, 2009, at 11:20 PM, Dewdman42 wrote:
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?
As far as I know, only Emmanuel Maillard has touched the MIDI code in the Core Audio driver. I'm CC'ing him, just to be sure he sees this.
Cheers, Ken
------------------------- Steve Schow steve(a)bstage.com 206-724-8083
Thanks for that. Hope we can get to the bottom of the issue. Ken Thomases wrote:
On May 6, 2009, at 11:20 PM, Dewdman42 wrote:
As far as I know, only Emmanuel Maillard has touched the MIDI code in the Core Audio driver. I'm CC'ing him, just to be sure he sees this.
Cheers, Ken
-- 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.
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.
Thanks for responding. I'm just sending midi notes around, no sysex. Sometimes the ports work and sometimes they don't. I may be finding that the problem is more related to Reaper bugs, I'm not sure yet. Seems like it will not work and then sometimes after a few minutes, it will suddenly start working. Seems possibly related to flushing, but I'm not sure. I'm not a wine developer, so I will just note your comments about MIDIClientCreate and keep testing from my end. Emmanuel Maillard-3 wrote:
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.
-- 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.
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ? Have you see fixme about MOD_MIDIPORT in log ? Emmanuel Le 25 mai 09 à 17:59, Steve Schow a écrit :
Thanks for responding. I'm just sending midi notes around, no sysex. Sometimes the ports work and sometimes they don't. I may be finding that the problem is more related to Reaper bugs, I'm not sure yet. Seems like it will not work and then sometimes after a few minutes, it will suddenly start working. Seems possibly related to flushing, but I'm not sure.
I'm not a wine developer, so I will just note your comments about MIDIClientCreate and keep testing from my end.
Emmanuel Maillard-3 wrote:
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.
-- 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.
it seems like what happens is that i select an IAC or virtual midi port from some windows host inside Wine and everything looks ok, but no events are sent. Nothing. But sometimes it works and sometimes it doesn't. Once it is working it works fine. Sometimes I have started it up and it was not working, then I forgot that i had set it up and 5-10 minutes later suddenly it would start sending the data across. Seems like somehow the windows host was not flushing the buffer or something. I had this problem with Reaper and the latest version of Reaper seems to be working ok, so maybe this was a Reaper problem, not wine. I didn't see that fixme you mentioned. Where can I find that? I'm actually using CrossOverGames for this, I was never able to get Wine to work with JackOSX. Emmanuel Maillard-3 wrote:
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ?
Have you see fixme about MOD_MIDIPORT in log ?
Emmanuel
Le 25 mai 09 à 17:59, Steve Schow a écrit :
Thanks for responding. I'm just sending midi notes around, no sysex. Sometimes the ports work and sometimes they don't. I may be finding that the problem is more related to Reaper bugs, I'm not sure yet. Seems like it will not work and then sometimes after a few minutes, it will suddenly start working. Seems possibly related to flushing, but I'm not sure.
I'm not a wine developer, so I will just note your comments about MIDIClientCreate and keep testing from my end.
Emmanuel Maillard-3 wrote:
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.
-- 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.
-- 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.
Le 25 mai 09 à 20:54, Steve Schow a écrit :
it seems like what happens is that i select an IAC or virtual midi port from some windows host inside Wine and everything looks ok, but no events are sent. Nothing. But sometimes it works and sometimes it doesn't. Once it is working it works fine. Sometimes I have started it up and it was not working, then I forgot that i had set it up and 5-10 minutes later suddenly it would start sending the data across.
Seems like somehow the windows host was not flushing the buffer or something. I had this problem with Reaper and the latest version of Reaper seems to be working ok, so maybe this was a Reaper problem, not wine.
How does it work on linux ? Did you take a look to AppDB ?
I didn't see that fixme you mentioned. Where can I find that? I'm actually using CrossOverGames for this, I was never able to get Wine to work with JackOSX.
Emmanuel Maillard-3 wrote:
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ?
Have you see fixme about MOD_MIDIPORT in log ?
Emmanuel
Le 25 mai 09 à 17:59, Steve Schow a écrit :
Thanks for responding. I'm just sending midi notes around, no sysex. Sometimes the ports work and sometimes they don't. I may be finding that the problem is more related to Reaper bugs, I'm not sure yet. Seems like it will not work and then sometimes after a few minutes, it will suddenly start working. Seems possibly related to flushing, but I'm not sure.
I'm not a wine developer, so I will just note your comments about MIDIClientCreate and keep testing from my end.
Emmanuel Maillard-3 wrote:
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.
-- 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.
-- 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.
it seems like what happens is that i select an IAC or virtual midi port from some windows host inside Wine and everything looks ok, but no events are sent. Nothing. But sometimes it works and sometimes it doesn't. Once it is working it works fine. Sometimes I have started it up and it was not working, then I forgot that i had set it up and 5-10 minutes later suddenly it would start sending the data across. Seems like somehow the windows host was not flushing the buffer or something. I had this problem with Reaper and the latest version of Reaper seems to be working ok, so maybe this was a Reaper problem, not wine. I didn't see that fixme you mentioned. Where can I find that? I'm actually using CrossOverGames for this, I was never able to get Wine to work with JackOSX. On May 25, 2009, at 11:47 AM, Emmanuel Maillard wrote:
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ?
Have you see fixme about MOD_MIDIPORT in log ?
Emmanuel
Le 25 mai 09 à 17:59, Steve Schow a écrit :
Emmanuel Maillard wrote:
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ?
Have you see fixme about MOD_MIDIPORT in log ? Emmanuel:
Pardon my barging into this conversation, but music does not play correctly with Doom. Not the CD Music, but the background music. I get no error messages in the log file either about MOD_MIDIPORT. MacOSX 10.5.7 James McKenzie
I think Doom use the MIDI Synth not an external MIDI instrument. so no log about MOD_MIDIPORT but eventually MOD_MIDISYNTH (or something like that) Emmanuel Le 26 mai 09 à 02:08, James McKenzie a écrit :
Emmanuel Maillard wrote:
Does notes play well when playing ? Correct duration, correct tempo or other kind of timing issue ?
Have you see fixme about MOD_MIDIPORT in log ? Emmanuel:
Pardon my barging into this conversation, but music does not play correctly with Doom. Not the CD Music, but the background music. I get no error messages in the log file either about MOD_MIDIPORT.
MacOSX 10.5.7
James McKenzie
participants (6)
-
Dewdman42 -
Emmanuel Maillard -
James McKenzie -
Ken Thomases -
Steve Schow -
Steve Schow