"Convert step got some problems" error message (41

[TubaDad]

I have loaded all of the patch. Got it the day after it was published. Don't have any of the devices that are patched, so those aren't loaded.

I can't go back to VS8, I had way too many out of sync problems to go back there. I am eyeballing the competition, but it is hard to make that jump after being with VS since 5.

[Ken Berry]

My point really is to wonder whether VS9 WITHOUT the patches would come up with this message. (I guess it does.) But for someone who has been using VS9 without problems to suddenly have this one appear, makes me wonder if somehow one of the patches might be causing it. As I said in another thread, if it ain't broke, don't fix it. I haven't applied the patches as yet simply because VS9 seems to be working just fine without them...

[TubaDad]

Ken,

That is one of the things that I have been considering. Unloading and reinstalling without the patch. But I ran with the patch for nearly two weeks, and burned several new projects before this started happening. I have tried to burn old projects from after, and before, the patch, both with no luck. It is almost like there is a corruption in one of the program files that is not interpretting somthing right. But that is way beyond my skill set. Thanks for the comment.

[Trevor Andrew]

Hi

When the patch for Vs 9 was first mentioned i installed it only to have problems with Viseo Studio.
I cannot remember the exact problems i encountered, but re-installed the program without the patch.

I am a firm believer in what Ken said (if it ain't broke, don't fix it.) so why on earth i took this action i will never know.

The point is i did have trouble using the patch.

Trevor

[TubaDad]

Thanks Trevor, That is my plan for today. There are some programs that I try to keep up to date with the patches and VS became one of those last year when every patch was going to fix the OOS audio problem. I will find the uninstall tips this morning and get VS9 reinstalled.

One thing that this latest problem did is get me to burn my first Studio 9 DVD. Not sure I like it as much as VS, but it does sit there as a viable option now.

[TubaDad]

Quick Update:

I uninstalled UVS9 and 3D. Reinstalled UVS9, with no patches. Immediately burned the same project that was giving me the 4101 error without a problem. Just for a test I tried burning it one more time before I uninstalled and it was still failing, so I know the exact same project file, with the same contents worked after I reinstalled.

I don't like this problem. I looked through my restore points and I had not installed anything between the last time I successfully burned a project and when I started getting the error. In fact, I had installed the patch a week before my last good burn, so that causes me some concern that something got corrupted, in the program, while I was an innocent bystander.

[gardnerra@tpg.com.au]

Have encountered the same issue as described above.

Previous versions of VS7 & 8 worked fine. VS9 also performed flawlessly on initial install, however within the last month has had failed to burn DVD's with the error 4101 message.

Have been able to get it to burn DVD's by changing the Project Settings to anything other than the default setting, ie forcing it to convert the entire captured project to a lower quality/long play DVD.

Have also been having similar problems when trying use MYDVD LE 7 (by Sonic) to burn DVD's.

Nero 6 appears to be working ok.

Prefer VS9 since it produces higher quality finished product with menu's etc.

Will continue reading posts to see if anyone else has a solution other than re-installing ... but will give that a go if the concensous is that that is what is needed.

Thanks

[TubaDad]

Gardnerra,

I can tell you that I did not like the idea of uninstalling, but was pleasently surprised when I did. I had created separate folders for video files and a few templates that I expected to disappear, so I copied them to a separate directory. These did not disappear as I was expecting. I know this means that it did not completely uninstall, and I have to admit I was concerned that I was going to run into the problem again when I saw them, but it all worked out well. Hopefully that helps you on a decision to uninstall or not, in my case it was well worth it, and I was still able to retain some of my customizations.

To me it just shows that some file in the program is getting messed up rather than a setting in the registry. But I could be wrong, I am not a technoweenie.

[zipdrive]

I've been looking all morning for answers to this dang 4101 error, not to mention the illiteracy the programmer displays in English to tell you the problem... sounds like something a Korean hacker would pop up.

Anyway I found the information posted up here, especially since its been almost 3 months ago since someone posted to it, that the so called patch update is the root of all evil. I've been using VS 8 before and had no problems even with the patches... but this was one for the books, a patch fix to bring on a problem that never really existed until it's sorry behind came into existence (meaning the patch). Anyway I took the advice of one of you and uninstalled and reinstalled (didn't have to reboot) and took the existing project I had started and finished in a little over an hour... not bad for my system. Hopefully with the P4 3.2GHz HT 1MB L2 DIE Cache with the DDR400 (2) 512= 1 gig memory I have on the way in the mail for my Gigabyte MB, the speed issues will hopefully come to a min. I found that 9 is not as much of a hogger as 8 was, but at least 8 worked without the cumbersome issues that were faced with the update. I found it refreshing and hopeful that I had not really went thru a complete project before I applied that dang update... anyway, I will stick with the motto in here like one of the veterans said "If isn't broke, don't fix it".. sorry I forgot your name because I don't feel like losing all that I wrote here by hitting the back button, but thanks for your advise...

Also if anyone has tried that Shrink mechanism that appears to be part of the burn process in VS, some type of DVD shrink I assume,, I'd like to hear how it works for you.

Thanks for your time..

Zip

[Ken Berry]

...And for the record, following on my 5 September post on this thread, three months later and I still have not applied the patch and VS9 continues to work just fine without it!

[zipdrive]

"If it's not broke, don't fix it!!"

LOL!!!


Take Care All, hopefully this will put a death end to 4101.

[captkras]

Hey all,
I too ran into this problem. I captured the video from my camera using this software, (I had already run the patch). Created a video using the wizard, and BLAM! It blew up. I uninstalled, and then reinstalled, NOT installing the patch. And lo and behold....I can burn a DVD ISO image.

Has anyone informed tech support that their patch broke stuff as of yet?

[rfields]

am i doing something wrong. my creat disc is greyed out and i can not burn a cd. does video 8 capable of doing this . i am new to video and can not seem to find an answer yet.

[Ron P.]

am i doing something wrong. my creat disc is greyed out and i can not burn a cd. does video 8 capable of doing this . i am new to video and can not seem to find an answer yet.

Hi Rfields, welcome to the forums..

First off, what version of VS8 are you using? It is a full version, or a bundled version (SE), meaning it came with some hardware?

Do you have a DVD burner, or just a CD burner?

What steps do you go through leading up to wanting to burn the DVD?
Do you have any video clips in the timeline at the time? You should not. When you are going to burn a Disc it is best to have nothing in the timeline.

Please read the following posts;

Read This First Sticky

Recommended Procedures

Ron P.