From: Colin Fletcher <colinf@axicon.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: linux-usb-devel@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net, david-b@pacbell.net
Subject: Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface
Date: Mon, 27 Jun 2005 22:32:34 +0100 [thread overview]
Message-ID: <42C07072.1050105@axicon.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0506271650140.7308-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> I'd like to know if playback and/or MIDI work. It may be possible
> that the driver doesn't send playback PCM data at exactly the correct
> rate because the playback stream should have been synchronized to the
> capture stream.
I don't have any MIDI hardware to hand at the moment: I can try to dig
out my old Roland drum machine next week if that will help.
Meanwhile, I've tried playback (with jack 0.100.1, ardour, &
realtime_lsm loaded).
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.
Using the same kernel and jackd settings, but with the sound/ and
include/sound directories from ALSA CVS of about 7:30 this evening, it
seems to work fine, at least for a couple of minutes of stereo playback.
At 128 frames/period, both kernels have a crackling background noise: I
haven't experimented with any other settings yet.
I hope this is useful: I'm afraid I'm not going to have time to try much
more until next week now.
Colin Fletcher
--
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-06-27 21:32 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 ` Colin Fletcher [this message]
2005-06-28 2:03 ` [alsa-devel] " david-b
2005-06-28 2:30 ` Lee Revell
2005-06-28 3:31 ` [linux-usb-devel] " david-b
2005-06-28 4:10 ` [alsa-devel] " Lee Revell
2005-06-28 10:19 ` 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=42C07072.1050105@axicon.com \
--to=colinf@axicon.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--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