VideoStdudio v10+ NOT WORTH OWNING

[jparnold]

Thanks Graham,
I did get a screen displayed advising that my request had been received. Never received an email advising the same and to expect a reply in x days.
Yes Optus (my ISP) has a spam filter and I also have one set up in my email client (Eudora) and I do check the folders where supposed spam is sent but never noticed anything from Ulead.
I think what I will do is enter the problem again on Ulead's technical support web page and take screen dumps of every screen I see inclusing my post and hope for the best.

It is just so frustrating that after using previous versions of VS (8 and 9) WITHOUT ANY problems that I now get VS10+ crashing using the same hardware.

I recently REinstalled all the drivers which came with my motherboard (chipset, audiu, usb etc drivers) as my PC started to make stuttering sounds when playing windows 'event' sounds and windows (actual windows displayed on the screen) were slow at being updated. After reinstalling those drivers all those problems disappeared. Althought these problems were not present last time I used VS10+ when it crashed maybe they were starting to occur and had something to do with VS10+ crashing. What do you think, could faulty drivers cause software to crash? Remember everytime VS10+ crashed I was merely selecting video clips with PREVIEW and AUTO PLAY on?

Getting back to SH's posts and receiving replies from Ulead suggesting (only) to re-install - I wonder why Ulead doesn't ask for a copy of the files produced when applications crash which can be automatically sent to Microsoft? If those files contain information for Microsoft to investigate (if they ever do) then surely that same data might assist Ulead determine why VS is crashing?

I still like VS regardless as I have tried quite a few other video editing applications (trial versions) and still preferred VS. If I still have problems with 10+ I will revert to 9 as 10+ only offers me more video tracks on the timeline (I have no use for HD capability at this time).

[dadidu]

so JParnold - welcome at the club of frustrated VS10 users....

I can really smack myself of selling my fine and well functioning VS8 pro, and today I will buy another box for 15 Euros because it WORKS and does EVERYTHING exept importing DVDs from my tiny little dvd camcorder. But that's a minor problem that can be solved by nero recode or vision express or any other dvd copy tool.

VS10 retail is buggy with and without the SP1 - my PC had a stalled preview window or distorted colors, and when upgrading my video driver (I have an ATI Radeon X850) to version 6.5 the display errors in the preview window have decreased to a short flicker. The end of a DV tape is not recognised, pressing 'stop capture' does not stop the capture process immediatly, the PAL settings in one property menu is not recognised in other menus... my dear god, since 10 years there's a shiny thing with the name windows registry!

But I am angry - there are less options for DVD title generations, the autosave of edited chapter menus does not work (30 minutes work lost), and DivX6.0 is not recognised in the AVI codec options. And this nice sticky tutorial - which functions not to use, e.g. including project files in the burning DVD window, and creating avi files before making a dvd... blocking my USB keyboard in the dvd burning window (sometimes) and nobody will really burn a DVD from an empty time line.

I assume you have some driver problems, and the nuke solution (format the harddisk) doesn't give you a clean solution because it would run only on some configs without problems. Maybe another graphics card will help, maybe with a chipset from the other manufacturer (use ATI if you nave Nvidia, and vice versa) .... maybe your VS performs well if you install the chinese language addons for the internet explorer (traditional and simplified chinese)... or if you install the chinese IME for office XP becuause you have the asian version and that might miss some components in a western XP version.

If you also have installed Nero you may have two concurrent INCD services running, freezing the system when inserting any kind of burnable media (look in the control panel, software section).... and I don't believe that your MESSER tool does affect your system, at least not VS10.

[heinz-oz]

I would say your problems stem from an incompatibility problem with the ATI catalyst drivers.

Read all about it here http://phpbb.ulead.com.tw/EN/viewtopic.php?t=18809

I just installed VS 10+ and did some quick tests. Everything seems to work fine. I ignored the "recommended procedure" and added a number of DV-Avi files to the time line. Added a few transitions and went straight to burning an ISO image. No problem at all

[jparnold]

Just checked the link to post suggested by Heinz (for ATI drivers - I do NOT have an ATI card - mine is an older GeForce MX440).
Wow another user of VS10+ had problems.
It seems to me that perhaps another patch for VS10+ is well and truely required.

Could anyone confirm or not that installation of heaps of different Codecs (there are currently a number of downloads from various web sites which contain what is supposed to be "every codec you will ever need") could cause problems with VS10? I am just trying to eliminate possible reasons for VS10 being unstable on some peoples PCs because there must be reasons why some users have problems and some not - it would be really great to be able to compile a list of hardware/software/driver which have possible issues (problems) with VS10.

[Ken Berry]

Sorry -- but mega codec packs of just about every variety are notorious as a source of problems.

They are a rag tag and bobtail mix of every codec anyone can think of, thrown together with no attention to how old they are, whether they were overtaken when Windows 3 came out, let alone XP; whether they work with only one program or in another operating system... let alone together.

With the exception of specialist codecs like DivX, which are sold by their manufacturer in their pro versions or distributed freely in their public versions, just about any video editing program I know either uses codecs installed by Windows or by its own software. Unless you want to experiment with older (but still high quality) codecs like MJPEG (which are still used by certain still cameras), there is virtually never any reason to have to install any of these codec packs. And if you do have recourse to them, then select only the codec(s) you need -- not the whole box and dice.

Uninstalling any you have installed may not solve your current problem, but it may go some considerable way in doing so...

[skier-hughes]

Totally agree with [Kevin]. Ooops sorry Ken!!!!
The codec packs could well be the source of your trouble.
Each one tries to be the first one used, they interfere with each's proper working.
I would never install a codec pack.
Some have even been found to contain Malware, so if you found your pc was playing up - your sounds etc - after the installation of these codecs then I'd use system restore to move my pc back to pre codec installation, if you don't use system restore regularly to make restore points then I'd seriously consider the format disc and re-install XP option.

As for the windows reports going to Ulead, I expect MS would not allow it, as it may well contain info they don't want other companies to have.

Your video card is not getting long in the tooth. Does it meet the recommedation for VS10+? Have you got the latest drivers for N-vidia for it? It may be that spending a few pounds on a newer card may help.

[heinz-oz]

Just checked the link to post suggested by Heinz (for ATI drivers - I do NOT have an ATI card - mine is an older GeForce MX440).
Wow another user of VS10+ had problems.
It seems to me that perhaps another patch for VS10+ is well and truely required.

Could anyone confirm or not that installation of heaps of different Codecs (there are currently a number of downloads from various web sites which contain what is supposed to be "every codec you will ever need") could cause problems with VS10? I am just trying to eliminate possible reasons for VS10 being unstable on some peoples PCs because there must be reasons why some users have problems and some not - it would be really great to be able to compile a list of hardware/software/driver which have possible issues (problems) with VS10.

Sorry about the mishap John, my reply was aimed at dadidu.

Other than that, I can only second what Ken and skier-hughes stated. If you want trouble, find another, especially free one, of those all in one codec packs and install that one too. I have never needed one. All the codecs I need do come with the software I install. If I do need one, I get that one from a renowned source.

[2Dogs]

Just checked the link to post suggested by Heinz (for ATI drivers - I do NOT have an ATI card - mine is an older GeForce MX440).

I have an MX440 in my pc, and it gives me no problems, and is quite sufficient for video editing use. I can even play older DirectX 8 games with it, so it's a bit of a step up from integrated graphics. It's also easy to overclock it by around 20% using Riva Tuner, although that gives no benefit nor has any effect on video editing usage.

[johnevans4]

I have the same problem with VS10+ I have just bought a new computer 3800 amd dual proccessor 1gig ram 160 gig HD on board graphics .The old computer was amd 1800 3/4 gig ram 120 gig HD's .I had the old computer about 5 or 6 years ago and ran VS9 on no trouble but when I got VS10 , when previewing clips the program would just dissappear from the screen , so when I bought the new computer I thought all that was over a more modern version of XP and compared to the old one a mega powerful computer . Not so I get exactly the same problem with VS10 on the new set up. Anyway I just womdered with all this info passing around the globe about VS10 has anybody actually solve the problem .

