.bdmv, .clpi, .mpls and .m2ts - Exact specs of AVCHD/BD structure and files

kaefert · 28th July 2018, 16:29

I have ton's of BMDV folders coming from a Panasonic video camera. I would like to parse the timestamp of each recorded clip from the clpi files. (I know the date of each recording, but not time.)

I'm trying to identify possible byte addresses of that possibly stored timestamp within the clpi files by comparing clpi files from the same day versus comparing clpi files from different days vs from different years. (I'm using "vbindiff" to make the differences visible)

Addresses that look more different the farther apart two clips are should be good candidates for timestamps.

I'm documenting my findings here, maybe they will be useful for others too:

0x17 & 0x1B: single bytes that always have different values, 0x1B seems to be equal to the value of 0x17 plus 4.
0x39 - 0x3B: 3 bytes always different, didn't find a pattern yet.
0xE2 - 0xEA: Most clips: ASCII "00001M2TS" where the number is counting (and is always the number in the filename+1), Those clips have a 0x01 at address 0xDD. Clips with a 0x00 at 0xDD don't have this ASCII string. Some of the clips without ASCII string have value 0x00F6 instead of 0x0106 @ 0xE & 0xF. Those files are missing 0x10 bytes between 0xC3 & 0xEF. So for those clips 0x10 must be subtracted for any address higher than 0xEF for the value to match the discription.
0x100 - 0x105: Clips on the same day mostly only vary on 0x101 & 0x103 - 0x105, clips from different days also vary in 0x100.
0x119 contains the 0x30 described by others above as coding for aspect ratio at address 0x109 (which is the address of this 0x30 for clpi files without the ASCII string mentioned 3 lines above.)
0x146 - 0x147, 0x151 - 0x153, 0x15B: more changes. I can't see any patterns here..

28th July 2018, 16:29	#12 \| Link
kaefert Registered User Join Date: Jul 2013 Posts: 60	I have ton's of BMDV folders coming from a Panasonic video camera. I would like to parse the timestamp of each recorded clip from the clpi files. (I know the date of each recording, but not time.) I'm trying to identify possible byte addresses of that possibly stored timestamp within the clpi files by comparing clpi files from the same day versus comparing clpi files from different days vs from different years. (I'm using "vbindiff" to make the differences visible) Addresses that look more different the farther apart two clips are should be good candidates for timestamps. I'm documenting my findings here, maybe they will be useful for others too: 0x17 & 0x1B: single bytes that always have different values, 0x1B seems to be equal to the value of 0x17 plus 4. 0x39 - 0x3B: 3 bytes always different, didn't find a pattern yet. 0xE2 - 0xEA: Most clips: ASCII "00001M2TS" where the number is counting (and is always the number in the filename+1), Those clips have a 0x01 at address 0xDD. Clips with a 0x00 at 0xDD don't have this ASCII string. Some of the clips without ASCII string have value 0x00F6 instead of 0x0106 @ 0xE & 0xF. Those files are missing 0x10 bytes between 0xC3 & 0xEF. So for those clips 0x10 must be subtracted for any address higher than 0xEF for the value to match the discription. 0x100 - 0x105: Clips on the same day mostly only vary on 0x101 & 0x103 - 0x105, clips from different days also vary in 0x100. 0x119 contains the 0x30 described by others above as coding for aspect ratio at address 0x109 (which is the address of this 0x30 for clpi files without the ASCII string mentioned 3 lines above.) 0x146 - 0x147, 0x151 - 0x153, 0x15B: more changes. I can't see any patterns here.. Last edited by kaefert; 28th July 2018 at 22:03.