[Linux] Album art no longer displaying in list contexts

[Hayden]

I started using MusicBee a few months ago, and I love it, but I started to see album art not showing anywhere where there's a list


MusicBee main library view with a lot of albums, none of which have art on them and are using the default icons. The right side currently playing does display the current track album art, as well as the bottom status playback

I've also verified that tracks do indeed have media attached, and even expanding an album shows the correct art


Edit view showing that the album does have an image attached, and that the same images shows in the expanded album view

I've searched around a little bit and tried various things, though none of which I could get working.

I've tried changing the artwork settings under the Tags (1) preferences to no avail, I've reset the artwork cache multiple times, and rescanned all files, I even tried a new library to no avail.
Even launching as administrator also doesn't work (though I don't think that really does much through Wine)


Tags (1) settings menu showing the artwork retrieval filter priority

The only thing I could really think of is that there are some Linux oddities happening, as I am running MusicBee on Linux through Wine, though I find it strange that this just started randomly happening, especially since album art previously displayed perfectly fine


Album art mostly showing with all except one album, though it still shows in the expanded view

This is when it started happening, then nothing new worked after it, I was converting my WMA files to FLAC at the time since I couldn't get WMA playback working.

I'm genuinely at a loss now, and I'm not sure what else to try, this doesn't technically impede usability, though it does make it much harder to quickly look through things to find something

sources I found and tried when searching around for this problem
Cover art not showing
Absent album art

[Mayibongwe]

Hi, welcome to the forum.

The only thing I could really think of is that there are some Linux oddities happening, as I am running MusicBee on Linux through Wine...

I was looking for this line because I remember someone reporting this.
See if anything mentioned here helps: https://getmusicbee.com/forum/index.php?topic=37252.0

[Hayden]

It seems to be tangentially related, though doesn't quite seem to be the same issue, when I check my InternalCache folder it's very sparse, and I'm not sure if that's normal, but MusicBee can access it perfectly fine (After removing the folder, the only thing that's there right now is LastFM play count data) so I'm wondering if there's something else going wrong.

[hiccup]

You are not mentioning this in the topic header, nor in your start post, but are you using Linux?
If so, it might be good to mention that specifically.

[Steven]

as i dont use linux i cant help much, but was wondering what happens when you close MB, then delete the InternalCache\AlbumCovers folder and restart MB.
Does the folder get rebuilt with files in the sub-folders?

[Hayden]

You are not mentioning this in the topic header, nor in your start post, but are you using Linux?
If so, it might be good to mention that specifically.

My apologies, I'll get this fixed, I am indeed using Linux.

as i dont use linux i cant help much, but was wondering what happens when you close MB, then delete the InternalCache\AlbumCovers folder and restart MB.
Does the folder get rebuilt with files in the sub-folders?

I tried this in my last reply, I did close MB, remove/rename the InternalCache folder, and upon starting it up, the InternalCache folder does get rebuilt, but interestingly enough, the AlbumCovers folder inside of that just does not exist, the only content in the folder is LastFmPlayCountCache.dat.
And upon closing that instance, AlbumCoverHashes.dat is created in the MusicBee appdata root, not sure if that's anything important.

I tried this again as I was writing, and now the AlbumCover folder exists with four other folders with random single digit numbers as the name, however no album art exists in the main view still.
There are .png files in these folders, but opening them in my native image viewer says that loading meta information failed, and fails to display the image. Not sure if this is normal with how MB stores these files.

I clicked around, expanding some albums, and now these folders with images are being populated with the appropriate images, and they are displayed correctly by the OS, however everything still looks the same as the first and second image in my initial post.

Is there any like, debug logging option I can turn on somewhere or something? I don't get any error messages immediately, but it seems like the process is just failing to do something at some point, considering album art works fine in every other context but this main list display.

[phred]

You're not getting any error messages, but have you  checked the Error Log? Help > Support > View Error Log.

[Hayden]

I honestly didn't know that existed, though I'm getting another strange issue that is flooding my logs making it difficult to find anything, it seems that MusicBee is still trying to search for my old WMA files that no longer exist, despite being on a completely new library.

MusicBee throwing an object reference exception, stating it's unable to open a file from a folder that does not exist

It's doing this for all of my old WMA files, of which there are no trace of at all in my music library files. This could possibly be related? But I'm not sure.
Here's the full error log if anyone wants to take a look at it, I am seeing some other exceptions in there, though I think that relates to the lack of media notification abilities.

[phred]

In addition to failing to mention you're using Linux, you never said your music files are on Google Drive. And the MB isn't/wasn't connecting to it.

[Hayden]

That's just a remanent of an old file structure, I no longer use Google Drive for any of my storage anymore, and haven't for long before I started MusicBee and haven't had the chance to move hundreds gigabytes of data out of it, it's just more convenient to leave it as it is and not risk anything breaking from changing things around.

The only thing touching that folder for synchronization is Syncthing, though that is much less volatile with files than Google Drive was for me in the past, and I only make changes to this folder on this computer, everything else is just a mirror of this master folder.

[Hayden]

Okay, I feel kinda stupid now, I did not realize that the error log was for all time, not only just this instance, I'll try some things to see if I can get some relevant errors.

[hiccup]

In addition to failing to mention you're using Linux...

He did mention it.
It was just not in the topic title or the start post.