Bug 208429 - juk-jump tracks in playlist
Summary: juk-jump tracks in playlist
Status: RESOLVED DUPLICATE of bug 204391
Alias: None
Product: juk
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-24 21:15 UTC by Dimitrios Glentadakis
Modified: 2011-05-05 03:52 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitrios Glentadakis 2009-09-24 21:15:37 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Mandriva RPMs

sometimes (but very often) juk jumps some tracks in the playlist. it goes to the next song but only for 1 second and immediatly jumps to the after next.
Comment 1 Davide Cendron 2009-10-06 22:32:37 UTC
I confirm the same bug on Gentoo AMD64, with KDE 4.3.1 (it's a quite annoying bug *_* )
Comment 2 Nilli 2009-10-25 10:34:36 UTC
I suspect the bug is caused by fade-in and/or fade-out. The first few days of using JuK (a few weeks ago) the tracks faded into each other, but that gradually got replaced by playing a few seconds of the next track only to abruptly skip to a third track. My JuK no longer fades any tracks at all.

I'm using a playlist of 18 tracks from almost as many different folders, with the settings "Loop Playlist" and "Use Random Play".
Comment 3 Oleg Cukanov 2009-12-01 19:18:39 UTC
I encounter this problem when playing Ogg Vorbis

Track time to finish, but the progress bar is 2-3 seconds, begins to play the next track.When the playback indicator reaches the end, begins to play the third track.Every second track virtually skipped.

Noticed an arbitrary change in the volume of sound by a small amount
Comment 4 Davide Cendron 2009-12-02 17:19:22 UTC
This bug seems to be a duplicate of http://bugs.kde.org/show_bug.cgi?id=204391 (mark as fixed)
Comment 5 Michael Pyne 2011-05-05 03:52:10 UTC

*** This bug has been marked as a duplicate of bug 204391 ***