All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
	Arthur Marsh <arthur.marsh@internode.on.net>
Subject: Re: [PATCH] Revert "ALSA: emu10k1: fix synthesizer sample playback position and caching"
Date: Mon, 01 Apr 2024 19:02:42 +0200	[thread overview]
Message-ID: <87edbpt3rh.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240401145805.528794-1-oswald.buddenhagen@gmx.de>

On Mon, 01 Apr 2024 16:58:05 +0200,
Oswald Buddenhagen wrote:
> 
> As already anticipated in the original commit, playback was broken for
> very short samples. I just didn't expect it to be an actual problem,
> because we're talking about less than 1.5 milliseconds here. But clearly
> such wavetable samples do actually exist.
> 
> The problem was that for such short samples we'd set the current
> position beyond the end of the loop, so we'd run off the end of the
> sample and play garbage.
> This is a bigger (more audible) problem than the original one, which was
> that we'd start playback with garbage (whatever was still in the cache),
> which would be mostly masked by the note's attack phase.
> 
> So revert to the old behavior for now. We'll subsequently fix it
> properly with a bigger patch series.
> Note that this isn't a full revert - the dead code is not re-introduced,
> because that would be silly.
> 
> Fixes: df335e9a8b (ALSA: emu10k1: fix synthesizer sample playback position and caching, 2023-05-18)
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=218625
> Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>

Thanks, applied now.


Takashi

      reply	other threads:[~2024-04-01 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 14:58 [PATCH] Revert "ALSA: emu10k1: fix synthesizer sample playback position and caching" Oswald Buddenhagen
2024-04-01 17:02 ` Takashi Iwai [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=87edbpt3rh.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=arthur.marsh@internode.on.net \
    --cc=oswald.buddenhagen@gmx.de \
    --cc=perex@perex.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.