Advanced Linux Sound Architecture

Quoting Dave Ewart <davee@...>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> <chgans <at> free.fr> wrote:
>
> > I recently buy an "SB Audigy SE" [1], and i am unable to get it work.
> > I am using agnula distro with alsa-1.0.10.
>
> I also have one of these and would like to explore opportunities for
> supporting it.  I don't have enough expertise to write ALSA code, but a=
m
> happy to provide info, test and return debugging information about it
> ...

I have posted a request on
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3D1636.

I have made some investigation, but still can't get it worked.

Please could you provide details about the behaviour you get?
So that i will add a new comment on this request with the infromation you=
 give.
Or better, create an account on https://bugtrack.alsa-project.org and add=
 a
comment yourself dfescribing the distro you use, the alsa version, some l=
ogs,
etc...

Regards,
Christian


>
> Cheers,
>
> Dave.
> - --
> Dave Ewart - davee@... - jabber: davee@...
> All email from me is now digitally signed, key from http://www.sungate.=
co.uk/
> Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDnar0nhBnac0o2pIRAs4SAJ9YLy4gK+C6i9ptWsEFUXs/XQZnVwCcCvIW
> 5ahcr03mnMCzvbJbzVwD8i8=3D
> =3DPCYE
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday, 12.12.2005 at 19:58 +0100, chgans@... wrote:

> I have posted a request on
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1636.
> 
> I have made some investigation, but still can't get it worked.
> 
> Please could you provide details about the behaviour you get?
>
> So that i will add a new comment on this request with the infromation
> you give.

I've add my comments there now.  Is there any other info that might be
useful, do you think?

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDndm8nhBnac0o2pIRAt7NAKDirEu94gYGPWUFSRFL8Jw0LV7r9QCfYP++
GO6Hph/NwO8N0QGelOK29QE=
=EOBB
-----END PGP SIGNATURE-----

chgans@... wrote:
> Quoting Dave Ewart <davee@...>:
> 
> 
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>><chgans <at> free.fr> wrote:
>>
>>
>>>I recently buy an "SB Audigy SE" [1], and i am unable to get it work.
>>>I am using agnula distro with alsa-1.0.10.
>>
>>I also have one of these and would like to explore opportunities for
>>supporting it.  I don't have enough expertise to write ALSA code, but am
>>happy to provide info, test and return debugging information about it
>>...
> 
> 
> I have posted a request on
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1636.
> 
> I have made some investigation, but still can't get it worked.
> 
> Please could you provide details about the behaviour you get?
> So that i will add a new comment on this request with the infromation you give.
> Or better, create an account on https://bugtrack.alsa-project.org and add a
> comment yourself dfescribing the distro you use, the alsa version, some logs,
> etc...
> 
> Regards,
> Christian
> 
> 

Thank you for the bug report. Please see bug#1636 for patch to fix this.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 13.12.2005 at 11:27 +0000, James Courtier-Dutton wrote:

> Thank you for the bug report. Please see bug#1636 for patch to fix this.

I'll check the patch out this evening, when I'm back at the machine in
question - thanks James.

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDnrlQnhBnac0o2pIRAvSSAJ90ZXONMSxq9+sMrGat4z/4w1MZagCeJSMs
BpfJFSncrwHLOKglQ0MIvIc=
=06Ir
-----END PGP SIGNATURE-----

Selon James Courtier-Dutton <James@...>:

> chgans@... wrote:
> > Quoting Dave Ewart <davee@...>:
> >
> >
> >>-----BEGIN PGP SIGNED MESSAGE-----
> >>Hash: SHA1
> >>
> >><chgans <at> free.fr> wrote:
> >>
> >>
> >>>I recently buy an "SB Audigy SE" [1], and i am unable to get it work=
.
> >>>I am using agnula distro with alsa-1.0.10.
> >>
> >>I also have one of these and would like to explore opportunities for
> >>supporting it.  I don't have enough expertise to write ALSA code, but=
 am
> >>happy to provide info, test and return debugging information about it
> >>...
> >
> >
> > I have posted a request on
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3D1636.
> >
> > I have made some investigation, but still can't get it worked.
> >
> > Please could you provide details about the behaviour you get?
> > So that i will add a new comment on this request with the infromation=
 you
> give.
> > Or better, create an account on https://bugtrack.alsa-project.org and=
 add a
