namida icon indicating copy to clipboard operation
namida copied to clipboard

[ISSUE] Album art caching

Open WitnessTheFallacy opened this issue 4 months ago • 5 comments

Cool player, maybe even the best, with lots of settings and features, but the cover art caching is kind of horrible. The app caches the cover art for every track and seems to cache it at full size, causing it to instantly grow to 2 gigabytes when I launch it. With album grouping turned on, the situation is better and the app only saves about 270 megabytes of data, but if there are albums with the same title, they get one common cover art. This is definitely a flaw, for no other player has such a problem. It would be nice to have the option to at least disable caching completely. I hope this problem will be solved because I really liked the app, but this flaw is killing it for me.

WitnessTheFallacy avatar Sep 11 '25 10:09 WitnessTheFallacy

sorry for late reply. it's the only way out there now. we don't have the luxury of shared threads to extract images in background each time u scroll to a track, this would also mean increased cpu (and battery) usage

u have 2 issues and both have implemented solutions

The app caches the cover art for every track and seems to cache it at full size, causing it to instantly grow to 2 gigabytes

  • solution 1:

    1. advanced settings -> clear image cache
    2. turn on media store, now the artwork will be fetched from media store with low quality. when u play something it will then extract the full quality once and save it to cache. (this may cause slight lag while playing new stuff)
    3. note that if u reindex while media store is on, u might lose some extracted tags (since media store lacks them)
  • solution 2:

    1. advanced settings -> compress images
    2. select "Artworks" then compress
    3. after finishing, copy the "storage/Namida/Compressed" back to the artwork location (in Android/data/namida)
  • solution 3: (if ur library is usually from yt)

    1. advanced settings -> fix ytdlp big thumbnail size
    2. choose tracks folders, it will embed the ~100kb original thumbnail in each file (so backup first!)

With album grouping turned on, the situation is better and the app only saves about 270 megabytes of data, but if there are albums with the same title, they get one common cover art. This is definitely a flaw

it's not a flow, u need to specify what separate albums. go to indexer -> Album identifiers and enable year and album artist, then reindex with clear image cache

hopefuly its fixed for you with these.

MSOB7YY avatar Nov 03 '25 21:11 MSOB7YY

Hi, I don't know how it works, but many players can extract covers directly from file tags. I haven't noticed whether this increases the load on the processor and battery consumption, but even if it does, it's hardly worth worrying about. However, it completely solves the problem of a pile of junk from cached covers. What's more, this app doesn't even use a shared folder with cached images, but uses its own. It's quite strange that such an advanced app doesn't have a feature that even the simplest players sometimes have.

P.S. Sorry if the text sounds strange. My English isn't very good, so I'm using a translator.

WitnessTheFallacy avatar Nov 04 '25 12:11 WitnessTheFallacy

again its not feasible to extract artwork each time, it's not a native java/kotlin app and we don't have shared threads feature. see issue 333 on https://github.com/dart-lang/language/issues

but even tho, i will try to push the limits further and see if it would work out (to extract each time)

MSOB7YY avatar Nov 04 '25 12:11 MSOB7YY

Please don't take this as an insult or anything like that. I'm not familiar with the technical details, but as a fairly experienced user, I noticed this nuance. I just regret that I may have to give up an excellent application for such a ridiculous reason. So I decided to share my thoughts on this issue, not because I am terribly dissatisfied, but in the hope that it will help make the application even better. In any case, I wish you luck in your work.

WitnessTheFallacy avatar Nov 04 '25 17:11 WitnessTheFallacy

lmao no worriesss, i experimented a bit with it, it works fine and noticed no lag so far, but it sure takes time to load the image (especially on fast scrolling), there are also flickers when for example opening dialog/page with the same image (we can cache them in memory but we would need to manage that too)

your best bet for now is to either rely on media store or compress images as mentioned

thanks for the humble feedback tho! ^^

MSOB7YY avatar Nov 12 '25 19:11 MSOB7YY