[RESOLVED] Write To DVD Bug - VideoStudio needs to close

[awbarnett]

I have been using VideoStudio X2 for about 3 weeks. I bought the Box Version and stopped using my old Ulead version 8.**

Before posting this problem, I searched the forum for related Posts but did not find any. So, I do not know if others have experienced this same problem. I hope I am not wasting some ones time. Hopefully, this problem can be addressed by Corel and fixed.

The Problem:
When burning a project to DVD (under specific situations, listed below) the message "VideoStudio needs to close" appears at the very moment the program starts to write the project to the DVD disk.

I have spent many hours and used up a ton of disks tying to isolate, confirm and verify that the problem was just not a one time fluke and how to recover from the problems in order to get my computer back to it's normal operating condition.

What I'm attempting to do:
I have 4 separate projects that I have finished and have burned each of them to individual disks. Now I'm trying to burn all 4 of the projects on to just one disk (just like I have done numerous times using Ulead VS Version 8**).

I saved each of the 4 projects to separate mpeg files. Then, went directly to "Share" (new project) and loaded each of the 4 mpeg files via the "Add Media" option for video files (not the one for the .vsp project).

The four files load and the program completes the necessary processing OK. However, the very moment the program attempts to write to the DVD. . . . . the "Need To Close" window appears.

The "VideoStudio need to close problem" creates 3 problems:

1) Cannot eject DVD disk from drive.

2) At this point, when any disk is inserted into the DVD drive the "What do you want Windows to do" window never appears, regardless of how many times I try. This affected not just the DVD drive I was using but both of my DVD drives. When the disk is inserted in to the drive, the drive activity light flashes a few times then stops. The disk just sits in the drive.

3) The "Need To Close" problem looks like it's here to stay. No matter whether I attempted to re-burn an existing finished project again and/or create a new project, in all attempts, the moment the program starts to write to the DVD the "Need To Close" window appears.

None of these 3 problems have ever occurred prior to this "mpeg File" project. In fact, VideoStudio X2 had been working flawlessly.

My Recovery Solutions for the 3 problems:

Problem 1) cannot eject DVD disk from drive.
Solution: Rather simple, just restart windows and disk can then be ejected.

Problem 2) the "What do you want Windows to do" window.
Solution: Restore XP to an earlier restore point. There may be other ways to fix this but I don't recall them.

Problem 3) The "Need To Close" problem looks like it's here to stay.
Solution: Ran "Repair" for VideoStudio X2 program from XP's Add or Remove Program utility. Going back to an earlier restore point did not help.

Additional notes:

Note 1)
All three above problems occur each and every time I go directly to "Share" and attempt to burn a DVD by loading the 4 mpeg files via the Video File "Add Media" Icon. After each attempt, I re-do all of the above solutions, and then try it again.

Note 2)
I can however, go directly to "Share" and load the 4 VSP project files (instead of the mpeg files) via the Add Media "VSP Icon" and everything works, as it should.

Note 3)
Surprisingly, I can also go directly to "Share" and load the 4 VSP project files via the Add Media "Video File Icon" and everything works equally well that way also.

Note 4)
I have not tried saving each of the video files to some other format other than mpeg. At some later time, I may try using another format and see what happens.

Note 5)
On many occasions when XP starts acting strange, I have used Microsoft's "Windows Resource Tool" (subinacl.exe and related file reset.cmd) to correct the strange behavior. Unfortunately, this did not help resolve any of these 3 problems.

Note 6)
Using Windows XP Pro with SP2 and SP3.
Current with all new Windows Up Dates.
The recent VideoStudio X2 Patch is installed.
DirectX is up to date and etc.
Ample free HD space (using just 23% on my C drive).
Using all SATA drives. No Raid.
I have 4GB of memory (XP's maximum).
Using a FoxConn Destroyer Mobo with an AMD Dual Core 2.7 processor, etc.

Note 7)
I always maintain a minimum of 2 Back-Ups (clones) of my hard drive C. I use an "old school" Symantic DOS program on a bootable floppy called "Ghost". Anyway, I always use one of my back-up HD's to experiment with and never have to fear that I will trash my good daily use HD.

[Ron P.]

It seems there is something about your created MPEG files VS does not like. Could you right-click on one of them in the editor, select Properties and post them?
When there is no problem using VSP files, VS is creating the DVD Compliant MPEG files during the burn, and using the correct properties. Since you're not having any issues using VSP files, there's nothing wrong with that workflow. The suggested workflow, is just that, a suggestion for those that do have problems when jumping into the burn module and not first creating DVD Compliant MPEG files.

I will say this is the first I've heard of a crash locking up the DVD drives. Do you by chance have other DVD authoring programs installed?

[Black Lab]

Maybe the program is backlashing because you are calling it Visual Studio. The product is called VideoStudio.

Visual Studio is a Microsoft programming app.

[awbarnett]

Hello Ron P

Thanks for your reply. Here are the properties for one of the mpeg files.



DVD Authoring programs on my computer . . . .if you mean something like Nero and/or Ulead VideoStudio ver 8**, then YES. I have both of these in addition to VideoStudio X2.

Hey Jeff! You are probably right
Although I'm taking a break for a few days, I am currently involved writing a large complicated program in VISUAL Basic and I guess I just have the word "Visual" on my mind.

[Ron P.]

Well except for the audio properties they appear to be DVD compliant. For NTSC, MPEG Audio is not compliant, they should be LPCM (linear pulse code modulation) or PCM (pulse code modulation), or Dolby. MPEG-Audio Layer2 is considered DVD compliant only for PAL. I would not think that this would cause VS to crash like it has been for you.

When you render your project to a video file, try choosing NTSC>DVD. That should provide all the correct properties. Then proceed from there to build and burn your DVD. Since you have already gone through numerous DVDs, try Creating DVD Folders, instead of actually burning a DVD. Just uncheck the Burn DVD and check the option to Create DVD Folders. If VS does not crash doing this, then there may be some other issue, as VS goes through the same process as burning to an actual DVD.

DVD authoring programs, like Nero have a data backup utility that allows you to drag and drop files to be burned to CD/DVD. I forget what it's called in Nero. Some of these actually hi-jack the burner, and refuse to allow any other DVD application to access it. Check Nero to see if it may be doing this. If so you need to disable or uninstall it.

[awbarnett]

Ron, thanks for the suggestions. I will check them out and get back when I finish. Thanks again!

[awbarnett]

Hello Ron!

Thank you very much for your assistance.
I followed your welcomed suggestions.

1) I loaded each of the 4 projects and saved each of the video files as NTSC>DVD

2) I attempted to change each the video file's Audio from MPEG to Dolby. However, 1 of the files would not convert to Dolby. I tried several times but each time I checked the properties of that file, it was still MPEG and not Doldy as the other 3 were.

In as much that I could not convert 1 of the files to Dolby, I also changed the project settings.

I changed two things in the MPEG properties for file conversion.
1) Un-Checked the "Do not convert compliant MPEG files".
2) Checked the "Treat MPEG audio as non-DVD compliant".

Normally, when I'm trying to isolate a problem I do one thing at a time. However, I have spent a lot of time on this projrct as it is, so this time I thought I would go for the whole bucket of bolts at one time.

Anyway, the bottom line is that all of my problems have been resolved. Unfortunatly, Im not exactly certain which of the changes I made corrected the problems.

Many thanks again,

[Ron P.]

Well as long as it is working don't worry too much about how. Happy to see it's working now..