This isn't to say that there is something else that I did that fixed it up (perhaps related to Direct X version, or CODECS), but if I have a problem again, I'd check those things I listed first as something to initially look at. In my case I was using a PCI Via J1394A1 capture card (generic brand) Problems may also vary according to the type of firewire card you plugged in. It always had to be the other way around. Turn on the ADVC THEN the PC, I could never get the signal. I have always found that there is a timing issue. You may think this illogical, as it SHOULD only relate to the 1394 driver, but computers are of course, the most illogical device I own )
Then go back and compare the two lists and see if you can isolate which driver may be causing the error. I did this using the Double Driver software (free) to analyse the driver on the working platform (do a print to get the list in txt form), then run it again on the platform that is not working and print off the listing.
Once you have a working base (preferably 32 bit), do a Driver compare. try and get the software working at some lower level, so that at least you have a starting point that works (at least this will rule out the attached ADVC - and associated devices - is broken factor) Most of the comments I've read state that you have to go to the legacy 1394 driver, but I have never had to do this.
Even now that I've got it working, I can't definitively state what specific step I did that solved it. It also seems that when you are dealing with DELL H/W, you get further complications. I've just finished getting this sorted out, in my case, trying to migrate from XP to Windows 7 / 64 bit. I have read many people just giving up, and just staying on an old OS, doing the capture there and then using their other OS to do the editing. Problems with Windows recognising ADVC devices
0 kommentar(er)
