Wired multiple eposidedetails in nfo file

[scegg 12]

There is a media file of a season of a TV series. If I place it (4th file in screenshot), not like its neighbors, displayed with a strange index. Checking the nfo file of this file created by EMBY, they are many episodedetails nodes as multiple roots. I tried to delete the media from EMBY, copy the media file back without NFO file. After rescanning the library, the problem still and the NFO is created as the same.

How to fix this?

[灼眼的夏娜II].[SumiSora&Ktxp][Shakugan_No_Shana_II][DVDRip][04][GB_BIG5][X264_AAC](4E1E933E).nfo

[GrimReaper 4740]

11 minutes ago, scegg said:

If I place it (4th file in screenshot), not like its neighbors, displayed with a strange index

What is the actual file name? Something in it is confusing parser/making Emby think it is multi-episode file, from Ep.4 to Ep.933, hence you're seeing that in the UI. 

11 minutes ago, scegg said:

Checking the nfo file of this file created by EMBY, they are many episodedetails nodes as multiple roots.

For the same reason as stated above, each episode's getting one <episodedetails> node written. 

Edit: Saw it in your screenshot. 

It's "4E1E933E" segment (likely CRC). Change/delete that part of the filename, rescan. 

Edited October 21, 2024 by GrimReaper
Append

[scegg 12]

1 minute ago, GrimReaper said:

What is the actual file name? Something in it is confusing parser/making Emby think it is multi-episode file, from Ep.4 to Ep.933, hence you're seeing that in the UI. 

For the same reason as stated above, each episode's getting one <episodedetails> node written. 

File name as in the screenshot: [灼眼的夏娜II].[SumiSora&Ktxp][Shakugan_No_Shana_II][DVDRip][04][GB_BIG5][X264_AAC](4E1E933E).mkv

I guess the problem is because the CRC part of the file name. But even I provide the NFO file myself by deleting all other nodes, it still won't take it but still creating those nodes.

[Happy2Play 9780]

5 minutes ago, GrimReaper said:

What is the actual file name?

Pretty sure it will come back to the parser reading this. 

[灼眼的夏娜II].[SumiSora&Ktxp][Shakugan_No_Shana_II][DVDRip][04][GB_BIG5][X264_AAC](4E1E933E)

 

Edited October 21, 2024 by Happy2Play

[GrimReaper 4740]

Just now, scegg said:

File name as in the screenshot: [灼眼的夏娜II].[SumiSora&Ktxp][Shakugan_No_Shana_II][DVDRip][04][GB_BIG5][X264_AAC](4E1E933E).mkv

I guess the problem is because the CRC part of the file name. But even I provide the NFO file myself by deleting all other nodes, it still won't take it but still creating those nodes.

Yeah, I already edited my post to refer to that segment.

4 minutes ago, GrimReaper said:

Edit: Saw it in your screenshot. 

It's "4E1E933E" segment (likely CRC). Change/delete that part of the filename, rescan. 

You'll have to correct manually.

[Happy2Play 9780]

1 minute ago, Happy2Play said:

4E1E933

As this would technically be Season 4 Episodes 1 thru 933.

But yes will come back to existing CRC topics.

[scegg 12]

Yes. In my test, EMBY is very not like to respect the data saved in NFO file. Even the property is strictly written there, EMBY still want to change it.

[Luke 42078]

2 hours ago, scegg said:

Yes. In my test, EMBY is very not like to respect the data saved in NFO file. Even the property is strictly written there, EMBY still want to change it.

HI, can you please provide a specific example of what you mean? 

[Happy2Play 9780]

2 hours ago, Luke said:

HI, can you please provide a specific example of what you mean? 

Using the example provided as you provide a nfo with correct metadata for S02E04 the parser ignores the nfo info and parses the episode as S02E04-E933 do to naming scheme.

here is the nfo that gets overwritten when episode is imported.

[灼眼的夏娜II].[SumiSora&Ktxp][Shakugan_No_Shana_II][DVDRip][04][GB_BIG5][X264_AAC](4E1E933E).expected.nfo

When you import said episode you then get the provide nfo is overwritten with what OP provided above.

 

[scegg 12]

5 hours ago, Luke said:

HI, can you please provide a specific example of what you mean? 

As I said in original post, if I provide an NFO file contains only the 1st root node with the file and scan the media file in EMBY, the EMBY will NOT use the info from NFO but fill all others into NFO, generating the file as attached.

 

I guess that EMBY can only GUESS the file info from the name and folder structure, that data can be inaccurate, comparing to the info provided with the existing NFO file. So, if the NFO file with the same file name and in the same folder as the media file, the NFO should be read and trust with more privilege than the EMBY scanner guessing. But the truth design is, EMBY always trust itself than the NFO.

Edited October 22, 2024 by scegg

[Luke 42078]

OK so the issue is that the data in the nfo is supported, but season and episode numbers come from the filename.

So the server will have to be able to handle that file name.

[scegg 12]

2 hours ago, Luke said:

OK so the issue is that the data in the nfo is supported, but season and episode numbers come from the filename.

So the server will have to be able to handle that file name.

yes. That’s the root cause. Emby read nfo but not the node episode/season of it. 

[scegg 12]

Is that possible to redesign the tvshow folder locating and episode nfo reading process in future ? If true, I guess I can provide a flow that I’m using for my own app.

[scegg 12]

I wrote a tool myself to process based on NFO files and creating junction files to another folder for Emby library. All my sources have tvshow.nfo or movie.nfo.

Step 1: Locate the folders for TVShows and Movies
(1) Find all tvshow.nfo as well as other top nfo files, like movie.nfo in all folders including subfolders. The folder has .ignore file should be ignored.
(2) Try to read those nfo files. Ignore all those in illegal format. Store the full path of the folder which includes the nfo file into a HashSet for tvshow and movie.
(3) Further, for scanning tvshows not with tvshow.nfo, all folders saved in this HashSet should be ignored, nor to included as a season of another tvshow either.

Step 2: Locate the season folders for each tvshow.
(1) In all found tvshow folder, locate the season.nfo in the folder itself and all subfolders. The folder has .ignore file should be ignored.
(2) Try to read those nfo files. Ignore all those in illegal format. Store the full path of the folder which includes the nfo file into a HashSet for all tvshows and a dedicated set for the processing tvshow.
(3) Further, for scanning tvshows not with tvshow.nfo, all folders saved in this HashSet for all tvshows should be ignored, nor to included as a season of another tvshow either.

Step 3: Locate episodes.
(1) For each season folder found, read all nfo files has episodedetails as the root node. If the nfo file has a "original_filename" node, read it as the media file name, or try to locate the media file with the same name as the nfo file. Save the media files into a HashSet.
(2) For all media files in this season folder but not in the HashSet, try to guess the episode number.

Step 4: For my tools only
Generate the folder structure and make junction files into them, linking to the original files.

[Luke 42078]

On 10/23/2024 at 9:39 PM, scegg said:

Is that possible to redesign the tvshow folder locating and episode nfo reading process in future ? If true, I guess I can provide a flow that I’m using for my own app.

It's currently intentional because so many users seem to not be aware of what's in their own nfo files, and then they think something is wrong with the software when they get unexpected season or episode numbers.

[scegg 12]

Okay, so far I'm OK with my own remapping tool. If NFO is out of option, please consider to add a manual mode, totally disable the auto scanning, just list the folder and files and allow user to create tvshow, season, eposide or movie manually.