Re: Altec Lansing FX5051 mixer

[Jeremy Nickurak <alsa-devel@atrus.rifetech.com>]

[-- Attachment #1.1: Type: text/plain, Size: 3651 bytes --]

Precisely the same problems with alsa 1.0.15rc1.


On Tue, Aug 28, 2007 at 01:43:51AM -0600, Jeremy Nickurak wrote:
> On Tue, Aug 28, 2007 at 08:50:00AM +0200, Clemens Ladisch wrote:
> > >         bmaControls( 0)      0x15
> > >           Mute
> > >           Bass
> > >           Treble
> > >         bmaControls( 1)      0x02
> > >           Volume
> > >         bmaControls( 2)      0x02
> > >           Volume
> > >         bmaControls( 3)      0x00
> > >         bmaControls( 4)      0x00
> > >         bmaControls( 5)      0x00
> > >         bmaControls( 6)      0x00
> > 
> > These descriptors say that there is a two-channel volume control that
> > applies to the front channels, but I guess it really affects all
> > channels.
> > 
> > Please show the output of "amixer contents" for this card.
> 
> numid=3,iface=MIXER,name='Tone Control - Bass'
>   ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0
>   : values=5
> numid=4,iface=MIXER,name='Tone Control - Treble'
>   ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0
>   : values=5
> numid=1,iface=MIXER,name='PCM Playback Switch'
>   ; type=BOOLEAN,access=rw------,values=1
>   : values=on
> numid=2,iface=MIXER,name='PCM Playback Volume'
>   ; type=INTEGER,access=rw---R--,values=2,min=0,max=49,step=0
>   : values=48,48
>   | dBscale-min=-49.00dB,step=1.00dB,mute=0
> 
> 
> > 
> > > ...
> > >         HID Device Descriptor:
> > >           bLength                 9
> > >           bDescriptorType        33
> > >           bcdHID               1.00
> > >           bCountryCode            0 Not supported
> > >           bNumDescriptors         1
> > >           bDescriptorType        34 Report
> > >           wDescriptorLength     172
> > >           Report Descriptor: (length is 172)
> > >             Item(Global): Usage Page, data= [ 0x0c ] 12
> > >                             Consumer
> > >             Item(Local ): Usage, data= [ 0x01 ] 1
> > >                             Consumer Control
> > >             Item(Main  ): Collection, data= [ 0x01 ] 1
> > >                             Application
> > >             Item(Global): Usage Page, data= [ 0x0c ] 12
> > >                             Consumer
> > >             Item(Local ): Usage, data= [ 0xe2 ] 226
> > >                             Mute
> > >             Item(Local ): Usage, data= [ 0xe9 ] 233
> > >                             Volume Increment
> > > ...
> > 
> > This describes an input device that reports 'key' presses to the
> > computer.  I guess the control panel and remote control don't have a
> > direct effect but expect the computer to explicitly change mixer
> > controls when a key is pressed.
> 
> Since it works fine in Windows without any non-ms software, would this 
> imply that this is somewhat standard behavior?
> 
> > 
> > However, this shouldn't prevent alsamixer from working.
> > 
> > It might be possible that the mixer controls don't have many steps and
> > that the step size used by alsamixer is so small that the device rounds
> > the setting back to the old position.  Please try PageUp/Down or Home/
> > End instead of Up/Down keys.
> 
> PgUp/PgDown don't do any better on any controls. I seem to be able to 
> drop the PCM volume to nothing in practice with End, but Home won't 
> restore it. Up/Down immediately brings it back up to 100%. The LED's on 
> the control reflect this btw, but alsamixer still reports 98%.

The control pad wouldn't be an especially big deal, if only alsamixer did work right.


-- 
Jeremy Nickurak -= Email/Jabber: atrus@rifetech.com =-

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel