(2022-03-07, 18:32)MB1968 Wrote: Fake files, or even a complete fake library can be handy for all sort of things. I'm currently reorganising all actor images. I prefer to store them locally instead of having weblinks in my .nfo.files. With Media Companion and a fake library I'm able to build future proof .nfo files, without harming my running .nfo files. Juan Mortyme explained recently how to store the actor images locally. Time consuming, but very useful.
The fix is working. Thanks a lot.
Just in case anyone missed my previous explanation or is interested in the couple new things I've learned since then I'll go over it again. As always, if I've missed or mistaken anything feel free to jump in and correct me.
I've recently taken it a step further (see third method).
So, there are a couple options when it comes to storing actor images locally.
First method. The easiest is to just use individual
.actors folder for each movie and show. Kodi should pick them up without having to modify the .nfo file:
Positives = (1) Simple to implement. (2) Should work on network shares (not tested). (3) Portability, if you change media source drive or folder the actor images will move along with your movies/shows since they are in the medias' home folder and should continue to work without having to make any changes. (4) Most external media management software will download and save actor thumbs to .actors folders for each movie/show automatically (Kodi scrappers may also do this?).
Negatives = (1) Requires more storage space which might become an issue. (2) Folders
must be located in the home folder of
each movie/show and named
.actors. (3) Higher maintenance, more time and attention required when updating or adding new images.
Second method. Another option is using central Actor folder(s) with paths in the .nfo files:
Positives = (1) Less storage space. (2) Easy to update or add new images once the .nfo is modified. For instance, I add paths even for actors who I don't currently have a thumb for so if/when in the future I do find one I can just simply add it to the central folder(s) and it is immediately available without any further action needed. (3) Allows for use of multiple central folders with names and locations of your choice. I use this method to have my music video (Matrix only) and concert film casts use thumbs stored in my Artist Information folder and sporting events use a Players and Team Logos folder.
Negatives = (1) Time consuming initial switchover of large library. This can be mitigated with Notepad++ using it's ability to batch search and replace. (2) I could only get it to work on my network if I had identical image folders names and paths on all devises on the network. Auto-sync software can be deployed to assist with syncing network devices. (3) Media Companion is the only program I'm aware of that with automatically download actor thumbs to a central folder of your choice and add the appropriate path in the .nfo file. (4) Need to change all paths in .nfo files should you decide to change media source or central actor storage location.
Third method. The method I currently prefer. Using the second method above along with a couple additional steps address the need for duplicate folders on network devices.
Positives = (1-3) above. (4) By using
mapped network drives in conjunction with adding
path substations for the actors thumb locations to my advanced setting I have eliminated the need for any additional actor thumbs other than the those scrapped and stored with Media Companion located on my host device (negative points 2 & 4 above solved).
Negative = (1) from above remains true as does (3) from above.
MODERATORS: If you feel this post is something that would benefit a wider audience you can duplicate it to a more obvious thread or copy it to the wiki at your pleasure.