VS X2 "catastrophic failure" error

Moderator: Ken Berry

Post Reply
HomerB
Posts: 2
Joined: Mon May 09, 2011 12:05 am
operating_system: Vista Home Premium
System_Drive: C
32bit or 64bit: 64 Bit
ram: 4 GB
Hard_Drive_Capacity: 500 Gig
Monitor/Display Make & Model: HP w2207

VS X2 "catastrophic failure" error

Post by HomerB »

Brand new to this board and hoping someone might help. I'm trying to render MTS clips into an AVI video

Project Properties -

NTSC drop frame (29.97 fps)
Microsoft AVI files
24 bits, 720 x 480, 16:9, 29.97 fps
Lower Field First
DV Video Encoder -- type 1
DV Audio -- NTSC, 48.000 kHz, 16 Bit, Stereo.

When the rendering completes, a "Catastrophic Failure" error code comes up. When I try to play the video in VLF, I get the following message

"AVI Index

This AVI file is broken. Seeking will not work correctly."

If I press "don't repair", the file plays, but the indexing bar does not run along the bottom of the player. Obviously something is wrong, but I can't seem to work it out.

The input files are as follows:

Video Type: H.264 video, upper field first
Attributes: 24 bit, 1920x1080, 16:9
Frame rate: 29.970
Data rate: variable, 16,800 kbps max

Audio type: Dolby digital
Attributes: 48000 hertz
Layer: none
Bit Rate: 256 kbps

I've tried uninstalling and reinstalling, with no luck. Anybody have any thoughts where I might look next? Thanks.
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Re: VS X2 "catastrophic failure" error

Post by Ken Berry »

Apart from being mystified as to why you would be going from high definition AVCHD to standard def DV, the only thing I can see wrong with those settings is that the original AVCHD is upper field first, whereas DV is always lower field first. And a basic rule of video editing is that you should always maintain the same field order as the original video throughout a project. But in this case you can't since DV is *always* lower field first and cannot be made into upper field first. But normally, mixing up the field orders would only case distortion artifacts in the rendered video, rather than caused the program to crash, and especially not with a catastrophic error message! :roll:

Perhaps if you could tell us why you are doing that particular conversion and perhaps someone might be able to come up with an alternative workflow...
Ken Berry
HomerB
Posts: 2
Joined: Mon May 09, 2011 12:05 am
operating_system: Vista Home Premium
System_Drive: C
32bit or 64bit: 64 Bit
ram: 4 GB
Hard_Drive_Capacity: 500 Gig
Monitor/Display Make & Model: HP w2207

Re: VS X2 "catastrophic failure" error

Post by HomerB »

Ken, the video is going onto a DVD that is for standard def TV. I'm working with some folks that produce the DVDs and this is the workflow that has been requested.

After sending up the smoke signal for help, I continued to search the forum for other "catastrophic failure" posts (I had done this earlier but found nothing with AVI Index issues). I did come across a post by Ron about "lost AVI codecs", and that branched into a problem that Ulrich Birch had with X4. His problem was described as not being able to import or edit AVI files that he had previously been able to view/edit.

He corrected the problem by downloading new K-Lite 32 bit and 64 bit codec packs, then using the K-Lite Codec Tweaking Tool to change the AVI setting from a third party codec to "Microsoft (recommended)". I followed his described procedure and viola, the problem was also corrected in my X2 software.

The fix also cleaned up the issues with the AVI files I had already rendered that gave the "AVI Index Error Message". So it looks like that was the problem.

Thanks to the board, Ulrich and you too for help. You can consider my issue resolved and close the thread as needed.

HomerB
Post Reply