Problems with capture device

[Dimicelli]

I am having a issue with my Ulead Video Studio. it no longer will read my capture device therefore not allowing me to capture video. I would like to see if anyone could help me!


Thanks for any help you can provide.

Randy

[sj1805]

Before anyone responds, This new member was having problems creating an account. I have created this account on his behalf and to prevent accidental deletion due to the Zero Posts Policy I have posted the problem he wishes to raise. At this stage this is all that was conveyed to me but hopefully once Dimicelli recieves from me his acount name and password he will update this link with the reqired information as per the link
Please Read This Before Posting

By the way - well done Dimicelli for finding out my private email address!!

[Ken Berry]

And would you care to share with the name and model of your capture device and how is it connected to your computer. Please also tell us which version of Video Studio you are using and whether it came with the capture device.

[SkipMcCormick]

I cannot capture video from my Canon ZR830 Digital Video Camcorder via Firewire any more-- OS doesn't detect the camera. This used to work (last May 07). I need to work on this year's Christmas video, but can't get the data into Ulead (VS10). The camera's still image transfer by USB still works - and the camera was new in May.

I rebuilt the entire system (fresh install on formatted disks) This was after trying everything else I could think of. XP Pro SP2

I'm using freshly reinstalled VS10 (bought online and downloaded 2 years ago).

I tried four different Firewire PCI adapters, 2 w/ VIA chips, one lucent, and one Ali. the OS detected and installed each one fine, but when I plugged in and turned on teh ply setting of my camera -- nothing was detected. I also tried a fresh (short - ~18") Firewire cable with the same results.

Project Settings (important): I wish I could get to this stage...

PAL or NTSC: NTSC

Error Codes (if any): Cannot locate a capture device...

I have seen a LOT of discussion about this same problem online - with most of the posters pointing at SP2 problems (there was a fix in it for Sony DVC's apparently). Some of the posts have reported successfully (manually) rolling back the ieee 1394 dirvers to pre SP2 versions - but that seems dubious to me.

Is this problem really common? What are people doing about it?

[Ron P.]

Some of the posts have reported successfully (manually) rolling back the ieee 1394 dirvers to pre SP2 versions - but that seems dubious to me.

That might work. I know the IEEE-1394 Host Controller driver on my system is dated 2001. I just tried to update it, and Windows could not find a more current driver.

You can try to see if your system can locate an updated driver, by right-clicking on the "My Computer" icon on your desktop and selecting Manage. Then locate on the left side Device Manager. Once the Device Manager opens, locate the IEEE 1394 bus Host Controllers, expand it, by clicking on the "+" . Then right-click on the controller (Mine is a Texas Instruments....) choose properties (or just double-clicking will open the properties dialog too). Go to the Drivers tab, and press the Update Drivers button. There's an option to allow it to search the internet.

Then also on this same tab is the option to rollback the driver. You can try this to see if it helps. You can try uninstalling the device, by right-clicking on it in Device Manager, select Uninstall. Then reboot, when it does Windows should see this "new device", and install it.

Back on the General Tab, at the very bottom, is a pull-down menu. Check to see if some how it has been set to disable.

Since the OS is not seeing your camera, after all this, I would suspect a faulty firewire port on the camera. Does it have other I/O ports, such as S-Video or RCA composite? If so you could use them, and a capture card.

[SkipMcCormick]

Thanks for the help. There is no driver to roll back to when I attempt it. I saw in another post here that you can disable the 1394 Network adapter without affecting the firewire capture, so I did that. Now just the "OHCI Compliant IEEE 1394 host controller" is enabled. Rolling back to SP1 drivers is a little more complicated -- javiers ( at http://www.fixya.com/support/t90018-fir ... ot_seen_xp) provided the following steps:

"... I'll give you the
manual way to do this. That is if your fortunate enough to have SP1
drivers available. If not, you can borrow someone else's SP1 CD.
Firewire Fix;
Go to C:\WINDOWS\Driver Cache\i386 & C:\dllcache in SP1 and copy out
the
following files
SBP2port.sys is in C:\Windows\System32\Drivers & \system32\dllcache
1394bus.sys is in C:\Windows\System32\Drivers
arp1394.sys is in C:\Windows\System32\Drivers
nic1394.sys is in c:\Windows\System32\Drivers
ohci1394.sys is in C:\windows\System32\drivers
enum1394.sys is in C:\windows\system32\drivers

Copy out the following files to a new folder you can call
"Firewirefix," (without quotes)

Stop XP Sp2 from re-installing it's drivers again by:
Renaming the XP2.cab file to (e.g. to XP2old.cab)

Replace the SP2 versions of these files with the SP1 versions in
C:\WINDOWS\system32\drivers & C:\WINDOWS\system32\dllcache in safe
mode.

Go to device manager for your ohci firewire card and update SP2 drivers
to the SP1 drivers by pointing to Firewirefix folder.(warning message
normal) Reboot...."

I thought about following his steps, but became concerned about side effects.

At this point, I'm going to build a completely separate PC and hold off o installing any service packs or updates until I have loaded VS10 on it and seen if it sees the camera. (I' really hoping that the camera's fw port is not hosed -- it was an expensive camera ).

I also have one other idea... I have a friend who has a fairly new sony DVC camera. I will see if I can borrow it long enough to see if it detects and if so to capture my cassettes' content (I'm thinking this might work, since the MS KB article that talks bout the patches in SP2 reference fixing the detection problem, but only for Sony cameras -- see http://support.microsoft.com/kb/318684/ ).

Thanks.