Tag Info

New answers tagged

0

The issue here was the volume levels in alsa were muted. Open a terminal and run alsamixer Find the output you want to use and if it says mm underneath it is muted, just press m to unmute it. If the audio quality is poor try adjusting other outputs levels in alsamixer until it sounds good. If all else fails, switch the sound to pulse audio Install ...


0

My guess is that alsa mixer works for you too? On my system, the sounds settings are active only while pulseaudio is running. To start the daemon manually: pulseaudio -D If it gets in the way of something else you can stop it by pulseaudio -k


0

I do not know about configuring .asoundrc but what I can tell you is that you should probably run: sudo apt-get update sudo apt-get install pulseaudio In order to properly install Pulseaudio.


0

try this sudo apt-get purge pulseaudio gstreamer0.10-pulseaudio pulseaudio-utils after that restart the computer and test it out It worked for me!


0

I have solved the issue. I found a setting in the alsamixer called auto mute, disabling this did the trick! exact steps: open terminal and type "alsamixer" Press f6 and choose the soundcard making the popping noise. Navigate to automute and press down. Hopefully, this can save other the trouble I been through


0

Using the hw device disables all automatic sample format conversions. (And aplay does not support FLAC files.) The correct way to set the default card in asound.conf would be this: defaults.pcm.card 0 defaults.ctl.card 0 However, card zero is the default one anyway; you don't need any asound.conf.


0

The alsa-utils package contains tools like aplay and alsamixer. The ALSA library is provided by the package libasound2. However, no ordinary user would actually try to compile something, so the files needed for development were moved into the separate libasound2-dev package.


2

It is hard to tell over the static but for me it sounds like one of the default pidgin sounds. It could also be the systembell. To Further debug you sound you could kill the existing pulseaudio server, with pulseaudio -k. And launch pulseaudio -vvvvv It could be that you have any kind of IM running in background? Is there anything visible running in your ...


0

I managed to solve this, although not a optimal solution, it'll work. I installed PulseAudio Volume Control. Then went to "Configuration" and under the correct sound card, I chose the correct output (Analog 5.1). Then it shows up in sound settings again. Although, if I change the device in Sound Settings, I sometimes have to open PulseAudio Volume ...


0

options snd_usb_audio index=0 This options tells the snd-usb-audio driver that when it loads, it must claim the first sound card index. However, If that sound card index is already used by some other driver (snd-hda-intel in your case), loading fails. In theory, you would need to prevent such conflicts by telling all drivers which index to use. But a ...


0

The issue was the result of a kernel bug Ubuntu's kernel version 3.19.0-18. The issue was fixed in a later update.


1

That's OK, I found a documentation for it, it was in ALSA API documentation (I just missed it on the first look): ALSA project - the C library reference (alsa-project.org) A sequencer core has two pre-defined system ports on the system client SND_SEQ_CLIENT_SYSTEM: SND_SEQ_PORT_SYSTEM_TIMER and SND_SEQ_PORT_SYSTEM_ANNOUNCE. The SND_SEQ_PORT_SYSTEM_TIMER ...


1

The VirMIDI driver is designed as an interface between programs that access RawMIDI devices (actually, OSS devices /dev/midi*) and ALSA sequencer clients. Everything received at the raw MIDI device (hw:1,* or /dev/*) is sent on to the sequencer port. Everything received at the sequencer port (Virtual Raw MIDI 1-*) is sent on to the raw MIDI device. To ...


0

I can now answer half of my question, and may be the second half will never receive a positive answer. One can list raw MIDI devices using amidi -l. I just don't see a way to list connexions and it also only list devices, not clients. May be there is nothing comparable to the ALSA's sequencer subscription mechanism with ALSA's raw MIDI, hence this part of ...


1

In that case, install the ALSA oem-audio-hda-daily-dkms package using the following commands: sudo add-apt-repository ppa:ubuntu-audio-dev/alsa-daily press Enter and then execute: sudo apt-get update sudo apt-get dist-upgrade sudo apt-get install --reinstall dkms linux-image-generic linux-headers-generic linux-tools-generic linux-source ...


0

Copied answer from comments: Somehow I have found a fix (upon boot there is nothing listed in devices): If I have something playing in chrome and then I sudo alsa force-reload then it works (there is no hdmi output device, it only shows when I plug it in)


0

I also have this problem on ubuntu 14.04. The simpliest solution is just add official blueman devs ppa: https://launchpad.net/~blueman/+archive/ubuntu/ppa It works for me after update.



Top 50 recent answers are included