Ok, so I'll send a patch for the LPIB quirk for Stefano Lodi's device.
If anybody else with an atom-based box, who can confirm that
position_fix=1 works for them, could you file a new bug against the
alsa-driver package (this will gather the relevant hw info) and point me
to it by posting a comment
Rhythmbox tests: I can still hear the loops I mentioned two posts ago,
however in almost all cases there is a recovery after a few loops, that
is, rhythmbox jumps ahead and proceeds normally. Gstreamer pipeline
still to test.
--
You received this bug notification because you are a member of Ubunt
I attach two logs obtained using vlc and position_fix=1. The audio
output suddenly stopped in both cases.
In the meantime I am continuing the tests using rhythmbox.
** Attachment added: "vlc + position_fix=1, 2 logs, compressed archive"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bu
I attach the output of alsa-info.
I'm trying the methods you suggested in a minute.
BTW yesterday I logged pulseaudio using vlc. No choppy sound, however
after a random number of minutes (at most 30) the audio output is
trapped into an infinite loop a few seconds long, and finally stops
completel
Could you please submit an alsa-info, see
http://wiki.ubuntu.com/Audio/AlsaInfo ?
Also, banshee uses gstreamer internally, so maybe another player (i e
Rhythmbox) would still show the bugs, although with less randomness? Or
even a raw gstreamer pipeline (the example is for an ogg file):
gst-launc
The high cpu usage is independent of position_fix=1. It looks like a
problem related to the interface, which for some reason is slow in
handling mouse events in submenus of Applications and in the Places
menu, to some extent also in file context menus and in Nautilus menus.
On the other hand I am
Thanks for your continued investigation. I'm wondering what to do next.
I could submit an LPIB quirk for your particular machine (for that I'll
need an alsa-info, see http://wiki.ubuntu.com/Audio/AlsaInfo ), which
would mean that in the next version of Ubuntu, position_fix=1 would be
the default.
Note that I have not updated my system, currently there are almost 150
updates involving GNOME and Banshee. My system is exactly as it was
when I attached the first logs here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
No, I do not remember noticing a hang. But I might have moved the Sound
preferences volume slider when or before the sound became corrupted.
That is the control I used in the last tests.
I have just repeated the test with position_fix=1. The sound distortion
I mentioned in the previous test did n
Thanks. So the most disturbing in the first log is:
( 262.115| 0.000) D: [alsa-sink] alsa-sink.c: Waking up in 43.01ms (system
clock).
( 270.521| 8.405) E: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a
value that is exceptionally large: 1822684 bytes (10332 ms).
This was probably wher
Here's the log of Banshee.
** Attachment added: "Banshee log for options snd-hda-intel position_fix=2"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/825709/+attachment/2604410/+files/gstlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
2nd test: With
- options snd-hda-intel position_fix=2 in /etc/modprobe.d/alsa-base.conf
- autospawn = no in ~/.pulse/client.conf
result: choppy sound, just as in my initial test (that is without the position
fix).
I kept a volume control window open during the test.
** Attachment added: "Pulseau
Here's the other log (Banshee).
** Attachment added: "gstlog.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/825709/+attachment/2604401/+files/gstlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
1st test: With
- options snd-hda-intel position_fix=1 in /etc/modprobe.d/alsa-base.conf
- autospawn = no in ~/.pulse/client.conf
result: fine sound until about 1'30 from start, then a few jumps ahead; finally
the sound became distorted until the end of the test (about 3').
I kept a volume contro
> Should I perform the tests with the installed version
1:1.0-0ubuntu3+bufferingtest or the new version 1:1.0-0ubuntu3.1?
Please use the 1:1.0-0ubuntu3+bufferingtest version. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I guess not with 1:1.0-0ubuntu3.1 if I have to record logs as that
version is listed in the official repositories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/825709
Title:
Choppy sound due to exc
Ok, I'll try first with a volume control open and then closed, as I do
not remember whether it was open or not.
I see there is an update (1:1.0-0ubuntu3+bufferingtest -->
1:1.0-0ubuntu3.1), however the changelog does not mention the bug of
this thread. Should I perform the tests with the installe
I also noticed that you might have had a volume control opened when you
tested? If so, make sure to repeat the test case with the same
conditions with the new position_fix versions. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
18 matches
Mail list logo
