[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packag
** Tags added: regression-release saucy
** Tags added: trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 su
> # Enable basic debugging, do jiffies check and enable one shot dump of last
> 10 ring buffer positions
> # Usefull, when the position is broken only after some of time (to reduce
> ksyslog messages)
> echo 101 > /proc/asound/card0/pcm0p/xrun_debug
That doesn't seem to do anything.
Just to be c
> did you find any message such as "PCM: hw_ptr skipping!" ?
No.
> did period update occur at period boundary ?
I don't know how to tell.
> are there any message by totem or gst ?
No messages from gst-launch.
These messages were produced by Totem, but they don't seem relevant:
(totem:5747):
> do jiffies check and enable one shot dump of last 10 ring buffer
positions
I don't know what a jiffies check is. I don't know how to dump ring
buffer positions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
ht
most of 5.1 audio are 48000Hz
but you try to use it as default device to play audio at any rate
try revert this patch to remove 48000Hz constraints
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/emu10k1/emupcm.c?id=57e5c63007955838043e34c732d224b2cbbb128f
--
You
# Enable basic debugging, do jiffies check and enable one shot dump of last 10
ring buffer positions
# Usefull, when the position is broken only after some of time (to reduce
ksyslog messages)
echo 101 > /proc/asound/card0/pcm0p/xrun_debug
--
You received this bug notification because you are
did you find any message such as "PCM: hw_ptr skipping!" ?
did period update occur at period boundary ?
are there any message by totem or gst ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchp
$ ./chmap -D pulse query
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection
refused
Cannot open PCM stream pulse for PLAYBACK
I guess this result is because this system is not running Pulse.
--
You received this bug notification because you are a member of Desktop
Pa
When I comment out my pcm.!default line in .asoundrc, I get this result:
$ ./chmap -D default query
Cannot query maps
it is because pulse plugin does not support channel map
./chmap -D pulse query
--
You received this bug notification because you are a member of Desktop
Packages, which is su
Setting xrun_debug to 29 and reproducing the problem yielded a ton of
debug hwptr_update and period_update messages in syslog. I'll attach
the messages that were logged when playing a few seconds of my 48000 Hz
test file.
** Attachment added: "xrun_debug messages from syslog"
https://bugs.lau
try
# Enable basic debugging, do jiffies check and dump position on each period
and hardware pointer update calls
# Usefull when the lowlevel (specific) hardware driver is somehow broken
echo 29 > /proc/asound/card0/pcm0p/xrun_debug
examine the system log to look for any message about the h
$ ./chmap -D front query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
FL FR
should the channel map use MONO instead of UNKNOWN for front device ?
http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/conf/cards/Audigy2.conf;hb=HEAD
$ ./chmap -D hw:0,0 query
Cannot query
>> pcm.!default {
>>type plug
>>slave.pcm "surround51"
>>}
>
>this won't upmix stereo to 5.1 as you expected (center and lfe are just left
>and right)
I don't expect it to upmix anything. I use that setting so that media
players can succeed at playing movies with 5.1 audio.
--
You rece
$ ./chmap -D hw:0,0 query
Cannot query maps
$ ./chmap -D front query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
FL FR
$ ./chmap -D rear query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
RL RR
$ ./chmap -D center_left query
ALSA lib pcm.c:2239:(snd_pcm
> did the problem occur with non 48000Hz audio ?
It definitely occurs with a 44100Hz PCM wav file. Gstreamer says this about
one file I'm using to test:
channels=(int)2, width=(int)16, depth=(int)16, signed=(boolean)true,
rate=(int)44100
It also occurs with a 48000Hz PCM wav file. I resampled
All these sound fine:
speaker-test -d -c 2 -t wav -D front
speaker-test -d -c 2 -t wav -D rear
speaker-test -d -c 2 -t wav -D center_lfe
speaker-test -d -c 4 -t wav -D surround40
speaker-test -d -c 2 -t wav -D default
speaker-test -d -c 4 -t wav -D default
speaker-test -d -c 6 -t wav -D default
-
> pcm.!default {
>type plug
>slave.pcm "surround51"
>}
this won't upmix stereo to 5.1 as you expected (center and lfe are just
left and right)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.la
http://git.alsa-project.org/?p=alsa-
lib.git;a=blob_plain;f=test/chmap.c;hb=HEAD
chmap -D hw:0,0 query
chmap -D front query
chmap -D rear query
chmap -D center_left query
chmap -D surround40 query
chmap -D surround51 query
chmap -D default query
--
You received this bug notification becaus
http://git.alsa-project.org/?p=alsa-
lib.git;a=blob_plain;f=test/chmap.c;hb=HEAD
chmap hw:0,0 query
chmap front query
chmap rear query
chmap center_left query
chmap surround40 queryy
chmap surround51 query
chmap default query
--
You received this bug notification because you are a member o
how about
speaker-test -d -c 2 -t wav -D front
speaker-test -d -c 2 -t wav -D rear
speaker-test -d -c 2 -t wav -D center_lfe
speaker-test -d -c 4 -t wav -D surround40
speaker-test -d -c 2 -t wav -D default
speaker-test -d -c 4 -t wav -D default
speaker-test -d -c 6 -t wav -D default
http
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=57e5c63007955838043e34c732d224b2cbbb128f
did the problem occur with non 48000Hz audio ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https:/
speaker-test -c 6 -t wav -Dsurround51 produces clear test sounds; no
crackling.
I'm attaching the alsa-info.sh output.
$ pactl list
The program 'pactl' is currently not installed. You can install it by typing:
sudo apt-get install pulseaudio-utils
$ pactl stat
The program 'pactl' is currently no
how about
speaker-test -c 6 -t wav -Dsurround51
post the output of alsa-info.sh
pactl list
pactl stat
and pulseaudio verbose log
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, wh
Possibly of interest: The noise occurs with both gst-launch-0.10 and
gst-launch-1.0.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in
26 matches
Mail list logo
