For better readability, "pactl list message-handlers" is introduced which
prints a formatted output of "pactl send-message /core list-handlers".
The patch also adds the function pa_split_message_response() for easy
parsing of the message response string.
---
man/pactl.1.xml.in | 2
---
doc/messaging_api.txt| 16 ++
man/pactl.1.xml.in | 7 ++
man/pulse-cli-syntax.5.xml.in| 7 ++
shell-completion/bash/pulseaudio | 5 +++--
shell-completion/zsh/_pulseaudio | 2 ++
src/pulsecore/cli-command.c | 44 +++
This patch adds a new feature to the core which allows to send messages
to objects. An object can register/unregister a message handler with
pa_message_handler_{register, unregister}() while a message can be sent
to the handler using the pa_message_handler_send_message() function.
A message has 4 a
This patch adds the PA_COMMAND_SEND_OBJECT_MESSAGE command to protocol-native
so that clients can use the messaging feature introduced in the previous patch.
Sending messages can in effect replace the extension system for modules. The
approach is more flexible than the extension interface because
This patch adds a small message handler to the core which enables
clients to list available handlers via the list-handlers message.
Command: pacmd send-message /core list-handlers
pactl can be used with the same parameters.
The patch also introduces a convention for the return string.
It consists
On Fri, 2017-10-27 at 21:39 +0200, Georg Chini wrote:
> On 21.09.2017 14:47, Tanu Kaskinen wrote:
> > When a new card shows up (during pulseaudio startup or hotplugged),
> > pulseaudio needs to pick the initial profile for the card. Unavailable
> > profiles shouldn't be picked, but module-alsa-card
Coverity complained about data->sink being possibly NULL when it's
dereferenced later. It was difficult for me to figure out whether that
was a false positive or not. Hopefully the comments make it a bit
easier to reason about the code in the future.
It might be a good idea to set data->req_format
Hi,
I'm getting a lot of "Unable to convert error string to locale, filtering."
errors in my /var/log/messages. I think PulseAudio is sending them out as
UTF-8.
However, my locale -a output contains UTF-8:
en_US ISO-8859-1
en_US.UTF-8
Is it a locale issue? If so, which locale should I add?
Or