amarok playlist error

Bug #119776 reported by Mario Young on 2007-06-11
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)

Bug Description

Binary package hint: amarok

hello developers:

Im having a problem with the amarok, everytime i add an album to the reproduction list that have more than 1 cd, the music player reproduced the 1st song from the 1st cd then jump over to the 1st song from the 2nd cd, then goes back to the 1st song of the 1st cd again, and so & so instead of reproduce the 2nd song of the 1st cd.

I think that amarok should recognize that the next song belongs to the same cd of the current song and of the same album.


Áron Sisak (asisak) wrote :

Thanks for reporting this bug. Which version of (K)Ubuntu and Amarok are you running?
I tried to reproduce this issue with latest Gutsy packages and failed.

Changed in amarok:
assignee: nobody → asisak
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Mario Young (mayeco) wrote :

I'm runing feisty, kde 3.5.7, amaroK 1.4.5

Áron Sisak (asisak) wrote :

Apparently we seem to run the same Amarok version. Are you sure everything is fine with disc number tags?

Mario Young (mayeco) wrote :

Try this:

1. take 4 mp3 files and put it in a folder
2. Tag the files with the album "DEMO"
3. Tag 2 files with disc number 1 and track number 1 and 2
4. Tag 2 other files with disc number 2 and track number 1 and 2
5. Add this 4 files to the playlist and play in "Random Album" mode

What my amarok does is play the frist track then jump to the 1 track with the tag cd numer 2 and GO BACK to the 1 track with the cd number 1 and loop forever.

Amarok random

See this files with the tags I use:

download and put it in your playlist in "Random Album" and "Repeat Playlist" mode and see what happend and just see amaroK.

Áron Sisak (asisak) wrote :

Sorry I was not aware of the "random album" mode.

Thanks for reporting this bug, nice catch! :)

Changed in amarok:
assignee: asisak → nobody
status: Needs Info → Confirmed
Andrew Ash (ash211) wrote :

In order for this bug to now be fixed, it must be reported upstream to Amarok developers for Amarok 2.0 Please file this bug again at against Amarok and then provide a link to that bug here so we can track it in launchpad.


Áron Sisak (asisak) wrote :

Actually it has been reported upstream. I was not familiar with KDE bug tracking.
I think reporting bugs upstream is more useful instead of adding a comment that this should be reported upstream... :).

Mario Young (mayeco) wrote :

The guys in think this bug is "trifles"


Changed in amarok:
status: Unknown → Rejected
Changed in amarok:
status: Confirmed → Rejected
Changed in amarok:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.