Would be great if tmm could update database by rescanning NFO files, thru either a separate command or the existing "Update Data Sources" command.
Currently, if I'm not mistaken, you have to start from scratch and rebuild the entire database to reflect any external changes made onto NFO files.
correct.
The reason for that is, that we never know, who is the "master".
If the value in DB differs from NFO, what's the correct / most recent one?
Should we write the DB value into the NFO?
Should we write the NFO value into the DB?
Which NFO in movieDir should we take? we can have multiple ones (with different content)
So the NFO is only read, if the movie is not in database.
Kodi behaves the same - changing the NFO and updating results in no changes in their database...
What we can do is to add a special "force update" function, to force the reloading of just the metadata.
But this might not be much faster than removing the complete movie anyway...
This request is already on our long todo-list
Thanks for your replies!
(2016-01-07, 19:57)myron Wrote: [ -> ]What we can do is to add a special "force update" function, to force the reloading of just the metadata.
Yep, that's the missing piece as you already have "Rewrite NFO" command and "Update media info" command.
(2016-01-07, 19:57)myron Wrote: [ -> ]But this might not be much faster than removing the complete movie anyway...
No, it would be a lot faster. For a thousand movies, scanning metadata takes only a minute except getting media info which takes 3 to 5 minutes depending on subtitles.
(2016-01-07, 19:57)myron Wrote: [ -> ]This request is already on our long todo-list
Hope to see this feature soon.