emu10k1: rear mono played on all exept rear

emu10k1: rear mono played on all exept rear

[Mikael Magnusson]

I discovered a bug in EMU10K1.pcm.rear.0 in EMU10K1.conf. It sends rear 
mono output to FX 0 and 1 instead of FX 2 and 3!

/Mikael Magnusson

--- cvs/alsa/alsa-lib/src/conf/cards/EMU10K1.conf      2004-07-13 
19:32:18.000000000 +0200
+++ /usr/share/alsa/cards/EMU10K1.conf  2005-02-16 11:56:24.000000000 +0100
@@ -41,7 +41,7 @@
                                 name "EMU10K1 PCM Send Volume"
                                 index { @func private_pcm_subdevice }
                                 lock true
-                               value [ 255 255 0 0 0 0 255 0 0 0 0 255 ]
+                               value [ 0 0 255 255 0 0 255 0 0 0 0 255 ]
                         }
                 ]
         }


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: emu10k1: rear mono played on all exept rear

[Lee Revell]

On Wed, 2005-02-16 at 12:19 +0100, Mikael Magnusson wrote:
> I discovered a bug in EMU10K1.pcm.rear.0 in EMU10K1.conf. It sends rear 
> mono output to FX 0 and 1 instead of FX 2 and 3!
> 
> /Mikael Magnusson
> 
> --- cvs/alsa/alsa-lib/src/conf/cards/EMU10K1.conf      2004-07-13 
> 19:32:18.000000000 +0200
> +++ /usr/share/alsa/cards/EMU10K1.conf  2005-02-16 11:56:24.000000000 +0100
> @@ -41,7 +41,7 @@
>                                  name "EMU10K1 PCM Send Volume"
>                                  index { @func private_pcm_subdevice }
>                                  lock true
> -                               value [ 255 255 0 0 0 0 255 0 0 0 0 255 ]
> +                               value [ 0 0 255 255 0 0 255 0 0 0 0 255 ]
>                          }
>                  ]
>          }
> 

This seems wrong to me.  Isn't the correct fix to do this:

{
      name "EMU10K1 PCM Send Volume"
      index { @func private_pcm_subdevice }
      lock true
      value [ 255 255 0 0 255 0 0 0 0 255 0 0 ]
}
{
      name "EMU10K1 PCM Send Routing"
      index { @func private_pcm_subdevice }
      lock true
      value [ 2 3 0 0 2 3 0 0 2 3 0 0 ]
}

The current config relies on the 3rd and 4th FX sends being set to FX 2
and 3.  It seems better to state this explicitly.

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: emu10k1: rear mono played on all exept rear

[Mikael Magnusson]

Lee Revell wrote:
> On Wed, 2005-02-16 at 12:19 +0100, Mikael Magnusson wrote:
> 
>>I discovered a bug in EMU10K1.pcm.rear.0 in EMU10K1.conf. It sends rear 
>>mono output to FX 0 and 1 instead of FX 2 and 3!
>>
>>/Mikael Magnusson
>>
>>--- cvs/alsa/alsa-lib/src/conf/cards/EMU10K1.conf      2004-07-13 
>>19:32:18.000000000 +0200
>>+++ /usr/share/alsa/cards/EMU10K1.conf  2005-02-16 11:56:24.000000000 +0100
>>@@ -41,7 +41,7 @@
>>                                 name "EMU10K1 PCM Send Volume"
>>                                 index { @func private_pcm_subdevice }
>>                                 lock true
>>-                               value [ 255 255 0 0 0 0 255 0 0 0 0 255 ]
>>+                               value [ 0 0 255 255 0 0 255 0 0 0 0 255 ]
>>                         }
>>                 ]
>>         }
>>
> 
> 
> This seems wrong to me.  Isn't the correct fix to do this:
> 
> {
>       name "EMU10K1 PCM Send Volume"
>       index { @func private_pcm_subdevice }
>       lock true
>       value [ 255 255 0 0 255 0 0 0 0 255 0 0 ]
> }
> {
>       name "EMU10K1 PCM Send Routing"
>       index { @func private_pcm_subdevice }
>       lock true
>       value [ 2 3 0 0 2 3 0 0 2 3 0 0 ]
> }
> 
> The current config relies on the 3rd and 4th FX sends being set to FX 2
> and 3.  It seems better to state this explicitly.
> 
> Lee
> 

Maybe, but it isn't explicit in Audigy.conf, Audigy2.conf either.

/Mikael Magnusson


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: emu10k1: rear mono played on all exept rear

[Jaroslav Kysela]

On Wed, 16 Feb 2005, Lee Revell wrote:

> The current config relies on the 3rd and 4th FX sends being set to FX 2
> and 3.  It seems better to state this explicitly.

The driver does this...

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: emu10k1: rear mono played on all exept rear

[Lee Revell]

On Wed, 2005-02-16 at 21:55 +0100, Jaroslav Kysela wrote:
> On Wed, 16 Feb 2005, Lee Revell wrote:
> 
> > The current config relies on the 3rd and 4th FX sends being set to FX 2
> > and 3.  It seems better to state this explicitly.
> 
> The driver does this...
> 

Right, I see.  It seems a bit odd that front/rear and center/lfe are
handled differently.  The kX driver uses sends 1 and 2 for
front/rear/center+lfe and sets sends 3 and 4 the same for all channels.
There are probably advantages to both approaches.

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click