PDA

View Full Version : 554 & 555 hang while doing a "QuickStream Fix" ...


Taipan
03-09-2008, 07:18 AM
I have a dvr-ms file (SD DVB-T) that I have tried to edit and save as an mpg, but part way through the process, VRD hung (with 100% CPU) and I had to use Task Manager to kill VRD.

So then I tried to do a "QuickStream Fix", thinking that may remove, or clean up, any corruptions that might be causing VRD to hang. But even the QuickStream Fix causes VRD to hang.

About 2 minutes into the process, the disk access ceases and then after about 30 seconds, a large yello triangle appears with an exclamation mark in it. But no useful error message or other warning is displayed. I can click on "Abort" and return to VRD, but the CPU% is stuck at 100% (VideoReDo3.exe).

I have tried both 554 and 555, and the same result with both. 554 was a fresh install after I completely un-installed 555.

Here is the VideoRedo.log file:-

2008-03-09 17:04:29

***** Loading: D:\Videos\TV Recordings\SBS_Omagh - M_200803082140p356.dvr-ms


2008-03-09 17:04:29 Using display driver: DX-RGB
2008-03-09 17:04:29 Temporal frame drop, at: 00:00:02.19, originalPTS: 2600.01 (00:00:02.15), frame type: 3, temporal: 2 (-1)
2008-03-09 17:04:29 Temporal frame drop, at: 00:00:02.19, originalPTS: 2600.01 (00:00:02.15), frame type: 3, temporal: 2 (-1)
2008-03-09 17:04:51 Opening: D:\Videos\TV Recordings\SBS_Omagh - M_200803082140p356.dvr-ms in QuickStream Fix Mode.
2008-03-09 17:04:51 Opening file: D:\Videos\TV Recordings\SBS_Omagh - M_200803082140p356.dvr-ms, filetype is: MPEG2 PIDs: xE0 / xC0
2008-03-09 17:04:52 Opening: D:\Videos\TV Recordings\SBS_Omagh - M_200803082140p356.dvr-ms in QuickStream Fix Mode.
2008-03-09 17:04:52 Graph monitoring thread started.
2008-03-09 17:04:52 Graph, monitoring thread received terminate signal.
2008-03-09 17:04:52 Graph monitoring thread finished.
2008-03-09 17:04:52 Program Information
File Name: D:\Videos\TV Recordings\SBS_Omagh - M_200803082140p356.dvr-ms
File Size: 4778128502 ( 4.45 GB )
Program Duration: 00:00:00.00
File Type: DVR-MS
Encoding: MPEG 2
Video stream Id: xE0
Encoding Dimensions: 720 x 576
Display Size: 720 x 576
Aspect Ratio: 16/9
Frame Rate: 25.00 FPS
Bit Rate: 5.000 Mbps
VBV_Buffer: 224 KB
Profile: Main/Main
Progressive: Prog or Int
Chroma: 4:2:0
Audio Format: Layer 2
Audio Stream Id: xC0
Audio Bit Rate: 192 Kbps
Audio Sampling Rate: 48000 Hz

2008-03-09 17:04:52 Starting new Frame Accurate Output Segment: start:0.000 (00:00:00.00), end:450359962737.044 (5795:20:33.03)
2008-03-09 17:04:52 QuickStream fix flag is ON.
2008-03-09 17:04:53 Temporal frame drop, at: 00:00:02.18, originalPTS: 3323.54 (00:00:03.08), frame type: 3, temporal: 2 (-1)
2008-03-09 17:04:53 Resync: removed 2 video frames, at video 00:00:02.19, original (00:00:03.07), sync changed from -180.02 to -33.83
2008-03-09 17:05:56 DVR-MS Tampered Content: 1
2008-03-09 17:07:40 **** Thread terminate ***** Thumbnail Timer


This issue may be caused by the particular dvr-ms file that I am trying to edit, but I would still expect VRD to be able to gracefully recover ... :confused:

Taipan
03-28-2008, 04:10 AM
I have had this problem occur again with another file recorded from a DVB-T broadcast. I have confirmed that the file is corrupted at the point that VRD freezes, but I would expect that:-

1. the purpose of the "Quick stream Fix" is to fix, or remove, any such corruptions?

2. VRD should not just hang when it encounters a corrupted section of the dvr-ms file?

3. a useful error message be displayed, rather than the unhelpful "black exclamation mark in a yellow triangle"?
Is this a "known issue", or do you need some more information from me?

DanR
03-28-2008, 02:31 PM
Its possible that the file is copy protected at that point in the file, and is returning bad data to VideoReDo. The problem with copy protected files is that the data returned to us by the MSoft reader routines in copy protected areas is indeterminate.

If you can upload a sample that creates this error we can take a look at it and see if we can make the product more robust.

Taipan
03-29-2008, 05:27 AM
Its possible that the file is copy protected at that point in the file, and is returning bad data to VideoReDo. .

I am not sure how the file could be "copy protected", as the file is a recording of a DVB-T broadcast from a TV station that does not protect any of its broadcasts. I think that the corruption (which is about 11 minutes into the file, for just a few frames) was caused by interference to the RF transmission, or occurred when the file was written to the disk. 99% of the file is fine.


If you can upload a sample that creates this error we can take a look at it and see if we can make the product more robust.

Unfortunately, I don't think I can do that?

The corruption occurs about 11 minutes into the file, so if I use "Trim and Copy Source File", I end up with a segment that is not mpeg compliant - is that useful to you?

If I try to run "QuickStream Fix" on the file, it will commence the QuickStream Fix and continue correctly until it encounters the corrupted section, at which point it will hang for a couple of minutes and then finally display the message window (quickstream fix error.jpg) attached below. As you can see, this message window is not very informative.

VRD will hang completely at this point (with VideoReDo.exe at 99% CPU) and I have to use TaskManager to kill VideoReDo.exe.

If I then re-open the file in VRD, but try to scan through to the corrupted frame/s, then I will get the error message in the attachment "seeking error.jpg" - which instructs me to run "QuickStream Fix" .... :confused:

Please confirm if a "Trim and Copy Source File" of the corrupted segment (about 10MB), which will not be mpeg compliant, will be useful to you to make VRD more robust?

DanR
03-29-2008, 12:57 PM
Trim and copy isn't very useful with DVR-MS files since, unlike MPEG or TS files, they have all kinds of internal indicies and pointers.

If the problem is in the MSoft DVR-MS reader then while we might be able to trap the error, we probably can't gracefully recover. If the problem is in videoredo code, then we can certainly fix it.

How large is the entire source file?
Can you play the entire file in MCE and/or Windows media player?