Hi,
two questions:
1) I connected my phone to the target using a2dp profile. Every time a
sound is emitted I need to restart pulseaudio because the bluez source
is deleted. Which parameter in the configuration files handle this behavior?
2) in order to provide the headset profile I added "hea
Il 09/05/2016 17:06, Alexander E. Patrakov ha scritto:
I suggest that you run pulseaudio as the same user that other software
runs as (i.e. not in system mode). This will allow using shm safely.
Now I'm starting with pulseaudio --start.
It works, but after stopping the execution of a song. The
09.05.2016 18:42, Marco Trapanese пишет:
Il 09/05/2016 15:38, Marco Trapanese ha scritto:
Removing that flag I now see the bluez source with pactl list sources.
But when I start playing a song from the smartphone something weird
happens:
I add that pactl modules shows:
Module #14
Name:
Il 09/05/2016 15:38, Marco Trapanese ha scritto:
Removing that flag I now see the bluez source with pactl list sources.
But when I start playing a song from the smartphone something weird
happens:
I add that pactl modules shows:
Module #14
Name: module-bluez5-device
Argument: path=/
Il 09/05/2016 15:13, Alexander E. Patrakov ha scritto:
The problem is likely --disallow-module-loading, because
module-loopback is, well, a module. You can remove this argument if
you have no users except root on your system.
Thanks! One step forward!
Removing that flag I now see the bluez s
09.05.2016 17:21, Marco Trapanese wrote:
I'm running pulseaudio8 and bluez5 in a buildroot environment (RPi3).
When I connect the smartphone I can successfully pair and authorize
UUIDs for Advanced Audio Distribution and for A/V Remote Control.
It doesn't ask for Audio Source.
In fact pactl list
I'm running pulseaudio8 and bluez5 in a buildroot environment (RPi3).
When I connect the smartphone I can successfully pair and authorize
UUIDs for Advanced Audio Distribution and for A/V Remote Control.
It doesn't ask for Audio Source.
In fact pactl list sources doesn't show the bluetooth sour
On Mon, 9 May 2016, at 03:40 PM, Arun Raghavan wrote:
> Following up from the bug about this [0], we have a couple of patches to
> deal with multiple PulseAudio instances mixing with ALSA mixer controls
> when a jack event occurs.
That would be: https://bugs.freedesktop.org/show_bug.cgi?id=93259
This is needed so we don't keep stale jack availability information
while the card is suspended.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=93259
Signed-off-by: Arun Raghavan
---
src/modules/alsa/module-alsa-card.c | 36
src/pulsecore/card.c
From: Tanu Kaskinen
See the big comment in the code for more details.
BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=93259
Signed-off-by: Arun Raghavan
---
src/modules/alsa/module-alsa-card.c | 28
src/pulsecore/card.c| 5 +
src/pulsecor
Following up from the bug about this [0], we have a couple of patches to
deal with multiple PulseAudio instances mixing with ALSA mixer controls
when a jack event occurs.
The first is a patch from Tanu to keep track of a card's suspend state
and ignore jack events while a card is suspended.
The s
The current code is built with the assumption that the timestamp field
in one RTP header will be greater than the one from the preceding packet,
which is true when recieving from another PA instance, but not in the
general case.
According to RFC 3550 section 5.1: Several consecutive RTP packets wi
Although it should not trigger too often (cc is almost always 0) the
length calculation is obviously wrong here.
Signed-off-by: Cédric Schieli
---
src/modules/rtp/rtp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/modules/rtp/rtp.c b/src/modules/rtp/rtp.c
index 17c8d3c
According to RFC 4566 section 5: 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.
Right now, only LF-separated records are understood, so it's clearly a
bug. This has already been spotted her
This patch series aims at fixing a few interoperability issues found in
the rtp-recv module while attempting to stream from a third party
application (e.g. VLC).
The typical VLC command line would be something like the following:
vlc --sout-keep --sout '#transcode{acodec=s16b}:rtp{sap,dst=224.0.0.
Great, thanks a lot Arun!
G.
On sam., 2016-05-07 at 13:46 +0530, Arun Raghavan wrote:
> Hey Guillaume,
>
> On 18 March 2016 at 19:58, Guillaume Desmottes
> wrote:
> > For various use-cases a passthrough stream should have priority
> > over all
> > other streams and get exclusive access
16 matches
Mail list logo
