Bug 224345 - Individual file naming scheme configuration for each collection
Summary: Individual file naming scheme configuration for each collection
Status: RESOLVED DUPLICATE of bug 197573
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.2.2
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-26 17:16 UTC by Fabian Köster
Modified: 2010-01-26 22:57 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 Fabian Köster 2010-01-26 17:16:55 UTC
Version:           2.2.2 (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

I am experiencing the following problem:

I organised the files of my music collection on my computer using the format:

Collection Root/Artist/Year - Album/Track - Title.extension

In addition I have a Car Radio which can play MP3 and Ogg Vorbis files (VDO DAYTON TR7327B) but finds files only in "flat folders" (tree-depth 0 or 1) on SD-Cards or USB-sticks.

So I would like to copy music directly from Amarok to my USB-stick using the following scheme:

Collection Root/Artist - Album/Track - Title.extension

The problem with current Amarok (2.2.2) is, that it only allows to define a single naming scheme which will be applied every time I copy files to any collection and I therefore have to change it every time when I switched from one collection to another.

Amarok should support individual file naming schemes for each collection.
Comment 1 Myriam Schweingruber 2010-01-26 21:49:27 UTC

*** This bug has been marked as a duplicate of bug 197373 ***
Comment 2 Fabian Köster 2010-01-26 22:17:07 UTC
> *** This bug has been marked as a duplicate of bug 197373 ***

This is not a duplicate of bug #197373. A mistake?
Comment 3 Myriam Schweingruber 2010-01-26 22:57:28 UTC
Oops, my bad, wrong bug number. Sorry for the noise.

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