When using Jellyfin, Emby, or Plex Infuse pull details fetched by the server instead of reading the filenames directly - so unfortunately this new logic will not be available for those sources.
So that means, if Jellyfin is the source we’ll still be restricted to whichever version Infuse picks up on first?
This would be a separate feature and something we plan to support in a future version. You can follow this thread.
1 Like
Can we also get tag recognition for 3D titles? Both Side by Side (SBS) and Top over Bottom (TOB).
Also, if I have the following scenario, would Infuse show four versions? Two for resolution, two for cut?
Alien.1979.Theatrical.720p.mkv
Alien.1979.Directors.Cut.1080p.mkv
Maybe you’ll get dynamically adjusting options as I briefly sketched out in the image I posted here that I describe as working in a manner analogous to shopping for clothing or consumer electronics on Amazon …
Basically, to watch a one of your films you’d need to pair up two available options (as you need to choose both an in-stock shirt size and in-stock color (at the size) to add a t-shirt to your shopping cart.
But like shopping on Amazon, the buttons change dynamically as you go … so you can hit either the button for “extra-large” or the button for “blue”, and the rest of the buttons update based on what’s available. Select “4K” and the edits you have in 4K are highlighted. Or select “Director’s Cut” and whichever resolutions you have that version of the film in become highlighted. Pick two, add to cart (push play), and go watch your movie!
…
Or maybe it won’t be anything like that at all. lol. Someone taking part in the beta probably has an idea. 
Maybe at some point, though 3D seems to be fading out as a thing. For now, you could add these as an Edition tag.
You mean you have 4 individual files?
- Alien.1979.Theatrical.720p.mkv
- Alien.1979.Theatrical.1080p.mkv
- Alien.1979.Directors.Cut.720p.mkv
- Alien.1979.Directors.Cut.1080p.mkv
If so, then yes. Here’s what you’d see with those 4 files.
1 Like
I’m digging it. Very nice work. 
1 Like
Tell that to James Cameron.
Excellent. Very excited for this !!!
Here’s an updated list of all the automatically recognized tags.
- Director’s Cut
- Extended Cut
- Theatrical Cut
- Cinematic Cut
- Final Cut
- Unrated Cut
- TV Cut
- Uncut
- Special Edition
- Ultimate Edition
- Black & White
- Wide Screen
- Full Screen
- IMAX
- Part x (cdX, discX, diskX, dvdX, partX, ptX)
This is how the tags will appear in English. These will be localized for all the available languages for a more native experience.
2 Likes
These will need to be in the { } brackets correct? Not just part of the file name?
No, these would be detected without the brackets. In the bracket you can put whatever you want.
1 Like
I believe he wrote these will be parsed automatically (without brackets), and any other text not so treated can be included using the {edition-TEXT} format.
I thought the automatically recognized would not have to have the word “edition-_” on it.
There probably should be some other limiter as to where Infuse looks for these if not the {} brackets.
Maybe look for these words only after the year in the file name?
No brackets or ‘edition’ text required for this this particular list of items.
The edition tag can be used in addition to this if you want to specify other arbitrary tags, or tweak how the tags appear.
Also, these only kick in if you have multiple versions of the same item. If your library consists of single copies of everything (which is probably most people), this new feature will have no impact.
2 Likes
Just was looking at a few possible problem areas
And also movies like The Hunger Games where the words “Part 1” are actual parts of the name.
1 Like
Titles which have ‘Part 1’ as part of the actual title are ignored here. This applies to things like Harry Potter and The Deathly Hallows: Part 1.
If you have an item title that matches one of the tag items it will not affect matching.
2 Likes
Thanks James! Will continue poking at things with a stick. 
2 Likes
Exactly. No brackets, no “edition-“.
Agree it makes sense to only parse this info if included after the release year, but enough people don’t include the date that he’s probably decided accounting for that is too problematic.
(While writing my own scripts to parse filenames, I’ve had to account for dates that aren’t parenthesized, those that are, those that are in brackets, and those that I might misidentify because they’re actually movie titles or included in movie titles … which happens more than I’d thought … even after limiting my consideration to only 4 digit numbers beginning in 19 or 20).
The phrases listed are specific enough they aren’t likely to be included in the names of titles and be mistaken (though I wouldn’t be surprised if “black and white” won’t be at some point … I do know that just searching for “IMAX” and pulling the text from the title broke my parsing of one such item — “Voyage of Time - An IMAX Documentary” — which became just “Voyage of Time — An Documentary” in my first attempt).
Thus I get why my preferred abbreviations won’t be parsed that way. Though I do wish they might be if included in brackets absent “version-“ tagging …. but I grok why such accommodations inevitably lead to such considerations inevitably increasing the chances for things to break.
Another question, can the word “and” be used in place of the ampersand ?
There are still some that prefer not to use the ampersand in file names as some operating systems don’t handle it gracefully.