Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 Because your folder name and file name prefix are the same so they are considered the same and grouped into multi-version. As the kb rule has changed slightly to accommodate different variables but dev has not provided documentations for it. 21 Day Fix/21 Day Fix_ABS fix (2014) So all the files need to be in their own folders to not be grouped as I don't know the entire variable of grouping now as it use to be only this. Each version must begin with the folder name, followed by " - ". But not the case anymore.
GrimReaper 4740 Posted August 27, 2024 Posted August 27, 2024 17 minutes ago, Happy2Play said: Because your folder name and file name prefix are the same so they are considered the same and grouped into multi-version. As the kb rule has changed slightly to accommodate different variables but dev has not provided documentations for it. 21 Day Fix/21 Day Fix_ABS fix (2014) 21 Day Fix and Turbo Fire were not multi-versioned as opposed to Slim in 6 though all three of those folders and files underneath follow same naming structure, that's the inconsistency that was trying to be traced. 5 hours ago, BaronVonJ said: But why weren't the 21 Day Fix and TurboFire folders grouped together the same way then? All three folders had the same naming convention where the files have the <folder name>_ as a filename prefix.
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 Not sure then but either way the new rule partially applied and have seen similar in other topics as same folder and filenames will be an issue per grouping rules. If these are independant items really should be in their own folders.
GrimReaper 4740 Posted August 27, 2024 Posted August 27, 2024 I agree, but in current scenario, either all of them should've been grouped - or none should. Parser logic is breaking somewhere.
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 (edited) 9 minutes ago, GrimReaper said: I agree, but in current scenario, either all of them should've been grouped - or none should. Parser logic is breaking somewhere. Not sure as I get grouped versioning for 21 Day Fix with info provided and will guess I will if I tested each one shown they will all group. Edited August 27, 2024 by Happy2Play
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 Dev need to provide further guidance as you have to be creative with naming scheme to prevent grouping. 21 Day Fix/21 Day Fix = Abs Fix (2014)
GrimReaper 4740 Posted August 27, 2024 Posted August 27, 2024 Guess it's something particular to OP's setup, as both 21 Day Fix and TurboFire are clearly folders, while Slim in 6 multi-versioned movie. On 8/26/2024 at 2:54 PM, BaronVonJ said:
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 (edited) True and can be impossible to identify unless it is reproducible. As initially I was thinking collapse flags but that has nothing to do with multi-versioning. But since these are single files in a folder it creates a parsing variable verses file in their own folder. Edited August 27, 2024 by Happy2Play 1
BaronVonJ 12 Posted August 27, 2024 Author Posted August 27, 2024 @Happy2PlayNone of these three folders followed this documented convention: Each version must begin with the folder name, followed by " - ". The files were all named with folder name, followed by "_ ", and then the individual video name. The only thing I changed, for the only folder that was grouping the files, is to get rid of the underscore. I just tried the same process of removing the 21 Day Fix folder from the library folder, scanning, confirming them gone in the UI, rotating the log, and enabling debug log, then adding the files back in one at a time and scanning with each file. Doing them one at a time they were stacked. However, copying all the video files (without the nfo files) into the library and doing one scan they were again treated as a folder. I did not remove the underscore from the 21 Day Fix filenames during this test, neither did I add the provider IDs in the filenames. The initial library scan was, of course, done with all the files in all three directories present (with underscores and without provider IDs, and no NFO files). The only thing I can maybe think of is the Slim in 6 TMDB search results included one entry without the supplemental video name in the title and no metatadata other than an IMDB ID. I have since updated that entry in TMBD to be the Cardio video. I'm going to try removing it and re-adding it as the entire directory with the underscore and without the TMDB IDs. embyserver-63860371566.txt embyserver.txt
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 True as it is undocumented now. As there was a similar issue with Music Videos with Artist folder / prefixed Artist names. But do not know what version it happened in.
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 But would have to have seen the content of the nfo files but will guess they were multi-versioned containing the same info making all the same base item.
BaronVonJ 12 Posted August 27, 2024 Author Posted August 27, 2024 The NFO files from which folder? There were no NFO files present when I first created the library. All the NFO files I have were created by Emby.
Happy2Play 9780 Posted August 27, 2024 Posted August 27, 2024 (edited) 15 minutes ago, BaronVonJ said: The NFO files from which folder? There were no NFO files present when I first created the library. All the NFO files I have were created by Emby. Yes and per the parser on creation could think all these item are one per folder and file naming. But find it really odd in you getting random result as me reproducing multi-versions every time. But testing your naming scheme via 4.8.8.0 and 4.9.0.30 I get multi-versioning. Edited August 27, 2024 by Happy2Play
Luke 42078 Posted August 29, 2024 Posted August 29, 2024 We'll need to add options on the library to control whether multi-version should happen at all. Then you can just disable it.
Happy2Play 9780 Posted August 29, 2024 Posted August 29, 2024 (edited) 18 minutes ago, Luke said: We'll need to add options on the library to control whether multi-version should happen at all. Then you can just disable it. That may help some but situations like this, User has to know the variables that cause it as they may want multi-version only on correct content. As there are false matching happening on same folder/filename prefixing and requires creative naming hacks to prevent. Guess overall issue multiple videos in item folder with folder name prefix. Edited August 29, 2024 by Happy2Play 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now