alsa settings: I'm really mad!

alsa settings: I'm really mad!

[Cheryl Homiak]

Ok, has anybody ever had this happen, especially anybody using debian?
Al my setting were just fine and I didn't change them. but just now I couldn't
get my sound to work, even with using alsactl restore. Have to do everything
over again; all my settings are gone.
It has to be that something that upgraded in debian woody when I did my "apt-get
update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
this is ubelievable!
Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
settings have to be redone!

Re: alsa settings: I'm really mad!

[Charles Hallenbeck]

Cheryl -

Alsa is tough enough to tame without that happening too! I have
never had any similar experience on this Slackware system.
Chuck

On Mon, 29 Apr 2002, Cheryl Homiak wrote:

> Ok, has anybody ever had this happen, especially anybody using debian?
> Al my setting were just fine and I didn't change them. but just now I couldn't
> get my sound to work, even with using alsactl restore. Have to do everything
> over again; all my settings are gone.
> It has to be that something that upgraded in debian woody when I did my "apt-get
> update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
> this is ubelievable!
> Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
> settings have to be redone!
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
Visit me at http://www.valstar.net/~hallenbeck
The Moon is Waning Gibbous (86% of Full)

Re: alsa settings: I'm really mad!

[Terry Cudney]

Hi Cheryl, Chuck and everyone,

	My experience is not exactly the same as Cheryl's, but similar...

	Although running Debian, and doing the apt-get upgrade, etc I can't attribute it to Debian (at least I don't think so). With alsa 0.9beta11 and beta 12 I experienced difficulties with the alsamixer, such that capture was set "on" on multiple channels without my being able to detect that using speakup. I'm sure that a sighted person using alsamixer would have noticed immediately that the capture was "on" on more than one channel. It is possible that I inadvertently set the capture-on, but I don't think so. I believe that there is a big bug in alsamixer in beta 11 and 12.

	Anyway, in Debian, when you shut down/restart your system the mixer settings from the current session are saved in /etc/asound.state and these settings are used to initialize the sound card on next startup. If the settings re messed up and you restart the system for some reason, the asound.state file retains the messed up settings for subsequent sessions.

	My solution: Once I had my alsa settings the way I wanted them, I did an "alsactl store", then I went to /etc and copied the asound.state file to asound-state.good. Now, if ever the settings get messed up again, I'll just copy the asound-state.good back to asound.state, do an "alsactl restore" and carry on.


HTH,

	--terry

You wrote:

-=> Cheryl -
-=>
-=> Alsa is tough enough to tame without that happening too! I have
-=> never had any similar experience on this Slackware system.
-=> Chuck
-=>
-=> On Mon, 29 Apr 2002, Cheryl Homiak wrote:
-=>
-=> > Ok, has anybody ever had this happen, especially anybody using debian?
-=> > Al my setting were just fine and I didn't change them. but just now I couldn't
-=> > get my sound to work, even with using alsactl restore. Have to do everything
-=> > over again; all my settings are gone.
-=> > It has to be that something that upgraded in debian woody when I did my "apt-get
-=> > update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
-=> > this is ubelievable!
-=> > Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
-=> > settings have to be redone!
-=> >
-=> >
-=> > _______________________________________________
-=> > Speakup mailing list
-=> > Speakup@braille.uwo.ca
-=> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
-=> >
-=>
-=> --
-=> Visit me at http://www.valstar.net/~hallenbeck
-=> The Moon is Waning Gibbous (86% of Full)
-=>
-=>
-=> _______________________________________________
-=> Speakup mailing list
-=> Speakup@braille.uwo.ca
-=> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-=>


Name:	Terry D. Cudney
Phone:	(905)735-6127
E-mail:	terry@CottageInWasaga.com -or- tcudney@sympatico.ca
WWW:	www.CottageInWasaga.com

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html

Having a smoking section in a restaurant is like...
having a peeing sectionin a swimming pool.

Re: alsa settings: I'm really mad!

[Igor Gueths]

Hi Terry and all. This is why I'm not a big fam of alsamixer, although amixer is good. If I hit m on a control, it just says M. It doesn't say mute or unmute. In terms of the capture thing, I would set that using amixer, then finetune things with alsamixer. I just mak sure not to press other keys while tuning the settings so not to adjust things you didn't want to. 
----- Original Message ----- 
From: Terry Cudney <tcudney@sympatico.ca>
To: speakup <speakup@braille.uwo.ca>
Sent: Tuesday, April 30, 2002 7:43 AM
Subject: Re: alsa settings: I'm really mad!


