From: Ludwig Schwardt <schwardt@sun.ac.za>
To: alsa-devel@lists.sourceforge.net
Subject: Multiple Delta 1010LT woes
Date: Fri, 20 Feb 2004 17:51:10 +0200 [thread overview]
Message-ID: <40362CEE.8060907@sun.ac.za> (raw)
Hi,
I'm playing around with the M-Audio (MidiMan) Delta 1010LT card. My plan
is to install three of them, synced via word clock, and record the
resulting 24 analog channels via JACK. I understand this requires some
.asoundrc magic.
Questions:
- Why does the card show up with 12 inputs under JACK? As far as I could
tell, the card has 8 analog ins and 2 spdif ins. Where are the extra two
inputs? Shouldn't the card then be a Delta 1210LT? :->
- I've got the "plug" plugin in .asoundrc to select the first eight
channels, but this has latency issues. Is "multi" the right way to go?
- Repeated attempts to create a working multi plugin have failed, based
on all the usual multicard snippets floating around on the Web. I have
only one Delta at the moment, so I've tried it alone and together with
the dummy soundcard (i.e. one slave or two in the plugin definition). Is
it OK to have only one card in multi?
In JACK I get the error:
ALSA: no playback configurations available (Invalid argument)
And with aplay and arecord I get:
arecord: set_params:805: Broken configuration for this PCM: no
configurations available
Takashi suggested in an old post (can't find it now) that it might have
something to do with the lopsided input/output channel count of the
ICE1712. Any suggestions how to get past it, if that's the case?
I would really love to hear from anyone who managed to string two or
more ICE1712 cards together and used them successfully for recording
under JACK.
Thanks very much in advance,
Ludwig Schwardt
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
reply other threads:[~2004-02-20 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40362CEE.8060907@sun.ac.za \
--to=schwardt@sun.ac.za \
--cc=alsa-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