D
David
Listmates,
I am completely baffled. I have XP pro (sp1) running on
an Athlon 2800. I also have a Sony TRV-310 video camera
that I am trying to get video off of. I have Arcsoft
Showbiz loaded as well as movie maker as the capture
software.
The weird part. I installed all software and hooked my
camera up to the firewire port and the capture video to
dialog popped up. I selected showbiz as the software
and "presto" the showbiz capture dialog appeared and I
recorded about 100 meg of video as a test.
No problems. I went and edited the video, added titles,
effects, etc.. just to see what it could do. I then
imported the finished movie into movie maker 2 just to
see what it offered.
Two days later, without any changes whatsoever, to the
system or camera I sit down to record a tape from the
camera to the computer for editing. Attach the camera,
the same video capture to? dialog appears and I again
select Showbiz. Showbiz launches, but the capture dialog
appears but doesn't do anything else? I turn the camera
off and immediatly I get the "cannot connect to dv
device" error. So it is seeing my camera.
I check device manager and the "Sony DV Camcorder" is
listed under imaging devices. I turn the camera off and
imaging devices goes away. I turn it back on -- it comes
back like it is supposed to.
Well, I try capturing video to movie maker to see if that
helps. No joy, same result. In movie make I can get the
capture wizard to come up with a "test capture device"
button. Clicking it, it says the camera is functioning
properly, but still -- no joy in being able to capture
anything.
I have spent 2 days prowling the web tring to find an
answer to this problem. I bought another 1394 cable --
same results, it isn't the cable. I have read countless
pages about changing msdv, but that doesn't seem to be a
solution. The Sony DV Camcorder driver is the Microsoft
Driver version: 5.1.2600.0.
I am at wits end and looking for a pearl of wisdom (or
anything that makes sense to try for that matter) to try
and get the capture process working again. Anybody have a
clue as to what to check or where a driver conflict could
have come from?
Any help will be greatly appreciated.
I am completely baffled. I have XP pro (sp1) running on
an Athlon 2800. I also have a Sony TRV-310 video camera
that I am trying to get video off of. I have Arcsoft
Showbiz loaded as well as movie maker as the capture
software.
The weird part. I installed all software and hooked my
camera up to the firewire port and the capture video to
dialog popped up. I selected showbiz as the software
and "presto" the showbiz capture dialog appeared and I
recorded about 100 meg of video as a test.
No problems. I went and edited the video, added titles,
effects, etc.. just to see what it could do. I then
imported the finished movie into movie maker 2 just to
see what it offered.
Two days later, without any changes whatsoever, to the
system or camera I sit down to record a tape from the
camera to the computer for editing. Attach the camera,
the same video capture to? dialog appears and I again
select Showbiz. Showbiz launches, but the capture dialog
appears but doesn't do anything else? I turn the camera
off and immediatly I get the "cannot connect to dv
device" error. So it is seeing my camera.
I check device manager and the "Sony DV Camcorder" is
listed under imaging devices. I turn the camera off and
imaging devices goes away. I turn it back on -- it comes
back like it is supposed to.
Well, I try capturing video to movie maker to see if that
helps. No joy, same result. In movie make I can get the
capture wizard to come up with a "test capture device"
button. Clicking it, it says the camera is functioning
properly, but still -- no joy in being able to capture
anything.
I have spent 2 days prowling the web tring to find an
answer to this problem. I bought another 1394 cable --
same results, it isn't the cable. I have read countless
pages about changing msdv, but that doesn't seem to be a
solution. The Sony DV Camcorder driver is the Microsoft
Driver version: 5.1.2600.0.
I am at wits end and looking for a pearl of wisdom (or
anything that makes sense to try for that matter) to try
and get the capture process working again. Anybody have a
clue as to what to check or where a driver conflict could
have come from?
Any help will be greatly appreciated.