> Hi Cheryl, Chuck and everyone,
> 
> My experience is not exactly the same as Cheryl's, but similar...
> 
> Although running Debian, and doing the apt-get upgrade, etc I can't attribute it to Debian (at least I don't think so). With alsa 0.9beta11 and beta 12 I experienced difficulties with the alsamixer, such that capture was set "on" on multiple channels without my being able to detect that using speakup. I'm sure that a sighted person using alsamixer would have noticed immediately that the capture was "on" on more than one channel. It is possible that I inadvertently set the capture-on, but I don't think so. I believe that there is a big bug in alsamixer in beta 11 and 12.
> 
> Anyway, in Debian, when you shut down/restart your system the mixer settings from the current session are saved in /etc/asound.state and these settings are used to initialize the sound card on next startup. If the settings re messed up and you restart the system for some reason, the asound.state file retains the messed up settings for subsequent sessions.
> 
> My solution: Once I had my alsa settings the way I wanted them, I did an "alsactl store", then I went to /etc and copied the asound.state file to asound-state.good. Now, if ever the settings get messed up again, I'll just copy the asound-state.good back to asound.state, do an "alsactl restore" and carry on.
> 
> 
> HTH,
> 
> --terry
> 
> You wrote:
> 
> -=> Cheryl -
> -=>
> -=> Alsa is tough enough to tame without that happening too! I have
> -=> never had any similar experience on this Slackware system.
> -=> Chuck
> -=>
> -=> On Mon, 29 Apr 2002, Cheryl Homiak wrote:
> -=>
> -=> > Ok, has anybody ever had this happen, especially anybody using debian?
> -=> > Al my setting were just fine and I didn't change them. but just now I couldn't
> -=> > get my sound to work, even with using alsactl restore. Have to do everything
> -=> > over again; all my settings are gone.
> -=> > It has to be that something that upgraded in debian woody when I did my "apt-get
> -=> > update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
> -=> > this is ubelievable!
> -=> > Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
> -=> > settings have to be redone!
> -=> >
> -=> >
> -=> > _______________________________________________
> -=> > Speakup mailing list
> -=> > Speakup@braille.uwo.ca
> -=> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -=> >
> -=>
> -=> --
> -=> Visit me at http://www.valstar.net/~hallenbeck
> -=> The Moon is Waning Gibbous (86% of Full)
> -=>
> -=>
> -=> _______________________________________________
> -=> Speakup mailing list
> -=> Speakup@braille.uwo.ca
> -=> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -=>
> 
> 
> Name: Terry D. Cudney
> Phone: (905)735-6127
> E-mail: terry@CottageInWasaga.com -or- tcudney@sympatico.ca
> WWW: www.CottageInWasaga.com
> 
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
> 
> Having a smoking section in a restaurant is like...
> having a peeing sectionin a swimming pool.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: alsa settings: I'm really mad!

['Georgina']

Hi

Sorry, not much help but I'm a Debian Woody user and upgraded Sunday
night and haven't experienced the same.
Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>Cheryl -
>
>Alsa is tough enough to tame without that happening too! I have
>never had any similar experience on this Slackware system.
>Chuck
>
>On Mon, 29 Apr 2002, Cheryl Homiak wrote:
>
>> Ok, has anybody ever had this happen, especially anybody using debian?
>> Al my setting were just fine and I didn't change them. but just now I couldn
't
>> get my sound to work, even with using alsactl restore. Have to do everything
>> over again; all my settings are gone.
>> It has to be that something that upgraded in debian woody when I did my "apt
-get
>> update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
>> this is ubelievable!
>> Amixer and alsamixer still work and alsa apparently still gets loaded, but a
l my
>> settings have to be redone!
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
>-- 
>Visit me at http://www.valstar.net/~hallenbeck
>The Moon is Waning Gibbous (86% of Full)
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: alsa settings: I'm really mad!

['Georgina']

Hi
Well this is really strange.  I usually do a apt-get dist-upgrade and
I'm using alsa's beta 10.  But I can't see how the apt process can
affect a program that isn't part of its database.  Surely it wouldn't
touch the asound.state?  Surely its down to the alsa version or a
program that I do not have and one that you two share?

I wonder if our start up procedure is different too?  I've created a
file in /usr/local/bin called start which sets speakup speech rate loads
brltty and alsactl restore.  I've created a soft link to that file in
/etc/rc2.d/S10start.  Can't remember why I used a value of 10 but that's
how I've done it.

BTW:  I've also put a say line so that rsynth will invite me to log in.

Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>Hi Cheryl, Chuck and everyone,
>
>	My experience is not exactly the same as Cheryl's, but similar...
>
>	Although running Debian, and doing the apt-get upgrade, etc I can't att
ribute it to Debian (at least I don't think so). With alsa 0.9beta11 and beta 1
2 I experienced difficulties with the alsamixer, such that capture was set "on"
 on multiple channels without my being able to detect that using speakup. I'm s
ure that a sighted person using alsamixer would have noticed immediately that t
he capture was "on" on more than one channel. It is possible that I inadvertent
ly set the capture-on, but I don't think so. I believe that there is a big bug 
in alsamixer in beta 11 and 12.
>
>	Anyway, in Debian, when you shut down/restart your system the mixer set
tings from the current session are saved in /etc/asound.state and these setting
s are used to initialize the sound card on next startup. If the settings re mes
sed up and you restart the system for some reason, the asound.state file retain
s the messed up settings for subsequent sessions.
>
>	My solution: Once I had my alsa settings the way I wanted them, I did a
n "alsactl store", then I went to /etc and copied the asound.state file to asou
nd-state.good. Now, if ever the settings get messed up again, I'll just copy th
e asound-state.good back to asound.state, do an "alsactl restore" and carry on.
>
>
>HTH,
>
>	--terry
>
>You wrote:
>
>-=> Cheryl -
>-=>
>-=> Alsa is tough enough to tame without that happening too! I have
>-=> never had any similar experience on this Slackware system.
>-=> Chuck
>-=>
>-=> On Mon, 29 Apr 2002, Cheryl Homiak wrote:
>-=>
>-=> > Ok, has anybody ever had this happen, especially anybody using debian?
>-=> > Al my setting were just fine and I didn't change them. but just now I co
uldn't
>-=> > get my sound to work, even with using alsactl restore. Have to do everyt
hing
>-=> > over again; all my settings are gone.
>-=> > It has to be that something that upgraded in debian woody when I did my 
"apt-get
>-=> > update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff ou
t.
>-=> > this is ubelievable!
>-=> > Amixer and alsamixer still work and alsa apparently still gets loaded, b
ut al my
>-=> > settings have to be redone!
>-=> >
>-=> >
>-=> > _______________________________________________
>-=> > Speakup mailing list
>-=> > Speakup@braille.uwo.ca
>-=> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>-=> >
>-=>
>-=> --
>-=> Visit me at http://www.valstar.net/~hallenbeck
>-=> The Moon is Waning Gibbous (86% of Full)
>-=>
>-=>
>-=> _______________________________________________
>-=> Speakup mailing list
>-=> Speakup@braille.uwo.ca
>-=> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>-=>
>
>
>Name:	Terry D. Cudney
>Phone:	(905)735-6127
>E-mail:	terry@CottageInWasaga.com -or- tcudney@sympatico.ca
>WWW:	www.CottageInWasaga.com
>
>Please avoid sending me Word or PowerPoint attachments.
>See http://www.fsf.org/philosophy/no-word-attachments.html
>
>Having a smoking section in a restaurant is like...
>having a peeing sectionin a swimming pool.
>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: alsa settings: I'm really mad!

[Toby Fisher]

On Mon, 29 Apr 2002, Cheryl Homiak wrote:

> Ok, has anybody ever had this happen, especially anybody using debian?
> Al my setting were just fine and I didn't change them. but just now I couldn't
> get my sound to work, even with using alsactl restore. Have to do everything
> over again; all my settings are gone.
> It has to be that something that upgraded in debian woody when I did my "apt-get
> update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
> this is ubelievable!
> Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
> settings have to be redone!

Hmmm, I don't use Debian so don't know about this, but does this apdget
thing have an option that just tells you what it's going to do, rather
than doing it?  It's one of the things I like about the Slakware pkgtool,
there is a --warn option which tells you in full detail which
files/directories will be added/created/modified/overwritten/deleted etc.
Call me paranoid, but I really prefer this whenever possible, unless I'm
installing a lot of packages, for example the whole of X.

It's also why I've backed up my /etc/asound.conf, I can send it if you
want, you should then only have to change what you need.  Write to me
privately if this will help.

Cheers.

-- 
Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: alsa settings: I'm really mad!

[jwantz]

Hi,,
I don't see that apt-get had anything to do with your problem.  I had 
the same thing happen to me using Redhat long before I installed apt for 
rpm.  As somebody already suggested the best solution is to have a 
backup of your good alsa.state or alsa.conf file.

      Jim Wantz
On Wed, 1 May 2002, 
Toby Fisher wrote:

> On Mon, 29 Apr 2002, Cheryl Homiak wrote:
> 
> > Ok, has anybody ever had this happen, especially anybody using debian?
> > Al my setting were just fine and I didn't change them. but just now I couldn't
> > get my sound to work, even with using alsactl restore. Have to do everything
> > over again; all my settings are gone.
> > It has to be that something that upgraded in debian woody when I did my "apt-get
> > update' and "apt-get upgrade" wiped my alsa or at least alsactl stuff out.
> > this is ubelievable!
> > Amixer and alsamixer still work and alsa apparently still gets loaded, but al my
> > settings have to be redone!
> 
> Hmmm, I don't use Debian so don't know about this, but does this apdget
> thing have an option that just tells you what it's going to do, rather
> than doing it?  It's one of the things I like about the Slakware pkgtool,
> there is a --warn option which tells you in full detail which
> files/directories will be added/created/modified/overwritten/deleted etc.
> Call me paranoid, but I really prefer this whenever possible, unless I'm
> installing a lot of packages, for example the whole of X.
> 
> It's also why I've backed up my /etc/asound.conf, I can send it if you
> want, you should then only have to change what you need.  Write to me
> privately if this will help.
> 
> Cheers.
> 
>