From: Felix Homann <linuxaudio@showlabor.de>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Need expert's advice - Fast Track Ultra (8R) dropping samples
Date: Sun, 03 Oct 2010 13:50:50 +0200 [thread overview]
Message-ID: <4CA86E1A.30405@showlabor.de> (raw)
In-Reply-To: <4CA60C5B.6010809@ladisch.de>
Dear Clemens, dear Daniel,
thanks for your feedback!
Am 01.10.2010 18:29, schrieb Clemens Ladisch:
>
> Add an else to the inner if in retire_playback_sync_urb, and log the
> value of f.
>
> The value received in this function should be the desired sample
> frequency, relative to the USB frame rate. There are different formats
> (therefore we have three functions); maybe the FTU uses a fourth one.
>
>
Trying to log the value of f reveals that retire_playback_sync_urb()
doesn't seem to be called at all. What does that mean?
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?)
Some time ago I logged (via usbmon) the USB packets switching the device
on in Windows. Could these logs be useful?
Either way, I'll try to connect it to another SPDIF device and look for
differences.
> 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?
Kind regards,
Felix
next prev parent reply other threads:[~2010-10-03 11:50 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 [this message]
2010-10-03 12:00 ` Daniel Mack
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=4CA86E1A.30405@showlabor.de \
--to=linuxaudio@showlabor.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 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.