alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Felix Homann <linuxaudio@showlabor.de>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, Clemens Ladisch <clemens@ladisch.de>
Subject: Need expert's advice - Fast Track Ultra (8R) dropping samples
Date: Sat, 25 Sep 2010 11:57:53 +0200	[thread overview]
Message-ID: <4C9DC7A1.8050001@showlabor.de> (raw)

Hi,

in that past months I've been trying get the Fast Track Ultra devices 
working properly in Alsa. We've had lots of progress, most of the code 
has moved to Alsa git and today I've even posted a patch for getting 
mixer support for these devices.

Now, I need to get some expert's advice: The devices seem to drop 
samples or frames. Here's a report I've got today on the M-Audio forum:

"I've got a subtle problem to report: I think audio playback is dropping
sample frames. To hear the problem, open Audacity at 48 kHz and play
a 10-kHz. sine wave. When I do that I hear a regular clicking sound, about
four clicks a second. I've tried recording the output and if I'm seeing 
correctly,
exactly one sample frame in every 13312 (13x1024) is being dropped on 
output.
I don't see anything similar on input. When either jack or Pd has both 
the input and
the output open, the delay from input to output gradually decreases 
until it forces
occasional sync errors. (I haven't tried this with audacity though.)"

(see 
http://forums.m-audio.com/showthread.php?714-Not-a-problem.-FastTrack-on-linux&p=98101#post98101)

I could reproduce it on my machines, even at 44.1 kHz. The clicking 
sound is very subtle, it goes unnoticed when not listening to pure sines 
without attention to clicks.

How can this be sorted out. Any ideas?

Kind regards,

Felix

             reply	other threads:[~2010-09-25  9:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  9:57 Felix Homann [this message]
2010-10-01 11:00 ` Need expert's advice - Fast Track Ultra (8R) dropping samples Felix Homann
2010-10-01 16:29   ` Clemens Ladisch
2010-10-03 11:50     ` Felix Homann
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=4C9DC7A1.8050001@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 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).