On 8/1/20 3:16 AM, Malhaire Christophe wrote:
It works perfectly (see enclosed file), well done.
Glad to hear it. Hopefully everyone else is happy with it as well.
Haven't heard any complaints yet.
I think it's better this way. Thus, if for one reason or another a
device is not correctly detected (because it is switched off, or because
a usb cable is defective ...) the corresponding track will not send data
anywhere ("no connection" is preferable to "wrong connection").
Agreed.
-------------------------
"40:0 Streichfett MIDI 1 (duplex)"
"40:0 Streichfett MIDI 1 (duplex)"
Final score: 75
-------------------------
"36:0 XV-5050 MIDI 1 (duplex)"
"32:0 XV-5050 MIDI 1 (duplex)"
Final score: 75
I wonder why the "Final score" indicator has the same value (75) in both
cases?
I would have thought that the score would be higher in the first case
because the objective/source strings are equal, right?While in the
second case we have 36 different from 32.
The client numbers (36 and 32) are ignored. This was one of the
reasons the old algorithm would get so confused. It would give very
high priority to the client number. That's really not a good idea as
the client numbers are pretty random.
The client numbers are still used to make sure the device class
(internal/hardware/software) matches, and if they don't, the comparison
isn't even done. That's one reason why you might see some with no score
at all.
The code's pretty easy to read now. See
AlsaDriver::setPlausibleConnection():
https://sourceforge.net/p/rosegarden/code/15895/tree/trunk/rosegarden/src/sound/AlsaDriver.cpp#l1274
Comments appreciated.
Thanks for helping with this. Let me know if you run into anything else.
Ted.
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
