From: D. M. M. <mic...@ro...> - 2010-02-01 02:52:14
|
On Sunday 31 January 2010, D. Michael McIntyre wrote: AlsaDriver::setPlausibleConnection: connection like "" requested for device 0 AlsaDriver::setPlausibleConnection: fuzzy match 128:0 TiMidity port 0 (write) available with fitness 15 AlsaDriver::setPlausibleConnection: connection like "" requested for device 1 AlsaDriver::setPlausibleConnection: fuzzy match 20:0 UM-2 MIDI 1 (duplex) available with fitness 15 I'm continuing to refine it. It's working adequately for play devices. It prefers anything but hardware, and then falls back on hardware. This seems to be more a function of the order in which it considers choices than the tightness of my logic. For record devices, it always favors hardware, due to the order in which it considers choices, and the apparent looseness of the logic I was comfortable with until I got this far. I'll get there in a bit. Wanted you to know I'm tinkering with it so you don't get into it yourself. Goal: Connect one record and one play device in connectSomething(). Favor software over hardware for both record and play devices. Play: TiMidity/Q/Zyn is more likely to work than some random hardware MIDI port, but when utterly nothing else is there, choose some random hardware over nothing at all. Record: If we find VMPK, the user probably needs it. Favor software record devices over hardware just the same, but for slightly different reasons. Where I am with this is it's choosing my hardware MIDI record device over VMPK, and that's the hole I'm trying to plug. -- D. Michael McIntyre |