From: Eric Blake <eblake@redhat.com>
To: Geoffrey McRae <geoff@hostfission.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v8] audio/jack: add JACK client audiodev
Date: Mon, 11 May 2020 15:31:52 -0500 [thread overview]
Message-ID: <7250e8e8-842e-61cf-9bed-b6263ee92e4e@redhat.com> (raw)
In-Reply-To: <20200511042538.60E863A0386@moya.office.hostfission.com>
On 4/29/20 12:53 AM, Geoffrey McRae wrote:
> This commit adds a new audiodev backend to allow QEMU to use JACK as
> both an audio sink and source.
>
> Signed-off-by: Geoffrey McRae <geoff@hostfission.com>
> ---
> +++ b/qapi/audio.json
> @@ -152,6 +152,55 @@
> '*out': 'AudiodevPerDirectionOptions',
> '*latency': 'uint32' } }
>
> +##
> +# @AudiodevJackPerDirectionOptions:
> +#
> +# Options of the JACK backend that are used for both playback and
> +# recording.
> +#
> +# @server-name: select from among several possible concurrent server instances
> +# (default: environment variable $JACK_DEFAULT_SERVER if set, else "default")
> +#
> +# @client-name: the client name to use. The server will modify this name to
> +# create a unique variant, if needed unless @exact_name is true (default: the
Minor typos: @exact_name does not match...
> +# guest's name)
> +#
> +# @connect-ports: if set, a regular expression of JACK client port name(s) to
> +# monitor for and automatically connect to
> +#
> +# @start-server: start a jack server process if one is not lready present
already
> +# (default: false)
> +#
> +# @exact-name: use the exact name requested otherwise JACK automatically
> +# generates a unique one, if needed (default: false)
...the actual parameter @exact-name.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2020-05-11 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 5:53 [PATCH v8] audio/jack: add JACK client audiodev Geoffrey McRae
2020-05-11 14:53 ` Stefan Hajnoczi
2020-05-11 14:58 ` Geoffrey McRae
2020-05-11 20:31 ` Eric Blake [this message]
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=7250e8e8-842e-61cf-9bed-b6263ee92e4e@redhat.com \
--to=eblake@redhat.com \
--cc=geoff@hostfission.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).