Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: david-b@pacbell.net
Cc: linux-usb-devel@lists.sourceforge.net, colinf@axicon.com,
	clemens@ladisch.de, alsa-devel@lists.sourceforge.net
Subject: Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface
Date: Tue, 28 Jun 2005 00:10:06 -0400	[thread overview]
Message-ID: <1119931807.13519.13.camel@mindpipe> (raw)
In-Reply-To: <20050628033156.9FB22BFF40@blackbox.site>

On Mon, 2005-06-27 at 20:31 -0700, david-b@pacbell.net wrote:
> > From: Lee Revell <rlrevell@joe-job.com>
> > Date: Mon, 27 Jun 2005 22:30:11 -0400
> >
> > On Mon, 2005-06-27 at 19:03 -0700, david-b@pacbell.net wrote:
> > > > With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
> > > > itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
> > > > frames/period and 4 periods/buffer, I get a stream of xruns of about 
> > > > 0.020 ms, several per second.
> > > 
> > > In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
> > > will get unhappy with 256 msec per ISO URB, so I hope you're using
> > > "frame" without a necessary adjective ... ;)
> > > 
> >
> > "frame" = audio frame (4 bytes with S16LE).
> > "USB frame" = 1 msec
> 
> No.  "frame" == ambiguous.  This message is on a USB list, where the
> no-adjective version means "USB frame".  It's also cross-posted to
> a list where the no-adjective version means something very different.
> 
> The only solution that removes ambiguity for _everyone_ is to ensure
> that such words never appear without an adjective.
> 

OK, makes sense.

So what the poster was saying was that if he uses 64 audio frames per
period, which at 44.1KHz requires the audio interface to deliver a chink
of data every ~1.4ms, he gets periodic xruns, IOW the audio interface is
not able to do that.  If he uses 128, he gets no xruns, so he's getting
a chunk of data every 2.8ms, but it's corrupted, hence the crackling.

Lee



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

  reply	other threads:[~2005-06-28  4:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050623024635.5b873305.akpm@osdl.org>
2005-06-23 11:45 ` [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface Clemens Ladisch
2005-06-24  9:35   ` [linux-usb-devel] " Colin Fletcher
2005-06-24 10:28     ` Clemens Ladisch
2005-06-24 13:39       ` [alsa-devel] " Colin Fletcher
2005-06-27 15:05         ` [linux-usb-devel] " Clemens Ladisch
2005-06-27 21:32           ` [alsa-devel] " Colin Fletcher
2005-06-28  2:03             ` david-b
2005-06-28  2:30               ` Lee Revell
2005-06-28  3:31                 ` [linux-usb-devel] " david-b
2005-06-28  4:10                   ` Lee Revell [this message]
2005-06-28 10:19                     ` [alsa-devel] " Colin Fletcher
2005-06-28 13:39               ` Clemens Ladisch
2005-06-28  6:56             ` Clemens Ladisch
2005-06-28 10:23               ` Colin Fletcher
2005-07-06 18:24               ` [linux-usb-devel] " Colin Fletcher
2005-07-07 11:07                 ` Clemens Ladisch
2005-07-08 16:37                   ` UA-1000 MIDI control port (was - Re: [linux-usb-devel] [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface) Colin Fletcher

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=1119931807.13519.13.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=colinf@axicon.com \
    --cc=david-b@pacbell.net \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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