I've experienced and then searched the forums for issues regarding Windows 7, MC5, and Canopus 110. Is it still true that this mixture does not work together? If not, is this an Avid issue (since my PC seems to recognize the Canopus)?

 

Thanks

Steve

I remember seeing several posts in the past with users stating that their 110 no longer works.

vpcmike:

I remember seeing several posts in the past with users stating that their 110 no longer works.

There are plenty of things that doesn´t work with Media Composer and the firewire bug in Windows 7, ( all ) of the Canopus units belongs to those.

I was hoping for SP 1 for W 7 to fix this but that doesn´t seem to be the case from reports posted here so far.

An irritating thing is that it actually worked in an early beta of Windows 7 , a beta WU killed it.

Tomas, a happy Vista and Canopus user

 

mjolnarn:

the firewire bug in Windows 7, ( all ) of the Canopus units belongs to those.

Would installing the legacy FW driver for W7 several here in the forums have suggested help?

I am not sure.

But one should still use the LEGACY driver.

Works with my Mojo.

Cheers,

Radman.

mjolnarn:

vpcmike:

I remember seeing several posts in the past with users stating that their 110 no longer works.

There are plenty of things that doesn´t work with Media Composer and the firewire bug in Windows 7, ( all ) of the Canopus units belongs to those.

I was hoping for SP 1 for W 7 to fix this but that doesn´t seem to be the case from reports posted here so far.

Based on my reading about this issue (I have a Canopus ADVC-100), it appears that this is an MC5 issue, not a Win7 firewire bug issue.  There are reports from people saying that they were able to capture from the Canopus units if they used other software (i.e. something other than MC.)  For example, here is a quote from a thread on this very forum:

"I have Avid MC 5 and I am unable to use the canopus ADVC110 to capture.  The hardware is recognized by Windows 7 64bit and works with Sorenson squeeze and Window Live Movie Maker."

The quote is from this thread:  http://community.avid.com/forums/t/91347.aspx

If other software can capture from the unit, then clearly this is not an issue with Win7, but rather an issue with MC5.  In my case, my ADVC-100 is recognized by windows and everything "appears" normal -- it just doesn't show up in MC5.  I have not yet tried to get it to work with other software, however, so I can't confirm what software it works with.  I can only confirm that it does not work with MC5.

My hope was that MC5.5 would solve this, so I'm wondering if anyone with 5.5 has tried it yet.

Larry

lalittle:

If other software can capture from the unit, then clearly this is not an issue with Win7, but rather an issue with MC5. 

Yet another quote in this thread from a Canopus user goes "Tomas, a happy Vista and Canopus user" using the same logic surely means it cannot be a MC5 or MC 5.5 problem.

 

To the best of my knowledge Avid has always require handshaking protocols appropriate to each devices connection method (FW or Com 1) to work as per specific standards as determined by the connection method. (To stop digital copies being made when there is a fair chance that the person is not entitled to make that digital copy) As you may remember Larry from our early forum days  the Canopus 100 has a very simple button technique for overcoming the original commercial VHS copy protection.

 

A lot of other software does not require any handshaking standards and this IMO explains why programs like Windows movie maker etc etc have always been able capture from almost anything,

AndrewAction:

lalittle:

If other software can capture from the unit, then clearly this is not an issue with Win7, but rather an issue with MC5. 

Yet another quote in this thread from a Canopus user goes "Tomas, a happy Vista and Canopus user" using the same logic surely means it cannot be a MC5 or MC 5.5 problem.

I'm just saying that if it is indeed true that the Canopus units work with Sorenson and/or Windows Live Movie Maker, then it can't be said that these Canopus units don't work with "Windows 7."  The units CAN work in Win7 -- just not with MC5 in Win7.

That said, I'll fully admit that the issue could be the "combination" of Win 7 with MC5, and the actual "fault" could theoretically lie with either one, or a combination of both.  My point is simply that MC5 is the odd man out here since more than one other application works fine with the Canopus units and Win7 -- it's just MC5 that has a problem.  (On this note, I've read that Adobe Premier also works with these units.)

I have no idea whether or not this has something to do with handshake protocols as you said, but the Canopus response to this is that these device use standard protocols, and from the 110 onwards, they're "officially" supported in Windows 7.  Given all the evidence, it seems reasonable to look to MC5 as the "most likely" culprit in this scenario.

Can anyone confirm whether or not this is still an issue with MC5.5 and/or Win7 SP1?

Thanks,

Larry

I just wanted to add "+1" to the Sorenson Squeeze workflow.
I capture through an ADS Tech Pyro A/V Link.  The resulting files can AMA into MC5.

I realize this doesn't address the fundamental question this thread is asking, but it may be a solid workaround for some.