video/audio sequence glitch in generated DVD

deklerkt · Post by **deklerkt** » Tue Jun 27, 2006 2:58 pm

It's an old thread so probably the problems were fixed in the meantime (sounds as if some s/w is interfering with each other), but to the question of reading the ISO files: I can do so by using the free Daemon virtual DVD drive (www.daemon-tools.cc) - when you mount the iso file it will become a virtual DVD drive and (depending on settings) automatically start playing the disc.
Burning on DVD of course can be done by many tools, such as Nero Burning ROM.

David Mears · Post by **David Mears** » Fri Jun 30, 2006 3:54 pm

deklerkt wrote:It's an old thread so probably the problems were fixed in the meantime

I'm afraid not yet.

but to the question of reading the ISO files: I can do so by using the free Daemon virtual DVD drive (www.daemon-tools.cc)

An update . . . I installed the Daemon tools SW mentioned and was able to successfully "play" the entire .iso file gen'ed by DVD-WS, so it appears the .iso file is good and whatever corruption is happening occurs between the .iso file and getting burned onto the DVD media. As my next experiment, I swapped out my DVD burner for my older 2.4X burner, burned the DVD again with that HW and it had the same problem as before. So it appears it's not a hardware (DVD burner) problem.

sjj1805 · Post by **sjj1805** » Fri Jun 30, 2006 6:33 pm

Everything is a process of elimination.
so according to your Daemon tools you were able to play the video without synch issues. You've swapped your DVD burner.

Only one thing left then.... burn the iso with another program and see what happens.

David Mears · Post by **David Mears** » Sun Jul 02, 2006 11:56 pm

sjj1805 wrote:Only one thing left then.... burn the iso with another program and see what happens.

I downloaded the Trial version of Nero-7 which would allow me to burn the ULead .iso file out to a DVD and that worked just fine. The test DVD+RW I made played without error on the PC, and then I burned a DVD+R copy which I could then play OK on my DVD player. So it definitely looks like a problem relating to the DVD-WS code trying to burn the .iso file to DVD.

I'm now a bit suspicious of the "burning engine patch" I was directed by ULead to install from http://www.ulead.com/tech/general/burning_patch.htm when I reinstalled DVD-WS 1.2 due to an earlier problem, since the part of the code which appears to be failing sure sounds like the "burning engine." I have uninstalled and reinstalled DVD-WS without reinstalling this patch, though, so I don't know if this patch might have installed files which don't get uninstalled via the DVD-WS uninstall process.

Is there any way to remove this patch and return to whatever "burning" code I originally had (assuming that it isn't being removed by unistall DVD-WS itself)?

sjj1805 · Post by **sjj1805** » Mon Jul 03, 2006 1:07 am

Looking at the DVD Burning patch web page I see the following:

Who can update:

* Ulead DVD MovieFactory 3.0/3.5/4.0
* Ulead DVD WorkShop 1.X/2.0
* Ulead DVD PictureShow 2.0/3.0
* Ulead VideoStudio 6.0/7.0/8.0/9.0
* Ulead Video@Home 2.0
* Ulead MediaStudio Pro 6.5/7.0
* Ulead Ulead Burn.Now 1.X/2.0
* Ulead Photo Explorer 8.0/8.5

This tends to suggest that removing DVD WS will not remove the burning patch. The suggestion of the above list is that the burning engine is common to all of the above programs and not specific to any single one of them.

David Mears · Post by **David Mears** » Mon Jul 03, 2006 1:33 am

sjj1805 wrote:Looking at the DVD Burning patch web page I see the following:

Yeah, I noticed that too, which led me to believe it probably goes into some "common" area.

This tends to suggest that removing DVD WS will not remove the burning patch.

I think it also suggests that merely purchasing and installing DVD-WS 2.0 would not be a fix for the problem, as the patch seems to impact WS2 as well.

I have a reply back to ULead support; I'm hoping they can tell me how to remove the patch code from the "common" directory(es) and reinstall the original code from one of my original install files (I have my original downloaded VS6 and WS1.2 install files, as well as VS9 on CD).

sjj1805 · Post by **sjj1805** » Mon Jul 03, 2006 1:38 am

Just an idea that might work.
Download one of the trial versions higher than the above list such as VideoStudio 10+

Chances are that if it is a file common to all programs that one of the latest versions will have an updated burner module.

David Mears · Post by **David Mears** » Tue Jul 04, 2006 9:48 pm

Now I've got yet another problem.

Now that I have at least a temporary way to burn created disc images, I put together the second set of episodes for the TV show I'm trying to transfer from tape to DVD. I got everything built and was trying to create the ISO disc image from WS when it gave me an "Unexpected Error." Looking in the ~DVDPrjConvertLog.txt file, at the end, it says

**[DVD:FAIL] Fail to generate new vob folder C:\Documents and Settings\Owner\My Documents\Ulead DVD Workshop\Trax\~f\, cache vob folder resets.

That folder actually does exist now, but it doesn't seem to matter if it does or not, I always get that error in the log.

I've once again tried uninstalling DVD-WS and reinstalling per previous instructions, and have completely recreated the WS project from scratch (saving only the captured MPG files to build it from) but I can't seem to get rid of this problem.

I seem to recall having a problem like this once a long time ago but now I can't recall how I finally got rid of it. I thought it might've been by removing the project (and all of the cruft in the project folder) and recreating it from scratch but that isn't working this time.

David Mears · Post by **David Mears** » Sat Jul 08, 2006 11:01 pm

I have a new update, and this time it's good news!

David Mears wrote:Now I've got yet another problem.

Looking in the ~DVDPrjConvertLog.txt file, at the end, it says

**[DVD:FAIL] Fail to generate new vob folder C:\Documents and Settings\Owner\My Documents\Ulead DVD Workshop\Trax\~f\, cache vob folder resets.

I found the problem! Or, at least, I found what was causing the problem.

Somehow, in all my uninstall/reinstall (etc.) changes, my "capture" settings got set to use 44.1kHz for audio frequency instead of 48kHz. As long as there was any video within the project with 44.1kHz audio, the failure would occur. Using VS I re-edited the files to use 48kHz instead and things worked just great after that!

If anyone's maintaining an FAQ for problems, they might want to note this one! It sure was an odd one (with no suggestion in error messages anywhere that it related to audio frequency).