[Montellese]

Backlink to original: https://emby.media/community/index.php?/...ent=918659

I have just successfully installed Media Importer on a VM using `LibreELEC (community): devel-20200826165948-d8a7611 (Generic.x86_64)` and `Emby Media Importer 0.0.9`.

The entire setup process was quite elegant once I understood the new workflow for adding sources and realised it is best to avoid HTTPS for now.

I really dont have anything but positive feedback to report other than trivialities like the icon in Kodi settings for Media Sources is missing.

Thanks for your feedback and taking the time to test this. I very much appreciate it.
The missing icon for media sources in settings is because I'm not a designer / skinner and the location of the entry point will probably change in the final version.
 

I can see though that the FanArt cache is built on demand. I would like to request an option for all cover art to be pre-cached. In my experience on lower end devices lack of pre caching just results in an extended bad user experience until it is populated. In cases like this it is better to get this out the way once in advance. Obviously some consideration would need to be given to how remote the artwork is (i.e. internet vs local LAN) and if only covers vs actor etc are pre cached.

I havent tested it yet but it looks like we also follow the standard Kodi practice of a separate `/userdata/Thumbnails` cache per user. As stated previously this isnt viable for me on AML since the available device storage space is less than the space needed to hold 6 copies of the cache (one for each user). This forces me to use path substitution which immediately makes all my installs officially not supported.

Is there any option being considered to work around this?

TBH I haven't considered pre-caching artwork because I only tested this on my dev machine so far which is powerful enough to do this on-the-fly. But I can see this being an issue on a Raspberry Pi or similar platforms. I'll think about how this could best be achieved. Concerning the location media import doesn't have any custom / special handling for artwork. It simply gets the information from Emby (or any other source) and stores it in the database / library exactly the same as artwork provided by scrapers. So if you have a working solution for standard library items it should also work for media importing.