Grass Valley Forums Facebook   Twitter   YouTube  

Go Back   Grass Valley Forums > Converters > ADVC

Thread Tools Display Modes
Old 05-25-2018, 11:04 PM   #1
Junior Member
Join Date: Nov 2015
Location: Latvia
Posts: 7
Default ADVC and Windows 10

It is somehow strange to acknowledge that there are so many people who discover that their PC/Laptop does not recognize ADVC connected and are asking for help, but there is not a Sticky that tells what to do. :)
Here is my case. ADVC works under Windows 7 64Bit, but is not recognized under Windows 10 64 Bit. After some search in Google the solution appears to be quite simple- you need to install a Legacy IEEE1394 driver. Here is the link to it:
You will also find the instructions how to install the driver, once it is downloaded. The first trick is that after double-clicking on the driver .msi file no Window pops up, instead it is allready installed in the system in Program x86 folder. You must locate the .inf file, right click it and choose- Update Driver.
Don't rely on me, better follow the instructions. :)
Interestingly though my Sony miniDV camera was recognized in Win 10 even before this driver update. So there is some difference between a miniDV camera and Canopus ADVC-55. Certainly there may be other reasons why the ADVC is not recognized, like the lack of Power supply when connected from a 4 pin IEEE1394 port.
Good luck,
Canopus ADVC 110; 55, , Sony TRV33E miniDV, Blaupunkt RTV-950 S-VHS with TBC, LG LV880 HiFi, Sony SLV SE-630 HiFi, LG BL-162W, Sony Vegas Pro 12, WinDV
Maris is offline   Reply With Quote
Old 06-28-2018, 03:11 PM   #2
Junior Member
Join Date: Jul 2017
Location: Australia
Posts: 28
Default Problems with Windows recognising ADVC devices

Hi Maris,
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.
I've just finished getting this sorted out, in my case, trying to migrate from XP to Windows 7 / 64 bit.
It also seems that when you are dealing with DELL H/W, you get further complications. Even now that I've got it working, I can't definitively state what specific step I did that solved it. 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.

I have the following advice:
- 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)
- Once you have a working base (preferably 32 bit), do a Driver compare. 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. Then go back and compare the two lists and see if you can isolate which driver may be causing the error. 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 ;)
- I have always found that there is a timing issue. Turn on the ADVC THEN the PC, I could never get the signal. It always had to be the other way around. ALWAYS.
- Problems may also vary according to the type of firewire card you plugged in. In my case I was using a PCI Via J1394A1 capture card (generic brand)

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.

Good luck, and I hope these notes help someone in bother as well.
southskies is offline   Reply With Quote
Old 07-19-2018, 02:41 PM   #3
Senior Member
Join Date: Oct 2007
Location: USA
Posts: 1,871

Thanks for the posts. They help. To repeat a few key issues, at least for non-DELL, Windows 10 users.

The IEEE-1394 legacy drivers you download are from the Windows 8/8.1 section. That is OK. (Apparently there is no corresponding Windows 10 entry in the MS support pares, or MS wants everyone to forget about IEEE-1394).

The legacy drivers do not automatically fully install for the card, but they are placed in the "C:/Program Files (x86)" folder. You should see a "1394 OHCI Compliant Host Controller (Legacy)" folder containing both x86 (32-bit) and x64 (64-bit) legacy drivers.

When you go into Device Manager to update the driver for your IEEE-1394 card you may have to tell Windows 10 to look in the Program Files (x86) -> 1394 OHCI ... (Legacy) folder for drivers, it may not find them on its own. I selected the x64 Legacy driver for my Win 10 system.
dpalomaki is offline   Reply With Quote
Go Back   Grass Valley Forums > Converters > ADVC


Thread Tools
Display Modes

Similar Threads
Thread Thread Starter Forum Replies Last Post
windows 10 JohnyTDR EDIUS: Compatible Hardware and Accessories 1 02-15-2016 09:44 AM
Canopus ADVC-55 no device connected in Windows 10 x64 pedrok ADVC 1 11-03-2015 04:06 PM
ADVC 100 with OS X Yosemite 10.10.5 moostmartijn ADVC 1 10-08-2015 11:31 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT +1. The time now is 11:03 PM.

Copyright 2014 Belden Inc. All rights reserved.