2017-10-17, 15:32
Scott that is not a feature I have ever used, so my lack of awareness may have led to undesireable results (accident as opposite of design). In fact if I had known about it the *item functionality could even have been useful when debugging random art issues to see what Kodi thought was the folder for an artist. The voyage of Kodi discovery never ends!
EDIT: Had some trouble reproducing, it seems to behave like v17... Then I found that the behaviour you report happens only when no local art was in the folder during scanning. If there is a folder.jpg then you still get a *item when browsing.
I have been so focussed on how the automatic identification of artist art that is mixed in with music can go wrong, I had missed the ways it can be useful manually to have it there. So help we out with views on that.
b) Do we provide a quick route to the approriate folder within the Artist Info Folder?
Perhaps both, or maybe b) with fall back to a)?
I find that *item in v17 only goes somewhere useful for album artists, when on song artists (no album) or other contributing artists (producers, lyricist etc.) it just opens on my root directory.
For art found manually if you create a folder in the Artist Info Folder with the artist name Kodi will use, and put art in there, then scraping using "Query Info for all" with that artist present in the node (so you could be looking at producers and have art for them) will pick up that art. The nice thing is that is can be automated, you don't have to visit every artist and look at Artist Info dialogand pick art by hand etc. The hard thing is putting the art in the correctly named folder. Then again if in doubt export unscraped artists to separate files, and folders will be created for every artist that you can then manually populate with the art files.
What may catch people out is that pick up of art from Artist Info Folder is part of the scraping process, not the tag scanning one. The reason is technical, as I described in my brain fart a couple of posts above https://forum.kodi.tv/showthread.php?tid...pid2655747. I hope that users can get used to their local art being collected by scraping rather than the scanning phase. But the up side is that they can have automated art for any artist, not just album artists with limits.
EDIT: Had some trouble reproducing, it seems to behave like v17... Then I found that the behaviour you report happens only when no local art was in the folder during scanning. If there is a folder.jpg then you still get a *item when browsing.
I have been so focussed on how the automatic identification of artist art that is mixed in with music can go wrong, I had missed the ways it can be useful manually to have it there. So help we out with views on that.
Quote:I guess if all artist art is moved to a user-defined artist art folder tree the current functions don't make sense, but then you have to do a lot of clicking/scrolling to get to the folder containing the desired art.a) For backwards compatibility do we provide a way to get to the folder Kodi v17 and below would have taken as the artist folder (the folder above all the folders containing music by that album artist)? It will still pick up art from there if such a folder is unique for the album artist, but prefers art from the approriate folder within the Artist Info Folder if it exists.
b) Do we provide a quick route to the approriate folder within the Artist Info Folder?
Perhaps both, or maybe b) with fall back to a)?
I find that *item in v17 only goes somewhere useful for album artists, when on song artists (no album) or other contributing artists (producers, lyricist etc.) it just opens on my root directory.
Quote:Or maybe I don't understand the intent of how local artist art is intended to be added to the library in the new scheme.My focus so far has been that the art initially comes for online scraping. So one approach: fetch art from online sources (using scraper or other addons such as cdArt or Skin Helper Service); save to Artist Info Folder via export to separate files in library folder. Not the art is there in the Artist Info Folder, and should you do a clean install then scraping (not just scan of tags which does pick up art next to the music files) will pick it up.
For art found manually if you create a folder in the Artist Info Folder with the artist name Kodi will use, and put art in there, then scraping using "Query Info for all" with that artist present in the node (so you could be looking at producers and have art for them) will pick up that art. The nice thing is that is can be automated, you don't have to visit every artist and look at Artist Info dialogand pick art by hand etc. The hard thing is putting the art in the correctly named folder. Then again if in doubt export unscraped artists to separate files, and folders will be created for every artist that you can then manually populate with the art files.
What may catch people out is that pick up of art from Artist Info Folder is part of the scraping process, not the tag scanning one. The reason is technical, as I described in my brain fart a couple of posts above https://forum.kodi.tv/showthread.php?tid...pid2655747. I hope that users can get used to their local art being collected by scraping rather than the scanning phase. But the up side is that they can have automated art for any artist, not just album artists with limits.
