Non-standard tags in Mediainfo JSON

[BleakleyMcD]

@dericed @JeromeMartinez

The .json output bunching all these tags under some "extra" tag/field while the text output isn't.

/Users/bleakley/github/bleakley/bleakleymm
≈:≈ mediainfo -f --OUTPUT=Text /Volumes/JPCARCHIVE/TESTING/01_mkvEmbed_Testing/01_Crystal-Logic/JPC_AV_01632/JPC_AV_01632.mkv >> /Volumes/JPCARCHIVE/TESTING/01_mkvEmbed_Testing/01_Crystal-Logic/JPC_AV_01632/JPC_AV_01632_mediainfo-Text_output.txt 
                                                                                                                                          
/Users/bleakley/github/bleakley/bleakleymm
≈:≈ mediainfo -f --OUTPUT=JSON /Volumes/JPCARCHIVE/TESTING/01_mkvEmbed_Testing/01_Crystal-Logic/JPC_AV_01632/JPC_AV_01632.mkv >> /Volumes/JPCARCHIVE/TESTING/01_mkvEmbed_Testing/01_Crystal-Logic/JPC_AV_01632/[JPC_AV_01632_mediainfo-JSON_output.json](https://github.com/user-attachments/files/22727437/JPC_AV_01632_mediainfo-JSON_output.json) 

see attached files.

JPC_AV_01632_mediainfo-JSON_output.json
JPC_AV_01632_mediainfo-Text_output.txt

Tags under the "extra" part:

• ErrorDetectionType":"
• Attachments":"
• ATTACHMENTS":"
• CATALOG_NUMBER":"
• COLLECTION":"
• _ORIGINAL_FPS":"
• _PRE_TRANSFER_NOTES":"
• _TAGGED_BY":"
• _TRANSFER_NOTES":"

The four with leading underscore are tags devised for an internal project:
_TAGGED_BY : Entity, name, country ; ex. Smithsonian NMAAHC, James Smithson, US (use ISO 3166-1 alpha-2 codes)

_PRE_TRANSFER_NOTES : Free text for capturing anything concerning the inspection and any physical conservation or preparation of the tape. tape was baked for 20 hrs at 130°F, sticky leader was removed, treated for mold. etc. 

_TRANSFER_NOTES : Free text for capturing any technical notes about the transfer of the tape. drop out thought out picture, loss of tracking at tc 123, audio in left channel only. etc.

_ORIGINAL_FPS : For motion picture film, the frames per second at which the film was meant to be projected. most common - 16, 18, 24 ; ex. 24

COLLECTION and CATALOG_NUMBER are official tags according to this: https://www.matroska.org/technical/tagging.html

ATTACHMENTS may be unnecessary. I don't know about the first two.

@chialinchou1 @EmCNabs @crisanz6 @eddycolloton

[cjee21]

I don't know about the first two

Attachments are files embedded in MKV as attachments.

ErrorDetectionType is the presence of CRC32 in MKV elements. Per level 1 means present for level 1 elements only.

Both are MediaInfo fields, not MKV tags.

[JeromeMartinez]

The tags not in "extra" part are "standard" in MediaInfo, documented and in the MediaInfo XSD.
The tags in "extra" part are either:

• a field we quickly implemented in MediaInfo for a specific user / usecase, without the goal to unify the field across different formats.
• a "pass-through" between the format tag system and MediaInfo output.

for instance, e.g. "_PRE_TRANSFER_NOTES" is not known by MediaInfo (nothing in MediaInfo for handling such piece of metadata) so it is directly sent to the output without any change. As we know nothing about such field, no documentation and not listed in MediaInfo XSD.

ATTACHMENTS seems a duplicate of attachment names but not made by MediaInfo (readout of MKV elements).

COLLECTION and CATALOG_NUMBER should be better handled by MediaInfo.

[BleakleyMcD]

The tags not in "extra" part are "standard" in MediaInfo, documented and in the MediaInfo XSD. The tags in "extra" part are either:

• a field we quickly implemented in MediaInfo for a specific user / usecase, without the goal to unify the field across different formats.
• a "pass-through" between the format tag system and MediaInfo output.

for instance, e.g. "_PRE_TRANSFER_NOTES" is not known by MediaInfo (nothing in MediaInfo for handling such piece of metadata) so it is directly sent to the output without any change. As we know nothing about such field, no documentation and not listed in MediaInfo XSD.

OK. Is there a process to formally propose adding to the MediaInfo XSD?

ATTACHMENTS seems a duplicate of attachment names but not made by MediaInfo (readout of MKV elements).

Yes, that is exactly what it is. Sorry for not explaining that better.

COLLECTION and CATALOG_NUMBER should be better handled by MediaInfo.

OK.

[JeromeMartinez]

Is there a process to formally propose adding to the MediaInfo XSD?

Absolutely nothing up to now, it is more when we consider that this is useful for lot of people, that a field can be more or less well defined and that this field is found in several formats.

For instance:

• _TAGGED_BY: we already have Tagged_Application and Tagged_Date, so Tagged_By would make sense.
• _PRE_TRANSFER_NOTES & _TRANSFER_NOTES: We currently have nothing like that, maybe the Comment field but it is generic. I am afraid that it is very specific to a domain (digitization) but well, we have already specific fields (BPM, BarCode...) so why not...
• _ORIGINAL_FPS: I am more reluctant about this one, why not having the FrameRate this frame rate rather than another frame rate?

[BleakleyMcD]

• _ORIGINAL_FPS: I am more reluctant about this one, why not having the FrameRate this frame rate rather than another frame rate?

https://www.matroska.org/technical/tagging.html has an FPS tag:

FPS | UTF-8 | The average frames per second of the specified item. This is typically the average number of Blocks per second. In the event that lacing is used, each laced chunk is to be counted as a separate frame.

_ORIGINAL_FPS refers specifically to the original projection frame rate of a motion picture film that has been scanned. This information is often lost -- particularly in the case of amateur films -- or inaccurately represented in digital video files. The tag can also be used to indicate that the original film included segments shot at different frame rates (e.g., portions at 18 fps and others at 24 fps) which is something also common in amateur films and home movies.