alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Need expert's advice - Fast Track Ultra (8R) dropping samples
Date: Sun, 3 Oct 2010 14:00:45 +0200	[thread overview]
Message-ID: <20101003120045.GF10432@buzzloop.caiaq.de> (raw)
In-Reply-To: <4CA86E1A.30405@showlabor.de>

On Sun, Oct 03, 2010 at 01:50:50PM +0200, Felix Homann wrote:
> Am 03.10.2010 12:02, schrieb Daniel Mack:
> >How is this device clocked? It could be the PLL can't get a valid link
> >to its clock source and hence "jumps" once in awhile to compensate the
> >drift. Is there any possibility to sync the device to some sort o
> >digital input?
> 
> The device should be clocked internally. But it has an option to be
> clocked externally at least in Windows. I don't know how this is
> handled in Alsa's USB audio driver. (Could you please tell me?)

I assume the device implements UAC in version 1? In this case, clock
switching is not part of the standard and will most probably need
special handling in the driver (vendor specific requests).

For UAC2 though, there is a way to descrbibe avaliable clock sources,
switches etc.

> Some time ago I logged (via usbmon) the USB packets switching the
> device on in Windows. Could these logs be useful?

Switching the clock source you mean? Sure - code to generate these
packets should be placed in handlers for a device-specific mixer
control.

> Either way, I'll try to connect it to another SPDIF device and look
> for differences.

The idea of wrng clocking is just an assumption though. Maybe it is
totally unrelated. It's just that we had similar issues with PLLs going
nuts on missing sync input.

> >If the clicks you hear are very regular, it could also be that some
> >kind of buffer boundary is not handled properly. Do you have access to
> >an USB hardware analyzer to check whether the dropout is in fact part of
> >the USB data stream?
> >
> 
> The clicks are absolutely regular. Unfortunately, I don't have
> access to an USB hardware analyzer. Is there anything else I can do?

Unless you touched critical parts of the PCM data generating code, it is
unlikely that the dropouts are part of the USB data stream. A proper USB
dump is still very helpful, though.

Daniel

  reply	other threads:[~2010-10-03 12:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  9:57 Need expert's advice - Fast Track Ultra (8R) dropping samples Felix Homann
2010-10-01 11:00 ` Felix Homann
2010-10-01 16:29   ` Clemens Ladisch
2010-10-03 11:50     ` Felix Homann
2010-10-03 12:00       ` Daniel Mack [this message]
2010-10-05  7:21       ` Clemens Ladisch
2010-10-06 13:57         ` Felix Homann
2010-10-06 14:38           ` Clemens Ladisch
2010-10-06 16:31             ` Felix Homann
2010-10-07  6:37               ` Clemens Ladisch
2010-10-07  8:10                 ` Daniel Mack
2010-10-07  8:50                   ` Felix Homann
2010-10-07 11:35                   ` Felix Homann
2010-10-08  6:26                     ` Clemens Ladisch
2010-10-12  7:18                       ` Daniel Mack
2010-10-12  8:18                         ` Felix Homann
2010-10-12 10:26                           ` Daniel Mack
2010-10-13  7:47                             ` Felix Homann
2010-10-13 12:48                               ` Daniel Mack
2010-10-15  7:23                             ` Clemens Ladisch
2010-10-15  8:59                               ` Daniel Mack
2010-10-15 11:08                                 ` Felix Homann
2010-10-15 14:21                                 ` Clemens Ladisch
2010-10-03 10:02 ` Daniel Mack

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=20101003120045.GF10432@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linuxaudio@showlabor.de \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).