[linux-audio-user] RME Multiface with ALSA 1.08

[Kevin Ernste]

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.

Kevin


On Fri, 28 Jan 2005 16:35:23 -0500, Kevin Ernste <kevinernste at 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.
> 
> Kevin.
> 
> 
> On Fri, 28 Jan 2005 16:21:36 -0500, Lee Revell <rlrevell at 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.
> >
> > Lee
> >
>