Yes, except [Last Played] by itself generally returns different values for audio files (played) and image files (played = viewed). I need [Last Played (album)] to return the same value to both audio and image files in the current album in order for it to be useful as a common sort target. Same for
LastPlayedAlbum(mode).
I store album covers and artwork in files adjacent to my audio files, in a simple, usual, shallow Music > Artist > Album file structure.
I want "global" views of the album art which are sorted in the same way, 1-1, as the audio views.
Examples:
One tab with Audio view sorted by Most Recently Played and another tab with Image View of the covers and artwork sorted in the same order. Both are View As: Categories, grouped by [album].
Most Recently Added Audio <--> Most Recently Added Images
Artists Audio <--> Artists Images
Year (released) Audio <--> Year (released) Images
I have implemented all these synchronizations easily (each has View As: Categories, Expression to Group By = ...[album]...) with MC's view sorting capability, except the Most Recently Played has been a real challenge.
All the sorts are very fast, except for Most Recently Played because it is O(N
2) as discussed extensively in the later parts of the Reference.
Summary: I am looking for a synchronized O(N) sort for Most Recently Played, which means I need an O(1) method of finding Last Played in each album, and the identical result must be automatically distributed to both audio and image files whenever a change occurs.
A mouthful! But I really like the way these sorts look
.
PS: One could envision extending this concept to include document files, for a last played synchronized view of other album materials.