Can't burn to DVD

Moderator: Ken Berry

Post Reply
sselkirk

Can't burn to DVD

Post by sselkirk »

Hi all... I'm a new VS user, or I would be if I could get it to work.

Recently bought VS10+, installed it and got to work on a video. After completing my test video, I tried to burn it to DVD.

On the Share tab I pressed the Create Disc button and got the following error message: Failed to initialize internal modules

VS then hung and had to be terminated with task manager.

I have logged this call with Ulead support but after an initial reply of "try reinstalling" they've stopped responding to my emails. Must be a tough one for them.

So I followed their advice and the instructions in the email and reinstalled. No luck.

I then read the FAQ area and followed the instructions for how to do a complete fresh install, including using regedit to delete registry entries. Still no luck.

I tried looking for a fault in my source video (MJPEG btw). Decided I'd eliminate all of my own video and try to burn something that just uses the inbuilt VS clips, like V10, the countdown 5 to 1 intro clip. Exactly the same error.

Then I tried other burning software. No problem with Nero or iTunes. Both happily burnt DVDs and CDs.

I have a fairly new pc (3 months old), spec'ed as follows:

Gigabyte GA-M59SLI-S5 motherboard
AMD X2 5200+ CPU
2GB RAM
1.2TB HDD (4 x 320GB)
C: 320GB NTFS 143GB free VS installed here
D: 320GB NTFS 117GB free Source video and project stored here
G: 600GB R1 NTFS
Gigabyte GEF7600GT GPU
2 x Pioneer DVD-DVR11 DVD Burners

Software-wise I have a bunch of video and audio stuff such as itunes, divx, virtualdub, claddvd, dvd decrypter. No anti-virus, that was uninstalled trying to get this problem fixed.

So I've tried all the obvious stuff, followed Ulead's advice but I still can't burn. This problem seems faily unique to my pc because after extensive googling I can't find anyone with the same problem or even an exact description of what the error message means.

Hoping someone here might have something to offer... thanks for reading.
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

Post by Ken Berry »

If you started off with an MJPEG file (disguised with the .avi extension), edited it in that, did you first -- as I think you should have -- go to Share > Create Video File > DVD to produce a DVD compatible mpeg-2 from your project? If not, that could be your problem.

I suspect instead you left your edited project in the timeline and went straight to Share > Create Disc. That would have meant VS was left to convert your motion JPEG project AND multiplex and convert your menu to video, AND burn, all on the fly. The hardest part would have been to convert the MJPEG to mpeg-2, and since motion jpeg is not one of today's standard codecs (though an oldie but a goodie), I suspect this might just have been a bit too much for VS to handle.

Try the method outlined in my first para above. Then close the project by saving it and opening a new one. But leave the timeline empty. Then go to Share > Create Disc, to open the burning module. Insert your new mpeg-2, build your menu and burn. If 'do not convert compliant mpeg files' is ticked in the cogwheel Options icon in bottom left of the burning screen, there should not be any futher recoding of your mpeg-2, and the potential hiccough (hiccup for our American friends) point should not be encountered...
Ken Berry
sselkirk

Post by sselkirk »

Thanks for the advice Ken

I've had some success using this method, and unfortunately also a few crashes. There's obviously still something strange going on with my pc and VS but at least I am further than I was last week.

Cheers
sjj1805
Posts: 14383
Joined: Wed Jan 26, 2005 7:20 am
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB
Location: Birmingham UK

Post by sjj1805 »

This is simply an observation not a cure and I would invite others to comment. I notice that you have itunes installed.

I have previously noticed that this has an adverse affect on my Ulead Editing programs and have always suspected a conflict caused by the version of apple quicktime that is installed with itunes.

For that reason after removing it I banned any of my family members from installing it on my video editing machine. A few months later one of my sons forgot and installed itunes again, I again had issues with my Ulead editing programs which went away as soon as I removed itunes again.

Possibly just a problem with my system so before you try exploring that as a possible cause perhaps some of our other members can confirm they have itunes and VideoStudio working together in harmony.
etech6355
Posts: 2121
Joined: Fri Jul 29, 2005 3:24 am
Location: US

Post by etech6355 »

