From: Martin Langer <martin-langer@gmx.de>
To: alsa-devel@lists.sourceforge.net
Subject: which adat rates are possible?
Date: Tue, 4 Jun 2002 23:42:53 +0200 [thread overview]
Message-ID: <20020604214253.GA1214@localhost> (raw)
Hi,
I try to write some adat support for the Digi32/8, but I am not familiar with
adat up to now... and I don't have this adat model, but the driver should be
very similar to the rme96 one...
I know that the Digi96 has just Adat support for 44100 and 48000.
My problem: I don't know the working rates of the Digi32/8. Possible
frequencies of this card may be 32000/44100/48000 kHz, but are this all
possible in the adat world???
Or better: Is anybody there, who knows the RME Digi32/8 adat rates?
martin
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next reply other threads:[~2002-06-04 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 21:42 Martin Langer [this message]
2002-06-10 14:26 ` which adat rates are possible? Takashi Iwai
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=20020604214253.GA1214@localhost \
--to=martin-langer@gmx.de \
--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