On Tue, 2014-10-28 at 11:39 +, mailing lists wrote:
Hello Tanu,
I'm not sure if you mentioned this already before (sorry for not
bothering to check), but is the PA version the same between the
machines? If not, then something may have been fixed in PA, but in any
case it seems more
02.11.2014 18:11, Tanu Kaskinen wrote:
On Tue, 2014-10-28 at 11:39 +, mailing lists wrote:
Hello Tanu,
I'm not sure if you mentioned this already before (sorry for not
bothering to check), but is the PA version the same between the
machines? If not, then something may have been fixed in
On Sun, 2014-11-02 at 18:52 +0500, Alexander E. Patrakov wrote:
02.11.2014 18:11, Tanu Kaskinen wrote:
On Tue, 2014-10-28 at 11:39 +, mailing lists wrote:
Hello Tanu,
I'm not sure if you mentioned this already before (sorry for not
bothering to check), but is the PA version the same
And this is wrong. However, the strace from the previous email did not
find any custom ALSA configuration files that could affect the outcome.
Thus, I conclude that you, or maybe some stupid script that you ran,
modified some file in /usr/share/alsa in a bad way in the past. Please
Sorry for the spam, but you have a very serious smoking gun in your log:
I like this type of (instructive) spam ;-)
D: [pulseaudio] alsa-util.c: Plug PCM: Direct Stream Mixing PCM
PulseAudio must not be running on top of dmix. dmix is the thing that,
by default, uses 48 kHz and does not
30.10.2014 15:43, mailing lists wrote:
open(/usr/share/alsa/pcm/dmix.conf, O_RDONLY) = 4
That's normal as long as the devices contained there are not actually
opened and as long as no new devices are created that use the dmix plugin.
To debug the issue, I need the output of these two
To debug the issue, I need the output of these two commands:
aplay -vv -d 1 -f cd -D hw:0 /dev/zero
aplay -vv -d 1 -f cd -D front:0 /dev/zero
I'm sorry, here they are:
root@rpi:~# aplay -vv -d 1 -f cd -D hw:0 /dev/zero
Playing raw data '/dev/zero' : Signed 16 bit Little Endian, Rate 44100
30.10.2014 16:12, mailing lists wrote:
To debug the issue, I need the output of these two commands:
aplay -vv -d 1 -f cd -D hw:0 /dev/zero
aplay -vv -d 1 -f cd -D front:0 /dev/zero
I'm sorry, here they are:
root@rpi:~# aplay -vv -d 1 -f cd -D hw:0 /dev/zero
Playing raw data '/dev/zero' :
And this is wrong. However, the strace from the previous email did not
find any custom ALSA configuration files that could affect the outcome.
Thus, I conclude that you, or maybe some stupid script that you ran,
modified some file in /usr/share/alsa in a bad way in the past. Please
Alexander, thank you very much for the detailed explanation.
The theory is very simple. It probes at startup whether the configured
sample rate and the alternate sample rate (both can be seen in
/etc/pulse/daemon.conf) are supported. If none is supported, PulseAudio
picks a
29.10.2014 15:14, mailing lists пишет:
Alexander, thank you very much for the detailed explanation.
The theory is very simple. It probes at startup whether the configured
sample rate and the alternate sample rate (both can be seen in
/etc/pulse/daemon.conf) are supported. If none is
29.10.2014 15:37, Alexander E. Patrakov wrote:
29.10.2014 15:14, mailing lists пишет:
Alexander, thank you very much for the detailed explanation.
The theory is very simple. It probes at startup whether the configured
sample rate and the alternate sample rate (both can be seen in
29.10.2014 15:37, Alexander E. Patrakov пишет:
29.10.2014 15:14, mailing lists пишет:
Alexander, thank you very much for the detailed explanation.
The theory is very simple. It probes at startup whether the configured
sample rate and the alternate sample rate (both can be seen in
Upon reading your log further, I have a better guess. It looks like your
sound card supports only 48 kHz for capture, and, while capture is
active, also requires playback to be open at 48 kHz.
You can work around this limitation by setting the card profile to
output:analog-stereo using
The 8000, 11025, 16000 and 22050 values are capture samplerates (see
below /proc/asound/card1/stream0 output), for playback the card support
32000, 44100, 48000.
my laptop is running kernel 3.17.1 and the raspberry kernel 3.12.29,
which are less than a year apart and both reports the same
I had to put something like
pcm.!default {
type hw
card 0
}
in my /etc/asound.conf in order to get a default rate of 44100.
Laurentiu
it doesn't make any difference, the core problem is that pulseaudio detects
diferent capabilities on diferent architectures with the
Hello Tanu,
I'm not sure if you mentioned this already before (sorry for not
bothering to check), but is the PA version the same between the
machines? If not, then something may have been fixed in PA, but in any
case it seems more likely to me that there was some change in the kernel
driver
28.10.2014 16:39, mailing lists wrote:
Hello Tanu,
I'm not sure if you mentioned this already before (sorry for not
bothering to check), but is the PA version the same between the
machines? If not, then something may have been fixed in PA, but in any
case it seems more likely to me that there
On Tue, Oct 28, 2014 at 8:39 AM, mailing lists listas.cor...@yahoo.es wrote:
raspbian comes with PA 2, but I did compiled PA 5
FWIW, you could enable the jessie repository and pull pa 5 from there.
You could also pick up newer alsa-lib and kernel too.
deb
, mailing lists listas.cor...@yahoo.es wrote:
Subject: pulseaudio (V5) incorrect rate detection on usb sound card with
raspberry
To: pulseaudio-discuss@lists.freedesktop.org
Date: Wednesday, October 22, 2014, 1:23 PM
Hello,
I'm not entirely sure about if pulseaudio is the culprit
here
20 matches
Mail list logo