> > comment yourself dfescribing the distro you use, the alsa version, so=
me
> logs,
> > etc...
> >
> > Regards,
> > Christian
> >
> >
>
> Thank you for the bug report. Please see bug#1636 for patch to fix this=
.
OK, I will take a try tonight or tomorrow.

>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 13.12.2005 at 11:27 +0000, James Courtier-Dutton wrote:

> Thank you for the bug report. Please see bug#1636 for patch to fix
> this.

Just trying this now.  Your patch makes the driver installable and it
'feels' like it ought to be working, but no sound yet: the mixer seems
to be failing on me.

I'm using kmix under KDE, but other mixers (xmix, alsamixer) give the
same symptoms.  I don't appear to get any settings to change the INPUT
levels - I've moved all the OUTPUT levels up to about 75%; in kmix, the
INPUT tab shows nothing at all, i.e. no sliders.  With xmix, the input
sliders are all greyed out.  With alsamixer, I see no INPUT sliders at
all.

Thanks for your patch ...

Suggestions to fix this most welcome!

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDnyIhnhBnac0o2pIRAi/aAKDg4jRlttufAZwl0BUzBxfe/VHcLQCfXmQ9
wWVa4xm3LR0U91eNCNU77q8=
=sldO
-----END PGP SIGNATURE-----

Dave Ewart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tuesday, 13.12.2005 at 11:27 +0000, James Courtier-Dutton wrote:
> 
> 
>>Thank you for the bug report. Please see bug#1636 for patch to fix
>>this.
> 
> 
> Just trying this now.  Your patch makes the driver installable and it
> 'feels' like it ought to be working, but no sound yet: the mixer seems
> to be failing on me.
> 
> I'm using kmix under KDE, but other mixers (xmix, alsamixer) give the
> same symptoms.  I don't appear to get any settings to change the INPUT
> levels - I've moved all the OUTPUT levels up to about 75%; in kmix, the
> INPUT tab shows nothing at all, i.e. no sliders.  With xmix, the input
> sliders are all greyed out.  With alsamixer, I see no INPUT sliders at
> all.
> 
> Thanks for your patch ...
> 
> Suggestions to fix this most welcome!
> 
> Dave.
> - -- 

There are no input sliders, only switches.
alsamixer is the best program to use.
Do you get sound output?

James

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 13.12.2005 at 19:44 +0000, James Courtier-Dutton wrote:

> There are no input sliders, only switches.
> alsamixer is the best program to use.
> Do you get sound output?

Hmmm, OK, no input sliders.

I don't get any proper sound output (although I get some white noise,
see below), but the applications behave as if sound is being produced
(i.e. xmms plays happily, as does ogg123 etc.)

I must confess I don't quite understand all the switches: the only one
which seems to do anything is the one labelled SPDIF Out - when 'muted'
(shows as 'MM' in alsamixer), I get a white-noise hiss on the output
channel, when 'on' (shows as 'OO' in green), I get silence.

I have basic stereo speakers here and I've connected them to the 'green'
connector on the card, which is conventionally the speaker output: I've
tried the other connectors as well, just for good measure, but no output
there either.

Any ideas?

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDnzAHnhBnac0o2pIRAhBRAJ9Mt9oXbNaIspbH0Mvl+2bBIbnybgCgtpK3
xt+KJRDppuY4FmAVsaHX4mg=
=d3lI
-----END PGP SIGNATURE-----

Dave Ewart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tuesday, 13.12.2005 at 19:44 +0000, James Courtier-Dutton wrote:
> 
> 
>>There are no input sliders, only switches.
>>alsamixer is the best program to use.
>>Do you get sound output?
> 
> 
> Hmmm, OK, no input sliders.
> 
> I don't get any proper sound output (although I get some white noise,
> see below), but the applications behave as if sound is being produced
> (i.e. xmms plays happily, as does ogg123 etc.)
> 
> I must confess I don't quite understand all the switches: the only one
> which seems to do anything is the one labelled SPDIF Out - when 'muted'
> (shows as 'MM' in alsamixer), I get a white-noise hiss on the output
> channel, when 'on' (shows as 'OO' in green), I get silence.
> 
> I have basic stereo speakers here and I've connected them to the 'green'
> connector on the card, which is conventionally the speaker output: I've
> tried the other connectors as well, just for good measure, but no output
> there either.
> 
> Any ideas?
> 
> Dave.
> - -- 

try
speaker-test -c6 -Dplug:surround51

