Bug 229110 - MTP-devices: No subdirectories get created for artists/albums
Summary: MTP-devices: No subdirectories get created for artists/albums
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/MTP player (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-02 11:28 UTC by Jonathan Herdt
Modified: 2022-11-17 05:12 UTC (History)
4 users (show)

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 Jonathan Herdt 2010-03-02 11:28:11 UTC
Version:           2.2.2.90 (using 4.3.4 (KDE 4.3.4), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.33-0.slh.4-sidux-amd64

This is somehow an epilogue to https://bugs.kde.org/show_bug.cgi?id=176858
When sending files to an mtp-device the files are stored correctly in the MUSIC-folder but without the creation of subfolders for the artist and / or the album. Amarok is not the only application I explore my mtp-device with and it is a cumbersome task to delete a single album when all files are in one folder.
Comment 1 Wyatt Epp 2014-02-21 16:54:27 UTC
I think this may be higher than just a wishlist, because the vFAT filesystems on most external devices don't really cope well with hundreds (let alone thousands!) of files in a single directory. ;)

But I'd actually like to go even further and ask for an option to preserve my collection's directory structure when transferring the selected tracks (standard vFAT filename mangling rules apply, of course).

Currently, I have a janky process that sort of works where I export a playlist and run it through a shell script to make the necessary directories, do filename fixes, and copy the files to their destinations; but it's slow, inconvenient, and pretty much hacked-together crap.  I'd very much prefer a built-in solution in Amarok.

Background: My music collection is not a single flat hierarchy of $artist/$album/(? $disk/)$song.  Since about 2003 or so, I've first organised it into broad categories/sub-categories according to my own personal preferences (e.g. FM and PSG, Orchestral, Automata, 同人, etc.) and then continuing with directories for individual artists and albums.  This was originally motivated by poor filesystem performance with several hundred artist directories, but it also benefits me when navigating my collection tree with a shell or file browser (moderately frequently) and it's useful to get "sort of close" quickly.  

This structure follows me to all of my environments: my desktop, with my "main" collection; my personal laptop, with a moderate subset; and at work, where I have to rely on PortableApps playing music from my Rockbox iPod because of company computer policy.  (That last one has forced me to use the directory view much more often and prompted this wall of text.)
Comment 2 Dainius Masiliūnas 2014-02-21 20:41:32 UTC
Hmm? This bug is about MTP transfers. If you have access to regular FAT filesystems, then you can select what directory structure to create in collection options. For your preference directories, it sounds like it's all Genre – so clean up your tags to list those things as Genre and then set the collection to be stored as Genre/Artist/Album/Track (or Genre/Album Artist/Album/Track, for multi-artist albums).
Comment 3 Wyatt Epp 2014-02-25 11:29:41 UTC
(In reply to comment #2)
> Hmm? This bug is about MTP transfers.

Ah, so it is.  Then I'll open a new one.

I still think the priority of this should be higher than wishlist.  Regardless of how these devices present themselves, their underlying storage is very likely to be vFAT, which copes with thousands of files in a single directory...very, very poorly.
Comment 4 postix 2022-10-18 17:57:07 UTC
Is this still an issue?
Comment 5 Bug Janitor Service 2022-11-02 05:05:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-11-17 05:12:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!