Hi Elio,
> > I would recommend upgrading to 13.0.
> I'm quite recluctant to do this, since the Download PulseAudio page
> says it's a non-trivial job. Anyway, as a last resort, I will.
Maybe you could try a live CD / USB distribution that ships newer software.
That way you could at least find
Hi,
Is it possible that your sound card was held busy by another process,
maybe by Pulseaudio running under a different user?
The Pulse ALSA plugin usually prevents applications from opening the
hardware device (routing them through Pulse instead).
Laurentiu
On Mon, Sep 18, 2017, at 12:37,
Hi,
The 9.0 release notes mention memfd as a SHM transport variant that can
make Pulseaudio perform better when running in the system mode, but the
implementation seems to disallow it [1].
I'm wondering if there still are plans to make this work.
Laurentiu
[1]
Hi,
I'm a bit reluctant to write about it, but a while ago I wrote a Windows
driver to send audio as RTP to a PulseAudio receiver. It worked,
although it had some rough edges like not waiting for network sends when
shutting down, so if you disabled the driver while playing audio it
would crash.
On Thu, Oct 2, 2014, at 14:43, Raymond Yau wrote:
What do mean when you say default-fragments *
default-fragment-size-msec?
I suppose PulseAudio uses a ring of `default-fragments` buffers, with a
length of `default-fragment-size-msec` each. For example, for 4
fragments of 25 ms, I get
-29 16:33, Laurențiu Nicola wrote:
If nobody tried it, I might test the patch on my USB DAC. The problem is
that I'm not sure what's the best way to benchmark the playback. Do you
have some tips on that?
Run top in a low-latency playback scenario, that should be enough. You
might want
If nobody tried it, I might test the patch on my USB DAC. The problem is
that I'm not sure what's the best way to benchmark the playback. Do you
have some tips on that?
Laurentiu
On Mon, Sep 29, 2014, at 15:16, David Henningsson wrote:
On 2014-09-26 23:20, Pierre-Louis Bossart wrote:
On
to be expected, but it's still nice to
have confirmation.
Now if I only could check the performance of speex-fixed vs. speex-float
on my platform.. :).
Laurentiu Nicola
On Sun, Sep 14, 2014, at 16:34, Alexander E. Patrakov wrote:
07.09.2014 17:04, Laurențiu Nicola wrote:
Great, thanks
I have a question related to your tests. In my application, I need
resampling between close rates (let's say from 44200 to 44100). Do you
feel that the results would basically be the same in this kind of
situation?
Thanks,
Laurentiu Nicola
On Wed, Sep 3, 2014, at 10:25, Alexander E. Patrakov
Great, thanks!
On Sun, Sep 7, 2014, at 14:02, Alexander E. Patrakov wrote:
07.09.2014 16:58, Laurențiu Nicola wrote:
I have a question related to your tests. In my application, I need
resampling between close rates (let's say from 44200 to 44100). Do you
feel that the results would
Not sure whether it's the best way, but one idea would be to run
PulseAudio in system mode (with the necessary warnings:
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/
). You could then use Requires and After in the xbmc service file to
specify
Hello,
If I'm allowed to give my two cents here, I would prefer Tanu's design.
I find it much more natural (and useful) to reason about a general
volume and balance controls than about per-channel volumes. Of course,
an application can easily convert between the two representations.
As for the
While I agree, I think it's only fair to say that both Windows and
PulseAudio avoid the resampling if the source sample rate is the same as
the configured one. In my distribution (Arch), /etc/pulse/daemon.conf
has
; default-sample-rate = 44100
which means it's the default. Many audio sources are
Oh, that's interesting. I don't think I've ever seen such a device.
Laurentiu Nicola
On Mon, Jul 14, 2014, at 19:09, Jan Alexander Steffens wrote:
If the device does not support 44.1kHz but only 48kHz (and many cheap
integrated ones don't) then PA will still have to resample.
Hello,
I want to write a small application that reads some data from the
network and makes a few libpulse calls. I have some questions about the
PulseAudio non-threaded main loop.
1. Is there a way to add my fd to the PulseAudio main loop, so I can be
notified of any events? Would calling
Hello,
A while ago I submitted a small patch (subsequently included in PA 5.0)
that allows module-rtp-recv to work in an unicast environment. Perhaps
I'll try to do the same for module-rtp-send when I get some time for it.
Laurentiu Nicola
On Wed, May 28, 2014, at 7:53, Alexander E. Patrakov
Sorry for barging in on this, but is there a way to run a benchmark on
all the resamplers included in PulseAudio? For me, both speex-float-6
and speex-fixed-6 eat around 40% CPU.
Laurentiu Nicola
On Sat, May 10, 2014, at 20:29, Alexander E. Patrakov wrote:
10.05.2014 23:12, Peter Meerwald
Nicola
On Sat, May 10, 2014, at 20:53, Alexander E. Patrakov wrote:
10.05.2014 23:37, Laurențiu Nicola wrote:
Sorry for barging in on this, but is there a way to run a benchmark on
all the resamplers included in PulseAudio? For me, both speex-float-6
and speex-fixed-6 eat around 40% CPU
Hello,
In 88abd6c49ee7fb6aefb08ea36f2cda49955c5eda I made a change to only try
joining a multicast group if the configured sap_address is a multicast
address.
I don't have a freedesktop.org account, but perhaps a kind soul can
update the parameter documentation from
I can confirm that; with module-rtp-recv, I've seen latencies of tens of
seconds.
Laurentiu Nicola
On Tue, Feb 18, 2014, at 13:08, Thomas Martitz wrote:
Am 18.02.2014 10:06, schrieb Tanu Kaskinen:
On Tue, 2014-02-18 at 11:04 +0200, Tanu Kaskinen wrote:
On Tue, 2014-02-18 at 04:51 +0100,
Hello,
Are you using RTP or the native protocol? I'm having this kind of
difficulties with RTP, but in my case it's caused by the WiFi latency
jitter. While the throughput is clearly enough for audio, my network has
latency spikes high enough to -- I assume -- confuse the clock skew
estimation in
Hello,
I'm not sure this is what you expect to get as an answer, but I'm using
PulseAudio on a Raspberry Pi. It mostly works.
Laurentiu
On Sat, Feb 8, 2014, at 10:41, haman...@t-online.de wrote:
Hi,
are you aware of any reasonably priced device that could connect a common
active speaker
Hello,
I, too, am using module-rtp-recv and I encountered some issues with it.
My wireless network has high jitter and this seems to break the rate
estimation algorithm in that module. Specifically, after a while the
audio gets choppy and if I remember correctly, only restarting
PulseAudio
Hello Peter,
RFC 4556 specifies that
The sequence CRLF (0x0d0a) is used to end a record, although parsers SHOULD be
tolerant and also accept records terminated with a single newline character.
PulseAudio is only looking for LF characters, which leads to a few
problems:
1. If the version
24 matches
Mail list logo