Then, while playing, run alsamixer and toggle the spdif out on and then 
off, and see if one gives you sound.

Also, adjust the "Analog Front", "Analog Rear", "Analog Center/LFE" to 
all be 70%

James

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 13.12.2005 at 20:56 +0000, James Courtier-Dutton wrote:

> >I don't get any proper sound output (although I get some white noise,
> >see below), but the applications behave as if sound is being produced
> >(i.e. xmms plays happily, as does ogg123 etc.)
> >
> >I must confess I don't quite understand all the switches: the only one
> >which seems to do anything is the one labelled SPDIF Out - when 'muted'
> >(shows as 'MM' in alsamixer), I get a white-noise hiss on the output
> >channel, when 'on' (shows as 'OO' in green), I get silence.
> >
> >I have basic stereo speakers here and I've connected them to the 'green'
> >connector on the card, which is conventionally the speaker output: I've
> >tried the other connectors as well, just for good measure, but no output
> >there either.
> 
> try
> speaker-test -c6 -Dplug:surround51
> 
> Then, while playing, run alsamixer and toggle the spdif out on and then 
> off, and see if one gives you sound.
> 
> Also, adjust the "Analog Front", "Analog Rear", "Analog Center/LFE" to 
> all be 70%

OK ... when 'SPDIF Out' is muted, I get some noise when the speaker-test
is showing 'Front Left' and 'Front Right', although it sounds very
distorted (speaker-test is supposed to generate a clean sine wave,
isn't it?)

speaker-test -c2 -Dplug:default

gives the same results for 'Front Left' and 'Front Right', very
distorted.

When running an app which produces ALSA sound directly, i.e. xmms with
output plugin set to ALSA, I get white noise.

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDnzjInhBnac0o2pIRAgqlAKCGHYsY9AT/M2xSBD/1LA1JRDW0dwCbBC9u
mBObCEW9vX5V9KkyUiOu5t0=
=jpGi
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 13.12.2005 at 21:10 +0000, Dave Ewart wrote:

> > try
> > speaker-test -c6 -Dplug:surround51
> > 
> > Then, while playing, run alsamixer and toggle the spdif out on and then 
> > off, and see if one gives you sound.
> > 
> > Also, adjust the "Analog Front", "Analog Rear", "Analog Center/LFE" to 
> > all be 70%
> 
> OK ... when 'SPDIF Out' is muted, I get some noise when the speaker-test
> is showing 'Front Left' and 'Front Right', although it sounds very
> distorted (speaker-test is supposed to generate a clean sine wave,
> isn't it?)
> 
> speaker-test -c2 -Dplug:default
> 
> gives the same results for 'Front Left' and 'Front Right', very
> distorted.
> 
> When running an app which produces ALSA sound directly, i.e. xmms with
> output plugin set to ALSA, I get white noise.

Hmmm, I'm wondering whether I didn't build the modules correctly - will
have another go at that this evening.

Thanks for your continuing assistance, James!

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDn+SrnhBnac0o2pIRApPpAKCDfpV+0u4lcTMkBSjGx+sf8eTcxQCeJXIy
nqNX5dAkCJryZ4uvInoLmZ4=
=1Bus
-----END PGP SIGNATURE-----

Dave Ewart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tuesday, 13.12.2005 at 20:56 +0000, James Courtier-Dutton wrote:
> 
> 
>>>I don't get any proper sound output (although I get some white noise,
>>>see below), but the applications behave as if sound is being produced
>>>(i.e. xmms plays happily, as does ogg123 etc.)
>>>
>>>I must confess I don't quite understand all the switches: the only one
>>>which seems to do anything is the one labelled SPDIF Out - when 'muted'
>>>(shows as 'MM' in alsamixer), I get a white-noise hiss on the output
>>>channel, when 'on' (shows as 'OO' in green), I get silence.
>>>
>>>I have basic stereo speakers here and I've connected them to the 'green'
>>>connector on the card, which is conventionally the speaker output: I've
>>>tried the other connectors as well, just for good measure, but no output
>>>there either.
>>
>>try
>>speaker-test -c6 -Dplug:surround51
>>
>>Then, while playing, run alsamixer and toggle the spdif out on and then 
>>off, and see if one gives you sound.
>>
>>Also, adjust the "Analog Front", "Analog Rear", "Analog Center/LFE" to 
>>all be 70%
> 
> 
> OK ... when 'SPDIF Out' is muted, I get some noise when the speaker-test
> is showing 'Front Left' and 'Front Right', although it sounds very
> distorted (speaker-test is supposed to generate a clean sine wave,
> isn't it?)
> 
> speaker-test -c2 -Dplug:default
> 
> gives the same results for 'Front Left' and 'Front Right', very
> distorted.
> 
> When running an app which produces ALSA sound directly, i.e. xmms with
> output plugin set to ALSA, I get white noise.
> 
> Dave.
> - -- 

"speaker-test -c6 -Dplug:surround51" will output pink noise.
"speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine wave.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, 14.12.2005 at 11:51 +0100, chgans@... wrote:

> > Just trying this now.  Your patch makes the driver installable and
> > it 'feels' like it ought to be working, but no sound yet: the mixer
> > seems to be failing on me.
> 
> I have not yet tested the patch, i will probably do this tonigth
> (french time).
> 
> Is your soundcard reconized as "Audigy SE" now? (cat
> /proc/asound/cards) Last alsa version without the path give me the
> results you describe: noise on speakers or no sound at all depending
> of the state of the SPDIF output mute control.

Hmm, that's interesting.

I'll have to check that later too.  I have a feeling I mis-built the
module, actually, 'cos I just stopped I didn't have a properly
up-to-date CVS source before applying the patch:

My card *isn't* recognised as "Audigy SE" yet, no - that is perhaps the
problem.  It's reassuring to note that you saw the same behaviour with
the 'old' version.

I'll get a fresh CVS checkout this evening and apply the patch properly
:-)

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDn/rznhBnac0o2pIRAoRTAJ9ado2YIp/2Qbu4keLwJKWze0BzZwCgmkqC
sNVR5LUUG0kjk/EcQ791dY8=
=guuZ
-----END PGP SIGNATURE-----

Selon Dave Ewart <davee@...>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday, 14.12.2005 at 11:51 +0100, chgans@... wrote:
>
> > > Just trying this now.  Your patch makes the driver installable and
> > > it 'feels' like it ought to be working, but no sound yet: the mixer
> > > seems to be failing on me.
> >
> > I have not yet tested the patch, i will probably do this tonigth
> > (french time).
> >
> > Is your soundcard reconized as "Audigy SE" now? (cat
> > /proc/asound/cards) Last alsa version without the path give me the
> > results you describe: noise on speakers or no sound at all depending
> > of the state of the SPDIF output mute control.
>
> Hmm, that's interesting.
>
> I'll have to check that later too.  I have a feeling I mis-built the
> module, actually, 'cos I just stopped I didn't have a properly
> up-to-date CVS source before applying the patch:
>
> My card *isn't* recognised as "Audigy SE" yet, no - that is perhaps the
> problem.  It's reassuring to note that you saw the same behaviour with
> the 'old' version.

The card should be recognized as "SB Audigy SE [SBxxxx]", this means that=
 there
was a problem during the build or install of your new alsa drivers.

Hope this will work tonigth! ;o)




