Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] Don't use 16 bit signed integers for sample rate conversion.
Date: Tue, 17 Dec 2019 05:20:02 +0100 (CET)	[thread overview]
Message-ID: <20191217042002.2F70EF80234@alsa1.perex.cz> (raw)
In-Reply-To: <1576556398539288998-webhooks-bot@alsa-project.org>

alsa-project/alsa-plugins issue #5 was edited from crocket:

Sample rate conversion should be done with the highest resolution possible.
Maybe, double, unsigned int, or unsigned int64?
Once sample rate conversion is done, using S32_LE is meaningless.

Does dmix also use 16bits internally?

Issue URL     : https://github.com/alsa-project/alsa-plugins/issues/5
Repository URL: https://github.com/alsa-project/alsa-plugins
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

       reply	other threads:[~2019-12-17  4:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1576556398539288998-webhooks-bot@alsa-project.org>
2019-12-17  4:20 ` GitHub issues - edited [this message]
     [not found] <1576556494063792944-webhooks-bot@alsa-project.org>
2019-12-17  4:21 ` [alsa-devel] Don't use 16 bit signed integers for sample rate conversion GitHub issues - edited
     [not found] <1576452277002017021-webhooks-bot@alsa-project.org>
2019-12-15 23:24 ` GitHub issues - edited
     [not found] <1576452259561000109-webhooks-bot@alsa-project.org>
2019-12-15 23:24 ` GitHub issues - edited
     [not found] <1576451538989263058-webhooks-bot@alsa-project.org>
2019-12-15 23:12 ` GitHub issues - 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=20191217042002.2F70EF80234@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