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 at 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 at braille.uwo.ca >-=> http://speech.braille.uwo.ca/mailman/listinfo/speakup >-=> > > >Name: Terry D. Cudney >Phone: (905)735-6127 >E-mail: terry at CottageInWasaga.com -or- tcudney at 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 at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup
