Hi:
My mother gets this error message when we try to burn a DVD disk from Movie factory3 SE that was bundled with a winfast tv2000 TV capture card. Her system is:
Del Dimension 4500 384MB ram 80GB HDD with 62GB free LG 4167 DVD drive.
My query is this: I have an identical computer (except some different applications) same TV capture card in the same slot, same HDD, same DVD drive. Same Winfast PVR capture program, Same video source (I hooked her computer up to my VCR) My installation works and hers gives the above error message.
I have viewed the relevant posts on this error and have not seen a substantive solution proposed by ULEAD, even though this problem appears to have been reported as early as March 2005 (10 months ago). I have downloaded the 2 patches that I think are relevant (1 for MF3SE and 1 for Hauppage TVR (something like that)
Question: Is this error message part of ULEAD's code or is it from run-time libraries that you use? If it is from your code, what circumstances trigger the message? If it is from the RTLs, have you investigated this to find the cause?
Please I would like to see a positive answer to this problem, thank you
Source File had some problems (5003)
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
How are you recording the video file?
Are you using the WinTV software or MF software.
Burn the video file to a CD/DVD and copy to the working computer and
see if MF will open the file.
You first need to know if there's something wrong with the video file and
possibly in the capturing process on her machine.
Process of Elimination.
MD
Are you using the WinTV software or MF software.
Burn the video file to a CD/DVD and copy to the working computer and
see if MF will open the file.
You first need to know if there's something wrong with the video file and
possibly in the capturing process on her machine.
Process of Elimination.
MD
-
ScottHendry
maddrummer3301:
Thanks for your reply
Sorry it has taken so lon to respond, but I've been out of touch (on the boat) for 2 days.
The recording is done using the PVR program that came with the TV capture card as there are serious problems with ULEAD's capture program. ULEAD's capture program will NOT allow us to record in PAL format. Every time we change the setting from NTSC to PAL in the video format dialog and then close the dialog, the program switches back to NTSC. This happens with bot installations of Video studio and MF (My mother's machine and mine)
We did exactly as you suggested and recorded a clip on the bad machine, copied it to the good machine and MF read the file OK and created a DVD disk without problem, so the fault seems to be in the MF installation on the bad machine and not with the TV capture card or its program as I have read elsewhere in these postings.
We have re-installed MF several times and compared settings from the bad machine to the good machine but cannot discover any differences. We have spent 4 full days working this problem and are reaching the end of or patience with this brittle software so any help from the ULEAD community is most welcome and gratefully received
thanks
Thanks for your reply
Sorry it has taken so lon to respond, but I've been out of touch (on the boat) for 2 days.The recording is done using the PVR program that came with the TV capture card as there are serious problems with ULEAD's capture program. ULEAD's capture program will NOT allow us to record in PAL format. Every time we change the setting from NTSC to PAL in the video format dialog and then close the dialog, the program switches back to NTSC. This happens with bot installations of Video studio and MF (My mother's machine and mine)
We did exactly as you suggested and recorded a clip on the bad machine, copied it to the good machine and MF read the file OK and created a DVD disk without problem, so the fault seems to be in the MF installation on the bad machine and not with the TV capture card or its program as I have read elsewhere in these postings.
We have re-installed MF several times and compared settings from the bad machine to the good machine but cannot discover any differences. We have spent 4 full days working this problem and are reaching the end of or patience with this brittle software so any help from the ULEAD community is most welcome and gratefully received
thanks
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
I take it for granted you tried to use the same test clip also on the problem machine and still get the error?
That's windows, works on one machine and not another, depends on so many factors.
I use NTSC and one of my SE versions always reverted back to PAL.
It sounds like the error is being generated in a conversion stage and not
the actual burning stage?
I'm not very familiar with the MF3Se version but in the full version in the
burning stage there is an arrow on the right side of the screen.
Click on that to display additional burning options.
Un-Check "Create (Burn) DVD" and check the box that says
"Create DVd Folders", select a drive and directory to create the dvd folders.
If you still get the error then it's NOT in the burning stage of the dvd it's
in the conversion stage either creating the menu templates, converting the audio or the movie (depends on the source file). Also don't add any
background music or pictures that also require conversion.
When planning to record & create a dvd:
Try to record a dvd compliant file with the WinTV capturing software and
on the MF timeline click on the GEAR icon and make sure "Do Not Convert Mpeg Compliant files" is Checked ON. Don't edit the mpeg2 file.
No conversion of the source file is necessary and disk creation should be fast.
Just guessing but if your having a problem capturing with the MF3 software because of reverting back to NTSC something could also be
trying to revert to NTSC in the conversion process of maybe the menu
templates.
Maybe try the trial version of MF4.
Hope this helps,
MD
That's windows, works on one machine and not another, depends on so many factors.
I use NTSC and one of my SE versions always reverted back to PAL.
It sounds like the error is being generated in a conversion stage and not
the actual burning stage?
I'm not very familiar with the MF3Se version but in the full version in the
burning stage there is an arrow on the right side of the screen.
Click on that to display additional burning options.
Un-Check "Create (Burn) DVD" and check the box that says
"Create DVd Folders", select a drive and directory to create the dvd folders.
If you still get the error then it's NOT in the burning stage of the dvd it's
in the conversion stage either creating the menu templates, converting the audio or the movie (depends on the source file). Also don't add any
background music or pictures that also require conversion.
When planning to record & create a dvd:
Try to record a dvd compliant file with the WinTV capturing software and
on the MF timeline click on the GEAR icon and make sure "Do Not Convert Mpeg Compliant files" is Checked ON. Don't edit the mpeg2 file.
No conversion of the source file is necessary and disk creation should be fast.
Just guessing but if your having a problem capturing with the MF3 software because of reverting back to NTSC something could also be
trying to revert to NTSC in the conversion process of maybe the menu
templates.
Maybe try the trial version of MF4.
Hope this helps,
MD
-
ScottHendry
MD:
1) Yes, we tried the same clip on problem machine, and no the program will not create a dvd from the clip.
2) Yes we tried creating a dvd disk setup to hard drive as you suggested and, no we still got the error and it did,'t create the output files. I thought about creating the DVD layout and then using NERO in case the burning engine of MF was causing the problem but couldn't because no files got generated.
3) Yes we usually record in MPEG-2 format and yes the "do not convert" box is checked Also, we don't add any backgrounds or audios, just the built-in backgrounds that came with MF. At that stage of the process, we just hit the "next" button and go through this window and the next one which is the preview window.
4) I don't think that whatever is reverting the setup to NTSC is the problem as this happens on both computers but only my mom's falls over when starting the burn
I don't know if I mentioned it but we have shut down all other apps that we think might be causing problems such as Spybot, Zonealarm, Antivirus, odd toolbar stuff that she likes to use, to the point where the machine has little or nothing extraneous running in the background and still the problem persists.
A new problem has arisen since we started; I defragged her HDD as it was badly framented and now she gets a different error message (something about no disk in the drive or the drive being full) so I'll look at those postings now.
thanks for your suggestions
please "keep 'em coming"
1) Yes, we tried the same clip on problem machine, and no the program will not create a dvd from the clip.
2) Yes we tried creating a dvd disk setup to hard drive as you suggested and, no we still got the error and it did,'t create the output files. I thought about creating the DVD layout and then using NERO in case the burning engine of MF was causing the problem but couldn't because no files got generated.
3) Yes we usually record in MPEG-2 format and yes the "do not convert" box is checked Also, we don't add any backgrounds or audios, just the built-in backgrounds that came with MF. At that stage of the process, we just hit the "next" button and go through this window and the next one which is the preview window.
4) I don't think that whatever is reverting the setup to NTSC is the problem as this happens on both computers but only my mom's falls over when starting the burn
I don't know if I mentioned it but we have shut down all other apps that we think might be causing problems such as Spybot, Zonealarm, Antivirus, odd toolbar stuff that she likes to use, to the point where the machine has little or nothing extraneous running in the background and still the problem persists.
A new problem has arisen since we started; I defragged her HDD as it was badly framented and now she gets a different error message (something about no disk in the drive or the drive being full) so I'll look at those postings now.
thanks for your suggestions
please "keep 'em coming"-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
Scott,
When you assign the working folder (usually I assign a directory right under the root directory, ex: C:\MF4). You can monitor what the program is doing by opening up the working directory before MF starts.
During the creation process under the working directory will be additional sub-directories, temp etc.
You can see audio files being converted, menu templates & the actual mpeg2 file along the the Video_ts folder prior to burning (if you have the burning box checked).
The newest version of MF (MF4) you can directly convert the source files to Mpeg2 with a new feature called "Export".
To perform this with previous versions (get the mpeg2 file), you can grab it for the temp directory before you exit MF and it gets deleted.
You can view or switch to the working folders directory as MF is running by holding the Left <ALT> key down and at the same time hit the TAB key. This windows function allows one to hotkey being active running programs.
As MF is converting (working for outputting) and if you have the working folder open and also active (called Focus, the active window has Focus) Hitting the F5 key will refresh the contents of the windows and you can see the mpeg2 file increase in size and being created.
Then if you have "Taskmgr" also running and have it's option "Always on top" you can watch the memory usage & processor load etc.
I know these aren't answers but maybe could help you troubleshoot the problem. I have 2 dual-monitors on my system that makes this easy to do.
*Buy your mom a panasonic dvd recorder for her birthday.
Hope this helps,
MD
When you assign the working folder (usually I assign a directory right under the root directory, ex: C:\MF4). You can monitor what the program is doing by opening up the working directory before MF starts.
During the creation process under the working directory will be additional sub-directories, temp etc.
You can see audio files being converted, menu templates & the actual mpeg2 file along the the Video_ts folder prior to burning (if you have the burning box checked).
The newest version of MF (MF4) you can directly convert the source files to Mpeg2 with a new feature called "Export".
To perform this with previous versions (get the mpeg2 file), you can grab it for the temp directory before you exit MF and it gets deleted.
You can view or switch to the working folders directory as MF is running by holding the Left <ALT> key down and at the same time hit the TAB key. This windows function allows one to hotkey being active running programs.
As MF is converting (working for outputting) and if you have the working folder open and also active (called Focus, the active window has Focus) Hitting the F5 key will refresh the contents of the windows and you can see the mpeg2 file increase in size and being created.
Then if you have "Taskmgr" also running and have it's option "Always on top" you can watch the memory usage & processor load etc.
I know these aren't answers but maybe could help you troubleshoot the problem. I have 2 dual-monitors on my system that makes this easy to do.
*Buy your mom a panasonic dvd recorder for her birthday.
Hope this helps,
MD
-
ScottHendry
MD
Thanks for your suggestions. For me (computer literate) they sound OK but mom would never manage the task switching etc etc. I guess I'm just disappointed with MF as it seems to promise so much in the way of functionality, but fails to deliver by being such a fragile app.
I would like to thank all of you who posted suggestions for your support, but I will sign off here on this and say we failed at this point to solve the problem and I will make no more postings on this except if I find the solution. To everyone!
Thanks for your suggestions. For me (computer literate) they sound OK but mom would never manage the task switching etc etc. I guess I'm just disappointed with MF as it seems to promise so much in the way of functionality, but fails to deliver by being such a fragile app.
I would like to thank all of you who posted suggestions for your support, but I will sign off here on this and say we failed at this point to solve the problem and I will make no more postings on this except if I find the solution.
To everyone!