Bug 124733 - different model to manage files
Summary: different model to manage files
Status: RESOLVED DUPLICATE of bug 122672
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4-beta2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-02 09:55 UTC by Manuel Rodriguez
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Rodriguez 2006-04-02 09:55:25 UTC
Version:           1.4-beta2 (using KDE 3.5.2 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.8-default

I've lately discovered amarok's feature to manage the music files. It's a really usefull feature, but if you have many different genres, which should all be managed in a different way, it would be usefull to have the ability to save models. I'll give an example: All my classical music shall be organized with the format "%folder/%genre/%composer/%artist/%album/%track %title.%filetype". So I save a it as a model and call it "Classics". Another model could be "%folder/%genre/Compilations/%album/%track %title.%filetype" for Compilations. So everytime I want to manage some classical files, I choose the model "Classics", for compilations I choose "Compilations. These themes can individually be saved and changed. The user doesn't have to fill in the %composer-tag everytime he wants to organize sth. classical, for albums with many discs he doesn't have to fill in the %discnumber-tag everytime. It would save a lot of writing work.
Comment 1 Martin Aumueller 2006-04-10 08:32:21 UTC

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