>
> I'll get a fresh CVS checkout this evening and apply the patch properly
> :-)
>
> Dave.
> - --
> Dave Ewart - davee@... - jabber: davee@...
> All email from me is now digitally signed, key from http://www.sungate.=
co.uk/
> Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDn/rznhBnac0o2pIRAoRTAJ9ado2YIp/2Qbu4keLwJKWze0BzZwCgmkqC
> sNVR5LUUG0kjk/EcQ791dY8=3D
> =3DguuZ
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>

Quoting James Courtier-Dutton <James@...>:
>
> "speaker-test -c6 -Dplug:surround51" will output pink noise.
I get noise when SPDIF out is Muted, nothing when unmuted.

In alsamixer, the volume of the analog front output modify the frequency =
of the
noise (!?!) (speker-test is running)

> "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine wave.
speaker-test 1.0.8
speaker-test: invalid option -- t
Unknown option '?'


>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>

Quoting chgans@...:

> Quoting James Courtier-Dutton <James@...>:
> >
> > "speaker-test -c6 -Dplug:surround51" will output pink noise.
> I get noise when SPDIF out is Muted, nothing when unmuted.
>
> In alsamixer, the volume of the analog front output modify the frequenc=
y of
> the
> noise (!?!) (speker-test is running)

I also get like a "laser gun" sound followed by a transition to lower fre=
nquency
 when:
