Vargol / spatial-media

Specifications and tools for 360º video and spatial audio. Modified for Google's VR180
53 stars 11 forks source link

UDTA Content #6

Closed AlanKoschel closed 3 years ago

AlanKoschel commented 4 years ago

Is it possible to read out the udta box with all its content by using the source code? I want to access geo data and calibration data which is placed in the udta box.

Vargol commented 4 years ago

Yes and no :-) Yes it will read the mp4 down to the udta box and the boxes in the udta box as it knows that the udta is a container, but it will not interpret those boxes and does not know if any of those boxes are containers.

So you'll get down to this level with the source as is, the numbers are header size and content size..

└── udta [8, 438193]
     ├── modl [8, 6]
     ├── slno [8, 13]
     ├── fwvr [8, 9]
     ├── clor [8, 3]
     ├── rcid [8, 17]
     ├── scfg [8, 3]
     ├── pmod [8, 3]
     ├── zrdr [8, 1]
     ├── geol [8, 1]
     ├── rcrp [8, 15]
     ├── lcrp [8, 15]
     ├── cali [8, 2173]
     └── bmdt [8, 435830]
AlanKoschel commented 4 years ago

Thank you! By the way is it possible to access the content of the camm atom?

Vargol commented 4 years ago

Pretty much the same answer, according to the google api docs camm is part of the stsd container. I haven't got an example with a camm atom (box) but it knows stsd is a container and will read the boxes within. It doesn't know what to do with the data though :-)

 ├── moov [8, 47764]
 │   ├── mvhd [8, 100]
 │   ├── trak [8, 47550]
 │   │   ├── tkhd [8, 84]
 │   │   ├── edts [8, 28]
 │   │   └── mdia [8, 47414]
 │   │       ├── mdhd [8, 24]
 │   │       ├── hdlr [8, 37]
 │   │       └── minf [8, 47329]
 │   │           ├── vmhd [8, 12]
 │   │           ├── dinf [8, 28]
 │   │           └── stbl [8, 47265]
 │   │               ├── stsd [8, 241]
 │   │               │   └── avc1 [8, 225]
 │   │               │       ├── avcC [8, 45]
Vargol commented 3 years ago

Provided the information requested