From: "Zoltán Kővágó" <dirty.ice.hu@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] audio: add -audiodev pa, in|out.latency= to documentation
Date: Tue, 17 Sep 2019 21:47:11 +0200 [thread overview]
Message-ID: <9b2c9131-41d1-aee2-c40d-0f448c83b497@gmail.com> (raw)
In-Reply-To: <20190911145818.18962-3-stefanha@redhat.com>
On 2019-09-11 16:58, Stefan Hajnoczi wrote:
> The "latency" parameter wasn't covered by the documentation.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Zoltán Kővágó <DirtY.iCE.hu@gmail.com>
> ---
> How is this parameter related to buffer-length?
Pulseaudio being a client-server architecture is a bit different than
the other backends, plus it also has to mix multiple streams.
buffer-length corresponds to the buffer inside qemu, while latency
corresponds to pulseaudio. For playback, the latency should be "maximum
latency that the application can deal with", if a different client
request a lower latency, our latency will decrease too. It's up to the
server to figure out an optimal buffer size on the server side of the
things.
For recording it's the size of the buffer we will read at a time from
pulseaudio.
> ---
> qemu-options.hx | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index a4f9f74f52..82154cecf8 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -470,6 +470,7 @@ DEF("audiodev", HAS_ARG, QEMU_OPTION_audiodev,
> "-audiodev pa,id=id[,prop[=value][,...]]\n"
> " server= PulseAudio server address\n"
> " in|out.name= source/sink device name\n"
> + " in|out.latency= desired latency in microseconds\n"
> #endif
> #ifdef CONFIG_AUDIO_SDL
> "-audiodev sdl,id=id[,prop[=value][,...]]\n"
> @@ -630,6 +631,9 @@ Sets the PulseAudio @var{server} to connect to.
> @item in|out.name=@var{sink}
> Use the specified source/sink for recording/playback.
>
> +@item in|out.latency=@var{usecs}
> +Desired latency in microseconds.
> +
> @end table
>
> @item -audiodev sdl,id=@var{id}[,@var{prop}[=@var{value}][,...]]
>
next prev parent reply other threads:[~2019-09-17 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 14:58 [Qemu-devel] [PATCH 0/2] audio: -audiodev documentation tweaks Stefan Hajnoczi
2019-09-11 14:58 ` [Qemu-devel] [PATCH 1/2] audio: fix buffer-length typo in documentation Stefan Hajnoczi
2019-09-17 19:29 ` Zoltán Kővágó
2019-09-18 9:47 ` Stefan Hajnoczi
2019-09-11 14:58 ` [Qemu-devel] [PATCH 2/2] audio: add -audiodev pa, in|out.latency= to documentation Stefan Hajnoczi
2019-09-17 19:47 ` Zoltán Kővágó [this message]
2019-09-18 9:48 ` Stefan Hajnoczi
2019-09-17 15:58 ` [Qemu-devel] [PATCH 0/2] audio: -audiodev documentation tweaks Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b2c9131-41d1-aee2-c40d-0f448c83b497@gmail.com \
--to=dirty.ice.hu@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).