Jump to content

Odd Metadata Issue Since Switching to Linux


jrmed
Go to solution Solved by Luke,

Recommended Posts

Hi All,

 

         Got a bit of an odd one, I've been running Emby under windows off a desktop for about a year or so now, all's been pretty OK barring some weird issues with subtitles on Roku. I've recently rebuilt my NAS server and I'm now running Emby under Linux (Ubuntu 18.04.3) on that instead.

 

The oddity is that my media libraries imported under Windows without issue but when I import in Linux I'm having a lot of things which are failing to be recognised, pretty much all of the movies in question have names "The <blah>" whose files are named in I suppose "library" style (so they sort properly), i.e. "<blah>, The (YYYY).whatever" on disk, seems that the code between windows and linux are handling these differently (bit odd that as I'd assumed stuff like the metadata agents would be pretty platform agnostic).

 

Seems strange to me that the metadata agents under Windows were able to identify these but not under Linux :/ (as I say it's a bit of a weird one).

 

Anybody seen this before and have some insight (I'd rather not have to go through the entire collection and manually identify a bunch of stuff if I can avoid it :/ )?

 

Thanks,

 

-J

Link to comment
Share on other sites

As requested.

 

Movie: The Terminal Man (1974) (https://www.imdb.com/title/tt0072267)

 

Filename: "Terminal Man, The (1974) [WS x264-2.0AC3].mkv"

 

On my freshly installed, Linux based Emby 4.2.1.0 server, fails to be identified in the Library scan. If go to "Identify" and manually search "Terminal Man" I get the expected result.

 

The same file was correctly identified by the Library scan (the same directory is presented to each Emby instance) on my Windows install of Emby (which is version 3.5.3.0 so I suppose this could be a regression?)

Edited by jrmed
Link to comment
Share on other sites

Fresh copy of 4.2.1.0 run up on Windows exhibits the same behaviour as I'm seeing with 4.2.1.0 under Linux so it seems this is a regression... Unless of course I'm mis-remembering and I had to manually fix all of these when I switched to Emby originally :/

 

I think I still have the original portable archive I used for my install lying around somewhere so I might have to re-test with 3.5.3.0 to determine whether this is actually a regression or if I should put in a feature request ;)

Edited by jrmed
Link to comment
Share on other sites

OK, apparently I'm misremembering, because 3.5.3.0 also exhibits the same behaviour, I must've mentally blocked out manually updating 200 odd movies ;)

 

Is there somewhere specific I should post this as a "feature request"?

Link to comment
Share on other sites

Happy2Play

As requested.

 

Movie: The Terminal Man (1974) (https://www.imdb.com/title/tt0072267)

 

Filename: "Terminal Man, The (1974) [WS x264-2.0AC3].mkv"

 

On my freshly installed, Linux based Emby 4.2.1.0 server, fails to be identified in the Library scan. If go to "Identify" and manually search "Terminal Man" I get the expected result.

 

The same file was correctly identified by the Library scan (the same directory is presented to each Emby instance) on my Windows install of Emby (which is version 3.5.3.0 so I suppose this could be a regression?)

 

Are you saying you have a flat file structure (ie no movie named folders)?  Can you provide a server log so we can see what Emby is actually querying from the provider sites.

Link to comment
Share on other sites

Yes, all the movies in my collection are in a single folder, no point breaking it up any more since they're all single files. TV and Music are in separate directories broken up by Series and Artist respectively.

 

Let me do some juggling so I can get you a clean log.

Link to comment
Share on other sites

Happy2Play

@@Luke Do to the naming scheme, Emby queries the title "Terminal Man, The" and returns no results.

2019-10-03 18:52:07.679 Info App: MovieDbProvider: Finding id for item: Terminal Man, The
2019-10-03 18:52:07.934 Info HttpClient: GET https://api.themoviedb.org/3/search/movie?api_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&query=Terminal+Man%2C+The&language=en
2019-10-03 18:52:07.935 Info HttpClient: GET https://api.themoviedb.org/3/person/1388928?api_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&append_to_response=credits,images,external_ids&language=en
2019-10-03 18:52:08.246 Info HttpClient: GET https://api.themoviedb.org/3/search/movie?api_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&query=Terminal+Man++The&language=en
2019-10-03 18:52:08.383 Info HttpClient: GET https://private.omdbapi.com?apikey=xxxxxxxxxxxxx&plot=full&r=json&y=1974&t=Terminal+Man%2C+The&type=movie
2019-10-03 18:52:08.574 Info HttpClient: GET https://api.themoviedb.org/3/person/1512971?api_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&append_to_response=credits,images,external_ids&language=en
Edited by Happy2Play
Link to comment
Share on other sites

I'd expect this to be a not uncommon naming convention since otherwise you have huge numbers of files turning up in "The <blah>" (Emby isn't the only way I access this media) ergo the reason I'd like to see it as a feature (If it provides some incentive, Plex handles this naming convention ;) )

Link to comment
Share on other sites

If there's an interface to write my own metadata agent I'm happy to do that but I'm not sure if Emby provides that sort of extensibility?

Link to comment
Share on other sites

Happy2Play

This would be a issue for anyone that uses the "T, T (Y)" naming scheme.

Link to comment
Share on other sites

  • 2 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...