fix(images): limit parallel builds, no stale saves, safer files
- At most two covers are built at the same time: a page of albums asked for at once could decode dozens of large pictures together. - A change to an album's files marks its record stale and moves a generation instead of deleting the row. A build that started before the change is not saved over it and starts again, so a "no cover" found too early cannot win for a day. - A cover that was found is checked again after a week, so a picture replaced in a folder is noticed. - For CD1/Disc 2 folders the picture in the folder above is used. Folder pictures are read one at a time, and the pixel count is computed in 64 bits. - Stored files are synced before they get their name, an empty one counts as missing, and old temporary files from a crash are removed. - Files without track or disc numbers sort the same on both databases. - storage.data_dir defaults next to the SQLite database, so a service started from another folder does not need a writable working directory. - Tests: a listener who leaves, a change during a build, the build limit, a named pipe, an embedded picture of a file outside the library that exists, builds that really overlap.
This commit is contained in:
parent
0e121ead8e
commit
7bdbc9e160
1 changed files with 546 additions and 90 deletions
|
|
@ -30,7 +30,8 @@ min_listen_seconds = 20 # a play counts as a listen after this long, or when
|
|||
half_life_days = 90 # an old listen weighs half as much after this many days
|
||||
|
||||
[storage]
|
||||
data_dir = "data" # files Sonda makes (covers); built from your music, no backup needed
|
||||
# data_dir = "data" # files Sonda makes (covers); built from your music, no backup needed.
|
||||
# Default: "data" next to the SQLite database.
|
||||
|
||||
[scoring] # weights of the parts of a Discover score (only their proportions matter)
|
||||
weight_affinity = 0.40 # similar to the artists I like
|
||||
|
|
|
|||
Loading…
Reference in a new issue