12-01-2018, 04:05 PM
Hi,
Feature #2 is very similar to the way the Up Next queue works in iTunes. There have been several requests in the past that are are related for example:
a) insert track or album into the Playlist following the currently playing or last played track
b) select multiple tracks to be added by offering a check box after each track
Currently the Library offers the [Add, Play, Clear/Play] context menu when tapping the cover art or individual track. The cover art can represent the Entire Collection, Genre, Artist or individual Album.
I had (a) on the TODO list but will also look into doing something like your Feature #2 since it kind of does (b).
Feature #1 is non-trivial due to the structure of the data used to populate the Library list and cover panels. Its a JSON array (4 dimensions) thats generated on the server (Pi). It contains the entire MPD database.
When the client Browser opens the Library list/covers this array is loaded entirely into the Browser's memory. The benefit is fast navigation in the Library panel. The disadvantage is that tag substitution, sorting or other types of data manipulation for example prefixing Album with Year involve regenerating the JSON array on the server.
The Library works well for collections that use typical Popular Music tagging e.g., Genre | Artist | Album or AlbumArtist | Song, but does not lend itself to Classical collections which are typically organized by Composer tag or by some other tag that is manually used to represent Composition.
There may be ways to make it more flexible but I'm not seeing anything obvious yet. It probably needs another dev to take a look at the code from a fresh perspective.
-Tim
Feature #2 is very similar to the way the Up Next queue works in iTunes. There have been several requests in the past that are are related for example:
a) insert track or album into the Playlist following the currently playing or last played track
b) select multiple tracks to be added by offering a check box after each track
Currently the Library offers the [Add, Play, Clear/Play] context menu when tapping the cover art or individual track. The cover art can represent the Entire Collection, Genre, Artist or individual Album.
I had (a) on the TODO list but will also look into doing something like your Feature #2 since it kind of does (b).
Feature #1 is non-trivial due to the structure of the data used to populate the Library list and cover panels. Its a JSON array (4 dimensions) thats generated on the server (Pi). It contains the entire MPD database.
Code:
// generate library {Genre1: {Artist1: {Album1: [{song1}, {song2}], Album2:...}, Artist2:...}, Genre2:...}When the client Browser opens the Library list/covers this array is loaded entirely into the Browser's memory. The benefit is fast navigation in the Library panel. The disadvantage is that tag substitution, sorting or other types of data manipulation for example prefixing Album with Year involve regenerating the JSON array on the server.
The Library works well for collections that use typical Popular Music tagging e.g., Genre | Artist | Album or AlbumArtist | Song, but does not lend itself to Classical collections which are typically organized by Composer tag or by some other tag that is manually used to represent Composition.
There may be ways to make it more flexible but I'm not seeing anything obvious yet. It probably needs another dev to take a look at the code from a fresh perspective.
-Tim