- CAPTURE level is not null
- swithching SPDIF out from unmuted to muted

The higher the CAPTURE level is, the highest is the laser gun sound, at v=
ery low
level this doesn't sound like a laser gun sound anymore

When speaker-test is playing on left, i have a mix between the distorded =
sound
and this "laser gun" sound, but with higher frenquency for laser sound
when playing on rigth, i have the inverse: laser gun sound @ lowest frequ=
ency...



>
> > "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine wav=
e.
> speaker-test 1.0.8
> speaker-test: invalid option -- t
> Unknown option '?'
>
>
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUN=
K!
> > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@...
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dcick
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, 14.12.2005 at 10:27 +0000, James Courtier-Dutton wrote:

> "speaker-test -c6 -Dplug:surround51" will output pink noise.
> "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine wave.

Hmmm ... "-t" option is not available, I have speaker-test 1.0.8

Which leads me to a question: I have been building and installing all
the ALSA modules, from latest CVS, but I haven't updated my other ALSA
utilies, i.e. whatever comes in the Debian packages alsa-base and
alsa-utils:

ii  alsa-base      1.0.8-7        ALSA driver configuration files
ii  alsa-oss       1.0.8-1        ALSA wrapper for OSS applications
ii  alsa-source    1.0.8-7        ALSA driver sources
ii  alsa-utils     1.0.8-4        ALSA utilities

Would this matter??

I've also modified your patch, James, because the serial is different on
my card, which I've labelled as 'SBdavee' in my case:

- ------------------------------------------------------------------------
azimuth:/usr/src/alsa/alsa-kernel/pci/ca0106# cvs diff -u
cvs diff: Diffing .
Index: ca0106_main.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/pci/ca0106/ca0106_main.c,v
retrieving revision 1.27
diff -u -r1.27 ca0106_main.c
- --- ca0106_main.c       1 Dec 2005 10:49:58 -0000       1.27
+++ ca0106_main.c       14 Dec 2005 19:24:42 -0000
@@ -188,6 +188,16 @@
           .name   = "MSI K8N Diamond MB [SB0438]",
           .gpio_type = 1,
           .i2c_adc = 1 } ,
+        /* SB Audigy SE is a SB Live 24bit without AC97 */
+        /* Fixes alsa-bug #1636 */
+        { .serial = 0x100a1462,
+          .name   = "SB Audigy SE [SBxxxx]",
+          .gpio_type = 1,
+          .i2c_adc = 1 } ,
+        { .serial = 0x100a1102,
+          .name   = "SB Audigy SE [SBdavee]",
+          .gpio_type = 1,
+          .i2c_adc = 1 } ,
         /* Shuttle XPC SD31P which has an onboard Creative Labs Sound Blaster Live! 24-bit EAX
          * high-definition 7.1 audio processor".
          * Added using info from andrewvegan in alsa bug #1298
@@ -197,7 +207,7 @@
           .gpio_type = 1,
           .i2c_adc = 1 } ,
         { .serial = 0,
- -          .name   = "AudigyLS [Unknown]" }
+          .name   = "AudigyLS [ReallyUnknown]" }
 };
 
 /* hardware definition */
- ------------------------------------------------------------------------

I added the label 'ReallyUnknown' when I started trouble-shooting,
because /proc/asound/cards was telling me I have "AudigyLS [Unknown]"
and I wanted to be sure that it was because the card detection was
really falling through to this default setting!  It was at that point I
noticed that the serial number for my card was 0x100a1102 and not
0x100a1462 as in your patch, so I added the extra section to your
source: I don't really understand the source, but I guess what I've done
makes sense.

Anyway, having done all that, I get no sound at all now, apart from
white-noise when setting 'SPDIF Out' in the mixer.  All other things,
including speaker-test, fail to make any noise whatsoever ... :-/

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDoHNZnhBnac0o2pIRApMaAJ9UUvC7aI83ETVYG5drs2laPXtElwCdFilK
Dp5OXeilOCYCA18qYLr5x78=
=IqM1
-----END PGP SIGNATURE-----

Quoting chgans@...:

> Quoting chgans@...:
>
> > Quoting James Courtier-Dutton <James@...>:
> > >
> > > "speaker-test -c6 -Dplug:surround51" will output pink noise.
> > I get noise when SPDIF out is Muted, nothing when unmuted.
> >
> > In alsamixer, the volume of the analog front output modify the freque=
ncy of
> > the
> > noise (!?!) (speker-test is running)
>
> I also get like a "laser gun" sound followed by a transition to lower
> frenquency
>  when:
> - CAPTURE level is not null
> - swithching SPDIF out from unmuted to muted
>
> The higher the CAPTURE level is, the highest is the laser gun sound, at=
 very
