Can’t Capture Video from Camera in SV 13

[Graham Bernard]

[dave croonprince] “I have windows 7. Nothing has changed”

Well, evidently, something has changed.

Wanting to ensure that I was going to address this issue from a personal checked standpoint, and confirm that it wasn’t an issue with VP13 I conducted a controlled experiment on your behalf.

I dug out my ancient Canon XM2. Connected via f/w and immediately Windows 7 recognised it:

I inserted a DV-Tape and in VP13 the Canon was recognized:

I clicked on the Capture from DV Tape within the VP13 Project Media Pane and proceeded to capture straight from Camera:

OK, now I have reassured myself that the workflow works for me, might I suggest the following:

1] Check that your f/w port is active and not dead?

2] Confirm your VP13 Build number?

3] Confirm that you hadn’t any Windows Updates since your last successful DV Capture.

4] Ensure your .NET Framework is up to date.

Lastly or even before 1] above, try a Factory reset. Also do track down your copy of VidCap.exe and ensure it is available.

To restate, I have DV Capture working successfully in VP13 running W7. You have to have a local issue.

* Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Graham Bernard]

OK . . .

I’ve now Checked from VMS Plat 6 and all iterations of VEGAS Pro from VP9 > VP14, all working as they they should, from within their Vegas GUI. The ONLY one that is playing up is VP15. Really???

I’ve also tracked each and everyone of the instances of VidCap60.exe, and externally to Vegas and Plat including VP15, they all worked as you’d expect. Why VidCap wont work within the VP15 GUI? No idea . . . .

So, throwing you a bone, do try VidCap60.exe externally you VP13 and see how you go.

Oh yeah, do do confirm that you have the correct path for capturing externally. Here’s mine for VP15:

So, it would appear I also have something locally that is an issue for me for VP15, but the actual VidCap60.Exe for VP15 works externally to the VP15 GUI. Now THAT is screwy. I’m making a point here ços maybe just maybe you too have a local issue going on.

And again, do try your own VidCap60.exe for VP13 and see how you fair – yeah?

* Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Graham Bernard]

NB: Any reference I made to VidCap.exe should be VidCap60.exe – I missed out the “60”

Cheers!

G

* Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[John Norton]

FWIW, ( VP15 311) Previously I had everything working ok, DV firewire capture wise, then I did a big Win 10 update last night, the latest one that gives the Graphics card performance info. in task manager.

Anyway its still working fine. The Texas Instruments PCIE firewire driver is still intact, undisturbed in device properties.