Threaded Mode | Linear Mode

simbun · 28-12-2022, 21:14

I just caught that I wasn't actually indexing AlbumArtist, I was using AlbumArtistSort instead (and labelling it) because I thought it would be a lighter operation to just change the .displayFormat rather then the .value and .sort attributes.

(28-12-2022 14:48)simoncn Wrote: The selection of auto index art for AlbumArtist index entries is based on items in the index selection, not albums.

This bit confused me, but from what you said subsequently I assume you just meant that it's based on entries from the [n] items and not from [n] albums index, even though that index may not actually be shown because of the listViewAlbums setting?

(28-12-2022 14:48)simoncn Wrote: This means the artwork search order is the search order described for audio files in this section, so a disc image would be used in preference to an album image.

Similarly, the artwork selection order for AlbumArtist index entries is based on items.sortTags, not Album.sortTags. It should be similar to the order that the user would see in the 'n items' list.

I hadn't compared it to the Artist index before because I don't use it, but I'm not seeing any difference, is that correct bearing in mind the original quote?

Quote:For example, the Artist index entry for Pink Floyd will show an album cover from one of the Pink Floyd albums in your library

If the Artist index is supposed to show Album artwork I find it surprising that the AlbumArtist wouldn't given that the Artist index could include track artists. If Artist is supposed to work I could easily use this instead of AlbumArtist as I always have AlbumArtist populated.

(28-12-2022 14:48)simoncn Wrote: The code for choosing an automatic image for an artist or album artist needs to be simple and efficient because it is run for all entries in an Artist or AlbumArtist container when the user selects Artist or AlbumArtist. For example, clicking on Artist for an artist container that contains 1000 artists runs this code 1000 times before showing anything to the user. MinimServer works internally on lists of items and this is why an item-based approach is used. This is the reason for the "as far as possible" disclaimer in the User guide description.

Given how performant MinimServer is I thought you might be storing the sort order during the initial file index, but if you're doing it realtime then I completely understand!

Thanks for taking the time to respond.