Tools and other software tinyMediaManager - The Media Manager for MediaPortal (Win/Mac/Linux) (6 Viewers)

[megahorst]

last time i try to import the tmm mp nfo, it did not work for me, not in fanart-1,2,3,4 and not in certification .... and i think i post about it long time ego...
was "R" , then was change to "US_R" witch mp skins cannot read (i means as default setting and mp system) if a community skin designer make his skin logo the view in one way , is not mean he did the correct way for mp style...

You are right. I have initiated these changes to tmm too.

The fanart:
I have had discussions with @Deda regarding multiple fanart. He stated that this syntax have to be used:

<fanart>
    <thumb>videofilename-fanart.jpg</thumb>
    <thumb>videofilename-fanart1.jpg</thumb>
    <thumb>videofilename-fanart2.jpg</thumb>
    <thumb>videofilename-fanart3.jpg</thumb>
    <thumb>videofilename-fanart4.jpg</thumb>
  </fanart>

For me this works perfect. I have multiple fanart in MyVideos for all TMM imported movies. I have attached one of my working nfos.

Certification logos:
That is another thing ...
When I have talked to Manuel about the logos in 2013 TMM wrote this into the tag:
<mpaa>DE:FSK 12 / DE:FSK12 / DE:12 / DE:ab 12</mpaa>

This did not work, because the entry of the tag and the filename have to be equal (except the file extention)

Therefor Manuel and I have decided for the actual solution. With this notation it is possible to store separate logos for each country. I'm sure Manuel will find a solution for MePo if this did not fit the needs

US_G
US_PG
US_PG13
US_R
US_NC17
US_TVY
US_TVY7
US_TVG
US_TVPG
US_TV14
US_TVMA
DE_FSK0
DE_FSK6
DE_FSK12
DE_FSK16
DE_FSK18
GB_UC
GB_U
GB_PG
GB_12A
GB_12
GB_15
GB_18
GB_R18
RU_Y
RU_6
RU_12
RU_14
RU_16
RU_18
NL_AL
NL_6
NL_9
NL_12
NL_16
JP_G
JP_PG12
JP_R15
JP_R18
IT_T
IT_VM14
IT_VM18
IN_U
IN_UA
IN_A
IN_S
GR_K
GR_K13
GR_K17
GR_E
FR_U
FR_10
FR_12
FR_16
FR_18
CA_G
CA_PG
CA_14A
CA_18A
CA_R
CA_A
AU_E
AU_G
AU_PG
AU_M
AU_MA15
AU_R18
AU_X18
AU_RC
CZ_U
CZ_PG
CZ_12
CZ_15
CZ_18
CZ_E
DK_A
DK_7
DK_11
DK_15
DK_F
EE_PERE
EE_L
EE_MS6
EE_MS12
EE_K12
EE_K14
EE_K16
FI_S
FI_K7
FI_K12
FI_K16
FI_K18
FI_KE
HU_KN
HU_6
HU_12
HU_16
HU_18
HU_X
IS_L
IS_7
IS_10
IS_12
IS_14
IS_16
IS_18
IE_G
IE_PG
IE_12A
IE_15A
IE_16
IE_18
NZ_G
NZ_PG
NZ_M
NZ_R13
NZ_R16
NZ_R18
NZ_R15
NZ_RP13
NZ_RP16
NZ_R
NO_A
NO_7
NO_11
NO_15
NO_18
PL_AL
PL_7
PL_12
PL_15
PL_AP
PL_21
RO_AP
RO_12
RO_15
RO_18
RO_18X
ES_APTA
ES_ER
ES_7
ES_12
ES_16
ES_18
ES_PX
SE_BTL
SE_7 
SE_11
SE_15
CH_0
CH_7
CH_10
CH_12
CH_14
CH_16
CH_18
TH_P
TH_G
TH_13
TH_15
TH_18
TH_20
TH_Banned
NOT_RATED

 

[Lehmden]

Hi.
Right atm, we're working on the implementation of .nfo support in MP2. And for sure we will support tMM .nfo files in both, XBMC and MP style. During the developing we found a small issue, that you probably want to know about. Here is a quote from an internal posting on this topic:

tMM in XMBC mode uses a <tmdbId> tag (also in the new <ids> sub-tag> whereas MKVBuddy uses <tmdbid> (watch the casing of the 'i'). tMM in MP mode doesn't Export the tmdbid tag at all which is why you don't see the warning there.
I don't really know which one is right, but I think, MKVBuddy should be the right one as all other tags are written completely in small letters. The XML spec says that XML is case sensitive so according to the spec, These are two different fields.
As I said, not a big Problem, I'll Support both - only one additional line of code. But if I'm right with all letters in tagnames should be small: If someone knows the tMM programmers, it would probably be a good idea to tell them so they can check whether this was just a typo on their side...

 

[mlaggner]

Hi,

well, the <ids> tag is a tag we store for our own there is no such tag in the Kodi specification, but since Kodi ignores them, we thought, we use it for reimporting tags, after a databasee wipe.
Once we write our NFO, we write the imdbid to <id>, tmdbid to <tmdbid> and lose all other collected ids (like zelluloid, moviemeter.nl, odfb,...). This is the reason we've intoduced this new tag.
the subtag-name (e.g. <tmdbId> is simply the ID-key we use in our idstore inside tmm). this is why we can't change it at all (Java is case sensitive and a loaded tmdbid from the NFO will not match the tmdbId inside tmm);

But if you want to use it, we will find a useable solution (maybe we can change the id-keys to some sort of "standard" - I've only to get sure not to break the databases of our users )

 

[azzuro]

Hello
@mlaggner : i have send you message from your website, for support MediaPassion scrapper.
.
Can you support it ? it have it's own ID, the tag is "CinePassion".

Thank you

 

[Helios61]

Creating .nfo files doesn't work

Hi @mlaggner

While writing .nfo files, unfortunately i get the following error message ->

I hope, you can help. Log is attached.
Best regards
Helios

 

[mlaggner]

Please try to remove the movie from tmm and re-import it (update datasource).
looks like a database inconsistency (which happen from time to time until we can switch the engine :/( )

 

[Luca Brasi]

Hi mlaggner,

I've got an issue with the renamer.

My pattern is like this
$1\$M\$T ($Y) - $I{ - $3}

This results in
..\C\Captain America Collection\Captain America The First Avenger (2011) - tt0458339\Captain America The First Avenger (2011) - tt0458339.mkv"
which is as intended.

But now if the collections name and it's first character doesn't match the ones from the title I'll get this
..\V\Millennium Series\Verblendung (2009) - tt1132620
and
..\T\Millennium Series\The Girl Who Kicked the Hornet's Nest (2009) - tt1343097\The Girl Who Kicked the Hornet's Nest (2009) - tt1343097.mkv

Following the pattern it is pretty obvious to get this but obviously I'd like to go whith
..\M\Millennium Series\Verblendung (2009) - tt1132620
..\M\Millennium Series\The Girl Who Kicked the Hornet's Nest (2009) - tt1343097\The Girl Who Kicked the Hornet's Nest (2009) - tt1343097.mkv

I guess adding the collection's first character as a variable for renaming still wouldn't solve it cause it should only be used in place of $1 if a collection is present?

 

[mlaggner]

yes, sounds a bit more complicated
have to think about it, because we should solve this without getting too complex..

 

[Luca Brasi]

Good luck with that
What can I do?

 

[Helios61]

Hi @mlaggner
Is it possible to add an option to configure a standard view in one of the upcoming releases of tmm? Most of time i use the view by "date added". It would be great, if this view (or the latest used view) could be loaded at statup of tmm.
Best regards
Helios