quodlibet
Playback follows selection for albums
This behavior is very counter-intuitive to me, but I'm not 100% sure, maybe it's intended? Filing as a bug, but feel free to correct me if that's a mistake.
Steps to reproduce
"Follow Cursor" plugin is not enabled, nor selected as a play order.
Works in these views:
- Cover grid
- Album list
- Album collection (artist folders in place of albums)
- Paned browser (artist folders in place of albums)
Play any track from an album, then (single-)click a different album to select it. After that, wait for the current track to finish or press the "next" button.
Expected Output
Playback order is not affected by current selection
Actual Output
First track of currently-selected album plays
Test System
Which version of Quod Libet?
4.6.-1 (git)
Which operating system
Fedora 35
If it's audio-related, what back-end?
Pipewire 0.3.49
Additional Information
I sometimes like to look through my library while listening to music; checking tags, picking what to listen to next, etc. But with this behavior, I have to remember to press ctrl-J before the track is over, or some random track will start playing instead.
It doesn't matter which track is selected, it always skips to the first track in the selected album. Clicking around with the playing album has no effect. Selecting any number of other albums, then navigating back to the playing album before the track advances, results in a normal advance to the next track (i.e. no effect).
Running with --debug, I see these messages whenever I select a different album:
D: 96.575: PlaylistModel.set: Filling view model with 11 songs.
D: 96.989: PlaylistModel.set: Filling view model with 11 songs.
D: 97.913: PlaylistModel.set: Filling view model with 13 songs.
D: 98.244: PlaylistModel.set: Filling view model with 11 songs.
D: 98.754: PlaylistModel.set: Filling view model with 9 songs.
D: 99.840: PlaylistModel.set: Filling view model with 42 songs.
D: 00.826: PlaylistModel.set: Filling view model with 13 songs.
Seems to coincide perfectly with what get played next. This should happen when an album gets double-clicked, but not single-clicked, no?
Essentially I think this is expected behaviour (albeit a bit confusing for sure).
Some suggestions on what other users sometimes do:
- Use the queue proactively - to enqueue things to listen to, then browse around (queue takes preference by default)
- browse around with secondary browsers to leave the primary one to playing,
- use the Queue Only plugin to get behaviour closer to what you want (I think)
Cool, I know QL has had this behavior forever, so it makes sense that it was intentional. Out of curiosity, can you share why it works this way?
I was never able to get the Queue Only plugin to work. I'll take another look, maybe I'm remembering wrong.
I wonder if it would be possible to make a new play-order plugin, such that the selection has no effect on playback. Kind of like a polar opposite to "playback follows cursor". I might take a look in my spare time.
Apr 5, 2022 4:36:24 PM Nick Boultbee @.***>:
Essentially I think this is expected behaviour (albeit a bit confusing for sure).
Some suggestions on what other users sometimes do:
-
Use the queue proactively - to enqueue things to listen to, /then/ browse around (queue takes preference by default)
-
browse around with secondary browsers to leave the primary one to playing,
-
use the /Queue Only/ plugin to get behaviour closer to what you want (I think)
— Reply to this email directly, view it on GitHub[https://github.com/quodlibet/quodlibet/issues/3968#issuecomment-1089313350], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AB6TPN62MSAJ73XWGRBKH2DVDSP4NANCNFSM5SRB2AKA]. You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/AB6TPNYJAUHQA7MSFSFRA3DVDSP4NA5CNFSM5SRB2AKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIDWZURQ.gif]