Yellow triangle of death on 596-599, 595 OK

bpratt

Member
Yesterday I took several video shots using my Canon HF200 HD camcorder. It creates several .MTS files that I use the Joiner to combine into one. The last time I did this, I was on VideoReDo version 595 and everything worked well. This time on version 598, the Join crashed.

I noticed that this was a known problem, so I downloaded and installed 599. 599 Joined the files and created a single .ts file. When I edited the file and tried to save it using 599, I got the yellow triangle of death.

I then installed 596. 596 was able to join the files, create and save a single .ts file, but it crashed with the yellow triangle of death when I tried to edit and save the .ts file it had created.

Finally, I installed 595 (the version I know worked before). 595 was able to join the files, create and save a single .ts file and then save the edited version of the .ts file.

So I guess I'll stay on 595 until this problem is fixed.
 

MrVideo

Active member
I just tried editing pieces of previous edited programs and got the YToD as well, with 596.

The error is: Multiple samples not in range at Original PTS:

After 38 of these errors, the YtoD showed up. There were a total of 88 of these errors before I aborted the job. I was hoping the YToD would go away.

Off to try 595.
 

MrVideo

Active member
Could not run 595, as it complained about NavSliderBar being the wrong version.

Running 589 instead, as the files are MPEG-2. As of this writing, it has gotten well past the part where 596 died.
 

MrVideo

Active member
What should have take me about 1/2 hr to complete, has taken ~3 hrs. 589 kept wanting to throw away 3 frames from one file and 2 frames from the other, both at approximately the same location in the video. At these two files were captured, and edited, months apart.

In desperation, I took the offending section of video and ran it through 596. It didn't error on the segment. I then took that segment and used it instead of the orginal files and 589 finally gave a result without errors. Because each job took about 13 minutes, I had to wait a long time to find out if it was going to work or not.

Needless to say, 596 does have issues with previously created video, wanting to throw away video frames for no apparent reason.

When VRD 596 creates video that it doesn't like, you know there is something wrong.
 

bpratt

Member
This problem still exists on version 600. It fails the same as it does in 599. This is the last part of the log file:

2010-04-13 10:18:59 H.264, Starting stream open for: E:\00125a.ts
2010-04-13 10:18:59 H.264, Opening file: E:\00125a.ts, filetype is: H264 PIDs: x1011 / x1100
2010-04-13 10:18:59 Graph monitoring thread started.
2010-04-13 10:18:59 Adding module to graph: H264 decoder
2010-04-13 10:18:59 Setting graph input port: 0 to module: H264 decoder port: 0 Accepts EOF
2010-04-13 10:18:59 H264 decoder: Starting video, H264 decoder thread.
2010-04-13 10:18:59 Graph monitoring thread started.
2010-04-13 10:18:59 Adding module to graph: H264 decoder
2010-04-13 10:18:59 Setting graph input port: 0 to module: H264 decoder port: 0 Accepts EOF
2010-04-13 10:18:59 H264 decoder: Starting video, H264 decoder thread.
2010-04-13 10:18:59 H.264, Starting stream open for: E:\00125a.ts
2010-04-13 10:18:59 H.264, Opening file: E:\00125a.ts, filetype is: H264 PIDs: x1011 / x1100
2010-04-13 10:18:59 H264 video, using display driver: VMR9
2010-04-13 10:18:59 VMR9 (Windowed), MEDIASUBTYPE_RGB24
2010-04-13 10:18:59 VMR9 (Windowed), MEDIASUBTYPE_RGB24
2010-04-13 10:19:01 H.264, Starting stream open for: E:\00125a.ts
2010-04-13 10:19:01 H.264, Opening file: E:\00125a.ts, filetype is: H264 PIDs: x1011 / x1100
2010-04-13 10:23:40 H.264, Starting stream open for: E:\00125a.ts
2010-04-13 10:23:40 H.264, Opening file: E:\00125a.ts, filetype is: H264 PIDs: x1011 / x1100
2010-04-13 10:23:40 H.264, TS->Mux rate set to ATSC (19.2 Mbps)
2010-04-13 10:23:40 TS, Unknown PI type in BuildProgramMapFromProgramInfo: 2
2010-04-13 10:23:40 Graph monitoring thread started.
2010-04-13 10:23:40 Graph, monitoring thread received terminate signal.
2010-04-13 10:23:40 Graph monitoring thread finished.
2010-04-13 10:23:40 Graph monitoring thread started.
2010-04-13 10:23:40 Adding module to graph: H264 smart editor
2010-04-13 10:23:40 Setting graph input port: 0 to module: H264 smart editor port: 0 Accepts EOF
2010-04-13 10:23:40 Setting graph input port: 3 to module: H264 smart editor port: 2
2010-04-13 10:23:40 Adding module to graph: H264 decoder
2010-04-13 10:23:40 Adding module to graph: H264 encoder
2010-04-13 10:23:40 Connecting output of H264 smart editor (2) to input of H264 decoder (0)
2010-04-13 10:23:40 Connecting output of H264 decoder (0) to input of H264 smart editor (2)
2010-04-13 10:23:40 Connecting output of H264 encoder (0) to input of H264 smart editor (3)
2010-04-13 10:23:40 Connecting output of H264 smart editor (3) to input of H264 encoder (0)
2010-04-13 10:23:40 Adding module to graph: Audio recoder
2010-04-13 10:23:40 Setting graph input port: 1 to module: Audio recoder port: 0 Accepts EOF
2010-04-13 10:23:40 Adding module to graph: Output muxer
2010-04-13 10:23:40 Connecting output of H264 smart editor (0) to input of Output muxer (0)
2010-04-13 10:23:40 Connecting output of Audio recoder (0) to input of Output muxer (1)
2010-04-13 10:23:40 Graph, passes required: 1
2010-04-13 10:23:40 Graph, Output encoding bitrate: 16.0000 Mbps
2010-04-13 10:23:40 Graph, Encoding dimension: 1920 x 1080
2010-04-13 10:23:40 Graph, Cropping rect: (0 x 0 ) - (1920 x 1080)
2010-04-13 10:23:40 Graph, Maximum GOP: 0
2010-04-13 10:23:40 H264 smart editor: Starting H.264 smart editing thread.
2010-04-13 10:23:40 H264 decoder: Starting video, H264 decoder thread.
2010-04-13 10:23:40 H264 encoder: Starting video, H264 encoder thread.
2010-04-13 10:23:40 StreamProcess: Stream: 0, Starting audio coding thread.
2010-04-13 10:23:40 StreamProcess: Staring output muxer thread.
2010-04-13 10:23:40 Program Information
File Name: E:\00125a.ts
File Size: 2025947220 ( 1.89 GB )
Program Duration: 00:17:09.16
File Type: TS Stream
Encoding: H.264
Video stream Id: 4113 (x1011)
Encoding Dimensions: 1920 x 1080
Display Size: 1920 x 1080
Aspect Ratio: 16:9
Frame Rate: 29.97 FPS
Bit Rate: 16.000 Mbps
VBV_Buffer: 976 KB
Profile: High/4.0
Progressive: Interlaced
Chroma: 4:2:0
Audio Format: 2.0
Audio Stream Id: AC3: 4352 (x1100)
Audio Bit Rate: 256 Kbps
Audio Sampling Rate: 48000 Hz
TS Mux Rate (bps): -1
Est. video bit rate: 14.875 (Mbps)

