Announcement

Collapse
No announcement yet.

ADVC and Windows 10

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • KS80537
    replied
    My ADVC300 was showing up in Windows 10 as an unknown device represented by a number. With the 1394 driver you recommended, it now shows as AV/C Tape Recorder/Player. More importantly, Canopus Picture Controller will now run. THANK YOU.

    Leave a comment:


  • dpalomaki
    replied
    The Win 8.0/8.1 driver works in Win 10. Try
    https://www.microsoft.com/en-us/down....aspx?id=44218

    Leave a comment:


  • Videoman
    replied
    Canopus advc 110 windows 10.

    I am having issues my ADVC 110 is not working with windows 10. I can't find the 1394(legacy driver) the link is broken on the Microsoft website. I have tried everything.
    Should I downgrade to windows 7?

    Leave a comment:


  • volswagn
    replied
    Originally posted by Dancer View Post
    After spending more than 2 hours with Driver Support and trying several options, while it's clear the Canopus ADVC-55 is working properly and installed properly in the que, Edius sees it in Settings, but it was still unable to access the Capture function.

    Any thoughts would be appreciated.
    I don't know if it's just a coincidence, but I have been capturing things from VHS and LaserDisc very happily using my ADVC-110 for several years now after finding this forum and using the recommended legacy 1394 drivers in Windows 10.

    This week, the capture stopped working. My ADVC seems to be grabbing the video, and all my software sees the device as "online," and yet the actual capture window with video will no longer appear. I have completely uninstalled (including delete) the 1394 driver and have tried reinstalling after a reboot, but it's still not working. Extremely frustrating.

    My windows update history shows no updates in the last week or two.

    Very frustrating. If I discover anything, I'll report here. :(

    Leave a comment:


  • BernH
    replied
    Unfortunately I have no further input, as I am not on Win10 nor do I have an ADVC55 to test with.

    I am on Win7 and do have an ADVC110, but never a problem using it the hand full of times I needed to.
    Last edited by BernH; 08-08-2019, 04:04 PM.

    Leave a comment:


  • Dancer
    replied
    After spending more than 2 hours with Driver Support and trying several options, while it's clear the Canopus ADVC-55 is working properly and installed properly in the que, Edius sees it in Settings, but it was still unable to access the Capture function.

    Any thoughts would be appreciated.

    Leave a comment:


  • Dancer
    replied
    Continued ADVC issue

    This is quite strange. After making yesterday's adjustments and inputting nearly 4 hours of video elements, I shut down Edius after saving the project last evening.
    This morning, I opened Edius with the goal of adding the rest of the footage only to discover that the CAPTURE was not engaging.
    This is as it was yesterday morning.
    How is it possible that it works until it doesn't?
    I have a call in to Driver Support, but they won't respond until tomorrow.
    Stay tuned.

    Leave a comment:


  • Dancer
    replied
    ADVC to Windows 10

    Tried several steps:

    1) Exited Edius
    2) Opened Edius in New Project
    3) Uninstalled previous ADVC settings
    4) Installed new settings (which were actually identical) using a different icon
    (who knew)
    5) Unplugged ADHC and re-plugged it in
    6) Capture -is fully restored

    Thanks to all who offered suggestions.

    Leave a comment:


  • Dancer
    replied
    Still a problem

    Driver support updated NVIDIA again this morning, but it did not correct the problem.

    Leave a comment:


  • BernH
    replied
    Originally posted by Dancer View Post
    I manually updated the drivers.

    I am on Win 10.

    Agreed - Edius saw it before and nothing has changed re: connections. I can hear a handshake when I unplug and replug in the firewire.

    Nothing has changed in the device manager for the ADVC-55

    Edius sees the device in the protocol.

    The ADVC is working properly.
    By the sounds of that, you need to manually roll the drivers back to the version that worked

    Leave a comment:


  • Dancer
    replied
    I manually updated the drivers.

    I am on Win 10.

    Agreed - Edius saw it before and nothing has changed re: connections. I can hear a handshake when I unplug and replug in the firewire.

    Nothing has changed in the device manager for the ADVC-55

    Edius sees the device in the protocol.

    The ADVC is working properly.

    Leave a comment:


  • BernH
    replied
    Originally posted by Dancer View Post
    I made a capture device in Edius for the ADVC and established parameters for it initially. That capture device still exists and I used it to attempt to input new A/V.

    What I'm saying is that it worked last week and is not working today. That makes no sense to me.
    Assuming you have not disabled your windows updates, has Windows updated itself or have you manually updated any software or drivers?

    Is this on the Win7 system in your signature or a Win10 system? I ask because Win10 can forcibly update drivers, which can often "break" things.

    Edius just uses the firewire connection to access the ADVC boxes, so if the box is working and video is getting in to the firewire port, Edius should be able to see it.

    Can you check to see if video is getting in by using something else that can capture from a firewire port, such as windows movie maker?

    If you see video there, I'd suggest creating a new device preset in Edius, and if that doesn't work a new Edius user profile.

    If you don't see video in movie maker, make sure the ADVC is detected by windows. Try re-installing the windows firewire drivers.

    Try the ADVC on a different computer to see if the problem follows the ADVC, in which case the problem is likely the ADVC box itself.

    Leave a comment:


  • Thor
    replied
    Did you start playing the media? Some of my analog decks aren't "seen" by Edius until I start playing the media in a deck. The capture icon is grayed-out, but turns white when I start playing the tape.

    Leave a comment:


  • Dancer
    replied
    Originally posted by BernH View Post
    You have to make a capture device preset in edius.

    Basic guidelines for setting this up can be found in the manual
    https://wwwapps.grassvalley.com/manu...html#gsc.tab=0

    Also Edius may require the use of the windows legacy firewire driver.
    I made a capture device in Edius for the ADVC and established parameters for it initially. That capture device still exists and I used it to attempt to input new A/V.

    What I'm saying is that it worked last week and is not working today. That makes no sense to me.

    Leave a comment:


  • BernH
    replied
    Originally posted by Dancer View Post
    After applying all the driver updates for Windows 10 as well as some for G-Force, inputing video worked well last week.
    I have a new project that requires video coming from a different source (didgitalbetacam) thru ADVC. While ADVC has a green light Edius does not show the video thru the Capture windown even though the ADVC is selected. I can monitor playback on a different monitor, but cannot get Edius to see this feed from ADVC from either the original VHS playback or this digitalbeta.
    Thoughts?
    You have to make a capture device preset in edius.

    Basic guidelines for setting this up can be found in the manual
    https://wwwapps.grassvalley.com/manu...html#gsc.tab=0

    Also Edius may require the use of the windows legacy firewire driver.

    Leave a comment:

Working...
X