DVD content crashes VSX2 and DVDMF6

zforray · Post by **zforray** » Mon Mar 02, 2009 12:45 am

First off, I am fully patched on ALL Ulead/Corel products as well as Windows XP SP3.

Here is the story. This DVD created by a standalone JVC recorder (not by some special program on a computer or Mac - it is video camera input to a JVC DVD burner) causes some kind of issue/problem with both VSX2 and DVDMF6.

I imported the DVD contents into VSX2 (a little over 2-hours) so I could create a menued DVD. Imports just fine. No errors. Go to "create a disc"..... create 10-minute chapter points......chose the menu, go to the last screen to generate a Disc - BAM - crash and burn with the "do you want to send this crash to M$" error. I went back and tried 2-more time, to try to create just an ISO or the DVD folders - same crash. BTW, the mpg2 plays just fine, all the way down to the end. So does the DVD.

So, I think maybe something about VSX2 doesn't like something in the mpg and go to DVDMF6 (whatever happened to MF7 in the states??). Same scenario except for the error message. At the last screen, it just starts and immediately generates an "unknown error" type message (at least it doesn't completely collapse like VSX2).

To make matters even more interesting, since both of my Ulead/Corel products are failing me, I decided to fire-up Nero-8 Vision and it took the mpg imported by VSX2 and created a DVD just fine.

So what is it that gives both Ulead/Corel products such heartburn???

Post by **Ken Berry** » Mon Mar 02, 2009 1:00 am

It has become almost a mantra with me over the past couple of months to suggest people first go to the Microsoft DirectX website and download the latest update patch. The current one is dated November 2008 and can be found at http://tinyurl.com/6jj2lw

Note that it updates both DirectX 9.0c (XP) and 10 (Vista). The number of your DirectX installation will not change, but the patch gives extra functionality in a number of areas and corrects other faults in VS11 in particular -- and now also in X2 -- which appear linked to Windows updates. The menu preview , 'building preview
graph' and other problems in the burning module seem to be amongst them.

Note that DirectX is not included in the usual pattern of Windows automatic updates. It has to be done every so often by the user manually. So unless you have recently done this, you are probably still using the original, non-updated version of DirectX which came with your computer, even if you think that otherwise your computer is fully patched...

zforray · Post by **zforray** » Tue Mar 03, 2009 9:59 pm

Thanks for the suggestiong but I am already there. I build/repair/upgrade computers for a living and know about getting the latest and greatest updates/patches. I checked DXDIAG first and it showed me at 9.0c

However, I went ahead and downloaded the library you pointed to and ran the DXSETUP program. Didn't change anything. The module dates are still the same and VSX2 still crashes.

Ken Berry wrote:It has become almost a mantra with me over the past couple of months to suggest people first go to the Microsoft DirectX website and download the latest update patch. The current one is dated November 2008 and can be found at http://tinyurl.com/6jj2lw

Note that it updates both DirectX 9.0c (XP) and 10 (Vista). The number of your DirectX installation will not change, but the patch gives extra functionality in a number of areas and corrects other faults in VS11 in particular -- and now also in X2 -- which appear linked to Windows updates. The menu preview , 'building preview
graph' and other problems in the burning module seem to be amongst them.

Note that DirectX is not included in the usual pattern of Windows automatic updates. It has to be done every so often by the user manually. So unless you have recently done this, you are probably still using the original, non-updated version of DirectX which came with your computer, even if you think that otherwise your computer is fully patched...

zforray · Post by **zforray** » Wed Mar 04, 2009 7:18 pm

Well, I think I have solved the problem, at least for VSX2, although DVDMF6 still crashes.

I recall having similar problems with another video in DVDMF6 that was created using an AC-3 audio codec and installing the free AC-3 codec resolved the problem. So I thought maybe I am missing some audio codec it needs.

I checked this video/mpg and it said the audio codec was "Dolby Digital Audio".

So, I Googled "Dolby Digital codec" and came up with the AC-3 codec site. I installed it and now VSX2 doesn't crash and is actually rendering the DVD (so far - only 10% done). DVDMF6 still fails with the ever useful "unspecified error" shortly after I click the burn button to create an ISO or DVD folders. At least DVDMF6 doesn't crash-and-burn and I can save the project.

I would have figured that VSX2 with all the latest and greatest features could handle this. I would have hoped for better error recovery/management.....maybe something like "I am sorry, Dave....I can't do that.....you are missing a codec.....".

Ken Berry wrote:It has become almost a mantra with me over the past couple of months to suggest people first go to the Microsoft DirectX website and download the latest update patch. The current one is dated November 2008 and can be found at http://tinyurl.com/6jj2lw

Note that it updates both DirectX 9.0c (XP) and 10 (Vista). The number of your DirectX installation will not change, but the patch gives extra functionality in a number of areas and corrects other faults in VS11 in particular -- and now also in X2 -- which appear linked to Windows updates. The menu preview , 'building preview
graph' and other problems in the burning module seem to be amongst them.

Note that DirectX is not included in the usual pattern of Windows automatic updates. It has to be done every so often by the user manually. So unless you have recently done this, you are probably still using the original, non-updated version of DirectX which came with your computer, even if you think that otherwise your computer is fully patched...

Post by **Ken Berry** » Wed Mar 04, 2009 10:21 pm

The problem is, though, that X2 (and 11/11.5+), as well as MF6, if you have the full, registered versions, come with Dolby codecs which are installed. Trial versions and SE versions do not. So the program should have been able to both read incoming Dolby, and output to Dolby as well, like the rest of us...