2010-04-13 10:23:40 H.264, Starting new Frame Accurate Output Segment: start:0.000 (00:00:00.00), end:496466.011 (00:08:16.15), Mux delta: 0.00
2010-04-13 10:23:40 Preparing to send status to: 0 Audio volume changed
2010-04-13 10:23:40 Sending status: 'Audio volume changed' to module: 'H264 smart editor - 0', Type: Video frame
2010-04-13 10:23:40 Preparing to send status to: 0 Audio volume changed
2010-04-13 10:23:40 Sending status: 'Audio volume changed' to module: 'Audio recoder - 0', Type: Audio frame
2010-04-13 10:23:40 Adding new graph range, Start: 0 (00:00:00.00), End: 496466.01 (00:08:16.15)
2010-04-13 10:24:00 Active module list:
class CStreamProcessH264SmartEdit
class CVStreamBuffer<class CVideoFrameH264>, Fill: 0/5, Free: 6 Txn count: 437
class CVStreamBuffer<class CYUVFrame>, Fill: 0/5, Free: 6 Txn count: 0
class CVStreamBuffer<class CVideoFrameH264>, Fill: 0/5, Free: 6 Txn count: 0
class CStreamProcessH264Decoder
class CVStreamBuffer<class CVideoFrame>, Fill: 0/5, Free: 6 Txn count: 0
class CStreamProcessH264Encoder
class CVStreamBuffer<class CYUVFrame>, Fill: 0/4, Free: 5 Txn count: 0
class CStreamProcessAudioCoder
class CVStreamBuffer<class CAudioFrame>, Fill: 2048/2049, Free: 0 Txn count: 2586
class CStreamProcessMuxer
class CVStreamBuffer<class CVideoFrame>, Fill: 0/50, Free: 51 Txn count: 421
class CVStreamBuffer<class CAudioFrame>, Fill: 101/101, Free: 0 Txn count: 536
class CVStreamBuffer<class CSubtitleFrame>, Fill: 0/50, Free: 51 Txn count: 0
2010-04-13 10:24:42 Triangle displayed: 0, Ticks: 1197947, NoactiveCount: 57, Pos: 1.355396, previous pos: 1.355396
2010-04-13 10:24:42 Triangle displayed: 1, Ticks: 1198961, NoactiveCount: 58, Pos: 1.355396, previous pos: 1.355396
2010-04-13 10:24:42 Triangle displayed: 2, Ticks: 1199975, NoactiveCount: 59, Pos: 1.355396, previous pos: 1.355396
2010-04-13 10:25:29 **** Thread terminate ***** Thumbnail Video
2010-04-13 10:25:29 **** Thread terminate ***** Video
2010-04-13 10:25:29 Graph, monitoring thread received terminate signal.
2010-04-13 10:25:29 Graph monitoring thread finished.
2010-04-13 10:25:29 Graph, monitoring thread received terminate signal.
2010-04-13 10:25:29 Graph monitoring thread finished.
2010-04-13 10:28:18 Image support lib: 6.1 build 137.36, ippvcp8l.lib+
2010-04-13 10:28:18 Decoder support lib: 6.1 build 137.36, ippvcp8l.lib+
2010-04-13 10:28:19 VideoReDo TVSuite started. Licensed to: --, Version: 4.20.5.600 - Apr 11 2010, AVP On (00cf0046-89}
2010-04-13 10:28:19 Checking reg: 120
 
Last edited by a moderator:

Danr

Administrator
Staff member
bpratt, it looks like the problem is happening right at the beginning of your file. Can you use Tools>Trim to create a short (100-200 MB ) clip that duplicates the problem and then upload it our FTP?
 

trE

New member
I got this too. I recorded a show in two parts, then tried to join them. I ran QSF on the parts separately and then it was able to join them
 

bpratt

Member
bpratt, it looks like the problem is happening right at the beginning of your file. Can you use Tools>Trim to create a short (100-200 MB ) clip that duplicates the problem and then upload it our FTP?
I FTPed a 200 MB piece of the file and sent the email. What you refer to as "your file" was created by using VideoReDo to join 5 .MTS files that were created by a Cannon HF200 HD camcorder. The 00125a.ts file was created by VideoReDo.
The file I sent is called trim.ts and is the first 200 MB of 00125a.ts. It also fails with the Yellow triangle of death when Save As is performed.
 

bpratt

Member
Dan, what is the status of this problem? I am still able to join and edit these files on build 595 but I get the Yellow Triangle of Death on any newer builds. Will 601 be out soon and will it address this problem?
 
Top Bottom