Many thanx for your apt response. On Sun, 16 Dec 01 10:26:35 +0100 vanDongen/Gilcher <[EMAIL PROTECTED]> wrote: > >Q1. Can you enlighten me on the current status of the alsa rme96/8 > >driver effort. Is the rme96 driver appropriate at all for > >multi-channel use? > It works and yes, but the software must also have native alsa 0.9 > support and there are not that many programs yet.
As of 28-09-2001 the Ecasound nultitrack audio processing tool (http://www.wakkanet.fi/~kaiv/ecasound/welcome.html) has support for the latest ALSA 0.9 beta-releases (beta7 and newer). After getting ALSA up and running I plan to use the API for a custom application (multichannel watermark detection). > >Q2. How do I communicate to the card that it should use ADAT > >8-channel mode? > The driver defines 2 devices. One is spdif the other ADAT. Unless > you give these a name using the mysterious .asoundrc file, you can > often use "hw:0,0" and "hw:0,1" as device names, the zero is the > card number, as defined by your /etc/modules.conf. /dev/dsp is > always the spdif. f.i. aplay -D hw:0,1 eight.wav will play an 8 > channel WAV file using the ADAT mode of the optical output. [cut] > I think the flag should be: > -o alsa,hw:0,1 or something like this. See the ecasound manual. Just the hint that I needed :) > I currently use pd a lot, it works well in both ADAT and SPDIF mode. > You have to start the program, then quit and then start again to > switch between devices. For some reason. > I think Jmax (similas program) will also work. [cut] > I haven't really worked with ecasound, but -o /dev/dsp accesses the > OSS emulation not the native alsa interface. I got that impression judging error messages that started to appear recently. I have looked at pd. Interesting indeed. > >/lib/modules/2.4.9-ac10/misc/snd.o: insmod snd-card-rme96 failed > These errors are similar to what i had when my card was not properly > seated in its pci slot. > lspci found it, but it had these errors when loading the > alsa-drivers. It had come loose during transport of the computer. > Were you still able to play some sounds after this message? Somehow - without me changing anything (that I know of) - the system can't open the /dev/dsp input anymore, giving various errors, like "OSS doesn't accept sometrigger", "file does not exist". Before, I was able to use at least /dev/dsp in full-duplex mode. Output still works flawlessly... Janroel -- ________________________________________________________________ | | Janroel Koppen, (+31)(0)15-27.86224 | Information & Communication Theory Group, | Delft University of Technology, The Netherlands | [EMAIL PROTECTED], www-ict.its.tudelft.nl/~janroel |_______________________________________________________________ _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