> low
> level this doesn't sound like a laser gun sound anymore
>
> When speaker-test is playing on left, i have a mix between the distorde=
d
> sound
> and this "laser gun" sound, but with higher frenquency for laser sound
> when playing on rigth, i have the inverse: laser gun sound @ lowest
> frequency...

I have connected a 5.1 speaker system, and launch "speaker-test -c6
-Dplug:surround51" again:
- for each channel, i get the distorded sound in the coresponding speaker
- each channel volume control modulates the sound only for the corespondi=
ng
channel (ie: front left volume control modulate the sound played by
test-speaker only if it is played on the front left channel)
- the "laser gun" sound can be heard only on front rigth and left channel=
, not
on the others.

Just a remark, this card is a 7.1 output.

regards,
Christian

>
>
>
> >
> > > "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine w=
ave.
> > speaker-test 1.0.8
> > speaker-test: invalid option -- t
> > Unknown option '?'
> >
> >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through =
log
> > files
> > > for problems?  Stop!  Download the new AJAX search engine that make=
s
> > > searching your log files as easy as surfing the  web.  DOWNLOAD SPL=
UNK!
> > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> > > _______________________________________________
> > > Alsa-user mailing list
> > > Alsa-user@...
> > > https://lists.sourceforge.net/lists/listinfo/alsa-user
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUN=
K!
> > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dcick
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@...
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
>
>
>

Quoting chgans@...:

> Quoting chgans@...:
>
> > Quoting James Courtier-Dutton <James@...>:
> > >
> > > "speaker-test -c6 -Dplug:surround51" will output pink noise.
> > I get noise when SPDIF out is Muted, nothing when unmuted.
> >
> > In alsamixer, the volume of the analog front output modify the freque=
ncy of
> > the
> > noise (!?!) (speker-test is running)
>
> I also get like a "laser gun" sound followed by a transition to lower
> frenquency
>  when:
> - CAPTURE level is not null
> - swithching SPDIF out from unmuted to muted
>
> The higher the CAPTURE level is, the highest is the laser gun sound, at=
 very
> low
> level this doesn't sound like a laser gun sound anymore
>
> When speaker-test is playing on left, i have a mix between the distorde=
d
> sound
> and this "laser gun" sound, but with higher frenquency for laser sound
> when playing on rigth, i have the inverse: laser gun sound @ lowest
> frequency...

Here is another update:

I have connected a 5.1 speaker system and launch speaker-test:
- each volume

>
>
>
> >
> > > "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine w=
ave.
> > speaker-test 1.0.8
> > speaker-test: invalid option -- t
> > Unknown option '?'
> >
> >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through =
log
> > files
> > > for problems?  Stop!  Download the new AJAX search engine that make=
s
> > > searching your log files as easy as surfing the  web.  DOWNLOAD SPL=
UNK!
> > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> > > _______________________________________________
> > > Alsa-user mailing list
> > > Alsa-user@...
> > > https://lists.sourceforge.net/lists/listinfo/alsa-user
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUN=
K!
> > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dcick
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@...
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
>
>
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, 14.12.2005 at 19:32 +0000, Dave Ewart wrote:

> On Wednesday, 14.12.2005 at 10:27 +0000, James Courtier-Dutton wrote:
> 
> > "speaker-test -c6 -Dplug:surround51" will output pink noise.
> > "speaker-test -t2 -c6 -Dplug:surround51" will output a clean sine wave.
> 
> Hmmm ... "-t" option is not available, I have speaker-test 1.0.8
> 
> Which leads me to a question: I have been building and installing all
> the ALSA modules, from latest CVS, but I haven't updated my other ALSA
> utilies, i.e. whatever comes in the Debian packages alsa-base and
> alsa-utils:
> 
> ii  alsa-base      1.0.8-7        ALSA driver configuration files
> ii  alsa-oss       1.0.8-1        ALSA wrapper for OSS applications
> ii  alsa-source    1.0.8-7        ALSA driver sources
> ii  alsa-utils     1.0.8-4        ALSA utilities
> 
> Would this matter??

