"An error occured while capturing from the device. An invalid argument was specified."
When capturing using VV3, I usually (but not always) receive this error message when capturing. So far, the only official response I've had from SF is to try re-installing the software, which I did.
The capture can be restarted by "Reconnecting to the Device".
It seems logical to deduce then, that there is something which is causing a random disconnect. But....
As I pointed out in this forum weeks ago, there seem to be poor error detection routines in this part of the program. For example, if you delete the folder which you have set as the default for your captured clips, vv3 reports that it can not detect your camera (create the folder - viola! your camera is detected again).
This error message is so far off base, that I'm wondering if perhaps the above error message is leading me astray.
I have a pci ohci 1394 on its own irq.
The camera is a Sony TRV-320 and I use the analog-digital conversion for most captures. I can and have (occasionally) captured for over an hour without the disconnect (& error message) occuring.
The 1394 is a 3-port Dazzle OHCI compliant card.
I can find no pattern. It happens with live off-the-air captures, and vhs->adc captures. It can happen after an hour or after 5 minutes.
This problem would seem to have nothing to do with:
(a) dropped frames (I never drop any frames)
(b) audio (quality excellent, sync always perfect)
(c) hard drive(s) (7200 rpm dma enabled - dedicated for video, gigs of free space)
(d) background programs running (all disabled)
(e) incorrect drivers (1394 is using ms pci ohci drivers - not t.i.)
(f) video camera drivers (using ms dv camera & vcr)
(g) fat32 limitations (using win98se, & vv3 captures sequential 4 gig clips great)
Obviously, this is very frustrating, as I usually can not capture without multiple restarts (although, as mentioned, not always)....requring me to sit here and fuss with the capture for hours.
Once captured, vv3 performs flawlessly.
ANY help will be very much appreciated.
I was (and still am) hoping for more than a single email of "try reinstalling the software" when I reported this to sf.
Thanks for any assist. This forum is a god-send.
When capturing using VV3, I usually (but not always) receive this error message when capturing. So far, the only official response I've had from SF is to try re-installing the software, which I did.
The capture can be restarted by "Reconnecting to the Device".
It seems logical to deduce then, that there is something which is causing a random disconnect. But....
As I pointed out in this forum weeks ago, there seem to be poor error detection routines in this part of the program. For example, if you delete the folder which you have set as the default for your captured clips, vv3 reports that it can not detect your camera (create the folder - viola! your camera is detected again).
This error message is so far off base, that I'm wondering if perhaps the above error message is leading me astray.
I have a pci ohci 1394 on its own irq.
The camera is a Sony TRV-320 and I use the analog-digital conversion for most captures. I can and have (occasionally) captured for over an hour without the disconnect (& error message) occuring.
The 1394 is a 3-port Dazzle OHCI compliant card.
I can find no pattern. It happens with live off-the-air captures, and vhs->adc captures. It can happen after an hour or after 5 minutes.
This problem would seem to have nothing to do with:
(a) dropped frames (I never drop any frames)
(b) audio (quality excellent, sync always perfect)
(c) hard drive(s) (7200 rpm dma enabled - dedicated for video, gigs of free space)
(d) background programs running (all disabled)
(e) incorrect drivers (1394 is using ms pci ohci drivers - not t.i.)
(f) video camera drivers (using ms dv camera & vcr)
(g) fat32 limitations (using win98se, & vv3 captures sequential 4 gig clips great)
Obviously, this is very frustrating, as I usually can not capture without multiple restarts (although, as mentioned, not always)....requring me to sit here and fuss with the capture for hours.
Once captured, vv3 performs flawlessly.
ANY help will be very much appreciated.
I was (and still am) hoping for more than a single email of "try reinstalling the software" when I reported this to sf.
Thanks for any assist. This forum is a god-send.