Adds 24bit, 96khz support for multichannel playback on the Audigy 2 sound cards.
PATCH 1/1 Adds 24bit, 96khz support for multichannel playback on the Audigy 2 sound cards.
Please see readme.txt at http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txt
It works with the current alsa CVS.
I would like this to be merged with the CVS quite soon if possible.
Summary:
Add support for the P16V chip (CA0151-DBS) present on Creative Sound Blaster 2 ZS and Creative Sound Blaster 4 Pro sound cards. A new 8 channel playback device appears as device 4.
Signoff: James Courtier-Dutton
-------------------------------------------------------
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
Quoted 6 lines · James Courtier-Dutton
Please see readme.txt at
http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txtIt works with the current alsa CVS.
I would like this to be merged with the CVS quite soon if possible.
Could you cleanup a bit your code before merging? It seems that there is alot of #if 0 .. #endif parts....
Jaroslav
-----
Jaroslav Kysela <[email protected]>
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
Quoted 4 lines · Jaroslav Kysela
Could you cleanup a bit your code before merging? It seems that there is alot of #if 0 .. #endif parts....
The code inside the #if 0 .. #endif implements features that I have not yet finished merging. E.g. 24bit capture. As I fix each section, the #if 0 etc. will be removed.
Would you prefer that I just remove all the current sections under #if 0 and then add them back in as I get them working?
James
-------------------------------------------------------
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
Quoted 7 lines · James Courtier-Dutton
Quoted 5 lines · Jaroslav Kysela
Could you cleanup a bit your code before merging? It seems that there is alot of #if 0 .. #endif parts....
Quoted 5 lines
The code inside the #if 0 .. #endif implements features that I have not yet finished merging. E.g. 24bit capture.
As I fix each section, the #if 0 etc. will be removed.
Would you prefer that I just remove all the current sections under #if 0 and then add them back in as I get them working?
Okay, applied the stripped version and new code slipped into 1.0.9rc1 (will be available in next minutes)...
Jaroslav
-----
Jaroslav Kysela <[email protected]>
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
Quoted 9 lines · Jaroslav Kysela
Quoted 6 lines · James Courtier-Dutton
Quoted 3 lines · Jaroslav Kysela
Could you cleanup a bit your code before merging? It seems that there is alot of #if 0 .. #endif parts....
Quoted 8 lines
Quoted 3 lines
The code inside the #if 0 .. #endif implements features that I have not yet finished merging. E.g. 24bit capture. As I fix each section, the #if 0 etc. will be removed.
Would you prefer that I just remove all the current sections under #if 0 and then add them back in as I get them working?Okay, applied the stripped version and new code slipped into 1.0.9rc1 (will be available in next minutes)...
Jaroslav
Nice, thanks
James
-------------------------------------------------------
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
Quoted 9 lines · Jaroslav Kysela
Quoted 3 lines · James Courtier-Dutton
Please see readme.txt at http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txtCould you cleanup a bit your code before merging? It seems that there is alot of #if 0 .. #endif parts....
I have updated the p16v.c file as you requested. it is in http://www.alsa-project.org/~james/alsa-driver/p16v/p16v.c
-------------------------------------------------------
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
Hello,
Quoted 4 lines · James Courtier-Dutton
Please see readme.txt at
http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txt
Thank you for your work.
I have plain Audigy2 6.1 (SB0240) and I tried using alsa-driver-1.0.9rc1. speaker-test command from your readme worked more or less. When it worked, channels were swapped. speaker-test tried to shout from Rear Left, but I got sound from Center, Rear Right - LFE, Unk Left - Rear Left, Unk Right - Rear Right (I had to patch speaker-test a bit, so it doesn't segfault). I can't verify what channel sends sound to the "Back", because I have no 4-pin minijack.
BTW1: this incorrect "naming" maybe a more generic problem, because if I try to use multichannel device (plughw:0,3), i get same mis"naming".
BTW2: I wander when will ALSA support 6.1 configurations/cards correctly?
Also at some point p16v hanged, every program trying to use plughw:0,4 hangs at first poll(). modprobe -r snd-emu10k1 ; modprobe snd-emu10k1 cycle doesn't help. Later I'll try rebooting to see if it's permanent damage or not.
Signature · 9 lines
With best wishes Dmitry Baryshkov ------------------------------------------------------- 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
Quoted 21 lines · Dmitry Baryshkov
Hello,
Quoted 3 lines · James Courtier-Dutton
Please see readme.txt at http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txtThank you for your work.
I have plain Audigy2 6.1 (SB0240) and I tried using alsa-driver-1.0.9rc1. speaker-test command from your readme worked more or less. When it worked, channels were swapped. speaker-test tried to shout from Rear Left, but I got sound from Center, Rear Right - LFE, Unk Left - Rear Left, Unk Right - Rear Right (I had to patch speaker-test a bit, so it doesn't segfault). I can't verify what channel sends sound to the "Back", because I have no 4-pin minijack.
BTW1: this incorrect "naming" maybe a more generic problem, because if I try to use multichannel device (plughw:0,3), i get same mis"naming".
Quoted 7 lines
BTW2: I wander when will ALSA support 6.1 configurations/cards correctly?
Also at some point p16v hanged, every program trying to use plughw:0,4 hangs at first
poll(). modprobe -r snd-emu10k1 ; modprobe snd-emu10k1 cycle doesn't help. Later I'll try rebooting to see if it's permanent damage or not.
Please upgrade your speaker-test version to the latest in alsa-utils. Failing that, there is a newer version at http://www.alsa-project.org/~james/speaker-test/
The p16v does not support hardware mixing, so only one application can open it at a time.
James
-------------------------------------------------------
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
At Sun, 13 Mar 2005 21:43:26 +0000,
Quoted 32 lines · James Courtier-Dutton
Quoted 22 lines · Dmitry Baryshkov
Hello,
Quoted 4 lines · James Courtier-Dutton
Please see readme.txt at
http://www.alsa-project.org/~james/alsa-driver/p16v/
http://www.alsa-project.org/~james/alsa-driver/p16v/readme.txtThank you for your work.
I have plain Audigy2 6.1 (SB0240) and I tried using alsa-driver-1.0.9rc1. speaker-test command from your readme worked more or less. When it worked, channels were swapped. speaker-test tried to shout from Rear Left, but I got sound from Center, Rear Right - LFE, Unk Left - Rear Left, Unk Right - Rear Right (I had to patch speaker-test a bit, so it doesn't segfault). I can't verify what channel sends sound to the "Back", because I have no 4-pin minijack.
BTW1: this incorrect "naming" maybe a more generic problem, because if I try to use multichannel device (plughw:0,3), i get same mis"naming".
Quoted 7 lines
BTW2: I wander when will ALSA support 6.1 configurations/cards correctly?
Also at some point p16v hanged, every program trying to use plughw:0,4 hangs at first
poll(). modprobe -r snd-emu10k1 ; modprobe snd-emu10k1 cycle doesn't help. Later I'll try rebooting to see if it's permanent damage or not.
Quoted 3 lines
Please upgrade your speaker-test version to the latest in alsa-utils. Failing that, there is a newer version at
http://www.alsa-project.org/~james/speaker-test/
FYI, 1.0.9rc1 already includes the latest one (0.0.7).
Takashi
-------------------------------------------------------
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