-----Original Message----- From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio- user-bounces(a)music.columbia.edu] On Behalf Of Martin Wohlleben Sent: Tuesday, January 25, 2005 1:15 PM To: A list for linux audio users Subject: [linux-audio-user] RME Multiface with ALSA 1.08 Hello, is anybody using ALSA 1.08 with a RME Multiface over Cardbus interface? I'm currently working with a SUSE Kernel 2.6.5 and tried a SUSE Kernel 2.6.8 too. The Kernel 2.6.5 work's fine with ALSA 1.03 but after an upgrade to ALSA 1.08 I got problems with the hdspmixer from alsa-tools. The same problem occured with SuSE's 2.6.8 Kernel from SuSE 9.2 - even without an update to ALSA 1.08. After the upgrade the peaks of the first 7 analog channels jitter and the RMS values (calculated by Multiface) aren't updated right. The sound is ok but the hdspmixer problem is real annoying. Anybody who got his Multiface working with ALSA 1.08? -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.4 - Release Date: 1/25/2005

Similar problem here except probably worse. Nando has also reported similar issues on alsa-devel list. I'd suggest voicing your concerns there as to the best of my knowledge the hdsp stuff is broken in 1.0.8. Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/

Martin Wohlleben wrote : Hi, This is now fixed in alsa-cvs. Thomas

On Fri, 2005-01-28 at 16:12 -0500, Kevin Ernste wrote: These messages are normal anytime you upgrade to a newer ALSA that has different mixer controls. They are harmless, when you "alsactl restore" an old config any new controls get the default value. Maybe the error message should make it clear that this is normal if you just upgraded ALSA. Lee

After further testing I found that the lack of sound on the headphone out occured on my system only with rdt kernels from PlanetCCRMA (go figure). Other Planet kernels. including kernel-2.6.10-2.1.ll.rhfc3.ccrma work perfectly with the new driver.

I will investigate the cause, but wanted users watching this thread and planning an upgrade not to hesitate. The recent patches to hdsp.c are a godsend, thanks again, Thomas.

On Fri, 28 Jan 2005 16:35:23 -0500, Kevin Ernste <kevinernste(a)gmail.com> wrote: > Thanks Lee. Good to know. > > My primary concern was that this error message appeared at a glance to > be related to the loss of signal in the Analog output ( "mismatch > (Line Out/Precise Pointer for control #22") and that this information > might be useful to Thomas should this issue be something other users > report with this new version. > > On Fri, 28 Jan 2005 16:21:36 -0500, Lee Revell <rlrevell(a)joe-job.com> wrote: > > On Fri, 2005-01-28 at 16:12 -0500, Kevin Ernste wrote: > > > Reloading the driver (via the alsasound service in my case) gives the > > > following error, perhaps related to the Analog out issue: > > > > > > Restoring sound driver settings /usr/sbin/alsactl: set_control:930: > > > warning: name mismatch (Passthru/Line Out) for control #21 > > > /usr/sbin/alsactl: set_control:930: warning: name mismatch (Line > > > Out/Precise Pointer) for control #22 > > > /usr/sbin/alsactl: set_control:930: warning: name mismatch (ADAT Lock > > > Status/Use Midi Tasklet) for control #23 > > > /usr/sbin/alsactl: set_control:932: warning: index mismatch (1/0) for > > > control #23 > > > /usr/sbin/alsactl: set_control:1025: bad control.23.value type > > > [FAILED] > > > > These messages are normal anytime you upgrade to a newer ALSA that has > > different mixer controls. They are harmless, when you "alsactl restore" > > an old config any new controls get the default value. > > > > Maybe the error message should make it clear that this is normal if you > > just upgraded ALSA. > >

Hi, The problem is not a kernel problem. There is an alsa ctl called "Line Out" that controls the fact that the line outs are powered on. By default they are. As I removed some obsolete ctls and created new ones in the update, the name/number association changed. This confused alsactl. It probably tried to restore the stored value even if the ctl name had changed (passthru defaulted to 0 IIRC), thus muting the line outs. The driver should work with both kernels. You can change the value of the Line Out ctl with amixer, and then regenerate your /etc/asound.state file.