Repository navigation
More proper implementation of embedded art priority - #349
Merged
Merged
Conversation
Owner
Author
Closed
Contributor
|
This isnβt really constructive, but as a new user, I'd have no idea what the wizard is talking about, and I kind of still don't right now |
Contributor
|
Also Im confused by what the visuals could possibly mean/be referring to |
β¦when changing images from content view
Owner
Author
Just refresh the whole list :))
β¦ration for user set/unset + fix dyn playlist cover set/unset
Owner
Author
Contributor
|
nitpick but maybe there isn't a reason to add the subtitle explaining why euphonica needs it, perhaps put the explanation in a tooltip behind a help icon ( |
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Sequence
This is like, what, the 6th iteration of our album art loading algorithm? Hopefully the last.
When embedded-art optimisation is on, this matches the v0.99.6 behaviour of fetching just one image per folder, be it a
coverfile or a random track's embedded art. With that turned off, we STILL prefer thecoverfile, but now if one does not exist, we fetch every track's embedded art individually.Custom album arts are keyed at the track URI level if said optimisation is disabled (just like external sources or embedded art from MPD). Assuming the library remains constant and MPD doesn't change its behaviour, then the representative track for each album (fetched with window size 1) should always be the first track, and by using its URI as the embedded key of that album, the custom arts should be persisted across boots. This allows customising album arts even in libraries that don't follow the one-release-per-folder rule.
General guidelines
cover.{png,webp,jpg}file as Euphonica will just read the embedded art of one track and use it for all other tracks too.Optimise embedded cover loading), andcover.{png,webp,jpg}file in those folders. Even with the optimisation disabled, Euphonica will still try to opportunistically use said file (steps 1, 3 and 5 are always active in the above sequence).cover.{png,webp,jpg}FILES IN THEM. Without the optimisation, these files are required to prevent Euphonica from downloading the same embedded art again and again for every track in the same release.Rationale
In case the above still sounds so stupid, pls hear me out:
coverfiles. Without the optimisation, every embedded art from every track would be downloaded, blowing up the cache size and RAM usage.cover.{png,webp,jpg}files for folders that are single-release, and fall back to per-track embedded art for folders that aren't. I suppose the majority of people will have libraries that fall into this category (a few "unorganised" folders).cover.{png,webp,jpg}files, steps 1, 3 and 5 do nothing on their own and disabling the optimisation enables step 6 to write at track-URI level, correctly resolving one album art for every track.Other changes