From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: Capture from 3+ cards connected to a USB hub - distorted samples
Date: Mon, 26 Dec 2011 20:48:44 +0100 [thread overview]
Message-ID: <4EF8CF9C.4040007@ivitera.com> (raw)
In-Reply-To: <4EEE4A58.90709@ivitera.com>
Dne 18.12.2011 21:17, Pavel Hofman napsal(a):
> Dne 14.12.2011 13:30, Jaroslav Kysela napsal(a):
>> Date 14.12.2011 13:19, Pavel Hofman wrote:
>>>
>>> Dne 10.12.2011 00:23, Pavel Hofman napsal(a):
>>>> Hi,
>>>>
>>>> I have been informed about the following problem which I was able to
>>>> reproduce afterwards:
>>>>
>>>> * Latest git.alsa-project.org drivers
>>>>
>>>> * USB 2.0 hub, 3 or more USB soundcards (inexpensive USB sticks, USB
>>>> audio v.1 types, async capture, adaptive playback) hooked to the hub,
>>>> identified A, B, C, D.
>>>>
>>>> * NONE of these soundcards is playing back
>>>>
>>>> Now:
>>>>
>>>> * Card A begins microphone capturing (mono 48/16), result OK
>>>>
>>>> * Card B begins capturing (mono 48/16), both results still OK
>>>>
>>>> * As soon as the third card C begins capturing, the signal captured from
>>>> cards A and B gets distorted. Audacity shows some samples are
>>>> incorrect, distorting the expected sine waveform of the testing signal.
>>>> I can provide screenshots as well as recorded samples, if needed.
>>>>
>>>> * The signal recorded from card C is OK.
>>>>
>>>> BUT
>>>>
>>>> * If any card hooked to the HUB is playing back (even a fourth one D),
>>>> the distortion does not occur. It happens only when there is no playback
>>>> stream going through the hub. Traffic on another USB port has no effect,
>>>> in fact the test signal for the three cards was provided by a
>>>> multichannel USB card hooked to another USB port.
>>>>
>>>> It seems to me as if blocks of samples for each card in the USB frame
>>>> sometimes overlap by a few bits, corrupting the neighbouring card
>>>> samples, or are recovered incorrectly.
>>>>
>>>> I understand I have provided no real data, I am ready to do so plus any
>>>> tests you would consider useful.
>>>>
>>>> Thanks a lot for suggestions of the next debugging steps I should do.
>>>>
>>>
>>> Hi, please may I ask for help? I think we could fix this likely bug.
>>
>> This looks like a USB core issue (lost / unsynced URBs from isochronous
>> transfers). I would try recent linux kernels and/or ask on the USB
>> development list for a help.
>
> Hi Jaroslav,
>
> Thanks a lot for your suggestion. I tested latest stable kernel 3.1.5.
> The behaviour has somewhat improved (3 cards OK), but still IMO
> incorrect (the fourth card D distorts captured streams from C and D). I
> will ask at the usb development list.
>
I checked USB communication with wireshark and the reduced data payload
in URBs for card C and D suggest I am already hitting ceiling of the hub
throughput. I think the hub support is already correct in the latest kernel.
Best regards,
Pavel.
prev parent reply other threads:[~2011-12-26 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 23:23 Capture from 3+ cards connected to a USB hub - distorted samples Pavel Hofman
2011-12-14 12:19 ` Pavel Hofman
2011-12-14 12:30 ` Jaroslav Kysela
2011-12-18 20:17 ` Pavel Hofman
2011-12-26 19:48 ` Pavel Hofman [this message]
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=4EF8CF9C.4040007@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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.