Use realname instead of ID3 mp4 etc... tags

can we make it so that we can select between showing realn ame of the media and displaying of id3 mp4 tags?

some times downloaded media has scene and release data in the name and year field that mucks up the title names in the plex library.

Messing with the local agent priority does not fix the issue it would be nice to turn it off.

Plex is not a file browser. Never was, probably never will be.

Allow me to be blunt here: if you don’t pay for your music, then invest at least a little bit of work to clean up the embedded meta tags from all the spam.
It can even be automated to derive the most important things from the file names etc.

2 Likes

This problem happens with video media and metadata in the library viewit seems tags takes precedence over scraped metadata and the naming/ structure of the media folders and files.

Yes I have been cleaning it up with mp3tagtools, but as there is no formal standard for media tags in video i have been nuking them and only including date and title to fix the plex display.

What agent are you using? If it’s a modern agent (Plex Movie, Plex Series), ignore everything under Settings > Agents, and for each library, make sure Manage Library > Edit > ā€˜Prefer local metadata’ is unchecked:

All of my media has nfo and local assets scraped with media companion, but it preferred the embed tags over the nfo and name folder structure contents

Plex is not Kodi. Therefore it doesn’t use .nfo files.

Plex will only read embedded meta tags from video files if they are in MP4/m4v format.
If you are removing the embedded tags before adding the file to a Plex library, they won’t be any trouble.
The same applies if you change the container format to MKV.

If you name and organize your files as required, Plex can query metadata from its own metadata cache at plex.tv (if it is a video that can be matched)

If a video can be matched, and it has embedded meta tags as well, the check box ā€œprefer local metadataā€ decides which is given preference.

I was under impression the tick box means it uses local assets to scrap locally.
So that tick box makes it prefer the embed tags to the plex scraper?
So I will have to use a custom xbmcscraper if I want to import my own metadata?

Precisely.

You could do that, but:

  • the library would be one of the ā€œlegacyā€ type, so all the features which are available within a modern library are not available
  • currently there are only custom agents based on Python. And Python will be removed from Plex relatively soon (starting on the Shield, due to nVidia’s request)
  • a replacement API for custom agents that don’t use Python hasn’t been published yet (though it is in the works and will come before the removal of Python)
1 Like

To be honest I’m unsure if I have something wrong or are still on an old library or the UI has changed from the guides in the articles as the new plex scrapers do not show up in settings agents.

But if I go to advanced settings in the manage library it is set to the plex movie agent.

The migration information on the articles are I guess from an older version also as it suggests to select the radio button (upgrade matching) from the elipisis menu that is not on my version of plex server?

Under agents and movies I only see plex legacy one listed.

It would be It would be nice if they converted the articles to a user editable wiki as it seems a lot of it is outdated.

So they plan on implementing LUA or something why the hate for python from nividia?

If you are referring to the item ā€œAgentsā€ in the settings, that is indeed only referring to the legacy agents. Simply because only the legacy agents have global settings. Whereas the modern agents have all their settings per-library, and the place for their settings is the Advanced tab in the properties of each library.

There is also a ā€œlegacyā€ version of that agent. (It used to be called the ā€œIMDb agentā€, a long time ago.)

If the drop-down selector in your library only has legacy agents available, it means your library is of the legacy type.

That should be available in the ellipsis menu of all legacy libraries. But not if the library has been converted already.
And it never appears in the ellipsis menu of items within a library.

I don’t know any details myself yet.

That’s no ā€œhateā€. It’s reasonable in a way, simply because the version of Python in Plex is 2.5, which has long been deprecated. Though it would be quite elaborate to exploit its known security weaknesses, it’s not impossible. Removing it is therefore sensible.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.