On Wed, Aug 28, 2013 at 7:46 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 28 Aug 2013, Clemens Ladisch wrote:
Sorry, what I said applies more to explicit sync endpoints. When using
implicit sync, a playback URB is submitted for each completed capture
URB, with the number of
At 32 frames/period (reported round-trip latency 1.33ms), it starts up
but there are too many xruns for it to be usable.
James
On Thu, Aug 29, 2013 at 4:00 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 29 Aug 2013, James Stone wrote:
On Wed, Aug 28, 2013 at 7:46 PM, Alan Stern st
On Mon, Aug 26, 2013 at 7:37 PM, Alan Stern st...@rowland.harvard.edu wrote:
Clemens and everyone else:
Not having heard any responses to the patch posted last Wednesday, I
have updated and completed it. The version below is ready for testing.
Please let me know what you find.
It is not
On Sat, Aug 3, 2013 at 11:30 PM, James Stone jamesmst...@gmail.com wrote:
On Aug 3, 2013 9:28 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 2 Aug 2013, James Stone wrote:
OK - here's a trace with all patches applied. It didn't occur when
the
webcam was re-plugged this time
On Thu, Aug 1, 2013 at 5:43 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 1 Aug 2013, James Stone wrote:
SMIs are controlled by the BIOS, not by the kernel. I don't think
changing the kernel would affect their timings.
Hmm.. ok. So do I need to see if there is a bios update
On Fri, Aug 2, 2013 at 8:49 AM, James Stone jamesmst...@gmail.com wrote:
On Thu, Aug 1, 2013 at 5:43 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 1 Aug 2013, James Stone wrote:
SMIs are controlled by the BIOS, not by the kernel. I don't think
changing the kernel would affect
On Fri, Aug 2, 2013 at 8:02 PM, James Stone jamesmst...@gmail.com wrote:
On Fri, Aug 2, 2013 at 8:49 AM, James Stone jamesmst...@gmail.com wrote:
On Thu, Aug 1, 2013 at 5:43 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 1 Aug 2013, James Stone wrote:
SMIs are controlled by the BIOS
On Fri, Aug 2, 2013 at 8:40 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 2 Aug 2013, James Stone wrote:
Okay, so the USB controllers do share IRQ lines. Were you using the
other USB buses when the errors occurred?
Webcam microphone might have been on.
You should try
On Wed, Jul 31, 2013 at 4:48 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 30 Jul 2013, Alan Stern wrote:
I can try to ameliorate the situation. Although the 7-ms delay will
inevitably cause an underrun, it doesn't have to cause errors the way
it does now. I'll write a patch to
On Wed, Jul 31, 2013 at 10:07 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 31 Jul 2013, James Stone wrote:
On Wed, Jul 31, 2013 at 4:48 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Tue, 30 Jul 2013, Alan Stern wrote:
I can try to ameliorate the situation. Although
On Wed, Jul 31, 2013 at 10:07 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 31 Jul 2013, James Stone wrote:
On Wed, Jul 31, 2013 at 4:48 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Tue, 30 Jul 2013, Alan Stern wrote:
I can try to ameliorate the situation. Although
On Mon, Jul 29, 2013 at 9:41 PM, James Stone jamesmst...@gmail.com wrote:
On Mon, Jul 29, 2013 at 4:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 28 Jul 2013, James Stone wrote:
On Sat, Jul 27, 2013 at 6:45 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Sat, 27 Jul 2013
On Sat, Jul 27, 2013 at 6:45 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 27 Jul 2013, James Stone wrote:
OK. So this seems to have solved the starting jack at low latencies
problem, but I am still getting sporadic cannot submit urb (err = -18)
under normal use. Will try to add
On Fri, Jul 26, 2013 at 11:46 PM, James Stone jamesmst...@gmail.com wrote:
On Fri, Jul 26, 2013 at 11:43 PM, James Stone jamesmst...@gmail.com wrote:
On Fri, Jul 26, 2013 at 7:54 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Fri, 26 Jul 2013, Clemens Ladisch wrote:
Alan Stern wrote
On Wed, Jul 24, 2013 at 2:42 AM, James Stone jamesmst...@gmail.com wrote:
On Wed, Jul 24, 2013 at 12:23 AM, James Stone jamesmst...@gmail.com wrote:
On Tue, Jul 23, 2013 at 11:50 PM, Torstein Hegge he...@resisty.net wrote:
On Tue, Jul 23, 2013 at 21:13:23 +0100, James Stone wrote:
On Fri, Jul
On Thu, Jul 25, 2013 at 2:12 PM, Clemens Ladisch clem...@ladisch.de wrote:
James Stone wrote:
Ok -from the bisect, the problem of not being able to get to sub
64-frames per period starts with:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id
On Thu, Jul 25, 2013 at 4:29 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 25 Jul 2013, James Stone wrote:
On Thu, Jul 25, 2013 at 2:12 PM, Clemens Ladisch clem...@ladisch.de wrote:
James Stone wrote:
Ok -from the bisect, the problem of not being able to get to sub
64-frames per
On Thu, Jul 25, 2013 at 7:26 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 25 Jul 2013, James Stone wrote:
Please try the patch from here:
http://marc.info/?l=linux-usbm=137476385206265w=2
instead of the one I sent to you yesterday. I think it will fix this
problem
On Thu, Jul 25, 2013 at 10:24 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 25 Jul 2013, James Stone wrote:
On Thu, Jul 25, 2013 at 7:26 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Thu, 25 Jul 2013, James Stone wrote:
Please try the patch from here:
http
On Fri, Jul 19, 2013 at 4:17 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 19 Jul 2013, James Stone wrote:
The questions now are:
Why are the same requests sent over and over again?
Why does the ALSA driver attempt to set the clock frequency
while
On Tue, Jul 23, 2013 at 11:50 PM, Torstein Hegge he...@resisty.net wrote:
On Tue, Jul 23, 2013 at 21:13:23 +0100, James Stone wrote:
On Fri, Jul 19, 2013 at 4:17 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Fri, 19 Jul 2013, James Stone wrote:
The questions now
On Wed, Jul 24, 2013 at 12:23 AM, James Stone jamesmst...@gmail.com wrote:
On Tue, Jul 23, 2013 at 11:50 PM, Torstein Hegge he...@resisty.net wrote:
On Tue, Jul 23, 2013 at 21:13:23 +0100, James Stone wrote:
On Fri, Jul 19, 2013 at 4:17 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Fri
On Wed, Jul 17, 2013 at 7:48 PM, Alan Stern st...@rowland.harvard.edu wrote:
The 32-frames/period trace looks just like the 64 frames/period, only
worse. Each URB has only 4 packets, and the underrun problem is
severe. This won't happen after the minimum pipeline length is fixed.
The
On Wed, Jul 17, 2013 at 3:59 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Jul 2013, James Stone wrote:
Thanks. The patch allows jack to now start at (playback only) 64
frames/period. It doesn't work with 32 frames/period though (I think
you predicted this). This is still
On Tue, Jul 16, 2013 at 7:36 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 15 Jul 2013, James Stone wrote:
James, did you ever provide a usbmon trace for 3.8 doing playback only
and using 64 frames/period? I don't recall seeing any. It might help.
OK - will send it to you
On Mon, Jul 15, 2013 at 9:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 15 Jul 2013, Clemens Ladisch wrote:
The interrupts shouldn't differ by more than the duration of one URB,
which would be 1 ms. There is an initial delay when a stream is first
started, which generally
Hi Clemens,
On Mon, Jul 8, 2013 at 2:12 PM, James Stone jamesmst...@gmail.com wrote:
Snip!
Acquire audio card Audio0
creating alsa driver ... hw:USB,0|-|64|2|44100|0|0|nomon|swmeter|-|16bit
Using ALSA driver USB-Audio running on card 0 - Focusrite Scarlett 2i4
USB at usb-:00:12.2-3, high
On Sat, Jul 6, 2013 at 9:39 PM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 9:36 PM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 3:41 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 6 Jul 2013, James Stone wrote:
The output when I try to start
On Sat, Jul 6, 2013 at 9:57 AM, Clemens Ladisch clem...@ladisch.de wrote:
Alan Stern wrote:
The first half is audio-out only. About 2 seconds after the start, the
audio-in stream starts up. After 2 URBs (2 ms) of data, everything
is shut down for no apparent reason -- there were no I/O
On Sat, Jul 6, 2013 at 10:36 AM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 9:57 AM, Clemens Ladisch clem...@ladisch.de wrote:
Alan Stern wrote:
The first half is audio-out only. About 2 seconds after the start, the
audio-in stream starts up. After 2 URBs (2 ms) of data
On Sat, Jul 6, 2013 at 3:41 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 6 Jul 2013, James Stone wrote:
The output when I try to start jack with 128 frames/period is:
/usr/bin/jackd -dalsa -r44100 -p128 -n2 -D -Chw:USB,0 -Phw:USB,0 -I512 -O512
-S
jackdmp 1.9.9.5
Copyright 2001
On Sat, Jul 6, 2013 at 9:36 PM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 3:41 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 6 Jul 2013, James Stone wrote:
The output when I try to start jack with 128 frames/period is:
/usr/bin/jackd -dalsa -r44100 -p128 -n2
On Fri, Jul 5, 2013 at 3:31 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 4 Jul 2013, James Stone wrote:
Can you post the part of the trace showing where the audio-in Zi lines
first appear?
I think this is the start of the Zi lines:
8800b3585f00 3572683229 C Ci:1:004:0 0
On Thu, Jul 4, 2013 at 4:19 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 4 Jul 2013, James Stone wrote:
Apologies - I realised I hadn't also applied the 1ms usb patch. With that
applied, it will start OK at 256, but not at 128 frames/period. (on earlier
kernels it can start
On Thu, Jul 4, 2013 at 9:12 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 4 Jul 2013, James Stone wrote:
Another hint: The important lines are the ones containing Zi:1:002:2
-- the actual string may be slightly different, but it will definitely
contain Zi and it will match the E
On Thu, Jul 4, 2013 at 10:13 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 4 Jul 2013, James Stone wrote:
OK.. How is this:
-71:63:0 -71:126:0 -71:189:0 -71:252:0 504 =
To all appearances, this shows what
36 matches
Mail list logo
