Artwork issue

[mightyoakbob]

For many years I have managed to get an icon of a computer folder to display for "folder View". I did this simply by placing a folder.jpg image in the top level of the scan directory (top of my library).

The top level of my scan directory (or folder if you prefer) is full of directories like this...

Audio Books, Christmas, Classical, Home, iTunes (m4a), Jazz, Misc, mp3, Play_Lists, Rock and Pop, Samplers, Stage and Screen, Vinyl
and one image folder/jpg (a picture of a folder).

Suddenly, just before christmas this stopped working. Instead, Minimserver now ignores my folder.jpg and looks inside Audio Books and finds an icon there and uses that instead. Now the Audio Books directory only contains other directories and one image, no audio files at that level. However, that image works fine for an Audio Books icon. This seems to be a new inconsistancy to me.

What has caused this, I don't understand the mechanism for it. I tried an experiment, I created a top level directory name Aaa thinking this would be the top choice and placed a copy of the folder picture in there.
No, MinimServer ignored that and continued to use the Audio Books icon.

As the books directory has no audio files but does have other directories, I placed another directory with the picture inside Aaa.

No, MinimServer ignores that too. Grrrr.

It was fine before.
Can I switch this off?
Is there another solution?
Can I revert to earlier versions and just stay there?

Thanks.

Bob.

[simoncn]

Thanks for letting me know about this. It was an unintended change made as part of the recent enhancements to index artwork. My apologies for the inconvenience this has caused you.

This problem will be fixed in the next MinimServer update. If you have MinimWatch installed, you can use the Packages tab to revert to MinimServer update 263 until the fix is available.

I have locked the other thread that you opened to report the same problem and I will delete it soon. A problem should be reported on one thread only so that discussion about the problem is easier for people to follow.

[mightyoakbob]

(09-01-2026 21:19)simoncn Wrote:  Thanks for letting me know about this. It was an unintended change made as part of the recent enhancements to index artwork. My apologies for the inconvenience this has caused you.

I wasn't expecting that, you're more than welcome.

(09-01-2026 21:19)simoncn Wrote:  This problem will be fixed in the next MinimServer update.

That's great, thanks.

(09-01-2026 21:19)simoncn Wrote:  If you have MinimWatch installed, you can use the Packages tab to revert to MinimServer update 263 until the fix is available.

Brilliant but it's annoying not life threatening so I'll wait for the fix. :-)

(09-01-2026 21:19)simoncn Wrote:  I have locked the other thread that you opened to report the same problem and I will delete it soon. A problem should be reported on one thread only so that discussion about the problem is easier for people to follow.

Yes, I take your point. At first I thought this was a trivial matter that I didn't wish to make a fuss about. I expected some other power user to comment that I was making some silly mistake or other but no such comment arrived. At that point I thought I would ask for support on it. Sorry I got that wrong.

Bob.

[simoncn]

(10-01-2026 12:56)mightyoakbob Wrote:  Yes, I take your point. At first I thought this was a trivial matter that I didn't wish to make a fuss about. I expected some other power user to comment that I was making some silly mistake or other but no such comment arrived. At that point I thought I would ask for support on it. Sorry I got that wrong.

Bob.

In this situation it would be fine to ask for support by posting back to the same thread, just not to start another thread on the same topic. Also, if you want to change the thread subject to clarify or expand on the issue, you can do this by editing your first post.

[mightyoakbob]

(09-01-2026 21:19)simoncn Wrote:  This problem will be fixed in the next MinimServer update. If you have MinimWatch installed, you can use the Packages tab to revert to MinimServer update 263 until the fix is available.

I changed my mind (again) and decided it was a good idea to confirm the issues was down to changes since 263. I can confirm, running 263 DOES fix my issue.

Thanks.
Bob.