do not forget the album cover when using embedded cover images
ClosedPublic

Authored by mgallien on Apr 28 2019, 2:53 PM.

Details

Summary

Use embedded cover images when inserting an album in database allowing tracks and albums to use the right cover image

Currently require a reimport of database. Will fix that in a later revision.

CCBUG: 393486
BUG: 406482

Test Plan

Auto tests are OK. Attached test files show an embedded cover image.

Diff Detail

Repository
R255 Elisa
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
mgallien requested review of this revision.Apr 28 2019, 2:53 PM
mgallien created this revision.
mgallien added a project: Elisa.
ngraham accepted this revision.Apr 28 2019, 3:01 PM

Yep, confirmed that this fixes the issue for all of my albums that lacked art, after re-importing the library. Thanks!

This revision is now accepted and ready to land.Apr 28 2019, 3:01 PM

Yep, confirmed that this fixes the issue for all of my albums that lacked art, after re-importing the library. Thanks!

Yes but I think that it also needs to be fixed without re-importing. What do you think ?

Yep, confirmed that this fixes the issue for all of my albums that lacked art, after re-importing the library. Thanks!

Thanks for the test ;)

It would be nice to fix it without re-importing, yes. If that's necessary, it should happen automatically. Does that already happen for people who upgrade from one stable release to another?

mgallien updated this revision to Diff 57273.Apr 30 2019, 3:16 PM
  • allow proper load of embedded cover even when database has wrong data

allow proper display of embedded cover images even without a fixed database

mgallien retitled this revision from [WIP] do not forget the album cover when using embedded cover images to do not forget the album cover when using embedded cover images.Apr 30 2019, 3:17 PM

It would be nice to fix it without re-importing, yes. If that's necessary, it should happen automatically. Does that already happen for people who upgrade from one stable release to another?

I have pushed another fix that allows to display the embedded cover without database changes. I am testing upgrades from last stable version (currently the upgrade is broken (logic given I have not added automated tests)).

Out of curiosity where on disk is the database located, and is it safe to blow away for testing purposes?

Out of curiosity where on disk is the database located, and is it safe to blow away for testing purposes?

It is located in $HOME/.local/share/elisa/elisaDatabase.db .
You can wipe it out but you will lose your statistics (play count, first and last play date).
I definitely need to look again at a way to store those data in the music files (and push support in KFileMetaData).

ngraham accepted this revision.May 2 2019, 9:56 PM
This revision was automatically updated to reflect the committed changes.

So much better now!