Cypheros Transportstream Forum

Download:
Version 34.0.0 (32-bit)
Version 34.0.0 (64-bit)

Bug fixes

• mkvmerge: all subtitle frames are now treated as key frames in order to fix wrong data in source files. Fixes #2541.
• mkvmerge: AV1: fixed frame timestamp calculation when reading bitstreams that lack timing information from IVF files. Fixes #2553.
• mkvmerge: Matroska reader: fixed an infinite loop that could happen with large video frames and applied timestamp files due to too much data being buffered at the wrong time. Fixes #2550.

Hallo,
ich habe gerade auf die neueste Version aktualisiert. Jetzt stelle ich fest, daß nach dem Schnitt auch die herausgeschnittenen Dateien gespeichert werden. Die guten (grün) sind dabei nicht komplett. Es fehlt der Anfang, der jetzt mit an der zu löschenden Datei hängt.
Was ist da schief gelaufen? Habe keine Änderungen gegenüber vorher in den Einstellungen vorgenommen.

In this particular example The Doctor reported a bunch of warnings and errors in the saved file. They are shown in a graph and listed in the log with exclamation marks! I have a reasonable understanding of what makes up a transport stream, but many people that use TSD may not. There is a facility in TSD to play the affected areas, but it only appears if it decides the errors are serious enough.

My point is: Why not make it possible to check all problem areas in the built-in player whether they are serious or not?

I'm not concerned about this specific recording, it was just used as an example. I would like to be able to view problem areas in new saved files because TSD sometimes reports errors yet does not provide a way to play them.

I've checked the recording and no errors are reported or repairs offered. There is however, a 'pulse' in the PCR Check box. So I did a Check Only scan and here is the relevant part of the log...

Cut  in at PCR: 00:00:00.000 (22:31:18.783)
Cut out at PCR: 08:09:57.593 (04:10:32.658)

File changed to 000.ts  / Read index: 00000000  / Write index: 00000000 at 00:00:00.000

Starting at packet 00000000 PTS: 00:00:01.883 (22:31:18.783)
No cutting at the end needed

File changed to 001.ts  / Read index: 015C9F00  / Write index: 00000000 at 01:42:09.555
Changing file read to file: "001.ts"
TS  WARNING: For PID 0203 02:22:50.444 TS packet 01D06BE2: Packet discontinuity  last=14 , current=4
TS  WARNING: For PID 0203 02:27:09.333 TS packet 01DCF99E: Packet discontinuity  last=13 , current=13
TS  WARNING: For PID 028D 02:27:09.333 TS packet 01DCF99F: Packet discontinuity  last=4 , current=9
PES ERROR  : For PID 028D 02:27:09.385 PES packet 00059D13 is invalid (SizeMismatch), starting with TS packet 01DCF996 Size: 362 should be 730
TS  WARNING: For PID 0243 02:27:09.333 TS packet 01DCF9BC: Packet discontinuity  last=15 , current=11
TS  WARNING: For PID 0203 02:27:15.000 TS packet 01DD3D65: Packet discontinuity  last=13 , current=7
TS  WARNING: For PID 028D 02:27:15.000 TS packet 01DD3D74: Packet discontinuity  last=2 , current=14
PES ERROR  : For PID 028D 02:27:15.049 PES packet 00059DF7 is invalid (SizeMismatch), starting with TS packet 01DD3D5D Size: 730 should be 914
TS  WARNING: For PID 0203 02:33:26.259 TS packet 01F13850: Packet discontinuity  last=5 , current=8
TS  WARNING: For PID 0243 02:33:26.259 TS packet 01F13853: Packet discontinuity  last=14 , current=10
TS  WARNING: For PID 028D 02:33:26.259 TS packet 01F13857: Packet discontinuity  last=2 , current=9
PES ERROR  : For PID 028D 02:33:26.329 PES packet 0005DA5B is invalid (SizeMismatch), starting with TS packet 01F13846 Size: 178 should be 730
TS  WARNING: For PID 0203 03:34:35.481 TS packet 02B48D4B: Packet discontinuity  last=11 , current=0

File changed to 002.ts  / Read index: 02B93D00  / Write index: 00000000 at 03:36:07.074
Changing file read to file: "002.ts"
PTS wrap > (33 bit) at packet 030EC50F on PID 0203 detected!
PTS wrap < (33 bit) at packet 030EC5E5 on PID 0203 detected!
PTS wrap > (33 bit) at packet 030EC62B on PID 0203 detected!
PTS wrap > (33 bit) at packet 030EE801 on PID 028D detected!
PCR wrap between packet 030EE7E5 and packet 030EE887 on PID 0906 detected, PCR: 03:59:26.815

File changed to 003.ts  / Read index: 0415D900  / Write index: 00000000 at -21:10:46.125
Changing file read to file: "003.ts"

File changed to 004.ts  / Read index: 05727400  / Write index: 00000000 at -19:31:02.051
Changing file read to file: "004.ts"
Ending at packet 0661B9FF PTS: 08:09:55.741 (04:10:30.807)

Again, no error preview window 

This happens on such a regular base, it looks like it's intensionaly. Some broadcasters resetting the PCR out of nowhere. This is not problem for linear viewing but for random access to such recordings. In most cases TS-Doctor should detect PCR jumps and recommend to fix them first.

Do you get a message about "Invalid PCR jumps"?