Audigy and ac3-passthrough not working..

Audigy and ac3-passthrough not working..

[Pasi Kärkkäinen]

Hello!

Anyone working with SB Audigy driver to get hwac3 working?

I'm testing with mplayer (0.9pre9) and I get this:

mplayer -ao alsa9 -ac hwac3 foo.avi

Forced audio codec: hwac3
Opening audio decoder: [hwac3] AC3 pass-through SP/DIF
No accelerated IMDCT transform found
AUDIO: 48000 Hz, 2 ch, 16 bit (0x400), ratio: 56000->192000 (448.0 kbit)
Selected audio codec: [hwac3] afm:hwac3 (AC3 through SPDIF)

alsa-init: testing and bugreports are welcome.
alsa-init: requested format: 48000 Hz, 2 channels, AC3
alsa-init: soundcard set to iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2
ALSA lib pcm_hw.c:835:(snd_pcm_hw_open) open /dev/snd/pcmC0D3p failed: No
such device
alsa-init: playback open error: No such device
couldn't open/init audio device -> no sound
Audio: no sound!!!

Any ideas?


- Pasi Kärkkäinen


                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

Re: Audigy and ac3-passthrough not working..

[Takashi Iwai]

At Sun, 3 Nov 2002 22:49:10 +0200 (EET),
Pasi Kärkkäinen wrote:
> 
> 
> Hello!
> 
> Anyone working with SB Audigy driver to get hwac3 working?

unfortunately, it's not supported yet...
emu10k2 on audigy is not 100% compatible with emu10k1.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

Cards PCI ids

[Free Ekanayaka]

Hi,
	I'd like to modify the discover library
(http://hackers.progeny.com/discover) to use ALSA
modules names instead of OSS ones when detecting sound devices.

Is there a place where I can found a mapping like:

soundcard PCI Id ---> ALSA module name

?

thank you

Free



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

Re: Cards PCI ids

[Patrice Tisserand]

On Mon, 2002-11-04 at 15:35, Free Ekanayaka wrote:
> 
> Hi,
> 	I'd like to modify the discover library
> (http://hackers.progeny.com/discover) to use ALSA
> modules names instead of OSS ones when detecting sound devices.
> 
> Is there a place where I can found a mapping like:
> 
> soundcard PCI Id ---> ALSA module name
> 
> ?
> 
Hi, 
I don't know where you can find a such mapping, but maybe you can
extract it from drivers source code.
As far as I know, each pci driver contains a pci_device_id array
initialize with VENDOR_ID and DEVICE_ID of supported pci device.

For example, if you look into ens1370.c you will find:
static struct pci_device_id snd_audiopci_ids[] __devinitdata = {
#ifdef CHIP1370
        { 0x1274, 0x5000, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
ES1370 */
#endif
#ifdef CHIP1371
        { 0x1274, 0x1371, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
ES1371 */
        { 0x1274, 0x5880, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
ES1373 - CT5880 */
        { 0x1102, 0x8938, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
Ectiva EV1938 */
#endif
        { 0, }
};

I hope it will help you.

Best regards
-- 
Patrice Tisserand --- email:mailto:Patrice.Tisserand@ircam.fr
IRCAM 1 place Stravinsky 75004 Paris FRANCE




-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

Re: Cards PCI ids

[Takashi Iwai]

At 04 Nov 2002 16:24:31 +0100,
Patrice Tisserand wrote:
> 
> On Mon, 2002-11-04 at 15:35, Free Ekanayaka wrote:
> > 
> > Hi,
> > 	I'd like to modify the discover library
> > (http://hackers.progeny.com/discover) to use ALSA
> > modules names instead of OSS ones when detecting sound devices.
> > 
> > Is there a place where I can found a mapping like:
> > 
> > soundcard PCI Id ---> ALSA module name
> > 
> > ?
> > 
> Hi, 
> I don't know where you can find a such mapping, but maybe you can
> extract it from drivers source code.
> As far as I know, each pci driver contains a pci_device_id array
> initialize with VENDOR_ID and DEVICE_ID of supported pci device.
> 
> For example, if you look into ens1370.c you will find:
> static struct pci_device_id snd_audiopci_ids[] __devinitdata = {
> #ifdef CHIP1370
>         { 0x1274, 0x5000, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1370 */
> #endif
> #ifdef CHIP1371
>         { 0x1274, 0x1371, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1371 */
>         { 0x1274, 0x5880, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1373 - CT5880 */
>         { 0x1102, 0x8938, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> Ectiva EV1938 */
> #endif
>         { 0, }
> };
> 
> I hope it will help you.

or, you can check the file /lib/modules/VERSION/modules.pcimap,
which holds the all entries for pci modules (although it's a bit
cryptic :)


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en

Re: Cards PCI ids

[Free Ekanayaka]

On 05/11/02  Takashi Iwai wrote...


> > static struct pci_device_id snd_audiopci_ids[] __devinitdata = {
> > #ifdef CHIP1370
> >         { 0x1274, 0x5000, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> > ES1370 */
> > #endif
> > #ifdef CHIP1371
> >         { 0x1274, 0x1371, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> > ES1371 */
> >         { 0x1274, 0x5880, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> > ES1373 - CT5880 */
> >         { 0x1102, 0x8938, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> > Ectiva EV1938 */
> > #endif
> >         { 0, }
> > };
> >
> > I hope it will help you.
>
> or, you can check the file /lib/modules/VERSION/modules.pcimap,
> which holds the all entries for pci modules (although it's a bit
> cryptic :)
>
>

Thank you a lot for the indication. I think modules.pcimap is the
straighter way, as it simply contains what I want:

module_name vedor_id device_id (+other information, useless in this case)

Free




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en