Reading the documentation on the “add to library” feature, you’d be under the impression that the integration would be seamless and the correct metadata for the items you add would be exactly the same as they would be on Tidal - this is not the case.
What occurs is: when the item is added from Tidal into a library, instead of using the metadata from Tidal, it uses Musicbrainz which is the main source for Plex’s in-house ‘Music Scanner’ agent. This works perfectly if the metadata is present in Musicbrainz’s database; if the metadata doesn’t exist, then it will replace it with the closest match, which is either the wrong artist or album.
There is no method to revert the changes back to the metadata provided by Tidal (unmatch retains the metadata provided by Musicbrainz)—your only option is to add the metadata to Musicbrainz yourself or edit the metadata directly on Plex for every incorrect match. You can see how that can get troublesome when you want to consolidate your Tidal and local content together.
Going on a comment from a Plex employee on Reddit who coded the implementation, it’s intentional so the metadata and ids are consistent with the rest of the local content in the library.
I would appreciate it if Plex could reevaluate this implementation at some point as it could be improved by adding an option to use Tidal metadata or allow the linking of Tidal content to specific local content.
