alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Winfried Ritsch <ritsch@iem.at>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: RME AES32 & MADI
Date: Mon, 5 Feb 2007 10:27:28 +0100	[thread overview]
Message-ID: <200702051027.29226.ritsch@iem.at> (raw)
In-Reply-To: <s5h3b5ojtf6.wl%tiwai@suse.de>

Hello,

Am Freitag, 2. Februar 2007 19:39 schrieb Takashi Iwai:
> At Wed, 31 Jan 2007 13:11:48 +0100,
>
> Remy Bruno wrote:
> > Hello,
> >
> > I have been working on the AES32 and will soon provide a patch to get it
> > (hopefully) fully operational (hdspm code).
> >
> > Moreover, I also worked on the MADI card, but the original hdspm driver
> > didn't work for me (ie the code before my modifications to support
> > AES32). I had to deal with the following points:
> >   - it needed the DDS feature (clock divisor), as for the AES32 and
> > hdsp9632 cards (this may be a new behavior for recent cards)
> >   - the channel map needed to always be channel_map_madi_ss (and never
> >     channel_map_madi_ds, even at 96k), as for AES32. Otherwise, the
> > routing was not correct.
> >   - not enough DMA memory was beeing allocated (only for
> >     "params_channels(params)" channels whereas it should be allocated for
> > all the channels, otherwise it didn't work at 96kHz) (alsa-lib was
> > complaining, so I don't think an old MADI card would work either)
> >   - I had to play with the channel and rate rules
> >     (snd_hdspm_hw_rule_channels_rate and so on) to get it working. Not
> >     completely clear to me how it works but it didn't work as it was
> >
> > So here come my questions:
> >   - Was the MADI driver completely fonctionnal before now? In other
> > words, maybe an older revision of the card was working as the code
> > suggested (ie differently than the revision I have, which is 204), can
> > anyone confirm this?
>
> The early version has surely worked, IIRC.
> But, Winfried should know better....
>
Yes we are still working with MADI-Cards, on early version one version Rev 1.1 
and a newer card. The only thing is, that there are some troubles with  the 
correct Statusinformation, which are not functional limiting the card. 

We did not test DS mode extensively, but i can think of I tested it once MADI  
to MADI and it worked. 

> >   - As a corollary: should I keep the compatibility with the old code? IE
> > keep using channel_map_madi_ds, etc. for revisions < 204?
>
> Well, the only question is whether it breaks the older models.
>
If you post a patch or code so I can test it on old cards, it should be OK if 
you change this.

BTW:
Also I never finished to make a memory map interface for the mixer and meters, 
since it needs 16384 Bytes Mixer and the same for meters of values to copy, 
which is more ctl-interface can transfer at one time. Should we work on that, 
or everybody uses individual access to fader and meters for the software ?

mfg
   winfried

-- 
--
- ao.Univ.Prof. DI Winfried Ritsch 
- ritsch@iem.at - http://iem.at/ritsch
- Institut fuer Elektronische Musik und Akustik
- University of Music and Dramatic Art Graz
- Tel. ++43-316-389-3510 (3170) Fax ++43-316-389-3171 
- PGP-ID 69617A69 (see keyserver http://wwwkeys.eu.gpg.net/)
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2007-02-05  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 12:11 RME AES32 & MADI Remy Bruno
2007-02-02 18:39 ` Takashi Iwai
2007-02-05  9:27   ` Winfried Ritsch [this message]
2007-02-05 10:11     ` Takashi Iwai
2007-02-13 10:44     ` Remy Bruno
2007-02-14 15:00       ` Takashi Iwai
2007-02-20 17:04         ` Remy Bruno
2007-02-22 15:37           ` Takashi Iwai
2007-02-28 17:29             ` Remy Bruno
2007-03-08 13:40               ` 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=200702051027.29226.ritsch@iem.at \
    --to=ritsch@iem.at \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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).