GNOME Bugzilla – Bug 638943
Remove gapless setting (keep it always on)
Last modified: 2020-03-17 08:49:07 UTC
Looking at our bug reports most of our users are enabling gapless. Perhaps we should consider enabling it by default. Pros: Users are using it and consider it vital functionality. Cons: It seems to cause problems for playback in certain cases. Also the unit tests were likely written before gapless arrived or do not consider any impact it has. The code looks to have a lot of workarounds in place which could prove problematic.
*** Bug 638942 has been marked as a duplicate of this bug. ***
I thought gapless was already on by default, and unless some of the bigger "depends on" bugs are fixed before 2.0, I really think it should be off by default for that release. Another one to add to the list is Bug 619970 (and the possible duplicate: Bug 621222). Gapless has a tendency to double not only scrobbles, but play counts in the library as well, which can cause problems with the Unheard smart playlist.
Actually it appears to be, I must have tested with an old gconf profile in place. http://git.gnome.org/browse/banshee/tree/src/Backends/Banshee.GStreamer/Banshee.GStreamer/PlayerEngine.cs#n859 But then let's track this to see if we should flip this off for 2.0 unless we can fix the issues with it.
For 2.1/2.2 I'd like to remove this option, and have it always enabled. We now require recent enough gst to make this happen. I also want to nuke libbanshee, so we'll need to reimplement/test the gapless playback in the gst# backend.
(In reply to comment #4) > For 2.1/2.2 I'd like to remove this option, and have it always enabled. We now > require recent enough gst to make this happen. Renaming summary to map to this endeavor instead (happening real soon now).
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.