9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] games/snes audio patches
Date: Wed, 17 Feb 2021 10:10:18 +0100	[thread overview]
Message-ID: <CAFSF3XNfuXhyomuNRxwdC6n_OZknPiWiu8J_ORwpRxYUt5gTFg@mail.gmail.com> (raw)
In-Reply-To: <8FC6C05D-B926-418D-AF92-957C3D2D488A@gmail.com>

computational complexity doesn't matter any more for something
low-bitrate like audio.

i don't see why the resampler in pcmconv that's already there
shouldn't be reused. it seems you have a good enough excuse to make it
a library

On 2/17/21, Amavect <amavect@gmail.com> wrote:
> All,
>
> Here's something I dug up.
> http://yehar.com/blog/?p=197
> It has sample code for a ton of filters.
> A great deal of analysis is on 2^n-oversampled audio, which we aren't doing.
> There's a specific recommendation for 4-point Hermite interpolation in this
> case if you want high quality and speed.
>
> Section 7.
> "Also, it shall only be commented that using polynomial interpolators with
> unoversampled input is a choice that can only be made when the quality is
> not that important but speed is essential, the most useful interpolators in
> that case being linear and 4-point Hermite, and Watte tri-linear, which is
> somewhere between those two in both quality and computational complexity."
>
> Thanks,
> Amavect
>

  reply	other threads:[~2021-02-17  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 10:25 Michael Forney
2021-02-15 10:55 ` Steve Simon
2021-02-17  0:05 ` qwx
2021-02-17  5:31   ` Amavect
2021-02-17  9:10     ` hiro [this message]
2021-02-17  9:32       ` Steve Simon
2021-02-17  9:57         ` hiro
2021-02-17 10:24           ` qwx
2021-02-17 10:53     ` hiro
2021-02-21 11:06 ` [9front] " Michael Forney
2021-02-22  0:32   ` qwx
2021-02-22 15:15   ` qwx

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=CAFSF3XNfuXhyomuNRxwdC6n_OZknPiWiu8J_ORwpRxYUt5gTFg@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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).