Unable to capture DV video in VS11+

[Ron P.]

Corel FAQ

If your DV Camcorder is not detected by VideoStudio, please take note of these:

1. Make sure that you have the IEEE 1394/Firewire card properly installed;
2. Go to "Control Panel" (Classic View) then double click on "Network Connections". Right click on the "1394 Connection" then click "Enable";
3. Check the cable connections and make sure that the Firewire cable is connected properly to your camcorder and computer;
4. Turn on your camcorder into playback mode and wait for your camcorder to be detected by Windows.

Note: The use of IEEE 1394/Firewire connection instead of USB is highly recommended. USB connection for MiniDV camcorders are there for data transfers of still image captures and low quality video. But it is not actually optimal for video streaming.

[Ken Berry]

Have you updated your DirectX as suggested above?

[zipdrive]

in response to vidoman, wouldn't it stand to reason I would be having problems with 10, which I am not. Camcorder is being seen fine on the OS and in Studio 10, the problem is 11.

Thanks,
Zip

[2Dogs]

Zip, maybe it's a long shot, but do you have any friends with other miniDV camcorders? One way to narrow it down to a problem with VS and your particular Sony would be to be able to successfully capture from another camcorder.

I find this "substitution" method of trouble shooting quite useful, but then there are 6 pc's in my house at the moment....

[zipdrive]

as i stated to vidoman, if this was a camcorder issue, then I would not be able to use it with any VS product... does that make sense (please read previous posts) ? if your a developer at Corel or Ulead or whoever, and you develop a new software package that with a previous suite that you wrote caused no problems, but the new version was, would it not make sense that someone developing the program changed something up?

[Ron P.]

The problem I have with it being a "bug" in VS, is that I use a camcorder very similar to yours. I can capture using VS, without any problems. If it were a problem with the programming, then I along with several others would have this same issue.

If you check my System Specs, you'll see that I'm running XP Home, SP2, and have the most recent updates.

Ken and I are in the same camp, thinking that there may be some recent OS update that is now causing problems with VS. However again this hasn't posed a problem (yet) on my machine.

The Corel quote I provided above, was mainly to suggest a possible means to reset, jump-start VS into completely recognizing your camcorder, and allow capturing.

You might also try going to Device Manager, locating your Firewire (IEEE-1394), and uninstalling it. Then immediately re-boot windows. When windows restarts it should see that you have a "new device" and automatically re-install it. Once that is done try with VS to see if will now accept your capture.

I done some searching and reading on the capture graph errors. One solution found by a member...

http://phpbb.ulead.com.tw/EN/viewtopic. ... 948#118948
OK - I got it fixed. I am using HDR-HC3 and was getting the same error as everyone else. Here is the trick.
When installing VS11 - you MUST have your Camera plugged in. It will detect the correct settings. So in my case - I uninstalled VS10 and VS11 - restarted the PC - plugged my Sony Cam - then reinstalled VS11 - and all functions are now working correctly.
So nice of Corel/Ulead to tell us that in the installation. why not have something that says; STOP - plug your Camera in NOW before proceeding. Geez !

Hope this helps someone .

These are merely suggestions, that have corrected the problem for others. Also I just ran through my procedure of uninstalling the Firewire to ensure that windows would reinstall it, and it would still work afterwards. It still does. So why not give it shot..

[zipdrive]

that sort of contradicts Ken's answers on running 10 and 11 doesn't it? obviously they both do not run together nicely based on that user's posting.

Thanks,
Zip

[Ken Berry]

I don't read that thread as in any way suggesting that the two programs on one computer had anything to do with his problem. Yes, he uninstalled VS10 at the same time as he uninstalled VS11, and he only reinstalled VS11. But the thrust of his answer was that it was having his HD camera plugged in and switched on while reinstalling VS11 that did the trick; not uninstalling VS10...

I can only repeat that, like several others on this forum, I have all versions from, in my case, VS7 installed on the one computer. I would note that that computer runs XP Pro SP 2 as previous versions, with the partial exception of a patched VS10, do not work on Vista... Anyway, on that XP computer, all the versions co-exist just fine and have done so for a long time. The only caveat I can think of, indeed, is that you don't have two versions running on the same computer at the same time...

[2Dogs]

as i stated to vidoman, if this was a camcorder issue, then I would not be able to use it with any VS product... does that make sense (please read previous posts) ?

Not really. I think you're missing the point of my suggestion to try another camcorder. If you were to find that another, different camcorder also did not work with your install of VS11, then it would strongly suggest that there was a problem with your installation, and not with the program.

It's wrong to immediately assume that your problem is caused by a bug in VS11, and that is the most unlikely cause.

If, on the other hand, the second camcorder did work properly with VS11, it might suggest a problem specific to VS and your camcorder.

if your a developer at Corel or Ulead or whoever, and you develop a new software package that with a previous suite that you wrote caused no problems, but the new version was, would it not make sense that someone developing the program changed something up?

I think that Ken has already explained that the capture driver was changed, probably because it now has to be Vista compliant. With VS10, the program is not Vista certified.

that sort of contradicts Ken's answers on running 10 and 11 doesn't it? obviously they both do not run together nicely based on that user's posting.

Again, I'd say not really. The theory of the problem relating to a Microsoft update is not proven. It's only by being methodical that you can hope to work out solutions to such problems, otherwise you're relying on hitting on a solution by chance. Keep in mind that everyone posting here is doing so on a voluntary, unpaid basis.

[zipdrive]

I'll attempt the user's suggestion and post back on what I come up with.

Thanks for the suggestions.

Zip

[zipdrive]

after all the suggestions: uninstall firewire connection, re-install firewire connection, uninstall 10 and 11 and install 11 back with the camera on, and of course, updating to the Nov. 2007 version of Direct X, it still does not see the camera in 11. I have come to one conclusion and feel free to disagree, when 10 came out, it came out under Ulead, when 11 come out, it came out with Corel's name on it. I know, I know, same programmers and developers,,, blah...blah..blah..., but even after alll the efforts I've tried with help from you guys (and thanks for the suggestions) 11 just sux in my book. I will use it for editing but now I am forced to still use 10 to do the capture (was not crazy about WinDV, was dropping frames, not having that issue in 10 while capturing, and yes, I realize its free and now I know why), but thanks for suggesting a free possibility anyway, had nothing to lose but time. Thanks for all the suggestions, but unfortunately I am still at square one in using 2 programs that should be done in one.

Zip

[Ken Berry]

If you were dropping frames with WinDV, then there is something strange going on with your set-up. One of WinDV's major claims to fame is its stability and the very fact that it does NOT drop frames.... And believe me, I am not the only one who thinks this.

[zipdrive]

well, as I stated, capture in 10 works fine so I guess I'll just be using the 2 from now on until this 11.5 comes out. Is that version still in beta? I know you mentioned something about it.

Thanks,
Zip

[Ron P.]

No 11.5 is out, it is the version you end up with after installing the Power Pack.

I'll echo Ken's response on WinDV. It simply does not drop frames, unless there is a problem on your system.

[zipdrive]

I was wondering about that after I posted that question. That is applied by the way so that answers my question if fixed in 11.5. I think this is isolated to my camera b/c no one else has posted about this particular model except one guy who said he had his stolen before he could use it with Studio products or 11 anyway, so, if anyone from Corel/Ulead is reading this, please look into the Sony DCR-PC9 Digital Handicam with compatibility with 11+ (worked fine in 10). Just b/c some camcorders are similiar does not always mean they are going to run into the same problems.

Thanks,
Zip