Lowlander wrote:I presume that any implementation would be global to the Media Server, ie. if you'd set <Title> as <#> - <Title> it would be for all shared content in that Media Server as otherwise it would get overly complex to setup.
I think the intention of the feature request is to be more granular than that.
Ie have a way of using the tags to define the views you want in the folder hierarchy you want, where you want them.
that said some constraints to aid coding simplicity are workable I believe.
The use cases,and views I can think of that are personally usefull to me as DLNA user are:
Track/File Sort Order
Perhaps dynamic mapping of library to upnp tags could provide for all use cases, without need for granular configuration.
For audio views with content from only 1 album prefix dc:title with %track number%. ie '%tacknumber%. %tracktitle%'.
For audio views with content from more than 1 album prefix dc:title with %Album% - %Tracknumber%.
For audio views with content from more than 1 artist prefix dc:title with %artist% - %album% - %track number%.
For TV views with episodes in a single show/season prefix dc:title with 'Episode Number' - Title
all the way to TV views with episodes from multiple shows prefix dc:title with %Series% - %Season% - %Episode%.
Useful For/When
(this is useful for all users whose renderer doesn't sort track number (of which there are many).
Recent Lists and tag mapping
Whenever a folder of the type 'recent list' is being shown, prefix objects with MM's understanding of 'most recent' through numbered prefix.
This prefix sort tagging would be updated by MM as more recent items were added to the library. (and thus be reflected on the renderer as it refreshed its view of the recent list).
Useful For/When
Users want to see recent TV / Music / Podcasts that have been added to the library rather than browse a filesystem folder hierarchy.
It wouldnt be a big constraint if Recent Podcasts, Recent TV Shows, Recent Movies had to be separate objects to ease coding.
Example detail
Folder hierarchy/groupings
There is a more fundamental requirement just to define the folder hierachy, that is browsed through dlna to help structure and find desired content.
It might help for MM to have the concept of a video file being a TVSHOW or A Movie.
Allowing the user to define say up to 5 levels/groupings for a view in a collection.
Eg for TV
Level 1 - {Series}
Level 2 - {Seasons} in show
Level 3 - {Titles} in season
or
Eg for Movies
Level 1 - {Genres}
Level 2 - {Years} in genre
Level 3 - {Titles} in year
For the TV example
I would like to define dc:Title as {EpisodeNumber}-{Title} to ensure sort order again.
So perhaps for a given section of the collection, the ability to define the library- upnp tag mappings for the section would suffice.
otherwise the constraint that tag mappings were defined at the collection level would work (users might have to have separate tv and movies collections to get meaningful views)
Useful For/When
TV would be good to browse by Series, Seasons, Episodes (but episode titles need to be in sort order).
Movies might be good to organise by Genre then Title...or another user might want Genre, then Year, then Title
Subdivison of Folder hierachy
For each point in the hierachy, the option to define subdivision when necessary would be very useful.
Showing all movies which contains 1500 objects is not useful.
In the example of a folder 'All Movies', where there is only 1 grouping level presented as say '{title} {year}' with 1500 movies.
It would be useful to split the view into 'Titles beginning Numbers, Titles beginning A, Titles Beginning B....'
If too complex to configure subdivision 'per level of hierachy' or 'per collection', then a system wide setting to subdivide 'the hierarchy - levels' with more than X objects would be great.
MM seems to already do this for eg Entire Library - Title.
so I guess its a balance between user bang for buck of coding and workability in terms of user interface.
Subdivision algorithms could be system wide.
Library to Upnp tag mappings i think have to be per collection (at worst) or perhaps dynamic based on rules.
but could be hard coded just for particularly useful dlna views , recent tv, recent movies, recent podcasts.
[quote="Lowlander"]I presume that any implementation would be global to the Media Server, ie. if you'd set <Title> as <#> - <Title> it would be for all shared content in that Media Server as otherwise it would get overly complex to setup.[/quote]
I think the intention of the feature request is to be more granular than that.
Ie have a way of using the tags to define the views you want in the folder hierarchy you want, where you want them.
that said some constraints to aid coding simplicity are workable I believe.
The use cases,and views I can think of that are personally usefull to me as DLNA user are:
[b]Track/File Sort Order[/b]
Perhaps dynamic mapping of library to upnp tags could provide for all use cases, without need for granular configuration.
For audio views with content from only 1 album prefix dc:title with %track number%. ie '%tacknumber%. %tracktitle%'.
For audio views with content from more than 1 album prefix dc:title with %Album% - %Tracknumber%.
For audio views with content from more than 1 artist prefix dc:title with %artist% - %album% - %track number%.
For TV views with episodes in a single show/season prefix dc:title with 'Episode Number' - Title
all the way to TV views with episodes from multiple shows prefix dc:title with %Series% - %Season% - %Episode%.
[i]Useful For/When[/i]
(this is useful for all users whose renderer doesn't sort track number (of which there are many).
[b]Recent Lists and tag mapping[/b]
Whenever a folder of the type 'recent list' is being shown, prefix objects with MM's understanding of 'most recent' through numbered prefix.
This prefix sort tagging would be updated by MM as more recent items were added to the library. (and thus be reflected on the renderer as it refreshed its view of the recent list).
[i]Useful For/When[/i]
Users want to see recent TV / Music / Podcasts that have been added to the library rather than browse a filesystem folder hierarchy.
It wouldnt be a big constraint if Recent Podcasts, Recent TV Shows, Recent Movies had to be separate objects to ease coding.
Example detail
[img]https://dl.dropbox.com/u/84611964/Sortorder.jpg[/img]
[b]Folder hierarchy/groupings[/b]
There is a more fundamental requirement just to define the folder hierachy, that is browsed through dlna to help structure and find desired content.
It might help for MM to have the concept of a video file being a TVSHOW or A Movie.
Allowing the user to define say up to 5 levels/groupings for a view in a collection.
Eg for TV
Level 1 - {Series}
Level 2 - {Seasons} in show
Level 3 - {Titles} in season
or
Eg for Movies
Level 1 - {Genres}
Level 2 - {Years} in genre
Level 3 - {Titles} in year
For the TV example
I would like to define dc:Title as {EpisodeNumber}-{Title} to ensure sort order again.
So perhaps for a given section of the collection, the ability to define the library- upnp tag mappings for the section would suffice.
otherwise the constraint that tag mappings were defined at the collection level would work (users might have to have separate tv and movies collections to get meaningful views)
[i]Useful For/When[/i]
TV would be good to browse by Series, Seasons, Episodes (but episode titles need to be in sort order).
Movies might be good to organise by Genre then Title...or another user might want Genre, then Year, then Title
[b]Subdivison of Folder hierachy[/b]
For each point in the hierachy, the option to define subdivision when necessary would be very useful.
Showing all movies which contains 1500 objects is not useful.
In the example of a folder 'All Movies', where there is only 1 grouping level presented as say '{title} {year}' with 1500 movies.
It would be useful to split the view into 'Titles beginning Numbers, Titles beginning A, Titles Beginning B....'
If too complex to configure subdivision 'per level of hierachy' or 'per collection', then a system wide setting to subdivide 'the hierarchy - levels' with more than X objects would be great.
MM seems to already do this for eg Entire Library - Title.
so I guess its a balance between user bang for buck of coding and workability in terms of user interface.
Subdivision algorithms could be system wide.
Library to Upnp tag mappings i think have to be per collection (at worst) or perhaps dynamic based on rules.
but could be hard coded just for particularly useful dlna views , recent tv, recent movies, recent podcasts.