Daniel Skorka <skorka@xxxxxxx> writes:
> I don't know about reconfiguring wine, but why don't just connect the
> ports with aconnect?
Indeed,
aconnect 62:0 128:0
somehow works. For the first time, I've been able to listen to MIDI
music from within Wine!
However, I'm not convinced this is the right solution. Doing so
causes timidity to eat 25% of 600MHz CPU time even when there's
nothing to play!
I.e., as soon as I aconnect the above, CPU% goes up.
I'm afraid there's something like a recursive output loop happening
here, i.e. timidity receiving its own output?!?
Such does not happen when accessing timidity's port directly, e.g.
aplaymidi -p 128:0 foo.mid
without aconnect, in which case timitidy only eats CPU while playing
music (20-50% of 1.6GHz CPU, depending on the MIDI file).
Here's some mapping info:
aconnect -ol
client 62: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Connecting To: 128:0
client 128: 'TiMidity' [type=user]
0 'TiMidity port 0 '
Connected From: 62:0
1 'TiMidity port 1 '
2 'TiMidity port 2 '
3 'TiMidity port 3 '
wine-0.9.19 (from winehq)
timidity-2.13.2-7ubuntu2
on Debian Ubuntu Dapper
Thanks for your help,
Jorg Hohle
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
