On Mon, 2019-07-29 at 10:24 -0700, Brian Bulkowski wrote:
> Thank you Georg!
>
> About 12 hours ago I figured it out too.
> pa_context_set_sink_input_volume() is the function I was looking for,
> and I was mistakenly using pa_context_set_sink_volume_by_index(), an
> obvious flaw on my part.
>
Thank you Georg!
About 12 hours ago I figured it out too.
pa_context_set_sink_input_volume() is the function I was looking for,
and I was mistakenly using pa_context_set_sink_volume_by_index(), an
obvious flaw on my part.
The other way to get a sink-input id directly from a Stream, you
On 28.07.19 19:44, Brian Bulkowski wrote:
I posted yesterday, twice, about how the "stream get sink id" was
going to solve my problems.
In 10.0 ( the distro version on Debian Stretch on the Raspberry PI ),
the "sink ID" returned from that call is not a valid sink ID and
doesn't do anything
I posted yesterday, twice, about how the "stream get sink id" was going
to solve my problems.
In 10.0 ( the distro version on Debian Stretch on the Raspberry PI ),
the "sink ID" returned from that call is not a valid sink ID and doesn't
do anything good.
I am hoping this call is more
Answering my own question, it seems that a Stream ( from the client API
perspective ) creates a new Sink Input under the covers. Each Stream
ends up with a unique Sink, which combine further down the line.
The ID of that Sink Input can be grabbed with pa_stream_get_index, after
it is up and
Hi!
I'm trying to figure out if I can change a volume on a stream, not a sink.
The app is a fairly long story, and I'm happy to go into it, but it's a
lot of streams playing at the same time, and I want ( programmatic )
control over each and every stream's volume ( in real time ).
I see
