On Sunday 31 January 2010, Julie S wrote:
> I see the device manager correctly associates the port of the midi
> equipment attached to the single device in the playback list.
> * A record device was not connected even though the equipment I attached
> was a duplex USB MIDI enabled and detected as such.
I'm not exactly sure how the new logic is supposed to work myself, but I have
a good idea the reason you didn't get a record device connected was because
nothing was connected in the file:
<device id="1" ... direction="record" ... connection="" ...>
But the play device in that file :
<device id="0" ... connection="20:0 UM-2 MIDI 1 (duplex)" ...>
I'm fairly sure when I was reworking all of these files, I just decided not to
bother hooking up the record device to anything, as I was thinking of these
more as "read only" files where you wouldn't want to record. In fact, I think
toward the end of that I did a bunch with no default record device at all.
I suppose I need to go change all of that. I apparently need to save channel-
remapped versions of at least this one file too, so this indicates one more
trip through all the stupid demo files.
Bleck.
> Where was the new manager suppose to connect to the record device as well,
> or not?
I don't know, but let's test.
I pasted the same string in the empty connection="" (hand-editing the XML) and
when I loaded it, the record device came up connected too. This probably works
on some other system that doesn't have the same connection available, but I
can't test that from here.
> * I also notice that before I loaded Stormy Rider, The base studio (which
> is the default created from a fresh install) does not connect playback and
> record devices to the USB MIDI device attached.
>
> Was this intentional, or is this a bug?
It's supposed to make a best guess and attach to something. The guess could
be wrong.
I moved my autoload out of the way temporarily to have a look. Where I sit
now, I have:
14:0 Midi Through Midi Through Port-0
20:0 UM-2 UM-2 MIDI 1
20:1 UM-2 UM-2 MIDI 2
24:0 M Audio Audiophile 24/96 M Audio Audiophile 24/96 MIDI
129:0 Client-129 qjackctl
130:0 Client-130 qjackctl
The correct guess is "UM-2 MIDI 1" and Rosegarden's guess is [No Port].
If I start TiMidity and try again, Rosegarden's guess is TiMidity.
If I start QSynth and try again, Rosegarden's guess is TiMidity.
If I stop TiMidity and try again, Rosegarden's guess is QSynth.
If I stop QSynth and start ZynAddSubFx, Rosegarden's guess is ZynAddSubFx.
It's obviously targeting the first available ALSA soft synth, and it ignores
the range of hardware MIDI ports.
Also, the record connection is never at any time connected to anything
automatically. (Just looking at the new document with factory autoload case
now.)
I'd say the "connect to something" logic could be refined to add looking for
hardware MIDI stuff dead last.
It *might* work. It's better than nothing.
In general though, most hardware MIDI ports we detect are not in use. There
are tons of motherboards out there where ALSA comes up with available hardware
MIDI ports for features of a sound chip that aren't physically wired to
anything, and cannot possibly be used.
You and I have real MIDI gear, and we know a few people who do, but we're the
rare exception in the scheme of things. I can't fault the logic of choosing
hardware dead last, because it probably doesn't work. Never choosing it all,
I guess I'd consider that a bug though.
--
D. Michael McIntyre
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
