I’m splitting up my UHD content from normal content on my server by using editions.
Found that naming the movie either of these ways:
Movie (2000) {edition-[UHD]}/Movie (2000) {edition-[UHD]}.mkv
Movie (2000) {edition-[UHD] Director's Cut}/Movie (2000) {edition-[UHD] Director's Cut}.mkv
That the movie shows up in the Plex clients with an edition of [UHD.
Since { and [ are interchangeable (although not documented as such), this is most likely a regex bug where it is looking for an ending ] OR an ending } and then not looking for more characters.
I’ll just end up renaming the folders, but thought it would look nicer being:
[UHD] Director’s Cut than UHD Director’s Cut
Please add this to your backlog to address.
They are not.
Square brackets have a different function in Plex. Plex will ignore the content of the first pair of square brackets, so it doesn’t interfere with the matching process.
This is how I separate 4K versions from others.
Deadpool 2 (2018) {Edition - Super Duper Cut} [1080p]
Deadpool 2 (2018) {Edition - 4K Super Duper Cut} [2160p]
Please try this name and you will see that the 2nd set of [] also impacts how the file name is parsed:
Blade Runner 2049 (2017) [UHD,HDR10,22 mbps,MLP FBA+DTS 5.1+AC3 5.1] {edition-[UHD]}.mkv
Unfortunately, they are. Please also look at this example, where the file is named as such:
Blade Runner 2049 (2017) [UHD,HDR10,22 mbps,MLP FBA+DTS 5.1+AC3 5.1] [edition-TEST].mkv
As you can see, it will still use [] for things like edition. I know this is just for flexibility, but I do think this is why my initial BUG exists. There are other posts showing the interchangeability of [] and {}.
