Unrecognised movies & metadata

[Roofus]

Hi

Now I have re-maintained my library I have noticed something quite strange on the odd films metadata. For example I have a movie called "Tarzan (PG).mp4", this appears in my "Recently Added" playlist but as "tarzan (pg)". I checked the file data and there is no internal file name in the metadata and I have turned that off from being used anyway.

Whilst the maintain runs I can see all the movies change their existing names to the file name in lowercase but all drop off additional info like (2), (15) etc. It seems that some names fail to be found but rather than reverting to their old name or their file name, they drop into lowercase but retain the full name, i.e. the (PG) disappears but then returns as (pg).

Then to make things stranger I go to properties of the movie, remove the (pg) and hit search, it then find the movie without a problem.

I then test again but remove from the physical file name the (PG) and refresh the "Recently Added" playlist and Tarzan disappears. So I go to the Folder view and find him, click on the name and the metadata is fully updated correctly. Go back to recently added and he's back again. I am guessing this is happening because when I rename the file and refresh at that stage its not been re-added with the new name and as it doesn't exist on the old name it drops, when I click on the folder it forces Mezzmo to re-add and that's why it reappears in recently added.

Steve

[Roofus]

Ok, just spotted the obvious, its all my "PG"'s. All my (U), (12A), (12), (15) & (18) are ok, its (PG), none of these have worked.

Steve

[Paul]

Hi Steve,

So you are saying that "Tarzan (PG).avi" does not get correct movie metadata when you add this file into Mezzmo or maintain it?

[Roofus]

Correct nothing with (PG) on the end does. I created a new playlist by rating and the only pg ones I have is where I havnt given them a pg rating myself. I.e I suffixed with (15) but metadata shows as pg so they work but when I have used (pg) they don't get recognised.

Ps: have you changed time zone or something. I didn't expect an answer until 1am

[Paul]

Understand. Having (PG) at the end does confuse searching for movies on online web sites and that's why you are getting differing results. The normal approach is to name your movies with the year - e.g. Inception (2010).

[Roofus]

Thanks Paul, I can rename all my movie files now anyway because of v4, I will just keep the (Cert) in the folder name so folder view still shows the rating. Will adding the year help the search when the file is a remake?

What I didn't expect is (U) works fine, as does (12A), if it were just numbers in between the () I could understand the issue.

My only worry is some of the ratings look rather dubious, I cant see why but for example the Disney TV film Dadnapped gets an R18! When I check online in Mezzmo under properties the rating comes back as "G (US)" on the details but hitting OK turns it to a R18.

Another example is say "Cougars Inc." IMDB site shows as UK15 with an MPAA of R. When I check online in Mezzmo under properties the rating doesn't return as UK, it normally returns a US even though my preference is UK, then it translates it to R18

Animals United is similar, that returns "0 (DE)", has a MPAA of PG but turns into a R18, in the UK its a "U"

Would I be correct in thinking that although I have selected UK certificates it returns an American MPAA and translates it from a US rating to UK rather than actually finding out what the UK BBFC certificate is and sometimes this translation gets it wrong?

Obviously none of these files are great and my filter to prevent these being streamed is probably a bonus but I am worries some 15+ rated films will get streamed as a lower age range.

Steve

[Paul]

Adding the year does help when there are multiple movies with the same name. For example, 'Cape Fear' was made in 1962 and 1991. Without the year, Mezzmo will collect just the first match (the 1991 remake), which may or may not be what you want.

Regarding the wrong UK content rating, we've reproduced your error and have fixed it just now. The fix will be included in the v4.0.2.0 minor release that we are preparing now.