Summary: | m3u playlists mess up the collection | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Matthias Weiss <matias.liberta> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | lfranchi, nhn |
Priority: | NOR | ||
Version: | 2.0-rc | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matthias Weiss
2008-12-04 11:40:57 UTC
Matthias, could you please retry this with a more recent version, like 2.0.1.1 or perhaps even current trunk and report back if the issue still persists? Sorry Nikolaj for the delay. Yes, still buggy. I played around with it a bit and it seems that having .m3u files together with the mp3, ogg or flac files starts the troubles. A second cause seems to be installing the .m3u files after the initial setup. Here is what I've tried: 1.) I'm starting with all amarok configs cleaned out (rm -fr .kde4/share/apps/amarok .kde4/share/config/amarok* ) 2.) I add the ~/tmp directory as the collection root directory. In the tmp directory tree (the usual Artist/Album structure) there are only audio files, no .m3u playlists. 3.) I finish initial configuration and quit amarok. 4.) Then I move the .m3u files in the collection, e.g. "Artist 1 - Album 1.m3u" into "~/tmp/Artist 1/Album 1/" directory. As you see, I have 1playlist per album. 5.) When I start amarok afterwards it scans my collection and starts messing up: those tracks I've listed in the .m3u files are gone in my "Local Collection" tree. 6.) After quitting amarok and restarting it gets messier: Now suddenly in "Local Collection" I have a "Various Artists" entry with an "unknown" album which has no tracks. The tracks from the .m3u files are still missing and even more tracks are lost from one artist. It appeared to me, that having more than 1 playlist per artist could be the cause, so I tried all 6 steps with only 1 playlist per artist but t he result was the same. Then I had the idea that this bug happens only when I have a playlist from an artist where I have more than 1 album so I repeated the 6 steps from before but added only .m3u files from artists where I have only 1 album. Unfortunately, the bug stayed the same. Than I tried it again with a change in step 2.), now I have all .m3u files installed right from the start. And suddenly the bug is gone. Last I tried it again with audio files (mp3, ogg, etc.) seperated from the .m3u files and made a change to the directory structure: now I have the audio files in "~/tmp/music/Artist 1/Album 1/" etc. and the playlists in "~/tmp/playlists/Artist 1 - Album 1.m3u". I did the same 6 steps like before (starting with no .m3u files in "~/tmp" ) but in step 4.) I move the whole playlists directory from outsideinto "~/tmp/playlists". There is no bug with this seperation of audio and .m3u files. Oh, I forgot: I'm running amarok svn 935422 from debian experimental. This report is still unconfirmed since it's report 4 months ago. Can somebody reproduce it with 2.1 beta1 or SVN?? I'd like to check it again but currently there is no new version of amarok in debian experimental. As you can see from commend #2, in mid march the bug was still there. Matthias, for what I know there is a new version in the Debian experimental repository, please try that one and report back. I retested with 2.0.96 and the bug is still the same. Confirmed then. Could this be a MIME-type mismatch? No, I doubt it's a MIME-type issue. I just tested it again, starting again with no amarok config and this time having the audio files (mp3, ogg, flac) together with the m3u files (every m3u file in the appropriate album directory) right at the initial collection scan. I see no bug with this setup. So I suspect that the collection update routine has some troubles when in a directory it allready knows there are suddenly some m3u files added. this sounds like another dupe of https://bugs.kde.org/show_bug.cgi?id=178973 In that bug the mess isn't caused by the playlists but by the rescan itself. *** This bug has been marked as a duplicate of bug 178973 *** |