From: Daniel Mack <zonque@gmail.com>
To: Alan Horstmann <gineera@aspect135.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: USB audio devices on Audio 4DJ and similar
Date: Sun, 08 Apr 2012 16:12:13 +0200 [thread overview]
Message-ID: <4F819CBD.2010809@gmail.com> (raw)
In-Reply-To: <201204062209.21564.gineera@aspect135.co.uk>
Hi Alan,
On 06.04.2012 23:09, Alan Horstmann wrote:
> At present I am involved with resolving some issues that have arisen from
> people using the Audio 4DJ interface with Portaudio, and I hoped it would be
> OK to check a few Alsa details with you? Unfortunately I have limited
> experience of USB audio.
What are those issues? Can you elaborate?
> Apparently the 4 audio inputs/outputs appear as 2 stereo sub-devices on the
> first device, rather than a single 4-channel device - is this correct?
Yes.
> Assuming that is correct, does that arise as a result of the intrinsic nature
> of the interface, or is it by developer choice in the driver (for example so
> that it can be opened as 2 stereo streams)? Is there (or could there be) a
> way to change this, eg by module option or udev rule? I notice in the source
> #define CHANNELS_PER_STREAM 2
The device itself implements 4 audio channels which are synced to each
other. In other words: the hardware is not able to only enable one of
them and leave the other ones paused or set sample rates individually.
When I implemented the driver, it seem most logical to follow the way
the device denotes it channels though. The documentation and silk screen
presents them as pairs of stereo, and so the driver does the same thing.
> Is there a way at present that the device can be accessed as a single
> 4-channel stream other than by creating a custom ~asoundrc with a pcm
> definition using 'multi' to join the 2 stereo streams?
No, you would need to join them in software. But as all inputs and
outputs share a single clock domain, there won't be any drift between
them that need special attention.
> I don't see any USB audio units having files in /usr/share/alsa/cards; is it
> not relevant, not normally necessary or something no-one has got round to
> writing?
For this particular device, there wasn't any need yet.
Daniel
next prev parent reply other threads:[~2012-04-08 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 21:09 USB audio devices on Audio 4DJ and similar Alan Horstmann
2012-04-08 14:12 ` Daniel Mack [this message]
2012-04-11 10:59 ` Alan Horstmann
2012-04-11 15:17 ` Daniel Mack
2012-04-11 15:20 ` Daniel Mack
2012-04-11 17:00 ` Alan Horstmann
2012-04-11 17:10 ` Daniel Mack
2012-04-12 7:34 ` Takashi Iwai
2012-04-16 20:55 ` When to use sub-devices? (was Re: USB audio devices on Audio 4DJ and similar) Mark Hills
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=4F819CBD.2010809@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=gineera@aspect135.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).