Re: [pulseaudio-discuss] Edinburgh Murphy meeting notes

On 11/07/2013 10:20 AM, Tanu Kaskinen wrote: > On Thu, 2013-11-07 at 08:55 +0100, David Henningsson wrote: >> On 11/06/2013 06:21 PM, Tanu Kaskinen wrote: >>> On Wed, 2013-11-06 at 15:31 +0100, David Henningsson wrote: On 11/06/2013 02:04 PM, Tanu Kaskinen wrote: > On Thu, 2013-10-31 at 14

[pulseaudio-discuss] [PATCH 5/9] source: Initialize pa_source.monitor_of already in pa_source_new()

The knowledge about whether the source is going to be a monitor source is necessary already in pa_source_new(), because the monitor source node will be created based on that information. --- src/pulsecore/sink.c | 3 +-- src/pulsecore/source.c | 8 +++- src/pulsecore/source.h | 2 ++ 3 files

[pulseaudio-discuss] [PATCH 8/9] node: Generate a nice name for monitor nodes

Just take the name of the node that this node is a monitor of, and append ".monitor". --- src/pulsecore/node.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/src/pulsecore/node.c b/src/pulsecore/node.c index 8749295..7b4d61f 100644 --- a/src/pulsecore/node.c +++ b/sr

[pulseaudio-discuss] [PATCH 0/9] Create more nodes

I planned to start implementing node-based routing for sink inputs, but I realized that that would cause regressions if nodes don't exist for all sinks and sink inputs. After this patch series we should have "full coverage" in terms of node support in backends. Tanu Kaskinen (9): Create nodes fo

[pulseaudio-discuss] [PATCH 6/9] sink: Create the sink node before creating the monitor source

The sink node object will be used during the monitor source creation to figure out whether the monitor source should create a node for itself. --- src/pulsecore/sink.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/pulsecore/sink.c b/src/pulsecor

[pulseaudio-discuss] [PATCH 7/9] Create nodes for monitor sources

The node is created only if the sink has a node. If the sink has ports, then a separate monitor node should be created for each of the sink ports (will be implemented later). --- src/pulsecore/node.c | 6 ++ src/pulsecore/node.h | 2 ++ src/pulsecore/source.c | 5 + 3 files changed, 13

[pulseaudio-discuss] [PATCH 3/9] Create nodes for sinks

All sinks that don't have ports should have nodes, because otherwise routing streams to those sinks won't work when sink input routing is changed to be node-based. --- src/modules/echo-cancel/module-echo-cancel.c | 3 +++ src/modules/macosx/module-coreaudio-device.c | 3 +++ src/modules/module-com

[pulseaudio-discuss] [PATCH 2/9] Create nodes for source outputs

All user-routable source outputs should have a node, so that those entities stay user-routable also after source output routing has been converted to be node-based. --- src/modules/echo-cancel/module-echo-cancel.c | 3 +++ src/modules/module-loopback.c| 4 src/modules/module-r

[pulseaudio-discuss] [PATCH 4/9] Create nodes for sources

All sources that don't have ports should have nodes, because otherwise routing streams to those sources won't work when source output routing is changed to be node-based. Support for monitor sources is not yet added in this commit, because that's a bit less straightforward thing to implement. ---

[pulseaudio-discuss] [PATCH 9/9] device-port: Generate monitor nodes for output ports

Having a single monitor node for the monitor source that is associated with multiple output ports doesn't really make sense, so I'm generating separate nodes for each output port. --- src/pulsecore/device-port.c | 31 +++ src/pulsecore/device-port.h | 1 + src/pulsecor

[pulseaudio-discuss] [PATCH 1/9] Create nodes for sink inputs

All user-routable sink inputs (i.e. those that don't set PA_SINK_INPUT_DONT_MOVE) should have a node, so that those entities stay user-routable also after sink input routing has been converted to be node-based. --- src/modules/echo-cancel/module-echo-cancel.c | 3 +++ src/modules/module-equalizer-

Re: [pulseaudio-discuss] make pulseaudio-aggregate-configure error for Android 4.2.2_r1.2

Arun Raghavan collabora.co.uk> writes: > That should pretty much be it. This tree has none of the AudioFlinger > emulation bits, but should at least get you a functional PA build (with > audio, if you're running a Galaxy Nexus (tuna)). > It works. Thanks. Now we realize we need the audioflinge

Re: [pulseaudio-discuss] Is it possible to connect to an existing stream using pulse audio?

On Thu, 7 Nov 2013 11:48:19 +0530, sathishkumar sivagurunathan wrote: > Hello, > > My aim is as follows. > > 1) I have a audio player like Vlc running. I have checked with PAMAN > command that VLC as a client and a stream with stream name is created. > > My intention is to connect to this pret

Re: [pulseaudio-discuss] Is it possible to connect to an existing stream using pulse audio?

Thanks David, Sorry if I had framed my question in the wrong sense. I had tried to explain what I am trying to do in an elaborate way. 1) I am currently working on an Audio Manager project. 2) There are two applications ( for example:- VLC player and TOTEM media player) t

Re: [pulseaudio-discuss] Edinburgh Murphy meeting notes

On Thu, 2013-11-07 at 08:55 +0100, David Henningsson wrote: > On 11/06/2013 06:21 PM, Tanu Kaskinen wrote: > > On Wed, 2013-11-06 at 15:31 +0100, David Henningsson wrote: > >> On 11/06/2013 02:04 PM, Tanu Kaskinen wrote: > >>> On Thu, 2013-10-31 at 14:28 +0100, David Henningsson wrote: > On 10

Re: [pulseaudio-discuss] Is it possible to connect to an existing stream using pulse audio?

On 11/07/2013 07:18 AM, sathishkumar sivagurunathan wrote: > Hello, > > My aim is as follows. > > 1) I have a audio player like Vlc running. I have checked with PAMAN > command that VLC as a client and a stream with stream name is created. > > My intention is to connect to this pretty existing