I noticed the same thing. Watch the little seek bar carefully as it switches to the next song! It goes down to a high percentage of the song time before going back down to zero. It looks like Amarok is unaware that the track has switched or something, and continues to play from a time equal to the end of the previous song, before kicking back to the beginning. So it tried to read an impossible time from a track, gives up (because that SHOULDN'T work), and skips the song.

grrrv wrote:edit: The skipped track are not completely skipped, but it seems like Amarok plays 1-5 seconds from the end of the track. (Of course, on many tracks this would be silence.)

As far as I'm concerned, Amarok plays the beggining...

grrrv wrote:edit2: I did some testing and it looks like a track is skipped if it's shorter than the previous track, even if the previous track had been skipped too.

I can confirm that! Interesting

anthon wrote:

grrrv wrote:edit: The skipped track are not completely skipped, but it seems like Amarok plays 1-5 seconds from the end of the track. (Of course, on many tracks this would be silence.)

As far as I'm concerned, Amarok plays the beggining...

Likewise (definitely beginning is played for me).

grrrv wrote:edit2: I did some testing and it looks like a track is skipped if it's shorter than the previous track, even if the previous track had been skipped too.

Yup, exactly the same here.

mliddle wrote:

grrrv wrote:edit2: I did some testing and it looks like a track is skipped if it's shorter than the previous track, even if the previous track had been skipped too.

Yup, exactly the same here.

It's so obvious now!

mliddle wrote:

anthon wrote:

grrrv wrote:edit: The skipped track are not completely skipped, but it seems like Amarok plays 1-5 seconds from the end of the track. (Of course, on many tracks this would be silence.)

As far as I'm concerned, Amarok plays the beggining...

Likewise (definitely beginning is played for me).

Hmm. In my tests so far it's definitely been the end of the song. What a weird bug...

As a temporary workaround I tried adding a very short track (I used Kyuss - Yeah (0:04)) whenever a song is followed by a shorter one in the playlist. Now the Kyuss track is skipped entirely and the rest of the playlist plays fine. A silly hack, but it works

seems fixed in trunk

tek wrote:seems fixed in trunk

Not for me BUT (using trunk)
I have a couple of albums in my collection with all tracks displayed 0:00 in the playlist. (scan problem? whatever) So 0:00 is displayed, but tracks are ok when played.
And for those tracks, the "shorter track rule" doesn't apply. Amarok does not skip.
My 2 cents

I installed from the Ubuntu nightly builds (Project Neon PPA) and the problem appears fixed.

I did some testing and seems that the problem was related to the Now Playing plasmoid. Removing the widget on my desktop solved the problem.

uicz wrote:I did some testing and seems that the problem was related to the Now Playing plasmoid. Removing the widget on my desktop solved the problem.

Indeed o_O

uicz wrote:the problem was related to the Now Playing plasmoid. Removing the widget on my desktop solved the problem.

Wow, looks like you're right.   Well that's one widget I won't be touching again.

Interesting. Was it because your CPU load was going through the roof while the plasmoid was running? I experience same problem (CPU load) on OS X, but only if that particular plasmoid is set to run on launch of Amarok.
If I start it after Amarok is running, I don't have the same problem. Could someone try that, please?

No particular CPU load for me... And launching the plasmoid after Amarok doesn't change anything (still skipping).

it also seems to lock plasma completely when amarok is scanning stuff like playlists or collections