Bug 120082 - juk random album play oddities
Summary: juk random album play oddities
Status: RESOLVED LATER
Alias: None
Product: juk
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-14 05:29 UTC by Marcelo Vanzin
Modified: 2021-03-10 04:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Vanzin 2006-01-14 05:29:01 UTC
Version:           2.3 (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
Compiler:          gcc (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux) 
OS:                Linux

When using random album play on juk, some of the app's behavior is kinda odd:

- when first starting the application and starting playback, the first song of an album is chosen; when that song is finished, juk changes to another random album, instead of continuing to play the first one.

- when starting playback of an album from a song that is not the first one (by using the playlist), juk cycles back to the first song of the album until all tracks are played; so if you start to play an album with 5 tracks at track 3, juk will play "3 1 2 4 5", while I'd expect it to play "3 4 5" and the switch to the next one.

Adding a little bit to the second case above, I think that when the user interacts with the playlist directly, the state of the "random album" support should be reset; so that if the user chooses to replay the song that just played manually, he doesn't end up in some weird loop.
Comment 1 Michael Pyne 2010-05-10 06:48:10 UTC
Took a crack at it but my first attempt is crashy. Maybe in 4.5.2. :-/
Comment 2 Justin Zobel 2021-03-09 06:26:56 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.