Cypheros Transportstream Forum

Eng English-speaking Support => TS-Doctor 2.x => Thema gestartet von: jaydear am Mai 10, 2019, 05:20:43

Titel: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 10, 2019, 05:20:43
Sometimes I'll get an error or a warning or both  :o in a saved file. If I look in the log I can eventually find a list of the timecode/s. Sometimes I exit the log and I get a little window that lets me play the areas so I can see how bad the problem is. This is GREAT, but I have no idea how that was triggered or how to manually open it. There is a problem (I think) ... I can play one problem area once and that's it, the window closes, never to be seen again.

Is there some way to 1. Get another look, and 2. View other problem areas that may have been listed? 3. How did I trigger it in the first place?
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Cypheros am Mai 10, 2019, 14:42:32
You should get a list with stream error areas and if you double click on one of them or you click "play", a preview will show up.
If you close the preview window, the list with the stream error areas should stay and you can select another area.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Mam am Mai 10, 2019, 16:28:25
We should note that the list is "WHAT THE DOC THINKS THE ERRORS MIGHT BE".
Actually, its really optimistic to think you might watch really the error region.
Most of the time, everything looks good, later on it turns out that the error was some 5mins away...

 >:(
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 10, 2019, 22:20:34
I don't see the Stream Errors List very often. Obviously, I don't expect to see it if no errors have been reported, but I hardly ever see it when there are errors. Is there a way to view it when it fails to open automatically? I am optimistic  ;D
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 11, 2019, 05:42:37
I just saved an edit and had an unusually high 4 errors plus 9 warnings. I looked at the log and when I OK'd out of that and the "errors / warnings" window I had no "stream error list" <sigh>.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Mam am Mai 11, 2019, 07:23:01
I just saved an edit and had an unusually high 4 errors plus 9 warnings. I looked at the log and when I OK'd out of that and the "errors / warnings" window I had no "stream error list" <sigh>.
it usually has a list, but it is filtered.
If the errors are so small, the doc assumes that they are invisible/unhearable. Therefor it does not write them to the log at all.
If there are many errors (dont ask me for the threshold), they still are listed there.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 11, 2019, 08:22:24
This is from that log. It doesn't mean a lot to me, but from what you're saying it would not be problematic...

Creating new file F:\2019Wk19\Pgm1,Pgm2,Pgm3.ts [1]
TS  WARNING: For PID 0203 00:00:00.000 TS packet 01D06BE2: Packet discontinuity  last=14 , current=4
TS  WARNING: For PID 0203 00:00:00.000 TS packet 01DCF99E: Packet discontinuity  last=13 , current=13
TS  WARNING: For PID 028D 00:00:00.000 TS packet 01DCF99F: Packet discontinuity  last=4 , current=9
PES ERROR  : For PID 028D 00:00:00.051 PES packet 00055F89 is invalid (SizeMismatch), starting with TS packet 01DCF996 Size: 362 should be 730
TS  WARNING: For PID 0243 00:00:00.000 TS packet 01DCF9BC: Packet discontinuity  last=15 , current=11
TS  WARNING: For PID 0203 00:00:00.000 TS packet 01DD3D65: Packet discontinuity  last=13 , current=7
TS  WARNING: For PID 028D 00:00:00.000 TS packet 01DD3D74: Packet discontinuity  last=2 , current=14
PES ERROR  : For PID 028D -00:00:00.211 PES packet 0005606D is invalid (SizeMismatch), starting with TS packet 01DD3D5D Size: 730 should be 914
TS  WARNING: For PID 0203 00:00:00.000 TS packet 01F13850: Packet discontinuity  last=5 , current=8
TS  WARNING: For PID 0243 00:00:00.000 TS packet 01F13853: Packet discontinuity  last=14 , current=10
TS  WARNING: For PID 028D 00:00:00.000 TS packet 01F13857: Packet discontinuity  last=2 , current=9
PES ERROR  : For PID 028D 00:00:00.069 PES packet 00059CD1 is invalid (SizeMismatch), starting with TS packet 01F13846 Size: 178 should be 730
Cutting the end at packet 0219467E PCR: 02:40:55.222 (25:18:57.284)
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Mam am Mai 11, 2019, 09:09:40
its not me to say this  ;D
the doc thinks, its not important. If there are very few packets missing within a certain time period, its not very likely that they will produce visible disortions (but of course, they also may have hit critical portions).
The error could be in an unused audio stream or teletext or whatever.
The doc only gets alarmed if there are many packets in a row missing/in error.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Cypheros am Mai 12, 2019, 01:59:58
Strange thing is, that PCR/PTS is in most cases 00:00:00.000 . That is special and not looks like a coincidence.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 13, 2019, 08:26:26
Hmmmm... the plot thickens  ::)
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Cypheros am Mai 14, 2019, 00:37:09
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"?
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 14, 2019, 04:25:04
I agree that there are tricks being played. I only ignore the PCR message if I'm not expecting that anything worthwhile was recorded. I'll check back.
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 15, 2019, 10:41:12
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  ::)
Titel: Re: Viewing problem areas in new saved files
Beitrag von: Mam am Mai 15, 2019, 20:09:57
I dont see any problems with your logfile ?!?!?!?

Ok, there are a few and very small errors (lost pockets) at the beginning, but from your writing I assume, they are outside the needed region, so they are cutted away anyway.

A "PCR wrap" is not an error at all, it happens every 23hrs on every channel. It just means that the 33bit timer that holds the runtime wrapped around. This does not generate any visible or hearable problem, it just makes the reading of the logfile a bit harder. Like a clock passing midnight, you have part of the film with time a (lets say 22:45 to 23:59) and the rest with time b (lets say 00:00 to 00:55). For your convinience the doc tries to rebuild this wrap by always starting the film counter with 00:00:00 and counting upwards, so that the broadcast time looks like the playtime. This does not work for recordings longer than 23hrs!
(it cannot compensate two wraps of course!)
Titel: Re: Viewing problem areas in new saved files
Beitrag von: jaydear am Mai 15, 2019, 21:43:01
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.