James: following your post indicating that you've had the new driver
working successfully followinga arrival of the card from Creative, I
still find that it doesn't work for me.

I previously asked the question above about my general ALSA setup, which
no-one replied to.  Do I need ALSA *everything* from CVS, or just the
drivers?

I'm getting 'laser-gun' like sound when doing a speaker-test (either a
six-channel or a two-channel output).  The driver appears to have loaded
cleanly, however:

# cat /proc/asound/cards 
 0 [CA0106         ]: CA0106 - CA0106
                      Audigy SE [SB0570] at 0xdf00 irq 5

# lspci -vv
0000:01:08.0 Multimedia audio controller: Creative Labs SB Audigy LS
        Subsystem: Creative Labs: Unknown device 100a
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (500ns min, 5000ns max)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at df00 [size=32]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

# lsmod
Module                  Size  Used by
snd_ca0106             33764  1 
snd_rawmidi            26464  1 snd_ca0106
snd_seq_device          8908  1 snd_rawmidi
snd_ac97_codec         97696  1 snd_ca0106
snd_pcm_oss            54176  0 
snd_mixer_oss          19712  1 snd_pcm_oss
snd_pcm                95240  3 snd_ca0106,snd_ac97_codec,snd_pcm_oss
snd_timer              26500  1 snd_pcm
snd                    59236  10 snd_ca0106,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              10400  1 snd
snd_ac97_bus            2176  1 snd_ac97_codec
snd_page_alloc         10952  2 snd_ca0106,snd_pcm
nvidia               3921916  12 
ipv6                  265728  12 
parport_pc             35908  1 
lp                     12420  2 
parport                37832  2 parport_pc,lp
eth1394                20168  0 
ohci1394               35508  0 
ieee1394              305080  2 eth1394,ohci1394
amd74xx                13852  0 [permanent]
ehci_hcd               36168  0 
ohci_hcd               22212  0 
i2c_nforce2             6784  0 
i2c_core               22288  1 i2c_nforce2
ide_scsi               17860  0 
tsdev                   7872  0 
mousedev               12064  1 
psmouse                30852  0 
ide_generic             1280  0 [permanent]
ide_disk               19072  0 
ide_cd                 42692  0 
cdrom                  40544  1 ide_cd
ide_core              130004  5 amd74xx,ide_scsi,ide_generic,ide_disk,ide_cd
forcedeth              19392  0 
evdev                   9792  0 
unix                   29104  246

Where do I go from here?  It would be really nice to have this sound
working before Christmas :-)

Thanks in advance for any assistance,

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDqbjvnhBnac0o2pIRAjduAJ9esTbC0KKFgKQSDFHgUMMgDbb8IQCg50l6
vjNAImvA4eD5Xc35bKAP/OA=
=EmQg
-----END PGP SIGNATURE-----

Dave Ewart wrote:
>>
>>ii  alsa-base      1.0.8-7        ALSA driver configuration files
>>ii  alsa-oss       1.0.8-1        ALSA wrapper for OSS applications
>>ii  alsa-source    1.0.8-7        ALSA driver sources
>>ii  alsa-utils     1.0.8-4        ALSA utilities
>>
>>Would this matter??
> 
> 
> James: following your post indicating that you've had the new driver
> working successfully followinga arrival of the card from Creative, I
> still find that it doesn't work for me.
> 
> I previously asked the question above about my general ALSA setup, which
> no-one replied to.  Do I need ALSA *everything* from CVS, or just the
> drivers?
> 

Dave,

I would install everything from CVS.
alsa-driver:
./cvscompile --with-cards=ca0106
make
make install

alsa-lib
./cvscompile --prefix=/usr
make
make install

alsa-utils
./cvscompile --prefix=/usr
make
make install

Then at least you will be on the same versions at me and we can diagnose 
this further.

James

On 21/12/05, Dave Ewart <davee@...> wrote:
>
>
> I'm getting 'laser-gun' like sound when doing a speaker-test (either a
> six-channel or a two-channel output).  The driver appears to have loaded
> cleanly, however:
>
>
I noticed a problem with my last patch.
The latest CVS should fix it.

James

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, 21.12.2005 at 22:40 +0000, James Courtier-Dutton wrote:

> > I'm getting 'laser-gun' like sound when doing a speaker-test (either
> > a six-channel or a two-channel output).  The driver appears to have
> > loaded cleanly, however:
>
> I noticed a problem with my last patch.  The latest CVS should fix it.

