From: Daniel Mack <zonque@gmail.com>
To: Daniel Griscom <griscom@suitable.com>
Cc: Eldad Zack <eldad@fogrefinery.com>,
Alsa Developer <alsa-devel@alsa-project.org>
Subject: Re: USB hardware that supports implicit feedback?
Date: Sun, 18 Nov 2012 18:10:29 +0800 [thread overview]
Message-ID: <50A8B415.5010008@gmail.com> (raw)
In-Reply-To: <p06240807cccb56d116e2@[192.168.1.12]>
On 16.11.2012 10:39, Daniel Griscom wrote:
> At 7:22 AM +0800 11/16/12, Daniel Mack wrote:
>> Hi Daniel,
>> Hi Elad,
>>
>> On 16.11.2012 05:32, Daniel Griscom wrote:
>>> At 10:02 PM +0100 11/15/12, Eldad Zack wrote:
>>>> Hi Daniel,
>>>>
>>>> On Thu, 15 Nov 2012, Daniel Griscom wrote:
>>>>> I'm having trouble getting implicit feedback working with my custom
>>>>> capture/playback USB audio class device, even with the latest kernel. I
>>>>> presume it's a problem with my device's configuration, but
>>>>> can't figure out
>>>>> exactly what the problem is (after a whole lotta investigation).
>>>>
>>>> What exactly doesn't work?
>>>
>>> The audio output stream (from the computer to my device) runs at a
>>> few frames per second higher or lower rate than that of the input
>>> stream (from my device to the computer). The actual difference seems
>>> to be stable on a specific machine, but varies greatly between
>>> machines (I've seen differences from +7fps to -2fps; I presume this
>>> is due to differences in CPU clock frequencies).
>>
>> So you're saying that this is what you experience after you added code
>> to make the driver use the implicit feedback mechanism? Over which time
>> did you measure this and how exactly? Because frankly, I doubt that -
>> the data rate is purely derived from the number of incoming samples.
>
> This has been the case for a while; we started work with ALSA 1.0.23,
> but upgrading to kernel 3.6.6 (with included ALSA code) didn't change
> anything. We have yet to do any patching of ALSA for this matter.
Well, afaik, ALSA 1.0.23 is what ships with a kernel <= 3.4, and the
code for implicit feedback went in for 3.5.
>> Does your device demand the same number of *bytes* or samples/channel to
>> be sent?
>
> I'll have to check that.
Let me rephrase the question: does the number of input and output
channels match? Eldad had a patch in his series that should make it work
for both scenarios.
>> The code I wrote for implicit feedback is used by the M-Audio FTU
>> devices,
>
> So, with an FTU the implicit feedback code works?
Yes, it does for many others.
> What version of
> kernel/ALSA should I use - the latest?
Yes, always use the latests from git, especially for such relatively new
features.
Daniel
next prev parent reply other threads:[~2012-11-18 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 20:11 USB hardware that supports implicit feedback? Daniel Griscom
2012-11-15 21:02 ` Eldad Zack
2012-11-15 21:32 ` Daniel Griscom
2012-11-15 23:22 ` Daniel Mack
2012-11-16 2:08 ` Eldad Zack
2012-11-16 2:39 ` Daniel Griscom
2012-11-18 10:10 ` Daniel Mack [this message]
2012-11-16 2:10 ` Eldad Zack
2012-11-16 2:41 ` Daniel Griscom
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=50A8B415.5010008@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=eldad@fogrefinery.com \
--cc=griscom@suitable.com \
/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