Episode name prefixed with '-2'

[PatrickStar 2]

Hi,

I am encountering an issue with a file that is not being recognized properly by my Emby server. I am using youtube-dlp to directly load content from a YouTube playlist onto my server, and the files are named using the video's title and ID. However, Emby is displaying the file incorrectly by treating the "2.0" in the file name as part two of the same episode, even though the video ID comes after it.

This is how the file is stored on the filesystem:

Die Geschichte des Drachenlord - Episode 76： Discord 2.0 [1ZXRMArFl1s].webm

I suspect that the "2.0" in the file name is causing the issue. Is there a way to prevent Emby from detecting the file in this way? As i do use a NodeJS script to do this, ideally, i would like to use a solution that does not require any changes to the Emby server.

I would appreciate any advice or suggestions on how to resolve this issue.

Best Regards
Patrick

[GrimReaper 3289]

Several naming conventions are supported for naming episodes:

Quote

Episode naming conventions

A number of naming conventions are supported:

• show name - S01E01 - Episode Name.ext
• show name S01E01 Episode Name.ext
• anything_s01e02.ext
• anything_s1e2.ext
• anything_s01.e02.ext
• anything_s01_e02.ext
• anything_1x02.ext
• anything_102.ext
• anything_1x02.ext
• 02 Episode Name.ext
• s01e02.ext
• 1x02.ext

By date

Common for long-running daily shows, you can also use the date the episode aired.

• anything_1996.11.14.ext
• anything_1996-11-14.ext
• anything_14.11.1996.ext

https://support.emby.media/support/solutions/articles/44001159110-tv-naming

 

If you don't adhere to those or provide files named in such a manner that they might be interpreted as one of the supported ones - I'd say it's only natural to expect that you'll encounter issues. 

[PatrickStar 2]

9 minutes ago, GrimReaper said:

If you don't adhere to those or provide files named in such a manner that they might be interpreted as one of the supported ones - I'd say it's only natural to expect that you'll encounter issues. 

I'm wondering if there's a way to "escape" numbers in an episode name, for example by using visual spoofing. While I could filter out trailing numbers, I'd prefer a solution that allows me to keep them in the "same name", if possible.

Best Regards
Patrick

[Happy2Play 8281]

Naming scheme should be okay as it is "02 Episode Name.ext" but would guess conditions of a Season folder as would not identify if not in my test.

@Lukewould have to comment but yes numbers in episode name can create issues with multi-episode but the number should never be smaller than the first.

• TV
  • The Tale of the Dragon Lord
    • Season 1
      • The Tale of the Dragon Lord - Episode 76： Discord 2.0 [1ZXRMArFl1s].strm

 

 

But metadata is correct

Nfo has episodenumberend

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<episodedetails>
  <plot />
  <outline />
  <lockdata>false</lockdata>
  <dateadded>2023-03-11 15:31:57</dateadded>
  <title>Discord 2.0</title>
  <year>2023</year>
  <sorttitle>Discord 2.0</sorttitle>
  <tvdbid>9627751</tvdbid>
  <uniqueid type="tvdb">9627751</uniqueid>
  <episode>76</episode>
  <episodenumberend>2</episodenumberend>
  <season>1</season>
  <aired>2023-02-17</aired>
  <fileinfo>
    <streamdetails />
  </fileinfo>
</episodedetails>

Tested on .22

[PatrickStar 2]

So i did some more testing today and it seems that my idea of using visual spoofing does indeed work, so the following map can be used to replace "real" digits in the string:
 

0 => 𝟢
1 => 𝟣
2 => 𝟤
3 => 𝟥
4 => 𝟦
5 => 𝟧
6 => 𝟨
7 => 𝟩
8 => 𝟪
9 => 𝟫

This is how my emby server is recognizing it now:

 

This might be an acceptable solution as i could simply add an option to my script to visually spoof numbers in the video title and put the real title into the files meta tags for any processing down the road, it might also make it compatible to other media servers as i suspect they work the sameish way when it comes down to the library structure.

[rbjtech 4257]

If you are scripting - then maybe use the -o template from yt-dlp to format the output before processing - attributes like the Playlist Index etc can then be used to name it how you see fit - and if you match the emby requirements, then it should be picked up by emby ok.

https://github.com/yt-dlp/yt-dlp#output-template