Germany
- Thread starter
- #11
Hi.
Lots of metadata fields like Actor, language or director are probably multi value fields. A movie has more than one actor and it can have more than one language or director. MKV needs those as many items with one entry each. Lots of tools store this as one item with many entries. Some tools separate those entries with "/", others are using "|" and others are using "," and so on...
To give you a short impression here is Stanley Kubrick as director of "A Clockwork Orange" stored in your movie.xml file (generated by MediaBrowser, if I'm right):
And here is James Cameron as director of "Avatar" stored in avatar.nfo generated by tinyMediaManager:
For Stanley Kubrick it would look like:
For mkv tagging this has to be in this form:
As you can imagine this is a huge amount of comparing and calculating. The tMM version would be much easier to transform into a valid MKV tag. But it has to be done completely different for every tool out there that will generate such metadata files. The tags MKV Buddy uses are stored the same or a similar way in nearly all those metadata files. That's why I've added "MPAA ratings" but not added "Genres". Every extra tag I will add let the failure rate increase enormous.
This is a general decision if I only support a single tool (and that would be tMM as I use it for real) and add as much tags as possible (also I personally don't need or use a lot of them) or try to support as much tools as possible by using the most important tags only... I went for the later one as it would be useful to a lot more people out there.
This nearly is impossible to achieve. Every app is generating different named tags in the nfo files. To tag mkv files those fields need to have specific formats... I need to transform those entries in the code. An user editable ini file will make this nearly impossible.
Lots of metadata fields like Actor, language or director are probably multi value fields. A movie has more than one actor and it can have more than one language or director. MKV needs those as many items with one entry each. Lots of tools store this as one item with many entries. Some tools separate those entries with "/", others are using "|" and others are using "," and so on...
To give you a short impression here is Stanley Kubrick as director of "A Clockwork Orange" stored in your movie.xml file (generated by MediaBrowser, if I'm right):
Code:
<Person>
<Name>Stanley Kubrick</Name>
<Type>Director</Type>
<Role>
</Role>
</Person>And here is James Cameron as director of "Avatar" stored in avatar.nfo generated by tinyMediaManager:
Code:
<director>James Cameron</director>For Stanley Kubrick it would look like:
Code:
<director>Stanley Kubrick</director>For mkv tagging this has to be in this form:
Code:
<Simple>
<Name>DIRECTOR</Name>
<String>Stanley Kubrick</String>
<TagLanguage>und</TagLanguage>
<DefaultLanguage>1</DefaultLanguage>
</Simple>As you can imagine this is a huge amount of comparing and calculating. The tMM version would be much easier to transform into a valid MKV tag. But it has to be done completely different for every tool out there that will generate such metadata files. The tags MKV Buddy uses are stored the same or a similar way in nearly all those metadata files. That's why I've added "MPAA ratings" but not added "Genres". Every extra tag I will add let the failure rate increase enormous.
This is a general decision if I only support a single tool (and that would be tMM as I use it for real) and add as much tags as possible (also I personally don't need or use a lot of them) or try to support as much tools as possible by using the most important tags only... I went for the later one as it would be useful to a lot more people out there.
And then something like Icaros would have to expose them to the operating system... Tough.