Infuse is very good when it comes to metadata, but sometimes it leaves files as individual episodes even if it recognized the metadata correctly, so to keep my collection organized, i have to use folders (see example screenshot). It would be nice if there in such cases there was an option to create a regular season item manually so they would appear as a single season instead of multiple episodes
Today’s new features email reminded me about this feature and how much I would like to see it implemented. Status has changed to “planned” since the last time I checked… does that mean there’s an actual release date?
TMDB always d!cks around with their stupid rules and that so called “bible” of contribution.
If you want to add something to TMDB, knowing that it’s probably not worth your time, what you can do is to add a movie or a TV show with 2 episodes with the most bare bone Information, then report yourself or mention it in their discussion/talk page. The “moderators” will come and look at your page and probably delete it. If they don’t, then you can go back and flush out the rest.
If they tell you to piss off in a passive aggressive way, at least you didn’t spend much time on it and wasted their time too.
I don’t want to like your post because I don’t want to jinx anything.
But with the 7.5.5 stuff I was so excited for being pushed back from “in progress” to “pending” and no earlier than 7.6.1, which is at least 5 update cycles away now … I’m kinda getting my heart broken.
It would be great to have a category for self-managed videos next to Movies and TV Shows.
This could be used for stand alone videoas (eg home movies) and series (eg lectures/tutorials spread over a series of videos, or home videos grouped per year).
The NFO files would explain if these are individual videos or series, and Infuse could present them accordingly.
I’m new to Infuse and this forum and I wasn’t aware of this “drama”…
I had to fix tv show titles for all shows that have a different episode count in TMDB than in my country (Germany). Obviously the TMDB titles don’t match the episodes in this case.
Not knowing that this isn’t supported, I created XML-files with the corrected titles according to the instructions on the Firecore website. And it worked as expected on all my devices (iMac, iPad, Apple TV). And yes, I tried other tags (e. g. description), but they didn’t work… I thought it must be a bug, but I didn’t care…
Last week I noticed in my living room (on Apple TV) that all(!) corrected show titles show up with the wrong matching episode from TMDB. This means the XML-files are no longer respected. Not even the title tag!
I checked Infuse on my iMac and my iPad - and I was surprised to see that everything still works on these devices. All corrected show title are perfectly shown in the Infuse GUI. But not on my Apple TV…
I opened a support request and informed Firecore about this new bug in Infuse on Apple TV. And only in Infuse on Apple TV! They answered, that XML-files for metadata are not supported for tv shows at all and they didn’t accept this as a bug. In addition they sent me a link to this discussion…
And I find myself sitting in the living room as an Infuse Pro user looking at the “title mess” for many tv show episodes Infuse now has created on my Apple TV… this is ridiculous…
Fortunately this mess isn’t synced to other platforms e. g. each platform seems to do it’s own metadata mapping (and has it’s own implementation of respecting local XML-files or not).
as I described in my last post, XML-files for tv shows work with same tags, e. g. “title”. That’s exactly, what I used so far - not knowing, that this is not a supported feature.
I didn’t create “custom tv shows” by choosing any tv show for something. I selected the right tv show and had to override the episode titles because of a different episode count in TMDB.
Unfortunately they broke this with one of their last Infuse updates for Apple TV - iMac and iPad still work as before and override the tv show title from the XML-file, Apple TV doesn’t anymore.
They don’t accept this as a bug, because it’s not supported. I’m still hoping that they will fix it…