19 Nov
2010
19 Nov
'10
6:57 p.m.
I've recently updated my system from Ubuntu 9.10 to 10.10. One
unresolved problem I have now is the sequencer port number assignment.
On a boot, sometimes it comes up as 20:0 ... other times as 16:0.
I do have 2 audio cards on the system, but only one has a seq.
bob$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 Ensoniq AudioPCI ES1371
And in my /etc/modprobe.d/alsa-base.conf file:
bob$ cat alsa-base.conf
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe
--quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist
snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ;
/sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi
; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist
snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from being loaded as first soundcard
options snd-usb-audio index=-2
I'd love to fix this one way or the other ... either get a reliable
value for the port (which I always did under 9.10) or figure a way to
set the value to something I want.
Thanks.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
19 Nov
19 Nov
8:18 p.m.
On 11/19/2010 07:57 PM, Bob van der Poel wrote:
I've recently updated my system from Ubuntu 9.10
to 10.10. One
unresolved problem I have now is the sequencer port number assignment.
On a boot, sometimes it comes up as 20:0 ... other times as 16:0.
I do have 2 audio cards on the system, but only one has a seq.
bob$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 Ensoniq AudioPCI ES1371
Hello Bob,
But it always has port name ES1371. You can use that too instead of the
port number. In what context are you facing this issue? A script?
Session management?
Best,
Jeremy
8:29 p.m.
On Fri, Nov 19, 2010 at 1:18 PM, Jeremy Jongepier
But it always has port name ES1371. You can use that too instead of the port
number. In what context are you facing this issue? A script? Session
management?
Yes, it is always ES1371. Mostly I use aplaymidi and it picks up the
port number from the ALSA_OUTPUT_PORTS variable set in my .bashrc.
I suppose I could somehow set this via a script ... but seems a bit awkward?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
8:48 p.m.
On 11/19/2010 09:29 PM, Bob van der Poel wrote:
On Fri, Nov 19, 2010 at 1:18 PM, Jeremy Jongepier
But how do you use aplaymidi? It doesn't matter if you use either
aplaymidi -p 20:0 or aplaymidi -p ES1371:0 so I'm still a bit confused here.
Best,
Jeremy
But it always has port name ES1371. You can use that too instead of the port
number. In what context are you facing this issue? A script? Session
management?
Yes, it is always ES1371. Mostly I use aplaymidi and it picks up the
port number from the ALSA_OUTPUT_PORTS variable set in my .bashrc.
I suppose I could somehow set this via a script ... but seems a bit awkward?
8:58 p.m.
On 11/19/2010 09:48 PM, Jeremy Jongepier wrote:
But how do you use aplaymidi? It doesn't matter if
you use either
aplaymidi -p 20:0 or aplaymidi -p ES1371:0 so I'm still a bit confused
here.
Oops, sorry I think you need to address the client name, not the port
name, so in your case something like aplaymidi -p "Ensoniq AudioPCI":0
But then aplaymidi needs to support that and according to its man page
it does. So you can even use just aplaymidi -p Ensoniq
Best,
Jeremy
10:26 p.m.
Oops, sorry I think you need to address the client
name, not the port name,
so in your case something like aplaymidi -p "Ensoniq AudioPCI":0 But then
aplaymidi needs to support that and according to its man page it does. So
you can even use just aplaymidi -p Ensoniq
Okay ... learn something new every day! I had no idea one could use a
device name.
But, it doesn't seem to work here :)
First, the version of aplaymidi I have.
bob$ aplaymidi -V
aplaymidi version 1.0.23
And, I checked the man page and it does say one can use the device name.
And the ports are:
bob$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 Ensoniq AudioPCI ES1371
But, it doesn't work as advertised:
bob$ aplaymidi -p ES1271 test.mid
Invalid port ES1271 - No such file or directory
or
bob$ aplaymidi -pEnsoniq test.mid
Invalid port Ensoniq - No such file or directory
However, it does appear that a full name does work:
bob$ aplaymidi -p "Ensoniq AudioPCI" test.mid
And export ALSA_OUTPUT_PORTS="Ensoniq AudioPCI" also seems to work.
is something broken here since I can't use "Ensoniq" or "ES1271"
?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
20 Nov
20 Nov
12:27 p.m.
Lacking either connected MIDI hardware or a MIDI file to play, I was
limited in how much testing I could do; however, the aplaymidi man
page says it wants -p CLIENT:PORT but will assume port 0 if just given
a client. So it appears that you would be able to use:
aplaymidi -p 20
aplaymidi -p 20:0
aplaymidi -p 'Ensoniq AudioPCI'
aplaymidi -p 'Ensoniq AudioPCI:ES1371'
aplaymidi -p 'Ensoniq AudioPCI:0'
aplaymidi -p 20:ES1371
but not
aplaymidi -p 0
aplaymidi -p ES1371
Does that clarify matters?
On 19/11/2010, Bob van der Poel <bob(a)mellowood.ca> wrote:
Oops, sorry I
think you need to address the client name, not the port
name,
so in your case something like aplaymidi -p "Ensoniq AudioPCI":0 But then
aplaymidi needs to support that and according to its man page it does. So
you can even use just aplaymidi -p Ensoniq
Okay ... learn something new every day! I had no idea one could use a
device name.
But, it doesn't seem to work here :)
First, the version of aplaymidi I have.
bob$ aplaymidi -V
aplaymidi version 1.0.23
And, I checked the man page and it does say one can use the device name.
And the ports are:
bob$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 Ensoniq AudioPCI ES1371
But, it doesn't work as advertised:
bob$ aplaymidi -p ES1271 test.mid
Invalid port ES1271 - No such file or directory
or
bob$ aplaymidi -pEnsoniq test.mid
Invalid port Ensoniq - No such file or directory
However, it does appear that a full name does work:
bob$ aplaymidi -p "Ensoniq AudioPCI" test.mid
And export ALSA_OUTPUT_PORTS="Ensoniq AudioPCI" also seems to work.
is something broken here since I can't use "Ensoniq" or "ES1271"
?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
4:26 p.m.
Thanks. Makes perfect sense!
On Sat, Nov 20, 2010 at 5:27 AM, Gwenhwyfaer <gwenhwyfaer(a)gmail.com> wrote:
Lacking either connected MIDI hardware or a MIDI file
to play, I was
limited in how much testing I could do; however, the aplaymidi man
page says it wants -p CLIENT:PORT but will assume port 0 if just given
a client. So it appears that you would be able to use:
aplaymidi -p 20
aplaymidi -p 20:0
aplaymidi -p 'Ensoniq AudioPCI'
aplaymidi -p 'Ensoniq AudioPCI:ES1371'
aplaymidi -p 'Ensoniq AudioPCI:0'
aplaymidi -p 20:ES1371
but not
aplaymidi -p 0
aplaymidi -p ES1371
Does that clarify matters?
On 19/11/2010, Bob van der Poel <bob(a)mellowood.ca> wrote:
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
Oops,
sorry I think you need to address the client name, not the port
name,
so in your case something like aplaymidi -p "Ensoniq AudioPCI":0 But then
aplaymidi needs to support that and according to its man page it does. So
you can even use just aplaymidi -p Ensoniq
Okay ... learn something new every day! I had no idea one could use a
device name.
But, it doesn't seem to work here :)
First, the version of aplaymidi I have.
bob$ aplaymidi -V
aplaymidi version 1.0.23
And, I checked the man page and it does say one can use the device name.
And the ports are:
bob$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 Ensoniq AudioPCI ES1371
But, it doesn't work as advertised:
bob$ aplaymidi -p ES1271 test.mid
Invalid port ES1271 - No such file or directory
or
bob$ aplaymidi -pEnsoniq test.mid
Invalid port Ensoniq - No such file or directory
However, it does appear that a full name does work:
bob$ aplaymidi -p "Ensoniq AudioPCI" test.mid
And export ALSA_OUTPUT_PORTS="Ensoniq AudioPCI" also seems to work.
is something broken here since I can't use "Ensoniq" or "ES1271"
?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
19 Nov
19 Nov
8:48 p.m.
On Fri, Nov 19, 2010 at 3:29 PM, Bob van der Poel <bob(a)mellowood.ca> wrote:
On Fri, Nov 19, 2010 at 1:18 PM, Jeremy Jongepier
i think the idea is that you can refer to the ports as ES1371:0 rather
than 16:0 or 20:0
But it always has port name ES1371. You can use that too instead of the port
number. In what context are you facing this issue? A script? Session
management?
Yes, it is always ES1371. Mostly I use aplaymidi and it picks up the
port number from the ALSA_OUTPUT_PORTS variable set in my .bashrc.
4912
days inactive
4913
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Bob van der Poel -
Gwenhwyfaer -
Jeremy Jongepier -
Paul Davis