Identify not working

[crusher11 1101]

I recorded November (2017), which got identified for whatever reason as November (2025). So I manually identified it...and it changed the cast and crew, but nothing else. Release date is still 2025, overview is still the one from the TV guide, and there's no artwork.

embyserver.txt

[Luke 42077]

Hi, what metadata fetchers are enabled on the library and in what order?

[crusher11 1101]

I've just gone back to it and now it's identified it as November Fog (2025) for no apparent reason?

 

embyserver.txt

[Luke 42077]

4 hours ago, crusher11 said:

I recorded November (2017), which got identified for whatever reason as November (2025). So I manually identified it...and it changed the cast and crew, but nothing else. Release date is still 2025, overview is still the one from the TV guide, and there's no artwork.

embyserver.txt 6.74 MB · 1 download

Did you check the metadata editor for locked fields?

[crusher11 1101]

8 hours ago, Luke said:

Did you check the metadata editor for locked fields?

None of the fields were locked. Does Identify even observe field-locking? That would make no sense. And they're obviously not locked given everything has been replaced with the metadata for November Fog, but I have no idea how that happened as I manually identified it as November (2017) and even then nothing happened after that for several minutes. So it appears that a) it took several minutes for the Identify to work and b) it identified as the wrong film anyway.

[crusher11 1101]

@Luke

[crusher11 1101]

@Lukeit's bad enough in the beta channel, but with an issue affecting stable as well it really needs to be addressed.

[Luke 42077]

Hi, can you please show screenshot examples?

[Luke 42077]

I just tested this with a file name of November (2017),.strm and it worked just fine.

[crusher11 1101]

38 minutes ago, Luke said:

Hi, can you please show screenshot examples?

Of what?

[crusher11 1101]

Hmm. Seems it has the correct director and cast, but the wrong artwork, title, overview and release date:

 

 

It has IMDB ID tt29567915, which doesn't match either film, and its TMDB ID is for November Fog.

Edited October 10, 2025 by crusher11

[Luke 42077]

OK I would try using the Identify feature and see if that helps. If it doesn't, then try putting Omdb in the middle ahead of tvdb and then try again.

[crusher11 1101]

36 minutes ago, Luke said:

OK I would try using the Identify feature and see if that helps.

That's what I've been doing!

[Luke 42077]

2 minutes ago, crusher11 said:

That's what I've been doing!

OK please attach the log from trying them in that order. thanks.

[crusher11 1101]

21 hours ago, Luke said:

OK please attach the log from trying them in that order. thanks.

You suggested switching the order if using the identify feature didn't work, my point was that we already know it wasn't working because I've sent you multiple logs of me trying just that.

I just went to look at it again and it is now correctly identified, without me having done anything at all. So I guess the process of downloading and applying the metadata simply took several hours? My whole server has been uselessly slow of late.

[crusher11 1101]

It's happened again trying to identify Ambulance: it's got the cast and director right, but left the images, overview and release date untouched.

embyserver (1).txt

[crusher11 1101]

And an hour or so later, it's all correctly identified.

embyserver (2).txt

[crusher11 1101]

Great seeing @Luke providing assistance to people blatantly violating the ToS while this thread goes ignored.

[speechles 2055]

1 minute ago, crusher11 said:

Great seeing @Luke providing assistance to people blatantly violating the ToS while this thread goes ignored.

I think you should give Luke the same courtesy as all human beings are allowed. Sometimes we make mistakes and get the wrong idea. 

He saw the post asked for a discount for multiple premiere license purchases. The title asked that. He might not have read the entire post in that thread to see clearly it was something shady and underhanded. 

Luke is busy. He might not have had time to come up with a reply to this post yet. It might be in his "drafts" still. He was clearing out the ones where someone else should look at the posts and give input. He didn't do that on purpose and try to harm Emby. We are all human. I am sure he will reply when he has some time to devote to your issue. It is very hard to be in so many places at the same time and so often. Luke is the most dedicated person I know on this forum. Give him a little patience. Thanks.

[crusher11 1101]

4 minutes ago, speechles said:

I think you should give Luke the same courtesy as all human beings are allowed. Sometimes we make mistakes and get the wrong idea. 

He saw the post asked for a discount for multiple premiere license purchases. The title asked that. He might not have read the entire post in that thread to see clearly it was something shady and underhanded. 

Luke is busy. He might not have had time to come up with a reply to this post yet. It might be in his "drafts" still. He was clearing out the ones where someone else should look at the posts and give input. He didn't do that on purpose and try to harm Emby. We are all human. I am sure he will reply when he has some time to devote to your issue. It is very hard to be in so many places at the same time and so often. Luke is the most dedicated person I know on this forum. Give him a little patience. Thanks.

The last time I had an issue I had to wait for over a month while Luke went around bumping 2-year-old threads to ask people if they were still experiencing whatever issue they'd posted about. My server is currently so slow as to be completely useless.

[speechles 2055]

2 minutes ago, crusher11 said:

My server is currently so slow as to be completely useless.

I had the same damn issue the last 2-3 weeks with super slowness. Out of the blue it happened one day after an update. Once my library DB exceeded 4GB I started to get problems. Only had 16GB of memory. Bought 32GB and swapped that out and immediately I feel fast again. There is presently some memory spikes that happen when entering very large libraries. The free space on the Emby server should always be about the same. But it was several GB lower. I noticed the pagefile.sys was gigantic. Figured what could it hurt buy more RAM. Glad I did and now I have a fast Emby server again. Not saying that is your issue just that it was my issue. Old Dell Optiplex 7060 with i5-8500 and she sips power rather than guzzle.

[crusher11 1101]

I'm on a Synology NAS, so “just go buy more RAM” is not an option I have available.

Edited October 12, 2025 by crusher11

[Happy2Play 9780]

13 minutes ago, crusher11 said:

My server is currently so slow as to be completely useless.

OT: Will assume the new db options (system.xml) may need tweaked on a per system basis.

Beta updated

  <MaxLibraryDbConnections>20</MaxLibraryDbConnections>
  <MaxAuthDbConnections>5</MaxAuthDbConnections>
  <MaxOtherDbConnections>3</MaxOtherDbConnections>

Stable updated

  <MaxLibraryDbConnections>5</MaxLibraryDbConnections>
  <MaxAuthDbConnections>5</MaxAuthDbConnections>
  <MaxOtherDbConnections>3</MaxOtherDbConnections>

As I will guess this is another setting that will be completely different across all setups.

[speechles 2055]

15 minutes ago, crusher11 said:

I'm on a Synology NAS, so “just go buy more RAM” is not an option I have available.

Understand. There is only so much they allow. But at least they reverse their HDD decision. There is only so much you can do. I had options thankfully.

@Happy2Playinteresting. Thanks for that bit of info. That would explain the memory spike.

Edited October 12, 2025 by speechles

[crusher11 1101]

Those are 20/5/3 for me at the moment.