Bug 222157 - Bookmarks from *.cue file
Summary: Bookmarks from *.cue file
Status: RESOLVED DUPLICATE of bug 187587
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.2.1
Platform: Mandriva RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-11 02:01 UTC by Dmitry
Modified: 2010-01-11 10:43 UTC (History)
0 users

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 Dmitry 2010-01-11 02:01:21 UTC
Version:           2.2.1 (using KDE 4.3.2)
OS:                Linux
Installed from:    Mandriva RPMs

(Sorry for my bad english)

I have audio file and cue-file (with "cue" extension). cue-file defines bookmarks (subtracks) for audio file. If I will add this audio file to a playlist then Amarok automatically will be use cue-file to show bookmarks. It is good, but doesn't work if I add same audio file from scanned collection (musik library).

How to Reproduce:
1) First, place audio file with corresponding cue-file in same directory, this directory must not be included as a part of collection. Open audio file => Amarok shows bookmarks (don't close Amarok to avoid rescaning collection at starting Amarok and disable automatic rescaning).
2) Second, move files to collection directory, open => Amarok shows bookmarks.
3) Next, go to the options and force Amarok to rescan collection, open => Amarok doesn't show bookmarks.

Expected Behaviour:
It is a good idea to show for playing song current bookmark from cue-file. But for different bookmarks may be assigned different names of songs and performers. So, this behaviour may be in incompatibility with idea of groupping songs by performer or album, because the name of performer or/and album may change from bookmark to bookmark while playing one audio file.
Comment 1 Myriam Schweingruber 2010-01-11 10:43:34 UTC

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