Hi Mosu
I have some questions about mtxcfg file and JSON identify.
In an mtxcfg file exists more then one "type"-object. A "type"-object("type": 22 (for m2ts)) is used for a file and it is the same value like in JSON identify "container_type"
Code:
"container": {
"properties": {
"container_type": 22,
"is_providing_timestamps": true
},
"recognized": true,
"supported": true,
"type": "MPEG transport stream"
},
On the other hand, the "type"-object(MPEG transport stream) from this JSON identify sample is not used in mtxcfg, right?
In mtxcfg exists for each track also a "type"-object ("type": 0 for DTS-HD Master Audio) but in JSON identify the "type"-object is a string (video,audio etc).
Code:
{
"codec": "DTS-HD Master Audio",
"id": 1,
"properties": {
"audio_channels": 6,
"audio_sampling_frequency": 48000,
"language": "eng",
"number": 4352,
"program_number": 1,
"stream_id": 4352
},
"type": "audio"
},
Is this an issue?
How can I determine the right value for an mtxfcg track "type"-object with info from JSON identify?
Could you add this info?
I know, then are two "type"-objects present. Why exists so many same named objects with different usage?
Best regards hubble