by Barry4679 » Sun Apr 25, 2021 8:28 am
rusty wrote: ↑Sat Apr 24, 2021 9:11 pm
Re. MM failing to update the tracklist in response to an externally updated tag, are you referring to a case in which the file monitor is set to continuously monitor a directory and it fails to 'notice' the change?
No, not what I meant.
In MM4 I could update the MM database, with tag changes, using an external application, while MM4 was open and idle.
When I pressed refresh in MM4 it noticed the database change.
The same thing in MM5 only notices the change if I stop and then restart MM5. .. ie. MM5 does not re-read the database for a F5 refresh ... nor when a tab is closed and reopened ... nor when i navigate to a different collection, and then return to the collection that was open and idle when the database was changed.
An example is:
- MM5 is idle, and open at EntireLibrary node in List By Album mode, and is sorted by Last Played column
- an external program updates Last Played column for some new track plays
- go to MM5 and press F5, the newly played tracks do not raise to the top ... filter the display to one the albums which have just been updated .. tracks do not show the new play date
- close & reopen MM5, and everything is now updated
I have 47,000+ tracks, so I don't suppose that it is a memory cache .. ? You have a shadow database?
I am not saying this is a problem, because this practice is not recommended given that Sqlite is not multi-process DBMS. So I put this thread in the Developers' forum as a heads up, because this is a change from MM4 behaviour.
drakinite wrote: ↑Sat Apr 24, 2021 9:59 am
I can't give any answers to your other questions, but as for album art caching, there is currently no caching done for art thumbnails.
Yes, I should not have asked about the Album art ... Now that i think of it, this is a special case ... but what about the artist & composer art that has been downloaded and cached by MM5? ... Is the art still connected to correct composers and artists?
[quote=rusty post_id=480656 time=1619316665 user_id=182]
Re. MM failing to update the tracklist in response to an externally updated tag, are you referring to a case in which the file monitor is set to continuously monitor a directory and it fails to 'notice' the change?
[/quote]
No, not what I meant.
In MM4 I could update the MM database, with tag changes, using an external application, while MM4 was open and idle.
When I pressed refresh in MM4 it noticed the database change.
The same thing in MM5 only notices the change if I stop and then restart MM5. .. ie. MM5 does not re-read the database for a F5 refresh ... nor when a tab is closed and reopened ... nor when i navigate to a different collection, and then return to the collection that was open and idle when the database was changed.
An example is:
[list]MM5 is idle, and open at EntireLibrary node in List By Album mode, and is sorted by Last Played column[/list]
[list]an external program updates Last Played column for some new track plays[/list]
[list]go to MM5 and press F5, the newly played tracks do not raise to the top ... filter the display to one the albums which have just been updated .. tracks do not show the new play date[/list]
[list]close & reopen MM5, and everything is now updated[/list]
I have 47,000+ tracks, so I don't suppose that it is a memory cache .. ? You have a shadow database?
I am not saying this is a problem, because this practice is not recommended given that Sqlite is not multi-process DBMS. So I put this thread in the Developers' forum as a heads up, because this is a change from MM4 behaviour.
[quote=drakinite post_id=480631 time=1619276355 user_id=107828]
I can't give any answers to your other questions, but as for album art caching, there is currently no caching done for art thumbnails.
[/quote]
Yes, I should not have asked about the Album art ... Now that i think of it, this is a special case ... but what about the artist & composer art that has been downloaded and cached by MM5? ... Is the art still connected to correct composers and artists?