Cannot capture at all in VS10+

felix2 · Post by **felix2** » Sat Jul 07, 2007 3:20 pm

Sorry if I'm missing something daft, but I have tried searching help, knowledge base and forums...

I regularly capture from 3 or 4 different mini DV camcorders via firewire using other software on my Windows XP (SP2) PC (100GB separate video HDD, 1GB RAM). Unfortunately just one of them occasionally causes problems in that (capturing to DV-AVI Type 1), but it always used to capture perfectly in Ulead VideoStudio 8 (capturing to DV-AVI Type 2).

But now that I've upgraded, I cannot get VS10+ to capture from any camcorder at all without crashing before it can even begin.

Device Manager lists IEEE1394 bus host controller and Imaging devices: Panasonic DV camera (or whichever). I've tried shutting down all other programs, disconnecting from internet and disabling firewire and anti-virus.

But when I click on the 'Capture' tab, and 'Capture Video', the 'Source' and 'Format' options are greyed out and the whole program soon completely crashes and closes, with the Windows message : "Ulead VideoStudio has encountered a problem and needs to close. We are sorry for the inconvenience."

The only other thing that's changed since the upgrade (I think) is a new 19" monitor and graphics card - that couldn't be causing the problem could it...?

Any ideas please??... Thank you very much in advance, Giles.

Just seen post in other thread - I'll give WinDV a go - although it'd be nice to be able to (continue to use) Ulead 10+ since version 8 worked!

Post by **Ron P.** » Sat Jul 07, 2007 3:26 pm

Device Manager lists IEEE1394 bus host controller and Imaging devices: Panasonic DV camera (or whichever). I've tried shutting down all other programs, disconnecting from internet and disabling firewire and anti-virus.

If you did in fact disable your Firewire, then you certainly can not capture with it.. Did you disable it?

felix2 · Post by **felix2** » Sat Jul 07, 2007 3:34 pm

Doh! Sorry, I meant disabled Firewall!! Firewire was still very much connected!

Post by **Ron P.** » Sat Jul 07, 2007 3:59 pm

I wouldn't think that changing your graphics card and monitor would affect the Firewire. However since you've installed a new graphics card, have you checked to see if the drivers are up to date? The drivers provided on an install CD are not necessarily the most current.

Did you install the graphics card after VS10? Have you been able to capture at all using VS10? Did you uninstall VS8 after installing VS10? While multiple versions can reside happily on your system, sometimes when uninstalling an older version, it takes some files that the newer version needs, with it.

I'd be interested in knowing what WinDV does. It should capture without problems provided there is no problems with your Firewire cable, or port(s).

Do you have more then 1 firewire port that you are trying to use simultaneously?

Then if you have the install CD, you might try doing a repair install of VS10. If you can capture fine with WinDV, and doing the Repair does not correct your capture issue, you may have to try doing a complete/clean full uninstall/reinstall. We have directions in our tutorials section.

felix2 · Post by **felix2** » Sat Jul 07, 2007 4:16 pm

Hi Ron,

Thanks for taking the time to answer.

Yes, when I installed the graphics card last month, it confirmed the drivers were up to date. I installed the graphics card after VS10+ but hadn't tried capturing with VS10+ before that - or at least fairly sure I hadn't!

I certainly tried to uninstall VS8 but I'm not sure how successful it was. Obviously it wouldn't uninstall itself cleanly and I did try to use the guidelines on here about sorting it out - not sure if it was totally successful though - might be something for me to check, &/or repair / re-install VS10+

I'm only using the one firewire port and cable (which stays permanently attached and I just plug in the appropriate camcorder).

WinDV has just captured fine now - unfortunately I don't have the "troublesome" camcorder with me here at the moment (it's someone else's who videos some things for me), so don't know if that will overcome the problem yet... At least WinDV does offer Type 1 and Type 2 DV-AVI options.

Thanks again, Giles.

Post by **Ron P.** » Sat Jul 07, 2007 4:24 pm

So that does narrow it down to a software and not a hardware problem. If it was due to hardware, then WinDV would not have captured.

You mentioned that you don't have the Panasonic, and it being the troublesome camcorder. Have you tried capturing in VS with the same one that WinDV just captured successfully?

felix2 · Post by **felix2** » Sat Jul 07, 2007 5:03 pm

vidoman wrote:So that does narrow it down to a software and not a hardware problem. If it was due to hardware, then WinDV would not have captured.

OK, thank you.

vidoman wrote:You mentioned that you don't have the Panasonic, and it being the troublesome camcorder. Have you tried capturing in VS with the same one that WinDV just captured successfully?

Actually, an expensive (but well-used) Canon is the camcorder that casues problems in my other editing program.

The Panasonic works in WinDV (and in another 2 programs - I've just found I had another DVD authoring program that captures DV!), but still not in Ulead VS 10+.

I have just realised that although my version of Ulead VS is set up to be PAL / English, its standard Project Properties seem to be DVD PAL (instead of DV-AVI PAL), and when changed to DV-AVI revert to NTSC 30fps... I've tried going to the Capture step with DVD PAL, DV-AVI NTSC and manually set DV-AVI PAL project properties, and every time it crashes before it finds the camcorder...

felix2 · Post by **felix2** » Sat Jul 07, 2007 5:38 pm

This doesn't help with my problem of not being able to capture in Ulead, but I have found a way round the original problem with the troublesome camcorder.

To cut a long story short, that does seem to be an issue about Type 1 versus Type 2 DV-AVI files. In the other editing program, files captured from the Canon as Type 1 cause little beeps every now and again (where it thinks the signal has degraded). The other camcorders are OK. But converting the original problem Type 1 video file to a Type 2 using Ulead actually stops this problem in the other program!

So I'm hoping (strongly) that next time I capture from the Canon, if I capture in WinDV as a Type 2 it'll all be fine and great!

I really would still like to be able to capture in Ulead though. Maybe a full Ulead clean-up and re-install beckons, if I dare / have the time & inclination...