Vidcap Won't Run

dvogel wrote on 2/18/2009, 7:13 PM
Just today I went to run Vidcap (Vegas Pro 8.0) and it won't start. I ran it just a few days ago and it was fine. I have my PC connected to a Canopus box and that to a VCR. I use this configuration all the time with no problems.

I reinstalled Vegas but I get the same results. I can see from the Task Manager that no new processes start when I try to start Vidcap. Are there some log files within Vegas that I can look at to see if some kind of error is being reported? Any other suggestions for what might be wrong?

I'm running XP SP2. I've tried doing my capture through Vegas and by running the Vidcap.exe file directly, which I do from time to time. Same results. BTW, I was able to capture my video using another program (WinDV) so I know things are hooked up right. (Strangely, I didn't hear the audio during capture with WinDV but it was there in the captured file. I don't know if that has anything to do with this problem but there it is.)

Dennis

Comments

Grazie wrote on 2/18/2009, 11:33 PM
I'd be looking at my capturing pipeline.

You say you are getting a partial capture through the other software (audio being the partial bit). So that implies that "maybe" the cabling is okay. For whatever reason, this would appear to be the Canopus going sour on you. You should attempt to take the Canopus out of the equation and try capturing using a pass thru' option using a AV<>DV convert on a DV cammie. If this works, then you may have your answer. HAve you been fiddling with the Canopus drivers? Added new s/w that would impinge on the functionality of the Canopus? Have you downloaded new Canopus Drivers? My list isn't extensive, but you may get my point?

You may have an even simpler answer in that the connections to and from the VCR and or the PC have become unstable. One thing it WONT most likely be, and that is what you ARE proposing, is the actual VidCap s/w. If it were then there would be masses of complaints about it - and there aren't. Maybe a reinstall of the Vegas is required? Though do check out my points prior to something as rad as a reinstall!

So, check and re-check your physical connections; get the Canopus device out of the equation and maybe try another VCR.

I can tell you know your way around VidCap itself, so me blathering on about the settings in there concerning NO Digital control would be pointless - yeah?

Grazie

ChristoC wrote on 2/19/2009, 2:44 AM
As you managed a capture with WinDV I'd say there's nothing wrong with the Canopus box or the VCR or rest of setup.
(If it is one of the Canopus ADVCxxxx range, there are no drivers provided, or to download or update ..... - it just works)

Regardless, VidCap s/w should start fine even if there's no capture device connected - in which case you should get a message in the preview window "Please connect a device"; at least that is what happens here - therefore there is something preventing VidCap from starting or running. That could be due to a problem with Windows itself or maybe antivirus or a virus ....



Grazie wrote on 2/19/2009, 3:04 AM
My bad. Our chum DID say a Canopus BOX! I have a Canopus CARD which was installed into the pc.

Grazie

TGS wrote on 2/19/2009, 11:04 AM
Make sure, if you have more than 1 device plugged into your FireWire ports, that only the canopus is turned on. If 2 FireWire devices are on at the same time, you may get nothing. (although, you should get an error)

Have you deleted any programs lately, that may have shared dlls?
dvogel wrote on 2/19/2009, 7:34 PM
Thanks for the suggestions. I'll respond to them here:

1. There's only one Firewire device involved. This is the same config I've used for years with Vegas and Vidcap. I don't think there's anything wrong with the hardware setup. As mentioned, I can capture with WinDV with no problems. (The "issue" with the audio is not a problem. WinDV does not play audio during capture. This is the first time I've ever used it to capture through my Canopus. But I remembered that when capturing from a video cam, the audio comes from the cam, not WinDV. So the audio question I raised is a red herring so to speak. Ignore it.)

2. Yes, it is an external Canopus box. No, I haven't done anything to the Canopus drivers. And taking the Canopus box out of the chain won't help. I can't run Vidcap at all, Canopus box on or not. Likewise, connecting through a video cam with passthrough won't do anything different. Vidcap will not start up.

3. I have added and removed some software recently--a new mouse driver (for a new mouse), a keyboard key mapper program and removed an old mouse driver. I can't see how they might interfere with Vidcap but when I get some time I'll back them out and see what happens.

4. I did a reinstall of Vegas. Vidcap still won't start.

5. I'm not suggesting this is a Vidcap bug. I have used Vegas and Vidcap for many years. There is a bad file somewhere or some other conflict. That's why I asked if there was any kind of log file that might tell what is going on.

6. Yes, Vidcap should run even if there's no DV device connected. I do that all the time to set capture drives, etc. And it no longer starts whether a device is attached or not.

7. Virus was the first thing I suspected. Norton scan showed nothing.

Well, you are all as stumped as I am. I'm going to back out the programs I mentioned to see if that has any effect. I welcome any other suggestions.

Thanks

Dennis
dvogel wrote on 2/20/2009, 8:28 PM
Replying to my own post ...

I found the problem. Or at least the solution.

It seems as though there is a conflict between the new mouse driver I installed and Vegas Vidcap. Yeah, go figure.

I recently replaced my old Kensington mouse with a new Logitech LX3 optical mouse and installed the driver program for it called SetPoint. After that I could not get Vidcap to run. I uninstalled SetPoint and, after a few reboots, Vidcap ran fine. Just for fun I reinstalled SetPoint. Vidcap wouldn't run, as before. Uninstall SetPoint and Vidcap is fine again.

I can't explain it. Maybe someone else can. Luckily the mouse defaults to a standard 2 button and wheel mouse. The only features I can't access without SetPoint is the wheel click functions. I can live without them.

So, beware if you install any Logitech mouse/keyboard/trackball that uses SetPoint. Chances are you will get a conflict between it and Vidcap.

Thanks for all the suggestions that led me to this experiment and revelation.

Dennis
ChristoC wrote on 2/20/2009, 10:55 PM
Ahhh, glad you found it!
Sometimes I think Logitech should be forced by the trade descriptions act to change their name to Illogitech - they make nice kit, but awful drivers.