3 TS files are plain recordings, including PMT and PAT.
5 They don't have a private header.
9 .meta files have currently 4 lines:
16 The service reference contains the Service-ID of the recorded service. With
17 that ID, you can find the PMT and the elementary streams.
19 As a backup method, just find the first available PMT and use that.
21 Strings are always UTF-8 encoded.
25 Stored offsets and PTS values. They are collected while recording. Only
26 GOP starts are stored.
28 File format is network-ordered (i.e. big endian), each entry contains
29 two 64 bit values (PTS, offset).
31 PTS values are not corrected (i.e. they aren't zero-based), offsets are
32 relative to the beginning of the file (or first file, when we implement
37 Also network ordered, they contain a 64bit value (PTS) and 32bit value
38 (type) for each cut. (If you want file offsets, use the .ap file to look up
47 If the first 'out'-point is not preceeded by an 'in'-point, there is an
48 implicit 'in' point at zero.
50 If the there is no final 'out' point, the end-of-file is an implicit
53 Note that the PTS values are zero-based and continouus. If you want absolute
54 PTS values, you can either:
55 - use the .ap file, find discontinuities, and interpolate between the APs
56 - or just use the first PTS value as an offset, and work around PTS
57 wraparounds. (simple method)