PC won't output video back to camcorder via Firewire...why?

[Guest]

Hi,

I've successfully managed to capture footage from my DV camcorder onto my PC
via firewire without any problems but whenever I try to send my edited movies
back to the camera the playback jumps and judders and eventually drops out.
I've checked the firewire cabl and the camcorder and all is fine. This has
only started happening since I installed a new Firewire/USB2.0 card a couple
of weeks ago. Before, I used to use the firewire socket on my Soundblaster
Audigy card which worked perfectly but since installing my new card the
Audigy too gives stuttering output. Could it be something to do with drivers?
I am running XP with service pack 2. Any help much appreciated.

 

[Treeman]

Hi,

I've successfully managed to capture footage from my DV camcorder onto
my PC
via firewire without any problems but whenever I try to send my edited
movies
back to the camera the playback jumps and judders and eventually drops
out.
I've checked the firewire cabl and the camcorder and all is fine. This
has
only started happening since I installed a new Firewire/USB2.0 card a
couple
of weeks ago. Before, I used to use the firewire socket on my
Soundblaster
Audigy card which worked perfectly but since installing my new card
the
Audigy too gives stuttering output. Could it be something to do with
drivers?
I am running XP with service pack 2. Any help much appreciated.

Fizzgig,
Not to p*ss you off with my sarcasim, but let me tell you a little
story about the new firewire drivers for XP ala SP2. _They_just_suck!_
And you won't find anyone here that's gotten at least a free pen from
Microsoft that will tell you anything different.
They can't say why 1394 is a protected network device now, or if the
firewall is mucking it up. The coding for firewire was performed by
folks off the corner, "Work today, get paid today!"
So I'll point to the obvious and save them some time; Have you tried
different pci slots? Do you have spyware?
One thing that has worked for some is rolling back to SP1 drivers.
Unless someone can reply with an intellegent solution, I'll hold back
on that info.
We're waiting!
Best,
Treeman

 

[Guest]

Thanks for this Treeman, I've done the spyware/different pci slot thing but
still the same. I stumbled across another forum that was discussing using the
SP1 drivers, but every time I try and over-write the SP2 drivers they keep
re-appearing. What am I doing wrong? I've found 3 locations where the
1394bus, arp1394 and ohci1394 drivers exist but every time I overwrite the
one in the WINDOWS/system32/drivers folder it reverts straight back to the
SP2 version. I found a posting on this other forum (which looks to be from
your good self!) that mentions renaming the SP2cab files to SP2cabold. How do
I do this? On my system it will only let me rename the SP2 part of the file,
the cab is an extension (ie. it appears as SP2.cab)
Any further advice much appreciated!

 

[Treeman]

How ya doin?
You can slip in the old part just in front of the extention .cab
Just a sec . . .

Go to C:\WINDOWS\Driver Cache\i386 & C:\dllcache in SP1 and copy out
the
following files
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

MSDV.sys is in windows\system32\Drivers & \system32\dllcache
(Microsoft camera & vcr driver)

Stream.sys is in windows\system32\Drivers & \system32\dllcache
(WDM Codec)

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 SP2.cab file to (e.g. to SP2old.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.(warning message normal)
Reboot.

Plug in your camera in the transfer mode and see if it enumerates
(connects) this is the only thing I've seen work, short of format &
re-install XP SP1. Your mileage may vary.
All the best,
Treeman