All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Adrian Stancu <adrian.stancu.82@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd-usb-audio syncronisation problem
Date: Fri, 22 Feb 2008 14:09:14 +0100	[thread overview]
Message-ID: <47BEC97A.3030507@ladisch.de> (raw)
In-Reply-To: <43e8c7320802220151p177d2c73y2c9724a4cb4743ef@mail.gmail.com>

Adrian Stancu wrote:
> I'm using an E-MU 0404 USB interface with the snd-usb-audio module
> from alsa 1.0.16, operating in isochronous asynchronous mode. This
> interface was producing very annoying click/pop sounds at regular
> intervals during playback. Eventually I discovered that the
> syncronisation mechanism telling the driver to send audio data faster
> or slower to match the interface's consumption speed does not work as
> expected, for some reason.

The momentary frequency as requested by the device is shown in
/proc/asound/card?/stream? (if CONFIG_SND_VERBOSE_PROCFS is enabled).

Try something like:

while sleep 0.3; do grep "Momentary freq" /proc/asound/card0/stream0; done

In theory, once the device has determined its own speed relative to
the computer, this value should be nearly constant.  (When a stream has
just been started, the requested frequency usually is higher because the
device's buffer is empty.)


Regards,
Clemens

  reply	other threads:[~2008-02-22 13:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  9:51 snd-usb-audio syncronisation problem Adrian Stancu
2008-02-22 13:09 ` Clemens Ladisch [this message]
2008-02-22 13:45   ` Adrian Stancu
2008-02-22 13:57     ` Clemens Ladisch
2008-02-22 14:19       ` Adrian Stancu
2008-02-22 14:43         ` Clemens Ladisch
2008-02-22 14:51           ` Adrian Stancu
2008-02-22 15:05             ` ASoC AT91 : read dma buffer Alexandre BOUIN
2008-02-22 15:50             ` snd-usb-audio syncronisation problem Clemens Ladisch
2008-02-22 16:15               ` Adrian Stancu
2008-02-22 16:31                 ` Clemens Ladisch
2008-02-22 16:46                   ` Adrian Stancu
2008-02-22 16:49                     ` Adrian Stancu
2008-02-22 17:01                     ` Clemens Ladisch
2008-02-22 17:02                       ` Adrian Stancu
2008-02-25 12:44                         ` Clemens Ladisch
2008-02-25 18:32                           ` Adrian Stancu
2008-02-26  7:32                             ` Clemens Ladisch
2008-02-26  7:53                               ` Adrian Stancu
2008-02-26  8:14                                 ` Clemens Ladisch
2008-02-26  8:38                                   ` Adrian Stancu
2008-02-26  8:49                                     ` Clemens Ladisch
2008-02-26  9:20                                       ` Adrian Stancu
2008-02-26 11:36                                         ` Clemens Ladisch
2008-02-26 12:53                                           ` Adrian Stancu
2008-02-26 14:21                                             ` Clemens Ladisch
2008-02-26 15:08                                               ` Adrian Stancu
2008-02-26 13:45                                 ` Pavel Hofman

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=47BEC97A.3030507@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=adrian.stancu.82@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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.