From: Ludwig Schwardt <schwardt@sun.ac.za>
To: alsa-devel@lists.sourceforge.net
Cc: Doug <nostar@comcast.net>
Subject: Multiple Delta 1010LT woes: verdict
Date: Sun, 29 Feb 2004 14:42:53 +0200 [thread overview]
Message-ID: <4041DE4D.70504@sun.ac.za> (raw)
In-Reply-To: <403716BA.7010505@comcast.net>
Hi,
My quest for syncing two Delta 1010LTs under ALSA has gone on hold for
the time being... No success so far. Both cards work fine separately.
The main problem is that I cannot get either a word clock output or
SPDIF output going. Both these digital outputs remained dead no matter
what I did. I'm especially curious whether the word clock output has to
be enabled in some way by the driver. It seems that you have to enable
it under Windows, at least.
Luckily for me, my application didn't really depend on synchronization -
I only needed it to get JACK to record from all my soundcards at once.
After a switch to PortAudio I was able to simultaneously record
(unsynced) sound from all the soundcards. Both great APIs, by the way.
I would still be interested in any suggestions to get syncing to work,
as I have a few Delta 1010LTs left on which to experiment and I am a
willing guinea pig :->
Ludwig
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-29 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 18:29 Multiple Delta 1010LT woes: UPDATE Ludwig Schwardt
2004-02-21 8:26 ` Jaroslav Kysela
2004-02-21 8:28 ` Doug
2004-02-21 9:34 ` Tommi Sakari Uimonen
2004-02-29 12:42 ` Ludwig Schwardt [this message]
2004-02-29 21:04 ` Multiple Delta 1010LT woes: verdict Doug
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=4041DE4D.70504@sun.ac.za \
--to=schwardt@sun.ac.za \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nostar@comcast.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 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.