Hmmm, still doesn't seem to work here.  Also, I appear to be hitting
circular dependencies when trying to build the entire ALSA tree as you
suggested ...

I've spent about as much time as I can on this one, and unfortunately I
think I'm gonna have to give up on this for now and go back to my
onboard sound chip, which I know works, although it's a little shaky.

Many thanks for your assistance James, much appreciated: shame it
doesn't quite work for me.

Never mind ...

Cheers,

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDq8gtnhBnac0o2pIRAkzuAKCoGHZwDlvp4DPVxNRkeQQXPWvrFACdExKB
zsxssTQWFge3R+JNwWF2wa0=
=eg3z
-----END PGP SIGNATURE-----

Dave Ewart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday, 21.12.2005 at 22:40 +0000, James Courtier-Dutton wrote:
> 
> 
>>>I'm getting 'laser-gun' like sound when doing a speaker-test (either
>>>a six-channel or a two-channel output).  The driver appears to have
>>>loaded cleanly, however:
>>
>>I noticed a problem with my last patch.  The latest CVS should fix it.
> 
> 
> Hmmm, still doesn't seem to work here.  Also, I appear to be hitting
> circular dependencies when trying to build the entire ALSA tree as you
> suggested ...
> 

Dave,

To be able to install alsa-driver from CVS, you have to have compiled 
your own kernel, otherwise alsa-driver will not build.

I assumed that alsa-lib builds ok.

James

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday, 23.12.2005 at 11:01 +0000, James Courtier-Dutton wrote:

> >Hmmm, still doesn't seem to work here.  Also, I appear to be hitting
> >circular dependencies when trying to build the entire ALSA tree as you
> >suggested ...
> >
> 
> To be able to install alsa-driver from CVS, you have to have compiled 
> your own kernel, otherwise alsa-driver will not build.

I have my own kernel build - the alsa-driver section builds cleanly, as
it has done throughout my previous testing with the ca0106 driver.

> I assumed that alsa-lib builds ok.

No - it fails here, for what it's worth:

# ./cvscompile --prefix=/usr

[...]

make[1]: Entering directory `/usr/src/alsa/alsa-lib/alsalisp'
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src/alisp    -O2 -Wall -W -pipe -g -c alsalisp.c
make[1]: *** No rule to make target `../src/libasound.la', needed by `alsalisp'.  Stop.
make[1]: Leaving directory `/usr/src/alsa/alsa-lib/alsalisp'
make: *** [all-recursive] Error 1

I have the following 'libasound' packages already installed:

ii  libasound2     1.0.8-3        ALSA library
ii  libasound2-dev 1.0.8-3        ALSA library development files

which are the current packages from Debian / Sarge.

Dave.
- -- 
Dave Ewart - davee@... - jabber: davee@...
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDq9umnhBnac0o2pIRAmlUAJ4iomyTi2UKjS++jeez3V18qqJPZwCgqxPQ
DtgeO9Hb4bcS4YTAMF7H3AY=
=IUwI
-----END PGP SIGNATURE-----

On Wed, 2005-12-21 at 20:58 +0000, James Courtier-Dutton wrote:
> Dave Ewart wrote:
> >>
> >>ii  alsa-base      1.0.8-7        ALSA driver configuration files
> >>ii  alsa-oss       1.0.8-1        ALSA wrapper for OSS applications
> >>ii  alsa-source    1.0.8-7        ALSA driver sources
> >>ii  alsa-utils     1.0.8-4        ALSA utilities
> >>
> >>Would this matter??
> > 
> > 
> > James: following your post indicating that you've had the new driver
> > working successfully followinga arrival of the card from Creative, I
> > still find that it doesn't work for me.
> > 
> > I previously asked the question above about my general ALSA setup, which
> > no-one replied to.  Do I need ALSA *everything* from CVS, or just the
> > drivers?
> > 
> 
> Dave,
> 
> I would install everything from CVS.
> alsa-driver:
> ./cvscompile --with-cards=ca0106
> make
> make install
> 
> alsa-lib
> ./cvscompile --prefix=/usr
> make
> make install
> 
> alsa-utils
> ./cvscompile --prefix=/usr
> make
> make install
> 
> Then at least you will be on the same versions at me and we can diagnose 
> this further.
> 

It's probably easier to just to do:

cvs co .
./build prep
./build all

etc.

Lee