Debian Multimedia :: Change The Default ALSA Device?
Aug 24, 2010
I recently bought a logitech headset which is working very nice, the thing is that I cannot make it my default device when I plug it in. I edited /etc/modprobe.d/alsa-base.conf to make snd-usb-audio the default card but it only works when the computer is turned on with the headset plugged in. A workaround is to plug it and then "alsa force-reload" but I find it very ugly plus it kills all apps using audio and leaves the volume indicator unstable.
Pulseaudio got installed by default here during installtion. Since I don't want it I first ran "systemctl disable pulseaudio", "pulseaudio --kill", then without rebooting I use mpd with alsa alone and it worked fine.
But then i rebooted, and now all applications, mpd, mpv, chromium etc just says that alsa returns with "Device or resource busy", tried rebooting again with no effect.
The soundcard appears as card 1 according to the output of "aplay -l", and defined that card 1is suposed to be default with this in "/etc/asound.conf":
Code: Select allpcm.!default { type hw card 1 }
ctl.!default { type hw card 1 }
It occurred to me that there might be an issue with permissions to the soundcard so I ran "ls -l /dev/snd"
I recently installed a new sound card, and I need to find out how to change the default device. Currently, I'm dual-booting Windows, and I had re-enabled the on-board audio in the PC's bios. After doing that, Debian started detecting that on-board as the default sound device. Is there a way to set my sound card to be used instead? I found out that the 'alsaconf' utility has been phased out. I"m currently running Debian testing, for amd64.
I'm running 9.10. I was installing ALSA so that I could run my EMU 1616, and when I tried to go through the steps to install, I'm running into two errors that I've noticed so far. I think. Anyway, the first is that is states that the panelw library isn't there, and that alsamixer: function snd_ctl_open failed for default: No such device or address. The alsamixer one is really odd, since it's there, but I don't know why it won't run.
I initially had it running, and now it isn't. I've yet to get sound out of my EMU. the terminal window also tells me that it can't find the snd_emu file, even though it exists on the computer as well. I need an answer for a dummy.
I have a problem on a fresh install of Jessie with KDE. I have three soundcards. In Wheezy I used pavucontrol once for each application to change the sink from the internal to the external soundcard, and that setting would stick each time I rebooted the system (audio would go on the external soundcard). Now each time I reboot the audio gets routed to the internal soundcard and I have to use pavucontrol each time to route the audio back to the external one. URL...
and none of them has worked. I don't know if it's a related issue, but the settings I choose in the for Phonon in the KDE multimedia settings don't stick either. I select the external soundcard as default device and upon reboot the internal one is on top on the preferences list.
I have a Lubuntu installed Netbook (Toshiba NB200). When I try to watch a video and listen to music smoothly. So I started the program Audacious on the terminal and I get the following Warning Message:
Code:
** WARNING ** Audacious has detected that your ALSA device has a broken timer. A workaround is being used to prevent CPU overload. report this problem to your Linux distributor or to the ALSA developers. ALSA lib pcm.c:7316:(snd_pcm_recover) underrun occurred
I'm trying to monitor (listen to) a second ALSA device on the default first card (#0). The device seems properly configured - for example, Audacity can select the device and record from it just fine; and when I select "Start Monitoring" in the volume level menu (the small triangle..), the volume level reacts to the captured stream. The only thing missing is the actual sound.
Before going any further, here are my specs; up-to-date Debian Squeeze on amd64 (x86_64), kernel 2.6.33.2. Output of aplay -l: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: VT1828S Analog [VT1828S Analog] Subdevices: 1/2
[Code]...
p.s. In case you feel inclined to tell me the command above should be just fine for me and not to waste my time with looking for an easier way; that only works when no other application has the default device (or the second device!) in its claws. p.s.#2 : You probably noticed that the device is actually the third ALSA device. The real second device has no playback. I'm assuming this is no problem, since the same problem applies to that card.
I was having issues with the mic or line in on my onboard sound card, while trying to get my tvtuner patched in, later I gave OSS a try, I could not get it to work and decided to go back to Alsa, now my soundcard is not functioning.I have followed quite a few different guides, one of which is the sticky, please forgive me for not remembering which guides. I'm going nuts over this.As you can see below it looks like it is still using the oss driver.
uname -a Linux freekbox 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24 07:28:56 UTC 2010 i686 GNU/Linux
aplay -l aplay: device_list:223: no soundcards found...[code].........
I notice that each time I boot my computer, under the playback section of the ALSA Mixer the 'Speaker' volume control is turned all the way down. Even when I return it to the proper level, and then restart my computer later, the slider for 'Speaker' seems to default back to the previous state mentioned above. Is there a way to set the default for the ALSA mixer in a .conf file of some sort so that the default setting for 'Speaker' is always at max?
I've been struggeling with this for a few hours now, googleing and so on trying to find an easy way to just switch which device I want as primary for internet connections. After long battles I'm at a loss, this is the current automatic routing
Code: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 85.225.76.0 0.0.0.0 255.255.252.0 U 1 0 0 eth0 85.225.76.0 0.0.0.0 255.255.252.0 U 2 0 0 wlan0
I have recently been forced to do a hardware upgrade (my previous mobo died). Now, sounds works ok with,amarok because kde has recognized the new hardware and switched to it.
..... does not work, likely because flash uses alsa-oss which is probably not configured automatically. I have tried uninstalling and reinstalling both alsa-oss and flash, but it didn't solve the problem.
I'm having some trouble getting ALSA working on my system. I had been using OSS for awhile but decided to move to ALSA after a kernel upgrade. ALSA worked fine except for the tedious chore of having to run alsaconf everytime I booted up. I was getting errors message for OSS during boot up telling me OSS modules weren't loading properly and linux-headers needed to be installed to get it to work properly again. I ended up installing the linux-headers later due to some nvidia driver fiddling. My system has now reverted back to OSS and I can't seem to get ALSA to work at all. I have libasound2, alsa-base, alsa-utils and alsa-oss installed and alsaconf says no ALSA modules are loaded. I've been searching around and haven't found how to get rid of OSS to install ALSA properly.
Distro: Debian Lenny Kernel: 2.6.26-2-686 Sound Card: Creative Labs SB Audigy OSSv4.1 ALSAv-current packages according to synaptic
I use an echo indigo audio card. When I do aplay -l I see this card, and I can ouput audio through it by specifically telling mplayer to use this (alsa) device. Now I want to use this card as default for all audio. At the moment the default is pulseaudio through the built in soundcard. How can I change this? Im running Ubuntu 10.04.
I'm having here annoying "problem" with my webcamera. Everytime I want to use it as a microphone it needs to be switched manually in sound settings menu. It's not a big deal but I would really rather let it be switched automatically like plug and play or something like that.
VLC says: "main input error: ES_OUT_SET_(GROUP_)PCR is called too late" when I am playing back most Bluray discs I have tried.
See this bug post for what I am talking about: [URL].... It has to do with playing back h264 video with ALSA.
Possible fixes: 1. Obtain VLC 2.2.2 - see below 2. Fix by Modax here: https://trac.videolan.org/vlc/ticket/10422 - not currently using dmix and not sure how this will relate to HDMI sound 3. Use Pulseaudio - this does not work for me to get HDMI sound and I do not use Pulseaudio as a rule
I have just tried to compile VLC 2.2.2 and the configure script finished properly but early in the build it fails.
With make the error is:
Code: Select alljason@MEDIA:~/vlc-2.2.2$ make -j4 make all-recursive make[1]: Entering directory '/home/jason/vlc-2.2.2' Making all in compat make[2]: Entering directory '/home/jason/vlc-2.2.2/compat' GEN dummy.c make all-am
[Code] ....
And with compile the error is:
Code: Select allMAKE : compat MAKE : doc MAKE : po MAKE : share for f in vlc.desktop.in skins2/default/theme.xml skins2/default/subX/about.png skins2/default/subX/eq.png skins2/default/subX/font.otf skins2/default/subX/main.png skins2/default/subX/playtreeglyphs.png skins2/default/subX/pl.png skins2/default/subX/sysbuttons.png skins2/default/subX/vol_anim.png skins2/default/subX/vol_slider.png
[Code] ....
I have tried installing 3 different versions of libua-dev, 5.1, 5.2 and 5.3. What could be the problem?
With the bugged audio drivers I'm going to replace the computer but it would still be nice to be able to know the solution to compiling VLC 2.2.2.
I'm using Debian squeezy amd64-based with KDE4.3 from the repo. I've installed kde-minimal package with some additional packages from KDE. Also I have GNOME installed on my system.
So the problem is that when I'm in KDE alsa is not shares between applications. It means that when I'm listening Amarok, for example, I can't play any other sounds in the system, not in browser or KPlayer. And if I stop Amarok playback, I can start listening some other application or watch a movie with a sound. It looks like I'm using good old OSS again. Back to the 90's =)
In gnome meanwhile all works fine. I suggest that I'm missing some configuration or a package, or something else. I've also tried to install kde-full package, but nothing changed.
I am using a couple of Debian Distro (Sid and Lenny) add some Ubuntu into the mix. I made the switch because I was amazed and satisfied with Debian --> once installed, everything works. For me that's okay for o so many years now. I don't question a lot because it just works and I do my job on it satisfactorily. Namely programming the LAMP style programming. Lately I have been using Debian to communicate over the internet -- using Skype and Pidgin and other such things, not to mention listening to music, watching movies, just using the default applications when I originally install Debian.
Along the way, I need to configure something -- that is desktop related -- like the screen resolution of a new LCD monitor replacing the old one and such. Now about my sound -- I'm not touching it because it is working. But that is not the case always. Now I have a constant error -- it is irritating. Rhythmbox don't make a sound always when I have open a web browser (iceweasel, chrome, epiphany) and a site with multimedia object on it -- like a video or something. So how do I correct this? How do I know, too what I am using -- ALSA or Pulseaudio?
This is probably one of those situations easy to solve but I haven't had any success as I've been messing around with the sound handling in my system.
I found it had running ALSA, OSS and PulseAudio and ended up purging everything in the system except for ALSA. Pulse Audio, for some reason, would shut down the sound-card when I muted sound though keyboard shortcut; after that, I had to manually open the sound table and enable a master control that would always remained closed.
Now, after purging the system of the excess baggage, ALSA will not retain the settings of the user; system will always reboot with PCM sound control fully closed.
In the process of trying to get the softmodem working, I finally attached speakers to this laptop and tried to play some sounds. Nothing but silence. Both the KDE system sounds and a stand-alone player (noatun) produce nothing. No error messages that I can find, either. (That might explain why the softmodem is dead, too...) I've run alsaconf several times, and even uninstalled and reinstalled ALSA. It thinks it is working, but is not. What sorts of things do I need to check to find where it isn't working?
Info: The motherboard is a FIC 3500W with the VIA P4M800 integrated chipset. This includes the VIA 8237 sound system, which is what ALSA detects and tries to use. The machine also has a Realtek ALC655 but I don't see any drivers for that in the lsmod output, so this is a possible source of the trouble.
The sysytem I use is Debian Squeeze. what's wrong but jackd2 from debian official repositories does not work with alsa (I have alsa-base, alsa-tools, libaudio-dev, libaudiofile-dev and libasound2-dev installed). Now I downloaded fresh jackd2 source from sourceforge and when I try to "./waf -configure" it it says that there is no alsa package or it's too old in the system and configures itself without alsa support.
I have a E-MU 0202 USB soundcard that I want to use as a input for my Debian Squeeze 6.0.1. Stock squeeze (kernel 2.6.32-5-686, version 2.6.32-31) has alsa-driver 1.0.21 as kernel modules and alsa-utils 1.0.23. The E-MU needs 1.0.23+ alsa driver, with 1.0.21 it loads in alsa but is not functional (no input) So I tried to install the 1.0.23 modules with module assistant: m-a update && m-a prepare m-a a-i alsa I left all conf-files (like /etc/modprobe.d/alsa-base.conf) standard. When I now connect the E-MU device, my whole system becomes unresponsive (to keyboard/mouse), and I get the following messages in my console: BUG: soft lockup - CPU#0 stuck for 61s! [modprobe:1292] Also, when I start top before connecting, I can see modprobe process taking 100% for a few minutes before system freezes completely. It did generate an oops once: [URL].... Does anybody here have any ideas how to get this working?
I decided to break free from the horrible life of a windows vista user. I like my new debian (Wheezy) installation and everything worked fine so far. Now I stumbled upon a huge problem. When I want startup and login into my gnome installation the first application I open gets to play sound and others after that just don't work. I looked endlessly on google but in my understanding the problem is within the ALSA driver.
Some specs : OS version : Debian 7 (Wheezy) Laptop brand : Packerd Bell Easynote LJ-65 Kernel installed : 2.6.38-2-686 (Standard one in wheezy)
I want to remove pulse and install alsa instead but I can't seem to be able to do it. I tried to search for all packages with "pulse" in their names and purging them but it didn't work because aptitude wanted to remove all of the packages that used pulse with along with pulse.
I have detected some problems when I try to record sound in my Kubuntu 10.04 system.
The problem is that the "default" device for audio recording does not work but I have to select another device to do so. I always selected the "default" device for audio recoding but currently I have to select hw:0,2 device.
Another odd thing is that different programs show me different device. For example, Audacity shows me that I have the following audio recording devices:
- HDA Intel: ALC888 Digital (hw:0,1) - HDA Intel: ALC888 Analog (hw:0,2) - spdif - default
The only one that works is hw:0,2.
But arecord shows me (when I execute "arecord -L") the following:
Finally, in KDE system preferences for audio I get that I have 2 different audio devices for audio recording:
- HDA Intel (ALC888 Analog): it is said that it will try first x-phonon (CARD=0, DEV=0) and, if the latter does not work, it will try plughw (CARD=0, DEV=0)
- HDA Intel (ALC888 Digital): it is said that it will try first x-phonon (CARD=0, DEV=1) and, if the latter does not work, it will try plughw (CARD=0, DEV=1)
Where is the hw:0,2? and how can I set the alsa system to use hw:0,2 as the default device for audio recording?
All of that would not be a problem but I also have an ubuntu 9.04 installed on a virtual machine (by using virtualbox) and audio recording doesn't work there. I suppose that it is becase of the virtual sound card is using default devices for playing and recording audio.
I must say that audio playback works fine in both host and guest systems. It is just audio recording.
I'm having a problem all the sudden with amixer. set Master 5% used to control the pulse audio master volume. Suddenly, it will only raise and lower the headphone volume. Pulseaudio works, but I no longer have a master volume at all.
I'm at the tail end of my upgrade from Lenny to Squeeze and I think this sound issue is the last one I have. As usual I've tried hunting for some answers but it gets very confusing when people are using KDE or PulseAudio or Ubuntu or slightly different configuration to what I have.
My config: Debian Squeeze 2.6.32 Alsa (just because I was using that in Lenny and it was working, no other reason) Gnome Rhythmbox Skype
Skype is pretty good - it has the sound configuration built in, so I say ring the speakers and it does. I say talk to the headset and it does. Rhythmbox is my music player (again just because I was using it under Lenny) however it only wants to play through the headset. I can't seem to get it to play to the speakers attached to the rear port.
Summary of some settings (transposed manually) # aplay -l *** List of PLAYBACK hardware devices *** card 0: Headset (Logitech) device 0: usb audio subdevice 0/1 card 1: Intel HDA device 0: ALC883 Analog
I have recently acquired a Lenovo Q150 machine and attempting to use it as a HTPC. I've been reading that with this platform a newer kernel is required to make wireless, sound and a few other tweaks work correctly--so I bumped up to testing repositories to upgrade to the 2.6.38 kernel.[URL]...
The audio on this device has been more than a pain. I'm currently using XBMC to play media on this device and after setting the outputs to custom: plughw:1,9 sound is played correctly. I found this out by using alsamixer, selecting the sound card with the F6 key (Nvidia 1) unmutting all outputs, quiting, and running speaker-test -D plughw:1,X where X is the sub-device from the output of aplay -l until sound could be heard from the receiver.
Now my problem is that applications like mplayer, and iceweasel won't output any sound. I'd prefer not to use the optical out on the device and would like to send sound over HDMI. Has anyone had any luck getting it to work as it should?
I've also installed pulseaudio, not too sure if this is really needed. I've also used module assistant before upgrading to compile alsa from source, it worked but i just decided to upgrade the kernel instead of dealing with m-a every time an update comes through. Linux floppy 2.6.38-2-amd64 #1 SMP Thu Apr 7 04:28:07 UTC 2011 x86_64 GNU/Linux
