I think Peter has it - PLUS. . . .

VidCap is a separate prog to V7. When we do an update we aint necessarily updating the VidCap. Soooo... the last session of VidCap - here, maybe, you would have had no device Control - would still be in affect.

On this basis, and if my logic IS correct, then the UPDATE wouldn't have affected anything.

But I could be totally wrong!

Yes, I have 1394 checked off as video device

Its strange that the CPU recognizes the firewire is connected to my camera, brings up the window "what do you want to do, as in --->open file, use Movie Maker, Vegas capture, do nothing,etc." so that part is working. Everything works right until time for the app to operate my camera (which it doesn't) and when I find the manual 'capture' and 'play' buttons already depressed and nothing happens..only the 'stop' button which then brings up the capture summary window as if it had actually captured something even though it indicates 0 frames captured...

One thing I did notice is that in my folder for V7 app the capture app is identified as V6 VidCap .exe so maybe that didn't change with V7?

I'll have to get back to it tonight after work. Since this machine (older email CPU) is right next to newer video CPU I'll open up V7d side by side and make sure all settings are identical as this machine captured no problem the very same tape/camera set up.

Thanks much for you suggestions, I'll check it out this evening.

teaktart

Eileen, I think you missed Peter & Grazie's suggestion and that was to check your Vidcap settings.
Since your last capture session was Hi-8 tapes, odds are you disabled Enable DV device control under Options - General in Vidcap.
Another one to check is Enable DV scene detection under Options - Capture.
BTW, Vidcap hasn't been updated since (I believe) version 4 so the fact that it comes up as V6 is no big deal.
edit: BTW #2: HDV is captured using a different Vidcap so it's no surprise that it worked while SD didn't.

Mike

I've just double checked that all settings are exactly the same as those on this older computer which captured the tape just fine, and the suggestions you offered...mine were all set correctly.

I went ahead and did an uninstall of both V7d and my older V6d. Also went and removed any left over folders for each in Sony programs and Sony setup and also went into registry and removed any remaininfg V6 and V7 files.

Download and reinstall from website and same problem, can't capture SD with Vegas. All settings and preferences double checked again. And once more I was able to have the same camera and tape be captured by Windows Movie Maker so the hardware is working the camera as it should....but Vegas on newer CPU just won't do that same task.

Gave up and put in a support ticket after trying knowledge base instructions with no improvement.

Vegas was wonderfully stable for me till version 7c when all kinds of trouble started. Version 'd' cleared up all those problems until this new one with the capture failure.
I want my good old reliable performance back! Hate not being able to edit because of hours spent troubleshooting to no avail...

Thanks for your helpful ideas, which I did double check, wish they had solved my problems....

Teaktart

MEA CULPA !!!

One last thought nugget before giving up completely...

When looking at Computer/ Hardware/ Device Manager/ Imaging Devices I found two devices listed even though I only have one camera "device" .
One device was a generic AV device and the second one was Sony camera. I had looked at the drivers for each one but didn't know what to do about it. I tried to delete the generic one but was concerned I would be making some kind of error if I did, so chickened out and left it there.

Next went and unplugged my firewire from CPU and replugged it, rebooted camera, etc. No change.

But while unplugging camera firewire noticed that I had two other firewires plugged in : one for daisy chain of external hard drives and the other firewire goes to my ADS AVS Link conversion breakout box. I usually only turn this on when I want to monitor on my tv. Last time I used it I left it on....

It just occurred to me that this might perhaps be the second AV device listed as an "imaging device" and turned it off.

Restarted computer, restarted Vegas, restarted capture, restarted camera, and VOILA capture worked!!!!

What a fricken nightmare trying to figure out that this was a conflict and was keeping the Vegas capture app from working. Yes, it saw a device but must have been trying to operate the A/D conversion box instead of the Sony cam....(Somehow WindowMovieMaker didn't have a problem with this...)

Don't let this happen to you! A great way to waste an evening and countless hours...all solved by the push of a button to 'off' OUCH!!!

Need a padded helmet for this type of agony....headbanging--not fun, learning curve....excruciating.....hopefully never forgotten again.

Teaktart

Teaktart - LOL!! Been there done that . .will MOST likely repeat the exercise again.

Sorry, I should have also said check the device being used. But, as you rightly said, WMM was capturing, didn't give the "devices" any further thought.

Guess we have all learnt from your "headbanging". Really, thanks for getting back to us. Good result though! VEGAS ROX!!

As I said, been there myself. Of course there are others on this Forum who never, ever make mistakes - <wink>

Eileen, congratulations on having the persistence to see this problem through to a solution!!
Like Grazie, I never make mistakes either (inner voice: you do too, you idiot!!) so I'm always glad to have another troubleshooting chart to add to my arsenal.
Hope your head feels better soon :-)


Mike

Teakart,

Do not feel bad. That same conflict drove me nutz during setup for the sessions at Stanford. I am convinced that device conflicts are caused less by the devices and more by little gremlins that follow me from place to place.

Unfortunately I always forget how to solve the problem, so I carry that padded helmet with me.

Keith