sselkirk,
It would be helpful to other readers/troubleshooters if you could try this.
Start VS10+ and goto "Preferences" (F6 HotKey). Make sure your assigned "Working Folder" is pointing to a valid directory. Usually when running XP-Sp2 (VS10+ requires XP-SP2 as far as I know) I assign this working directory to another physical harddisk and assign/create a working directory right off the root of that drive.
Example: F:\VS10_Easter (The working folder for my Easter Videos, all the bunnies :) )
Also under preferences | Edit set the "Resampling quality" = "BEST".
Then exit VS10+ and restart again.
After you restart VS10+ do not load any videos into the timeline, go directly to "Share -> Create Disk" and see if you can get into the DVD Creation Module. If you can get into the DVD Creation module without errors then again goto "Preferences(F6 HotKey)" in the DVD Creation Module and make sure you assign a valid working directory for this module. The VS10+ and DVD Creation Modules can be considered as 2 separate programs. Doing this will eliminate any video conflicts being carried over from the timeline into the DVD Creation Module.

If you can't get into the DVD Creation Module it could be corrupted menu templates or VS is having a hard time accessing your DVD Writers. The Accessing problem could be other software on your computer that takes control of the dvd writers and will not share control of them.
Example: Nero InCD (sometimes), Roxio Drag2Disk, and other packet writing software that access the dvd's OR any dvd writer software that copies dvd's in exclusive mode such as programs used to copy commercial dvd's. DVD Decryptor doesn't install any drivers as far as I know so you probably can eliminate that program as causing any problems. But what is "CladDVD"? Does it install a driver / TSR?
(ripping software not supported on this board)
sselkirk

Post by sselkirk »

Thanks sjj1805... I think you are right about VS and itunes... when I get a chance I'll try removing itunes and see if VS is any better...

Thanks etech6355... have followed your advice and checked settings.

Start VS
Share ->Create Disc

Result: VS error "Failed to initialize internal modules", VS hangs

Start VS
File -> New project
Share -> Create

Result: No problem

According to the VS manual, when you start VS you are in a new project by default. As one would expect too. But if I don't go File -> New project then I can forget about getting into the burning module.

And to answer your other question... CladDVD is a ripper and it is not a TSR program. I think it's the least of my problems at this stage.

My gut feeling on this problem:

A bug inside VS that only shows under a complex set of circumstances that are rarely seen together.

If only Ulead support would search their source code and find out under what circumstances that error message is produced, rather than telling me to reinstall VS & XP.
etech6355
Posts: 2121
Joined: Fri Jul 29, 2005 3:24 am
Location: US

Post by etech6355 »

Maybe re-installing the software would help.

The first place I would look is the assigned "Working Folder" in the Burning Module. If this "Working Folder" is invalid then this will happen. Probably the 2nd time you go into the burn module the "Working Folder" gets reset back to it's default setting.
Another thing that can cause this are corrupted menu templates or file corruptiion (harddisk errors).
sselkirk

Post by sselkirk »

I've reinstalled VS a dozen times now... hmmm, maybe I'll get lucky with the 13th reinstall!

etech6355, have you had this error message (Failed to initialize internal modules) yourself ?? Has anyone had this error message?

You say that if your working folder is invalid then this will happen. I would find it absolutely astounding that the programmer, on finding a directory that didn't exist (or whatever), decided the appropriate error message would be "Failed to initialize internal modules".

Personally I would have made the error "Invalid directory" !!

Anyway, I can assure you that the working directory is valid. I can get into the burning module as long as I'm a good boy and select File->New Project before pressing Share.

Corrupted templates would be fixed on a reinstall so I don't think that's the problem.

And I think we can rule out file corruption, both at the application level (again, that would be fixed with a reinstall) and the disk level (nothing in the system log indicates disk retries or bad sectors/blocks).

Now don't forget that VS hangs after I get the error. Does that sound like normal behaviour for an application?

Or does that sound like an internal bug?

That's what it sounds like to me. An exception has occured that the programmer has not programmed for and so the application hangs.

So Ulead Support people, how about you step up to the plate and do the job properly? That means you need to search the source code for "Failed to initialize internal modules" and determine what conditions cause this error to be displayed. That's the only way you'll solve this for me.
Post Reply