pulseaudio-0.9.15-10.fc11.x86_64 gstreamer-0.10.22-3.fc11.x86_64 rhythmbox-0.12.0-5.fc11.x86_64 Here's the scenario: 0. Enable Rhythmbox crossfading backend, set rb volume to 50%, close rhythmbox 1. Desktop quiet, gnome-volume-control-applet shows volume at 55% 2. Start rhythmbox - rb's volume control reads 50% 3. Press play 4. g-v-c-a jumps to 93%. OW THIS IS REALLY LOUD. 5. Quickly adjust g-v-c-a to 50%. [Time passes] 6. Pause song. 7. Press play. Volume jumps to 93% again (goto 4). You can also cause the volume jump by clicking on rhythmbox's volume control button. Volume does *not* jump unexpectedly when the crossfading backend is disabled.
The second case - volume jumps when using the volume control in rhythmbox - still happens if the crossfade backend is disabled. Alas. Also, please note that the rb volume control has to be *changed* - moved up or down - to trigger the problem.
Should be fixed in 0.12.0.92, could you please test before I try to get this version tagged? http://koji.fedoraproject.org/koji/buildinfo?buildID=99125
Confirmed - this build fixes the volume jumps when hitting play/pause while using the crossfade plugin. (The volume still jumps around when I use the rb volume control, but I suppose that's a different bug.)
Tagging requested. https://fedorahosted.org/rel-eng/ticket/1610#preview
I'm not as irate as I used to be. BUT THIS IS A **!*!&!&! HEALTH HAZARD, and seems to be present in my fedora 11 rhythmbox. THIS IS UNACCEPTABLE. I seriously think I may have permanently damanged my hearing because of this. Not as much as the GNR+metallica concert I went to back in '93. But that was a willing choice. Seriously, there need to be measures taken to prevent ANYTHING like this bug from ever happening again, presumably in alsa/pulse. This bug needs to be reopened and assigned to F11 NOW. (I have a track record of making loud comments that turn out to be some problem with my environment. I consider this a serious enough issue that I don't care about getting egg on my face if I'm wrong) At least put a comment in the bug explaining how to reset gconf, reinstall whatever, blow away whatever file to undo this.