From: GitHub pull_request - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Add support for getting list of supported codecs
Date: Wed, 2 Nov 2022 09:28:51 +0100 (CET) [thread overview]
Message-ID: <20221102082851.7FDF1F8026D@alsa1.perex.cz> (raw)
In-Reply-To: <1667377723910022020-webhooks-bot@alsa-project.org>
alsa-project/tinycompress pull request #16 was edited from SanchayanMaity:
Right now, there is no way to expose a list of codecs from `tinycompress`. While one could theoretically call `is_codec_supported` multiple times in an application to check against a list of codecs, an API would make it easy to enumerate supported codecs. The IOCTL `SNDRV_COMPRESS_GET_CAPS` after all already exists.
Our use case is Pipewire where we would like the compressed sink node to advertise only codecs supported by the underlying hardware. So far we were just advertising the complete list of codecs and let node linking fail at runtime based on result from `is_codec_supported`.
Pipewire MR: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1431
Request URL : https://github.com/alsa-project/tinycompress/pull/16
Patch URL : https://github.com/alsa-project/tinycompress/pull/16.patch
Repository URL: https://github.com/alsa-project/tinycompress
next parent reply other threads:[~2022-11-02 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1667377723910022020-webhooks-bot@alsa-project.org>
2022-11-02 8:28 ` GitHub pull_request - edited [this message]
[not found] <1664975493385212898-webhooks-bot@alsa-project.org>
2022-10-05 13:11 ` Add support for getting list of supported codecs GitHub pull_request - edited
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=20221102082851.7FDF1F8026D@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.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).