8 May
2010
8 May
'10
1:17 a.m.
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
8 May
8 May
1:45 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Yo, back on Friday, May 07, 2010 Geoff King was all like:
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
Don't personally use Fedora, so I can be much help on "how" to do this, but
"what" you need to do is set the driver modules for these two interfaces to be
autoloaded. That way you can control the order in which they are loaded, which in turn
determines their order in ALSA. (Assuming of course that the drivers are loaded as modules
rather than built into the kernel)
Different distros have different means of setting this up.
-Reuben
1:45 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
On Fri, May 7, 2010 at 4:17 PM, Geoff King <gsking1(a)gmail.com> wrote:
I have problem that I've been trying to figure out
with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is
hw:1
etc, back and forth, each reboot...
Consider setting up /etc/modprobe.d/*.conf file to ensure a consistent
ordering of all your USB devices.
for example, I use:
-rw-r--r-- 1 root root 1760 2010-03-12 11:32
/etc/modprobe.d/snd_usb_audio.conf
##
## NPM: force ALSA USB sound device id's s.t. cat /proc/asound/cards gives
## 0 [Headset ]: USB-Audio - Logitech USB Headset
## Logitech Logitech USB Headset at
usb-0000:00:12.0-2, full speed
## 1 [SB ]: HDA-Intel - HDA ATI SB
## HDA ATI SB at 0xfb9f4000 irq 16
## 2 [M66 ]: ICE1712 - M Audio Delta 66
## M Audio Delta 66 at 0xe880, irq 21
## 3 [MT4 ]: USB-Audio - MT4
## Emagic MT4 at usb-0000:00:12.1-1, full speed
## 4 [BCD3000 ]: USB-Audio - BCD3000
## Behringer BCD3000 at usb-0000:00:13.1-2, full speed
## 5 [UM2 ]: USB-Audio - UM-2
## EDIROL UM-2 at usb-0000:00:12.1-3, full speed
## (see
## (see http://alsa.opensrc.org/index.php/MultipleUSBAudioDevices )
##
alias snd-card-0 snd-usb-audio ## --> Headset
## snd-card-1 ## --> SB
## snd-card-2 ## --> M66
alias snd-card-3 snd-usb-audio ## --
MT4
alias snd-card-4 snd-usb-audio ## --> BCD3000
alias snd-card-5 snd-usb-audio ## --> UM-2
alias snd-card-6 snd-usb-audio ## --> LPK25
##
## lsusb gives following devices w/ vid/pid's:
## Headset: Bus 003 Device 003: ID 046d:0a0c Logitech, Inc.
## MT4: Bus 004 Device 002: ID 086a:0003 Emagic Soft- und Hardware GmbH
MT4
## UM-2: Bus 004 Device 005: ID 0582:0005 Roland Corp. Edirol UM-2 MIDI
Adapter
## BCD3000: Bus 006 Device 005: ID 1397:00bf
## LPK25: Bus 005 Device 003: ID 09e8:0076 AKAI Professional M.I. Corp.
##
options snd-usb-audio index=0,3,4,5,6 vid=0x046d,0x086a,0x1397,0x0582,0x09e8
pid=0x0a0c,0x0003,0x00bf,0x0005,0x0076
I usually use qjackctl and have to keep changing the presets with settings
which is annoying.
You can also use "Symbolic" names for ALSA devices which will make them not
depend on a particular device number, e.g.
> aplay -l | grep M66
card 2: M66 [M Audio Delta 66], device 0: ICE1712 multi [ICE1712 multi]
So use "M66" as the ALSA name, for jack, e.g. '/usr/bin/jackd -dalsa
-dhw:M66 ...'
Niels
http://nielsmayer.com
PS: you may want to leave device 0 unreserved. That way when you plug in a
new USB device (before you've added it to /etc/modprobe.d) it won't get
assigned to card0 automatically. That's what would happen by default (a bug
IMHO) and prevent whatever you had setup previously as card0 from
iniitializing.
Then when jack or alsa attempts to use the card, it fails. In fact, plugging
in a new unrecognized usb device, then starting up qjackctl can cause
qjackctl to place some bad values in ~/.config/rncbc.org/QjackCtl.conf and
the next thing you know your audio is all horked up (even after removing the
offending USB device and rebooting) until you delete the QjackCtl.conf and
set it up from scratch.
3:30 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Thank you for the useful responses! One of those looks like it will
work. Geoff
1:57 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Excerpts from Geoff King's message of 2010-05-08 01:17:39 +0200:
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always just works.
If you have multiple other devices you need hardwired you might need
some other trickery, but I guess in your case it's a simple matter of
figuring out the right name for the maudio interface.
--
Regards,
Philipp
2:36 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
--- On Fri, 5/7/10, Philipp <hollunder(a)lavabit.com> wrote:
From: Philipp <hollunder(a)lavabit.com>
Subject: Re: [LAU] Please help with audio interfaces that keep changing after reboot
To: "linux-audio-user" <linux-audio-user(a)lists.linuxaudio.org>
Date: Friday, May 7, 2010, 7:57 PM
Excerpts from Geoff King's message of
2010-05-08 01:17:39 +0200:
Instead of aplay -l, I would use the list of cards in the file /proc/asound/cards
The proper name to use is the one between squared brackets [ ]. The command 'aplay
-l' has the reversed bracket "semantic".
J.
Hello,
I have problem that I've been trying to figure out
with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4
Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and
Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the
presets with
settings which is annoying.
I would greatly appreciate it if someone could provide
me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always
just works.
If you have multiple other devices you need hardwired you
might need
some other trickery, but I guess in your case it's a simple
matter of
figuring out the right name for the maudio interface.
-- 
10:14 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Philipp wrote:
Excerpts from Geoff King's message of 2010-05-08
01:17:39 +0200:
And maybe it's helpful to mention that you have to enter the cardname
manually in QJackCtl the very first time you configure it this way, you
can't select it. Out of my head the cardname for a M-Audio 24/96 is
'M2496' so in QJackCtl you can try 'hw:M2496' in the Interfaces field
(without the quotes of course).
Best,
Jeremy
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always just works.
If you have multiple other devices you need hardwired you might need
some other trickery, but I guess in your case it's a simple matter of
figuring out the right name for the maudio interface. 
10:51 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Jeremy wrote:
Philipp wrote:
The one on my laptop is "USB Audio Codec". QJackCTL won't accept it,
name has spaces ...
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Excerpts from Geoff King's message of
2010-05-08 01:17:39 +0200:
And maybe it's helpful to mention that you have to enter the cardname
manually in QJackCtl the very first time you configure it this way, you
can't select it. Out of my head the cardname for a M-Audio 24/96 is
'M2496' so in QJackCtl you can try 'hw:M2496' in the Interfaces field
(without the quotes of course). Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always just works.
If you have multiple other devices you need hardwired you might need
some other trickery, but I guess in your case it's a simple matter of
figuring out the right name for the maudio interface.
11:24 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
david wrote:
Jeremy wrote:
Then your card name is probably 'default' and QJackCtl should accept
'hw:default' then.
Best,
Jeremy
Philipp wrote:
The one on my laptop is "USB Audio Codec". QJackCTL won't accept it,
name has spaces ...
Excerpts from Geoff King's message of
2010-05-08 01:17:39 +0200:
And maybe it's helpful to mention that you have to enter the cardname
manually in QJackCtl the very first time you configure it this way, you
can't select it. Out of my head the cardname for a M-Audio 24/96 is
'M2496' so in QJackCtl you can try 'hw:M2496' in the Interfaces field
(without the quotes of course). Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4
Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always just works.
If you have multiple other devices you need hardwired you might need
some other trickery, but I guess in your case it's a simple matter of
figuring out the right name for the maudio interface.
12:11 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
Excerpts from Jeremy's message of 2010-05-08 11:24:19 +0200:
david wrote:
> Jeremy wrote:
>
> The one on my laptop is "USB Audio Codec". QJackCTL won't accept it,
> name has spaces ...
This seems strange to me, are you sure? Can you paste the output of aplay -l and/or cat
/proc/asound/cards ?
Then your card name is probably 'default' and
QJackCtl should accept
'hw:default' then.
Best,
Jeremy
I'd be careful with 'default'. Afaik 'default' is a special device in
alsa which has dmix automatically enabled and who knows what else. I'm
not sure this is true in jack context, I'd just be careful and rather
use a proper name. Also 'default' probably is another name for hw:0 plus
the aforementioned dmix.
--
Regards,
Philipp
12:57 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
Philipp wrote:
Excerpts from Jeremy's message of 2010-05-08
11:24:19 +0200:
You're probably right, 'default' doesn't seem to be a proper name one
should use.
Best,
Jeremy
david wrote:
> Jeremy wrote:
>
> The one on my laptop is "USB Audio Codec". QJackCTL won't accept it,
> name has spaces ...
This seems strange to me, are you sure? Can you paste the output of aplay -l and/or cat
/proc/asound/cards ?
Then your card name is probably 'default'
and QJackCtl should accept
'hw:default' then.
Best,
Jeremy
I'd be careful with 'default'. Afaik 'default' is a special device
in
alsa which has dmix automatically enabled and who knows what else. I'm
not sure this is true in jack context, I'd just be careful and rather
use a proper name. Also 'default' probably is another name for hw:0 plus
the aforementioned dmix.
9 May
9 May
1:33 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Philipp wrote:
Ah, that explains why "default" in JACK is the Intel audio this morning.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Excerpts from Jeremy's message of 2010-05-08
11:24:19 +0200:
aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel
82801DB-ICH4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958
[Intel 82801DB-ICH4 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 3: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem
[Intel 82801DB-ICH4 Modem - Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/cards
0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
Intel 82801DB-ICH4 with ALC250 at irq 17
1 [default ]: USB-Audio - USB Audio CODEC
Burr-Brown from TI USB Audio CODEC
at usb-0000:00:1d.1-2, full s
2 [XMidi1X1 ]: USB-Audio - E-MU XMidi1X1
E-MU Systems, Inc. E-MU XMidi1X1 at
usb-0000:00:1d.7-3.4.4, full speed
3 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
Intel 82801DB-ICH4 Modem at irq 17
david wrote:
> Jeremy wrote:
>
> The one on my laptop is "USB Audio Codec". QJackCTL won't accept it,
> name has spaces ...
This seems strange to me, are you sure? Can you paste the output of aplay -l and/or cat
/proc/asound/cards ? Then your card
name is probably 'default' and QJackCtl should accept
'hw:default' then.
Best,
Jeremy
I'd be careful with 'default'. Afaik 'default' is a special device
in
alsa which has dmix automatically enabled and who knows what else. I'm
not sure this is true in jack context, I'd just be careful and rather
use a proper name. Also 'default' probably is another name for hw:0 plus
the aforementioned dmix.
8:55 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Excerpts from david's message of 2010-05-09 01:33:42 +0200:
aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel
82801DB-ICH4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958
[Intel 82801DB-ICH4 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 3: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem
[Intel 82801DB-ICH4 Modem - Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/cards
0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
Intel 82801DB-ICH4 with ALC250 at irq 17
1 [default ]: USB-Audio - USB Audio CODEC
Burr-Brown from TI USB Audio CODEC
at usb-0000:00:1d.1-2, full s
2 [XMidi1X1 ]: USB-Audio - E-MU XMidi1X1
E-MU Systems, Inc. E-MU XMidi1X1 at
usb-0000:00:1d.7-3.4.4, full speed
3 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
Intel 82801DB-ICH4 Modem at irq 17
Ah, that explains why "default" in JACK is the Intel audio this morning.
Wow, you USB device really is called default. Quite bad. I must admit
that I'm surprised. I'd also try to use hw:default, which hopefully is
different from (default) in qjackctl, whatever that may be.
Really confusing..
--
Regards,
Philipp
Then your
card name is probably 'default' and QJackCtl should accept
'hw:default' then.
Best,
Jeremy
I'd be careful with 'default'. Afaik 'default' is a special device
in
alsa which has dmix automatically enabled and who knows what else. I'm
not sure this is true in jack context, I'd just be careful and rather
use a proper name. Also 'default' probably is another name for hw:0 plus
the aforementioned dmix.
10 May
10 May
11:32 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Philipp Überbacher wrote:
Excerpts from david's message of 2010-05-09
01:33:42 +0200:
So I just tried typing in "hw:default" for QJackCtl, and it got the USB
device. In the morning, I'll see what "hw:default" is. Selecting
"(default)" from QJackCtl's drop down list gives me the Intel audio
right now.
aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel
82801DB-ICH4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958
[Intel 82801DB-ICH4 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 3: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem
[Intel 82801DB-ICH4 Modem - Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/cards
0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
Intel 82801DB-ICH4 with ALC250 at irq 17
1 [default ]: USB-Audio - USB Audio CODEC
Burr-Brown from TI USB Audio CODEC
at usb-0000:00:1d.1-2, full s
2 [XMidi1X1 ]: USB-Audio - E-MU XMidi1X1
E-MU Systems, Inc. E-MU XMidi1X1 at
usb-0000:00:1d.7-3.4.4, full speed
3 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
Intel 82801DB-ICH4 Modem at irq 17
Ah, that explains why "default" in JACK is the
Intel audio this morning.
Wow, you USB device really is called default. Quite bad. I must admit
that I'm surprised. I'd also try to use hw:default, which hopefully is
different from (default) in qjackctl, whatever that may be. Then your
card name is probably 'default' and QJackCtl should accept
'hw:default' then.
Best,
Jeremy
I'd be careful with 'default'. Afaik 'default' is a
special device in
alsa which has dmix automatically enabled and who knows what else. I'm
not sure this is true in jack context, I'd just be careful and rather
use a proper name. Also 'default' probably is another name for hw:0 plus
the aforementioned dmix. Really confusing..
Part of what makes Linux audio so much fun!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
12:37 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
On Sun, 2010-05-09 at 23:32 -1000, david wrote:
Philipp Überbacher wrote:
"default" is ALSA's default "device", the one that implements dmix
etc.
on the first sound card found.
"hw:default" will directly use the sound card actually named
"default".
--
Peter
Wow, you USB device really is called default.
Quite bad. I must admit
that I'm surprised. I'd also try to use hw:default, which hopefully is
different from (default) in qjackctl, whatever that may be.
So I just tried typing in "hw:default" for QJackCtl, and it got the USB
device. In the morning, I'll see what "hw:default" is. Selecting
"(default)" from QJackCtl's drop down list gives me the Intel audio
right now.
Really confusing..
Part of what makes Linux audio so much fun!
12 May
12 May
6:59 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Peter Nelson wrote:
On Sun, 2010-05-09 at 23:32 -1000, david wrote:
That's exactly how it worked this morning. And (interestingly) the
little volume control widget also was using the sound card called "default."
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Philipp Überbacher wrote:
"default" is ALSA's default "device", the one that implements
dmix etc.
on the first sound card found.
"hw:default" will directly use the sound card actually named
"default". Wow, you USB device really is called default.
Quite bad. I must admit
that I'm surprised. I'd also try to use hw:default, which hopefully is
different from (default) in qjackctl, whatever that may be.
So I just tried typing
in "hw:default" for QJackCtl, and it got the USB
device. In the morning, I'll see what "hw:default" is. Selecting
"(default)" from QJackCtl's drop down list gives me the Intel audio
right now.
Really confusing..
Part of what makes
Linux audio so much fun!
9 May
9 May
1:26 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
Jeremy wrote:
david wrote:
QJackCtl accepted it, but this morning the system appears to think
"default" is the builtin Intel audio. Well, "aplay -l" still reports
that default is "USB Audio Codec," but with JACK set to play using
"default", sound went through the Intel audio.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Jeremy wrote:
Then your card name is probably 'default' and QJackCtl should accept
'hw:default' then. Philipp wrote:
The one on my laptop is "USB Audio
Codec". QJackCTL won't accept it,
name has spaces ...
Excerpts from Geoff King's message of
2010-05-08 01:17:39 +0200:
> Hello,
> I have problem that I've been trying to figure out with no luck. The
> audio interface keeps changing for example:
>
> Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
> Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4
> Anniv is hw:1
> etc, back and forth, each reboot...
> I usually use qjackctl and have to keep changing the presets with
> settings which is annoying.
>
> I would greatly appreciate it if someone could provide me some clues
> or links on how to fix this?
>
> I'm Using Fedora 12 w CCRMA.
>
> thanks, Geoff
The easiest solution might be, using my setup as example:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UA25 [UA-25], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
So I use hw:UA25 in jack instead of hw:0
Jack always uses this device if it can find it, it always just works.
If you have multiple other devices you need hardwired you might need
some other trickery, but I guess in your case it's a simple matter of
figuring out the right name for the maudio interface.
And maybe it's helpful
to mention that you have to enter the cardname
manually in QJackCtl the very first time you configure it this way, you
can't select it. Out of my head the cardname for a M-Audio 24/96 is
'M2496' so in QJackCtl you can try 'hw:M2496' in the Interfaces field
(without the quotes of course). 
8 May
8 May
7:10 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
On Fri, 2010-05-07 at 19:17 -0400, Geoff King wrote:
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is hw:1
etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
While you can force the order with the proper index=xx incantations in
modprobe.d/ files, that will fail if the computer is booted with a usb
sound card attached.
The proper fix is to not use the index (a number) when addressing the
card but use the name of the card. That will never change across
reboots. So, instead of "hw:0" use "hw:NAME" where NAME is what is
shown
between square brackets in the output of cat /proc/asound/cards
-- Fernando
8:21 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
On Saturday 08 May 2010 19:09:27 Fernando Lopez-Lezcano wrote:
While you can force the order with the proper index=xx
incantations in
modprobe.d/ files, that will fail if the computer is booted with a usb
sound card attached.
What? This works here for the last three years, was is all just a dream?
Of course the solution is to 'reserve' the higher indices for the usb-audio
stuff...
The proper fix is to not use the index (a number) when
addressing the
card but use the name of the card. That will never change across
reboots. So, instead of "hw:0" use "hw:NAME" where NAME is what is
shown
between square brackets in the output of cat /proc/asound/cards
The you only have to face apps that don't allow the selection of the soundcard
and apps that don't handle spaces in device-names.
Arnold
8:55 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
While you can force the order with the proper index=xx
incantations in
modprobe.d/ files, that will fail if the computer is booted with a usb
sound card attached.
Okay - I tried this way and it did fix my problem, but I have now
removed my changes to be cautious since I have a mix of PCI and USB
stuff.
The proper fix is to not use the index (a number) when addressing the
card but use the name of the card. That will never change across
reboots. So, instead of "hw:0" use "hw:NAME" where NAME is what is
shown
between square brackets in the output of cat /proc/asound/cards
This seems to be working fine also and is easier to do without the
need to edit system files.
Thanks.
9 May
9 May
3:33 p.m.
New subject: Please help with audio interfaces that keep changing after reboot
On Saturday 08 May 2010 13:09:27 Fernando Lopez-Lezcano wrote:
On Fri, 2010-05-07 at 19:17 -0400, Geoff King wrote:
Does this solve the identical sound card problem in any way? Say two identical
usb sound cards at the low and and two delta 1010's a little further up the
chain as examples.
Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is
hw:1 etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
While you can force the order with the proper index=xx incantations in
modprobe.d/ files, that will fail if the computer is booted with a usb
sound card attached.
The proper fix is to not use the index (a number) when addressing the
card but use the name of the card. That will never change across
reboots. So, instead of "hw:0" use "hw:NAME" where NAME is what is
shown
between square brackets in the output of cat /proc/asound/cards
-- Fernando
all the best,
drew
10 May
10 May
11:33 a.m.
New subject: Please help with audio interfaces that keep changing after reboot
drew Roberts wrote:
On Saturday 08 May 2010 13:09:27 Fernando
Lopez-Lezcano wrote:
Hmm, IIRC, can't you use the alias option to assign a name to a specific
soundcard?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
On Fri, 2010-05-07 at 19:17 -0400, Geoff King
wrote:
Does this solve the identical sound card problem in any way? Say two identical
usb sound cards at the low and and two delta 1010's a little further up the
chain as examples. Hello,
I have problem that I've been trying to figure out with no luck. The
audio interface keeps changing for example:
Today: Maudio 24/96 is hw:1 and Midisport 4x4 Anniv is hw:0.
Yesterday before reboot: Maudio 24/96 is hw:0 and Midisport 4x4 Anniv is
hw:1 etc, back and forth, each reboot...
I usually use qjackctl and have to keep changing the presets with
settings which is annoying.
I would greatly appreciate it if someone could provide me some clues
or links on how to fix this?
I'm Using Fedora 12 w CCRMA.
While you can force the order with the proper
index=xx incantations in
modprobe.d/ files, that will fail if the computer is booted with a usb
sound card attached.
The proper fix is to not use the index (a number) when addressing the
card but use the name of the card. That will never change across
reboots. So, instead of "hw:0" use "hw:NAME" where NAME is what is
shown
between square brackets in the output of cat /proc/asound/cards
5311
days inactive
5316
days old
linux-audio-user@lists.linuxaudio.org
21 comments
12 participants
participants (12)
-
Arnold Krille -
david -
drew Roberts -
Fernando Lopez-Lezcano -
Geoff King -
James Warden -
Jeremy -
Niels Mayer -
Peter Nelson -
Philipp -
Philipp Überbacher
-
Reuben Martin