[scott967]

Not sure what the requirement is, but prior to 3.5.6.2.c I had art as moviename-fanart and and moviename-poster. If I check the movie preference to save art as fanart and poster instead, the existing art using the other name convention no longer is displayed in the browser. Seems like it should still be displayed?

scott s.
.

A bit muddled there, but your saying existing moviename-fanart and -poster are not displaying if New Movies? scraped in format fanart.jpg and poster.jpg?

Your wanting any variation in fanart or poster to be displayed, no matter what the saving convention is set to? How will you know if you have artwork missing??

I'll have to check how the code is working out what artwork is available, but the idea is to have consistent artwork for a user's movies, ie: all as poster.jpg/fanart.jpg or all as -poster.jpg/-fanart.jpg.

All I know is I installed the new 62c build, saw now the option to either use moviename-fanart or fanart for file names when I set up the build, so I thought I would try changing the default movie-fanart to fanart (and also posters) to see what difference it would make/test. So I added my movie folder and rescanned. None of my existing movies showed any fanart or posters which I found surprising. After changing the option back, then the art was displayed. I don't know what the right answer is. It seems like the user would like to know if either moviename-fanart or fanart was available, but I can see how it could get more and more complicated. I guess if it was up to me I would propose a requirement that if any valid art is available it gets displayed in the main browser view, and the naming conventions only apply to scraping new art.

scott s.
.