2017-11-09, 15:59
(2017-11-07, 02:22)Guilouz Wrote: @rmrector
Here my french translation : https://drive.google.com/file/d/1qF5FNyQ...sp=sharing
Works perfectly, thanks !
(2017-11-07, 02:22)Guilouz Wrote: @rmrector
Here my french translation : https://drive.google.com/file/d/1qF5FNyQ...sp=sharing
(2017-11-09, 01:09)wallacebw Wrote: ...
Thanks, I took a look at the mklocal.py and *should* be able to make this work to write the art with the media, but won't artwork beef end up in the same place of either seeing the 'local' or 'internet' art as new or does artworkbeef leverage the texture.imagehash field to validate content regardless of SRC?
(2017-11-09, 16:21)lepoilu Wrote: Hello,
I have acted on the options to retrieve saga posters from movie folders, but it does not recover them.
On some pockets I have empty images.
...
Thank you very much for this remarkable work !
Quote:Quote:(2017-11-08, 18:09)wallacebw Wrote: ...
Thanks, I took a look at the mklocal.py and *should* be able to make this work to write the art with the media, but won't artwork beef end up in the same place of either seeing the 'local' or 'internet' art as new or does artworkbeef leverage the texture.imagehash field to validate content regardless of SRC?
Artwork Beef will only automatically search for new artwork from web services if you have less than the amount configured in the add-on settings, but if there are fewer images available from the web services then that could still happen. For my use I keep the limit at 5, and select more for items that can really benefit. Exporting with Kodi will make the exported files look new to Artwork Beef, which it then adds to the existing URLs (then rearranges them so that they get assigned to the order that their filename determines), resulting in doubles. Using mklocal will actually replace the URLs with local file paths so the next time Artwork Beef comes around it doesn't need to do anything; local artwork is already in the library, and there is enough to satisfy number requested by the configuration, so it doesn't try to add more from the web services. Perhaps an option to always replace URLs when new local files are found would work a bit better for folks using Kodi's export.
(2017-11-10, 04:02)rmrector Wrote: Yeah, Artwork Beef doesn't support movie set artwork in the library directly next to media files, "movieset-poster.jpg" and the like. I hadn't seen those before, are you getting them from TinyMediaManager? My quick first impression is that I really do not like that approach; it leaves duplicate files everywhere, and can be a pain to make sure each of them is updated properly when artwork changes; each made all the more problematic by the number of artwork that is supported. I suggest using a central artwork directory for local movie set artwork.
(2017-11-10, 15:56)lepoilu Wrote: ..
Thank you for your reply.
Exactly, I use TMM.
The illustrations are all in the folder of the film. No need for additional folder, and if it is necessary to rebuild its database one does not use the data on line every time, at least the waiters do not force.
...
Thank you.
(2017-11-10, 23:01)rmrector Wrote:(2017-11-10, 15:56)lepoilu Wrote: ..
Thank you for your reply.
Exactly, I use TMM.
The illustrations are all in the folder of the film. No need for additional folder, and if it is necessary to rebuild its database one does not use the data on line every time, at least the waiters do not force.
...
Thank you.
Storing these images in a central directory keeps all the images locally for a rebuild or additional Kodi installs just as well, and avoids the noted file synchronization problems. That option is to pull artwork from a parent directory of the movies if that parent is for the movie set. For instance, if your movie folders are stored like "AllMovies/Alien Collection/Alien (1979)/Alien (1979).mkv", this will find movie set artwork stored like "AllMovies/Alien Collection/fanart.jpg". I don't like this strategy for other reasons, though, but it does also avoid the noted problems.
I haven't come across any other tools that work with movie set artwork stored this way, but I do see several that use the Movie Set Artwork Automator style, including TMM. It seems a bad idea to support a third option that introduces a new set of problems and isn't really suppor
xml:14:26:58.010 T:9112 WARNING: CPythonInvoker(3, C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\service.py): the python script "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\service.py" has left several classes in memory that we couldn't clean up. The classes include: class XBMCAddon::xbmcgui:ialogProgressBG,class PythonBindings::XBMCAddon_xbmc_Monitor_Director
xml:14:27:12.595 T:10884 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.ImportError'>
Error Contents: No module named urllib3
Traceback (most recent call last):
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\service.py", line 3, in <module>
from lib.artworkprocessor import ArtworkProcessor
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\lib\artworkprocessor.py", line 9, in <module>
from lib.gatherer import Gatherer
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\lib\gatherer.py", line 1, in <module>
from lib import providers
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\lib\providers\__init__.py", line 2, in <module>
from lib.providers.base import ProviderError
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.artwork.beef\lib\providers\base.py", line 5, in <module>
from requests.exceptions import HTTPError, Timeout, ConnectionError, RequestException
File "C:\Users\mail\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\__init__.py", line 43, in <module>
import urllib3
ImportError: No module named urllib3
-->End of Python script error report<--