Tag Info

New answers tagged

1

You can usehdajackretask for that, which is part of the package alsa-tools-gui. You can install it with sudo apt-get install alsa-tools-gui.


1

SOLUTION: even if in the config file the Device parameter was set to default, you need to set the output device FROM THE MIXER. Yes, it was that easy.


0

I had the same problem (error: amixer: Unable to find simple control 'Master',0). When i added "-c 1", the volume increase and decrease commands do not unmute and the toogle command (mute / unmute) does not unmute. On another post, i finded to add "-D pulse" instead of "-c 1" and with this addon all commands are ok (increase and unmute, decrease and unmute, ...


0

What's happening in this case is that PulseAudio locks the ALSA Backend that LMMS tries repeatedly to access (causing the high CPU) and since Pulse has it locked, LMMS can't send audio through. You can easily disable PulseAudio while using LMMS by launching LMMS with the command pasuspenderlmms. That, or you could just stick to using Pulse as your output, ...


1

The subwoofer and rear speakers are not detected in Debian. You need to correctly assign the pins using hdajackretask. To install hdajackretask execute following command in terminal sudo apt-get install alsa-tools-gui now run the hdajackretask using terminal. A window will open with many options. Select the proper "Codec" and check the "Show unconnected ...


0

There is no system-wide GUI configuration for this. Many programs allow to configure the ALSA device name. ALSA's default hw and default devices, when not given a card number (i.e., not hw:0 but hw), use the ALSA_CARD or ALSA_PCM_CARD environment variables. So you can start your programs with scripts that set these environment variables appropriately.


0

Depending on the application, it might be possible to disable ALSA support so that it instead uses Pulseaudio directly. For example I have an OpenAL game which shows this problem. I edited /etc/openal/alsoft.conf and added the line drivers = pulse, so that OpenAL will always use Pulseaudio rather than checking for ALSA, OSS or other audio frameworks. Since ...


0

Alsa doesn't like only having USB audio and nothing else. In /etc/modprobe.d/alsa-base.conf, comment out this line: options snd-usb-audio index=-2


3

The first 0 is the card, and the second 0 is the device, as listed in the output of arecord -l: card 0: PCH [HDA Intel PCH], device 0: CX20585 Analog [CX20585 Analog]


0

This worked for me with a Lenovo 90W ultra dock and X240: options snd-hda-intel model=lenovo-dock


0

Seppo Erviälä's answer is right but not complete. As dma_k already noted, man alsactl clearly states at the end that, /var/lib/alsa/asound.state (or whatever file you specify with the -f flag) is used to store current settings for your soundcards. palacsinit appropriately noted that you can store config into your file with alsactl --file ...


0

Alsa-Json-Gateway https://github.com/fulup-bzh/AlsaJsonGateway supports store/restore of sound card sessions from JSON/REST API list sessions /jsonapi?request=session-list&cardid=hw:0 store session /jsonapi?request=session-store&cardid=hw:0&args=MySoundConfig restore /jsonapi?request=session-load&cardid=hw:0&args=MySoundConfig


0

I recently started having the same issue. I dual boot Windows 7 and Ubuntu 14.04. The issue seems to have started after Windows update installed a new Realtek HD Audio driver. A soft reboot from Windows to Linux results in audio consisting entirely of pop and crackle sounds. Completely unusable. While in this state the headphone jack on the front of my case ...


0

here is lsusb -v (as requested by CL) Bus 003 Device 003: ID 200c:100a Reloop Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol ...



Top 50 recent answers are included