From: Takashi Iwai <tiwai@suse.de>
To: Thomas Ebeling <penguins@bollie.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Clock sync problem?
Date: Mon, 08 Jun 2020 15:35:44 +0200 [thread overview]
Message-ID: <s5htuzl4r4f.wl-tiwai@suse.de> (raw)
In-Reply-To: <14f91307-c121-a9f8-4045-1319ee0ca49e@bollie.de>
On Mon, 08 Jun 2020 10:32:24 +0200,
Thomas Ebeling wrote:
>
>
> On 08.06.20 09:19, Takashi Iwai wrote:
> > On Sun, 07 Jun 2020 15:39:59 +0200,
> > Laurence Tratt wrote:
> >> Hello,
> >>
> >> I've found an interesting issue with an SSL2+ audio interface -- it plays and
> >> records fine (and, for the money, the sound quality is excellent!), but
> >> recording slowly but surely drifts over time. For example, if I record a
> >> click track in Audacity (or Ardour), play it through the interface and record
> >> it, and then line up the start of the recorded click track with the original,
> >> the two tracks will be around 5ms out of alignment after 30s. Interestingly,
> >> this problem does not happen with OpenBSD, where the two tracks line up
> >> precisely.
> >>
> > The recent change in USB-audio might help for a case like yours.
> > Try my sound git tree (for-linus branch) or Linus' tree. The former
> > should be pullable onto 5.7 kernel cleanly.
>
> Since I recently had clock drift issues with Audient devices, I'm
> intrigued by this. @Takashi Can you quickly elaborate, what you think,
> Laurance's issue might be and what has changed in that tree that might
> help him fix it? Is there some general issue with the current (stable)
> sound/usb implementation?
The frame size calculation in USB-audio driver wasn't accurate enough
because of the computation in Q16.16 format. It works OK for async
mode, but for others, it can accumulate rounding errors. The recent
change corrected it for a more precise way.
Takashi
next prev parent reply other threads:[~2020-06-08 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 13:39 Clock sync problem? Laurence Tratt
2020-06-08 7:19 ` Takashi Iwai
2020-06-08 8:32 ` Thomas Ebeling
2020-06-08 13:35 ` Takashi Iwai [this message]
2020-06-08 14:43 ` Alexander Tsoy
2020-06-10 7:44 ` Laurence Tratt
2020-06-10 13:49 ` Alexander Tsoy
2020-06-10 16:29 ` Laurence Tratt
2020-06-11 12:30 ` Takashi Iwai
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=s5htuzl4r4f.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=penguins@bollie.de \
/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