View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019582 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2022-11-23 11:53 | 2025-12-25 14:04 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | feedback | Resolution | reopened | ||
| Target Version | 2026 | Fixed in Version | 2024.0 | ||
| Summary | 0019582: Mask: Extend <Playlist> mask to support hierarchical playlist | ||||
| Description | We can extend <Playlist> mask to support hierarchical playlist The simplest solution would be to add <Playlist:?> where ? would be number of sub-playlist hierarchical path eg. like in example from 0016540 Track sync Mask "\Music\<Playlist:3>\<Auto Number>. <Artist> - <Title>" would result in file hierarchically "\Music\Tear 1\Tear2\Playlist 1\<Auto Number>. <Artist> - <Title>" Playlist sync Mask "\<Playlist:3>\" would be "\Tear 1\Tear2\Playlist 1.m3u" Default value would be 0 for compatibility. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2800 | ||||
|
|
Fixed in 2800 |
|
|
Verified 2804 |
|
|
I think this would probably work better as a on/off trigger. ie. you either created a folder hierarchy based on the MediaMonkey Playlist node or you don't. Would there be any benefit of allowing the user to limit it to for example 3 folders deep if they have 5 deep in the Library? |
|
|
Note that by default whole hierarchy is added so that user doesn't need to use <Playlist:X> at all --> i.e. just in case he really wants or needs to limit it.. So I think it works fine as is. |
|
|
@lowlander pointed out to review, I agree with him that this would be useful. Also I think that like <Folder> mask playlist hierarchical behavior should be same as like noted in 0016540 Some user would like to sync Playlist structure on USB for Car or to have export tracks for import in external devices/applications. |