GNOME Bugzilla – Bug 647960
Volume is reset when a new track starts to play
Last modified: 2020-03-17 09:19:29 UTC
How to reproduce: 1. play a song 2. Turn down the volume with the volume control in the banshee window 3. wait until the song is over -> For the new song the volume is back to a default value I have replay gain disabled gapless playback enabled in case that's important. I'm not sure if this is a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=613726 and https://bugzilla.gnome.org/show_bug.cgi?id=646411
Same problem here, Banshee 2.6.0 on Linux. Please set to CONFIRMED. (No progress over 17 releases and 18 months time since 2.0.0 and this report? Are there only the two of us hit by this?)
(In reply to comment #1) > Same problem here, Banshee 2.6.0 on Linux. > > Please set to CONFIRMED. Actually, the volume is reset to 100% only when skipping to a new track. If the track finishes naturally, volume is kept. Reproducable: always This is actually a different issue than the origial report, so I might file a different bug.
This bug is kind of similar to bug 686908. That bug has a patch in there, do you guys mind testing that patch? Thanks
this happens for me on Ubuntu 12.10, but not on Ubuntu 12.04, and happens on any track advance.
let me amend that: it appears to happen on any natural advance *while in Fullscreen Mode* and also triggered by the Screensaver I normal window mode, the volume persists across normal track changes, although not all the time, and not incrementally, it is fine for a few tracks, then bam, it's back up at 100%
I know everyone hates null results, but I've confirmed that the problem persists in Ubuntu Unity-2D, LXDE and Gnome Classic desktops, and the Rhythmbox player (which isn't as nice imho) even retains its volume setting between hard reboots.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.