I just switched to raspbian today and noticed a very dangerous little bug. The sound driver doesn't seem to be able to keep the volume of the soundcard at a set level. I've looked around a bit for anyone having a similar problem and seemed to notice most people had "no sound" or "not the best sound" and that luckily nobody else has managed to almost blow out their eardrums. Hopefully I've posted this before anybody gets hurt.
Story goes as follows
Flashed Raspbian to card
first order of business is to play music
taking lessons from previous experience with command line music, alsamixer, set master volume to 15% for safety.
playback at 100% volume
check alsamixer, volume reads at 15%
okay, we have a little problem.
I now have a severe pain in my left ear and sensitivity to sound. Permanent damage? probably not. Should we fix this before giving it to school children? Definitely!
I haven't gotten past being able to reproduce bug on demand yet, as I went strait for posting it after a few tests. However I will be happy to post the required information on demand, I'm a linux power user so don't be afraid to ask for even the most obscure of system logs.
However, I will post the results of my tests to date.
After a first fruitless attempt at using vlc, I chmod 7777 the /dev/snd directory and everything in it. This worked, vlc played sound. The volume is set to 15% for safety but playback is at maximum. I open lxterminal and run alsamixer.I jab the 2 key quick to drop down to 20% the volume quickly starts behaving itself until the song finishes and vlc moves on to the next one. I am forced to alsamixer the sound down to 20% again even though it shows the mixer being at that level already. I drop down to a console and test with omxplayer. The sound is at 100% again. close out of omxplayer to check levels in alsamixer still at 20%. I install oss-compat so I can compile and run an mp3 player I wrote in C that uses hip_decode from libmp3lame. pumping decoded pcm buffers into /dev/dsp at 44khz, stereo, signed 16bit little endian samples produces the same general behavior as omxplayer. Here I start to suspect the driver itself rather than any particular player. and then it was over to raspberrypi forum.
Anybody else experiencing this bug? Any particular information you would like me to post? Thanks in advance.