Summary: | random feature is broken in amarok2 (SVN) | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | David <StormByte> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | lfranchi |
Priority: | NOR | ||
Version: | 2.0-SVN | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David
2008-07-14 03:31:05 UTC
I've discovered more things in this issue. It seems that random is broken *only* is repeat is NOT disabled (i.e. selected repeat playlist, or albums), when repeat is off, random works as expected. Can someone review this? I've tried wih a clean amarok install (deleting all amarok related files from ~/.kde Yeah. To reproduce: add however many songs you like, enable random->track, repeat->track, click next until you reach end of a playlist absolutely sequentially. This is fixed now. Thank you for your report. I reopen. I've tested in svn rev 849896 and it is still present. Tested with repeat -> playlist and random -> tracks. Absolutely secuential here. Also, with trepeat -> playlist and random -> tracks, when a song finishes, the *same* song is played again. If you press manually next, then, that undesired secuential behavior is shown. Maybe it's worth rewritting from scratch that playlist management (random and repeat)? Ok more testing: It works here if dynamic mode is turned off and repeat is turned off. One could argue that random is pointless if you have dynamic mode enabled anyway. But it at least should work if you have repeat playlist enabled and dynamic mode disabled. (In reply to comment #7) > Ok more testing: It works here if dynamic mode is turned off and repeat is > turned off. > > One could argue that random is pointless if you have dynamic mode enabled > anyway. > But it at least should work if you have repeat playlist enabled and dynamic > mode disabled. > If never touched the Dynamic option, and by default is false, so this is really an important bug though :) *** This bug has been marked as a duplicate of bug 168594 *** |