TS-Doctor 2.0 www.cypheros.de

Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - jaydear

Seiten: [1] 2 3 ... 8
1
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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.

2
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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  ::)

3
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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.

4
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« am: Mai 13, 2019, 08:26:26 »
Hmmmm... the plot thickens  ::)

5
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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)

6
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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>.

7
TS-Doctor 2.x / Re: Viewing problem areas in new saved files
« 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

8
TS-Doctor 2.x / Viewing problem areas in new saved files
« 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?

9
TS-Doctor 2.x / Re: EPG not showing all programs
« am: Januar 15, 2019, 21:52:21 »
Still having this problem, which is now crashing TSD.

10
TS-Doctor 2.x / Re: EPG not showing all programs
« am: November 20, 2018, 21:53:22 »
I've just had another recording only showing the first part of the epg in the timelines. As before, the recording is actually complete, the full epg is present in the log, and it is fully editable in other s/w. Of course, without the full timeline I can't edit all of it in TSD. I'll send you a log, but I'm getting a "Bad request error" here.

11
TS-Doctor 2.1 (Beta) / Re: Huge log files
« am: November 20, 2018, 19:53:04 »
I'm getting a "bad request" error  ::)

12
TS-Doctor 2.1 (Beta) / Huge log files
« am: November 20, 2018, 00:15:00 »
Sometimes saving a new file takes longer than usual. I opened the log file from a slow save today because I noticed it was about 2.5MB instead of about 15KB. After a couple of hundred lines of details I found about 60,000 lines of "Cutting area problem" and then the last line was "Log too long, aborted."

This was just one file of three prog's from the same multipart recording being saved as separate files, the other two had normal size log files. There were no PCR problems reported in the initial scan. The file that produced the big log seems fine, so what do you think was the cutting area problem? There was plenty of space between edits.

13
TS-Doctor 2.1 (Beta) / Re: Opening one part of multi-part recordings
« am: November 07, 2018, 23:32:05 »
Ah, right. Yes, I agree.

When my workflow repetitive procedure editing technique is broken by a glitchy recording (thankfully, a fairly rare occurrence) I have usually been lucky enough that the problem is in an unwanted segment and I have been able to avoid opening the one/s containing the glitch. The epg is useful in this, but it would be very helpful if the start of each segment could be indicated on the timeline by a discreet little line or dot.

Anyhow, it's all good, just wanted a little variety. Making little changes makes me more efficient with the Doctor.

14
TS-Doctor 2.1 (Beta) / Opening one part of multi-part recordings
« am: November 07, 2018, 21:23:28 »
I've set "Dialog Settings / Multi part recording. Open complete recording?" to "Show Dialog", but v2.1.45 is still opening the whole recording without asking. Is this a bug or is there another setting somewhere? :-[

15
Thanks very much for the registry settings. They work well, but look nothing like I remember them ::)

If the interlacing problem is difficult, don't worry about it because I've found I can do the screen grabs quite well in PotPlayer.

Seiten: [1] 2 3 ... 8

www.cypheros.de