Quote:
Originally Posted by deank
I don't know if this is of any help, but since the early days when tsMuxeR needed fixclpi, multiAVCHD always checks each CLPI against the M2TS, sets proper packet count and verifies if in/out times match in all MPLS files, which refer to this m2ts, then puts the correct in/out values.
|
I think I do that too (check packet count). If I remember right some of the earlier TSMUXER versions used to set the packet count incorrectly. They also screwed up the EP tables, but I thought that was fixed. I'll go back and check that I haven't changed that.
I don't think I remember an issue with the MPLS in/out times... was that something that often happens? I'll also go back and see if I make any adjustments there. [Edit] Actually I have to rewrite all the IN/OUT times because of the timing changes TSMUXER makes and the fact that I use the original MPLS files.