On Monday 13 March 2006 13:32, Clemens Ladisch wrote:
> Oscar wrote:
> > But MIDI signal still doesn't come through.
> >
> > client 72: 'TASCAM US-X2Y' [type=kernel]
> > 0 'TASCAM US-X2Y MIDI 1'
>
> Are MIDI commands from your keyboard shown when you run
> "aseqdump -P TASCAM"?
>
> Does something arrive at your external device when you run
> "aplaymidi -P TASCAM something.mid"?
No, nothing at all.
What I did find is a "Detailed status" button in Rosegarden's Sequences
status, and buttons are there to click :-)
This is the output I found from RG's attempt to connect to alsasequencer.
There are a few "couldn't match" errors. Could that explain some missing
ports?
Output:
-------
Rosegarden 4-1.0 - AlsaDriver - alsa-lib version 1.0.8
JackDriver::initialiseAudio - JACK sample rate = 48000Hz, buffer size = 256
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 2 JACK physical outputs
JackDriver::initialiseAudio - connecting from "rosegarden:master out L" to
"alsa_pcm:playback_1"
JackDriver::initialiseAudio - connecting from "rosegarden:master out R" to
"alsa_pcm:playback_2"
JackDriver::initialiseAudio - found 2 JACK physical inputs
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_1" to
"rosegarden:record in 1 L"
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_2" to
"rosegarden:record in 1 R"
JackDriver::initialiseAudio - initialised JACK audio subsystem
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX)
[ctype 2, ptype 2, cap 99]
72,0 - (TASCAM US-X2Y, TASCAM US-X2Y MIDI 1)
(DUPLEX) [ctype 2, ptype 2, cap 127]
Creating device 0 in Play mode for connection 72:0 TASCAM US-X2Y MIDI 1
(duplex)
Default device name for this device is MIDI external device
Creating device 1 in Record mode for connection 72:0 TASCAM US-X2Y MIDI 1
(duplex)
Default device name for this device is MIDI hardware input device
Creating device 2 in Play mode for connection 62:0 Midi Through Port-0
(duplex)
Default device name for this device is MIDI output system device
Creating device 3 in Record mode for connection 62:0 Midi Through Port-0
(duplex)
Default device name for this device is MIDI input system device
Current timer set to "PCM playback 0-0-0"
AlsaDriver::initialiseMidi - initialised MIDI subsystem
Current timer set to "system timer"
AlsaDriver::setPlausibleConnection: connection like 72:0 TASCAM US-X2Y MIDI 1
(duplex) requested for device 0
AlsaDriver::setPlausibleConnection: exact match available
AlsaDriver::setPlausibleConnection: connection like 72:0 TASCAM US-X2Y MIDI 1
(duplex) requested for device 2
AlsaDriver::setPlausibleConnection: exact match available
AlsaDriver::setRecordDevice - couldn't match device id (5) to ALSA port
AlsaDriver::setRecordDevice - successfully subscribed device 1 as record port
AlsaDriver::setRecordDevice - couldn't match device id (4) to ALSA port
AlsaDriver::setRecordDevice - successfully subscribed device 3 as record port
AlsaDriver::setRecordDevice - couldn't match device id (7) to ALSA port
AlsaDriver::setRecordDevice - couldn't match device id (8) to ALSA port
AlsaDriver::setRecordDevice - couldn't match device id (9) to ALSA port
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX)
[ctype 2, ptype 2, cap 99]
72,0 - (TASCAM US-X2Y, TASCAM US-X2Y MIDI 1)
(DUPLEX) [ctype 2, ptype 2, cap 127]
AlsaDriver::setRecordDevice - attempting to set play device (5) to record
device
AlsaDriver::setRecordDevice - attempting to subscribe (1) already subscribed
AlsaDriver::setRecordDevice - attempting to set play device (4) to record
device
AlsaDriver::setRecordDevice - attempting to subscribe (3) already subscribed
AlsaDriver::setRecordDevice - couldn't match device id (7) to ALSA port
AlsaDriver::setRecordDevice - couldn't match device id (8) to ALSA port
AlsaDriver::setRecordDevice - couldn't match device id (9) to ALSA port
Received on Tue Mar 14 00:15:07 2006
This archive was generated by hypermail 2.1.8 : Tue Mar 14 2006 - 00:15:07 EET