[heinz-oz]

I have the same problem with VS10+ I have just bought a new computer 3800 amd dual proccessor 1gig ram 160 gig HD on board graphics .The old computer was amd 1800 3/4 gig ram 120 gig HD's .I had the old computer about 5 or 6 years ago and ran VS9 on no trouble but when I got VS10 , when previewing clips the program would just dissappear from the screen , so when I bought the new computer I thought all that was over a more modern version of XP and compared to the old one a mega powerful computer . Not so I get exactly the same problem with VS10 on the new set up. Anyway I just womdered with all this info passing around the globe about VS10 has anybody actually solve the problem .

Which problem are you referring to? I just recently installed VS10+ on an older PC and have none. It¡¦s on XP Pro SP 2, older ASUS P4 S800 MoBo with 3.0 GHz P4 with HT, 1 GB DDR400 RAM and a 120 GB HDD.

[sjj1805]

I think what he is trying to say is that when previewing clips, VideoStudio crashes. If so then the likely problems would include:

a. Faulty source material - We know nothing about his clips.
b. Faulty VideoStudio Installation
c. Missing codec
d. Conflict between VideoStudio and another piece of software.
e. Faulty Video Card
f. Faulty video or sound card drivers.

Simply..... we need a lot more information before we can progress the problem.

[maddrummer3301]

.

[johnevans4]

Well the info about :-

a. Faulty source material - We know nothing about his clips.
b. Faulty VideoStudio Installation
c. Missing codec
d. Conflict between VideoStudio and another piece of software.
e. Faulty Video Card
f. Faulty video or sound card drivers.

a.( Source material) straight from my camcorder it works Ok on media studio ,sony vegas and VS9 no crashes.
b. ( Faulty installation) New computer fresh copy of XP . New install of VS10.
c. (missing codec) Surely VS10 loads the codecs it needs to work satisfactorilly when you install it .
e.( Faulty video card ) New computer on board video , causes no problems with anything else appart from VS10 .
f.( Faulty video or sound card drivers ) The computer is an Acer straight out of the box with XP and all the latest drivers loaded.

You seem to be tryting to justify all these crashes when what is wanted is for Ulead to admit there is a problem and sort it and produce a patch to solve it.
Somebody has to take the blame for this piece of junk that people are paying good money for .

[sjj1805]

Just because you have a problem with videostudio does not mean that the software is buggy.

a.( Source material) straight from my camcorder it works Ok on media studio ,sony vegas and VS9 no crashes.

HOW are you getting the material from your camcorder to the hard drive.
Are you using a firewire or USB. In fact what tyope of camcorder are you using, MiniDV, Hard Drive, DVD. there are lots of different types of camcorder and each will have a different method of getting the material onto your hard drive.

b. ( Faulty installation) New computer fresh copy of XP . New install of VS10.

Like anything else NEW thats the time it is most likely to play up.
If it works correctly when first installed it is rare that it then plays up several months later - unless you've suffered other computer problems such as a hard drive crash etc.

c. (missing codec) Surely VS10 loads the codecs it needs to work satisfactorilly when you install it

We don't know what you have been doing to your computer and it is conceivable that you may have inadvertantly deleted something.

e.( Faulty video card ) New computer on board video , causes no problems with anything else appart from VS10 .

I refer to my earlier response.

f.( Faulty video or sound card drivers ) The computer is an Acer straight out of the box with XP and all the latest drivers loaded.

I refer to my earlier response.

If you want help from our forum members you need to give us as much information as possible otherwise it would be like me asking you to explain why my car didnt start this morning - it was working when I parked it last night.

[daniel]

Just checked the link to post suggested by Heinz (for ATI drivers - I do NOT have an ATI card - mine is an older GeForce MX440).

Just for the record.

I had this very same problem with autoplay freezing, also with an older nVidia card (Ti4200), but this was VS9. I just disabled the preview then to avoid the crashes.
When I bought my Geforce 6600 the problem disappeared. It nevre happened with VS10 either.
And no, I did not upgrade my drivers when installing the 6600, just rebooted, Windows was happy so didn't touch anything.