> Hello,
>
> We here are attempting to get the RME Hammerfall HDSP 9652 card working
> with ALSA 0.9.6 on a SMP redhat 9 box.  We're trying to use 12 input
> channels and three output channels, running at 96KHz 24bit samples.  The
> output of  "uname -a" on the box says:
>
>     Linux wombat 2.4.20-19.9smp #1 SMP Tue Jul 15 16:45:28 EDT 2003 i686
> athlon i386 GNU/Linux
>
> We had been successfully using the "old" RME Hammerfall 9652 with ALSA
> 0.9.0 beta12 on an older machine with the same channels/sample
> rate/sample size.
>
> With a signal connected to one input channel and nothing written to the
> card we're seeing output on several channels.  I think this could be
> related to settings of the hardware mixer?  I'm looking into the
> "amixer" utility but have so-far been unable to find any options that
> help.
>
> We have a known signal (IRIG-B) connected to one input channel and our
> software is now having trouble decoding the signal when it didn't
> before. We're not sure why this could be occuring.
>
> 1) first of all, we're assuming it is possible to get the card working
> on
>    this setup?
>

With this driver version the matrix mixer code is still broken and the
metering code is not implemented. Please apply the attach patch to correct
this. Mark Knecht is currently using this code with success, but the card
behaved strangely with rev. 104 (0x68) firmware. He had to downgrade it to
rev. 101 (0x65) for the card to work properly. Please let me know if
you're having the same problems.
I also have a development version of hdspmixer working for the card, email
me if you need it. I'll release it soon, as well as a huge driver patch,
when hdsp 9632 support will be completed (btw the 9632 driver code is
already functionnal, people can mail me if they need it right now).

> 2) I'm trying to determine if this card actually supports 96KHz (ie as a
>    parameter to snd_pcm_hw_params_set_rate_near() for example) -- the
> "old" card was always set to 48KHz and we "simulated" 96KHz with two
> 48KHz channels per 96KHz channel.  Is this still the way to do it?
>

The card needs to be set to 96 kHz, then the ADAT channel coupling will
work as you described.

> 3) It seems we need to find the right "amixer" incantations to get the
> driver
>    into a workable state.  The one thing that seems to have helped so
> far is to set the "Sample Clock Source" interface of the mixer to
> "Internal 96.0 kHz" with the command:
>
>         amixer -c 0 cset -numid=11 6
>

It looks good to me, except the '-' before numid. Note that you can also
use the hdspconf GUI to control this.

>    But we're not sure this is really what we want.  Are there other
> commands we need?  I don't believe we have a problem with output
> channel levels since we've played with these.
>

I think it's what you want. Please let me know if you have success with this.

Thomas


Attachment: hdsp9652.patch
Description: Binary data

Reply via email to