From: Dougall Irving <dougall.irving@versonic.com>
To: alsa-devel@alsa-project.org
Subject: RME HDSPe Raydat
Date: Mon, 1 Feb 2010 16:27:50 +0800 [thread overview]
Message-ID: <ac7eefbd1002010027g49148edfm45957d39b921b973@mail.gmail.com> (raw)
I've been trying to get an RME HDSPe Raydat working. I've installed
the latest firmware on the card using the Windows firmware uploader.
The stock hdspm module in ALSA version 1.0.22.1 doesn't work
correctly.
The first problem I found is that external ADAT equipment were not
able to sync with RME adat outputs. Following some old alsa code
posted on another site, I changed the HDSPM_freqReg to 100 MHz
(instead of 105) and found that I could get external equipment to sync
to the raydat at 48kHz.
The second issue I had was the audio output was turning on and off
every second. I found if I changed the .params to only use float 32
instead of int 32 and I forced the card to use precise pointer I could
get continuous audio but only with larger buffer sizes. I get a quite
a few buffer underruns also. With smaller buffer sizes I get silence.
There is a comment in the code which don't follow. I wonder if there
is an issue with this code....
/* hwpointer comes in bytes and is 64Bytes accurate (by docu since
PCI Burst)
i have experimented that it is at most 64 Byte to much for playing
so substraction of 64 byte should be ok for ALSA, but use it only
for application where you know what you do since if you come to
near with record pointer it can be a disaster */
position &= HDSPM_BufferPositionMask;
position = ((position - 64) % (2 * hdspm->period_bytes)) / 4;
Does anyone have any suggestions or ideas for debugging these
problems? Is there any information RME from available?
Alternatively, has anyone had success with this card and earlier
firmware revisions?
reply other threads:[~2010-02-01 8:27 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=ac7eefbd1002010027g49148edfm45957d39b921b973@mail.gmail.com \
--to=dougall.irving@versonic.com \
--cc=alsa-devel@alsa-project.org \
/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).