Missing music album cover art when browsing on album level #2747
Comments
|
Not sure if these things make any difference, but I have added to the |
|
Your configuration is almost fine. Without assuming an error in our system it should be |
|
Thanks! Just adding that didn't seem to do the trick so I played around a bit. Finally I ended up deleting the whole SQLite database and now I can not recreate it. But via the web interface and database "tab" I can only view the images for the cover art (below Photos) and playlists (below Playlists) for each album. But the virtual Album folder is empty, that is if I go to the Gerbera web page and select the database "tab" the Audio folder is "orange". However if I expand it, all of Album, Artists, Genres, Years, and so on are "black" (and empty) and can not be expanded any further. I can get Gerbera to rescan the folders, but that does not help and no new database file is created. But I can play tracks in the web browser via the playlist folder. I guess I need to add something more to my config file (see below) to get Gerbera to import my flac tracks? Please note that I have replaced my userid with " Please note that the reason for having the three elements |
|
By using command line option --add-file I was able to get Gerbera to import my flac files (via m3u import). I can get HiFi-Cast to connect to Gerbera and I see the virtual folders like Albums and so on (see My guess is that I am missing something in the configuration file and any help is really appreciated. :)
|
|
If you want to be sure that the import does not skip any image try this in your resources section The more entries you remove the faster the import will be. |
|
I’ll try your suggestion and report back what happens. :)Question: What does the values (2 in this case) set for the attributes parentCount and minDepth do? What would it mean if I changed one or both of them to 1, 3 or 4?Question: Is it possible to log the request the client sends to Gerbera and what answer Gerbera sends back? If so, how do I enable this?On 30 Nov 2022, at 23:11, Karlchen ***@***.***> wrote:
If you want to be sure that the import does not skip any image try this in your resources section
<container location="." parentCount="2" minDepth="2">
<add-file name="%album%.jpg"/>
<add-file name="%filename%.jpg"/>
<add-file name="%title%.jpg"/>
<add-file name="cover.jpg"/>
</container>
<fanart>
<add-file name="%album%.jpg"/>
<add-file name="%filename%-poster.jpg"/>
<add-file name="%filename%-landscape.jpg"/>
<add-file name="%filename%-fanart.jpg"/>
<add-file name="cover.png"/>
<add-file name="cover.jpg"/>
<add-file name="album.jpg"/>
<add-file name="front.jpg"/>
</fanart>
The more entries you remove the faster the import will be.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
For a description regarding the attributes I redirect you to https://docs.gerbera.io/en/stable/config-import.html#resources You can run gerbera with |
|
Thank you for the links, alas I have already gone through the documentation for the attributes and still can not make any sense of them :(I should have told you this when I asked my questions, sorry. :(The documentation for attribute parentCount says just “ Number of level which the fanart of a media file can be propagated upwards“. What does “level” mean in this context? For instance when you have virtual folders like Albums, how do you calculate which value to put there to ensure the fan art is accessible within Albums (I assume it is the browsing levels Albums and then the actual album that is referred to here). And what does a value of 0 (zero) mean?The same questions are also applicable for minPath which is documented with “Minimum number of path elements for container using fanart from media files.”. What is a “path element” in this context? Is it a file system path element (directory/folder), browsing path element (when navigating the media library like Artist/Year/Album/Song), or something else?I would like to understand how these two attributes interact with each other. For instance, what would a pathCount of 2 and a minPath of 1 mean? Or what would the opposite case mean, that is a pathCount of 1 and a minPath of 2?On 1 Dec 2022, at 08:38, Karlchen ***@***.***> wrote:
For a description regarding the attributes I redirect you to https://docs.gerbera.io/en/stable/config-import.html#resources
You can run gerbera with --debug to get load of details including requests and responses. If you are running curent head you can also set debug-mode to "Cds|Xml" (see https://docs.gerbera.io/en/latest/config-server.html#server) to reduce the number of messages you get.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
So the problem is that when writing the documentation I was not in the mood to do it properly. What do you think about the following text:
|
|
I understand what you are saying about not being in the right mood for writing documentation strings. :)The descriptions are much better now! I think I understand what the parentCount attribute does. But unfortunately I have problems with the minDepth attribute description.I’m happy to help you with this. I actually think it is a bit fun to figure out how to explain complex things in writing. But in order to do that I must first understand how the thing to describe works. A lot of questions pop up, for instance 1) What is the semantic difference between parentCount and minDepth? Why would I want to configure one or both of them?2) Is minDepth only for virtual folders? I guess not, but as it is written now you can be led to assume that is the case. If it is only applicable for virtual folders then I kindly propose that this is clearly stated in the description. Or perhaps all folders are virtual?3) The description for parentCount suggests that you start counting from the right (from the “leaf” i.e. Song), that is 1=Album, 2=Artist, 3=Audio, 4=Root. The description for minDepth suggests that you start from the left (but description is not as clear as it is for parentCount).4) What happens if minDepth is 0?5) Can a value of minDepth be in conflict with a value of parentCount? Is there any precedence between the two if that is the case? For instance minDepth=1 is Root (right? Since 3 is Artist?) and parentCount=1 would be Album. What would happen in this case?On 2 Dec 2022, at 08:38, Karlchen ***@***.***> wrote:
So the problem is that when writing the documentation I was not in the mood to do it properly. What do you think about the following text:
container
::
<container location="images" parentCount="2" minDepth="2"/>
* Optional
Set up container images. The fanart of a media file is added automatically as a thumbnail to the container (e.g. the album container).
::
location="..."
* Optional
Path to the directory containing the images to load. Relative paths are assumed to be under the server's home.
Drop your artists' images or logos for default containers here and they are displayed as thumbnail when browsing with a compatible client.
If the image is not found in that location, it is also searched in the physical folder itself.
::
parentCount="..."
* Optional
This setting allows to increase the number of levels which the fanart of a media file can be propagated upwards (examples refer to basic layout /Root/Audio/Artist/Album/song).
A value of 1 adds the fanart only to the direct parent container when a media file is added (e.g. the Album container).
A value of 2 means you propagate that image to the parent container as well (e.g. the Artist container).
A value of 0 blocks propagation completely.
::
minDepth="..."
* Optional
Depending on the virtual layout propagating thumbnails can reach containers like Video or Audio. This settings forces a minimal depth for propagation to apply.
It is setting the minimum number of path elements for container using fanart from media files (e.g. /Root/Audio/Artist has level 3 so the image can be set).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I do not understand how #2759 fixes this issue? I am a bit surprised that this issue got closed as I have neither got answers to my questions nor confirmed that the suggested configuration file changes fixes my issue. Can you please reopen this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm sorry if this is a bit vague, but here it goes anyway. When using an older version of Gerbera together with Android app Hi-Fi Cast UPnP client/controller I was able to get music album covers to show up when browsing on album level. What I mean is that when viewing an individual song I get the album art since I have embedded the album cover within my
.flacfiles, but when browsing on the album level I only see default/dummy images for the albums. To make matters worse I have also managed to loose my old Gerberaconfig.xmlfile (I had to re-install my computer and somehow missed to backup this file) so I am not sure how I had it configured before the upgrade; I'm thus starting from scratch with a defaultconfig.xmlfile for Gerbera 1.12 and also rebuilding the database...My music files are organized so that each album is in a separate folder and in this folder I also have a file named
cover.jpgwhich is the cover for the music album. Within this folder there is also an m3u file containing just the songs for the album. For instance/home/<userid>/Music/flac/Whale-We_Care/contain the filesWhat I am trying to figure out (and so far failed to recreate) is that Gerbera should pick up the
cover.jpgfiles for each album and provide them to the client (Hi-Fi Cast in this case) when I browse on the album level. I guess I need to add something to the Gerberaconfig.xmlfile, but I have so far not been able to figure out what I need to do. :(Any help/pointers are appreciated! :)
The text was updated successfully, but these errors were encountered: