Just installed my new MC4.0.2 (upgrade from XP) in my new computer and everything seems to be working fine except Capture.  I'm getting the dreaded "No Deck" no matter what I try.

I have the correct Pyro 1394a card (PVC-316) installed and it does work - Windows (Vista 64bit) Video will import video and control my deck.  But MC doesn't seem to recognize it.

I'm using a JVC BR-DV3000 that still works perfectly on my old computer and system.

I'm using Firewire on OHCI and I've tried both BR-DV3000U (my deck is not a U model) and generic.  Neither works.

The project is set to 30i and I'm trying to digitize SD miniDV.

If I click on check decks it doesn't help.  If I click on video or an audio track I get "no signal input present"

I've shut down the computer, made sure the recorder was on, restarted and entered Avid.  No help.  I've used Avid for years and thought I knew all the tricks - it's not like this hasn't happened occasionally before, but this time I can't get it to work.  I have to believe there is a setting or a fix that I don't know about, perhaps something in MC since I was an XpressPro guy until now.

Any suggestions?

http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=238603&Hilite=dvbuffers

Best of luck, JR

Thanks JR

I tried this:

1. Go to Program Files\Common Files\Avid.

2. Right click Dvbuffers.ax.

3. Select Open.

4. Choose to select the program from a list and click OK.

5. Browse to windows/system32.

6. Select regsvr32.exe.

But when I browse in step five nothing resembling windows/system32 shows up.

Prabably not showing up because you are using Vista 64 bit.  Only thing I can suggest is to delete your Deck Congfiguration settings and then reset and reapply them...then try again to capture.

I also tried to dowload the file given and my system told me Avid didn't support that file - it is probably too old for my system.  Can anyone help me find windows/system32?

Yeah, tried that any number of times with no luck.  Guess I'll have to make my one call to the techs and see if they have an answer.

http://community.avid.com/forums/p/62344/362649.aspx#362649

http://community.avid.com/search/SearchResults.aspx?q=no+signal+input+present&s=49

Good luck.

Checked some other sites and tried another suggestion - type in regsvr32 DVBuffers.ax and run it.  It told me that this file was not compatible with a 64bit system.  I suspect 64bit Vista is the problem, but since it's certified by Avid, there must be a way around this.  Can anyone help?

I'm down to my last try.  I think there must be a different file for a 64bit system.  (I've searched everywhere, but all information on my problem is at least a year old and references the fix described in the current readme.)  If anyone knows what the new file is or where I can download it to update my DVBuffers I'd be eternally greatful.  I've got 3500 bucks worth of brand new computer sitting here doing nothing - it sees the DV deck, Avid doesn't.  At least my dependable old XpressPro on my five-year-old computer is still chugging along.  If Avid is going to approve Vista 64Bit, at least they could provide the proper documentation in their readme.  Their fix is not applicable to 64 bit as far as I can see.

I'd send Marianna a note. I remember somewhere her saying they got a mojo working on a vista 64 machine. I'm sure they know which firewire card they used. I'm having trouble finding a fw card with 64 bit drivers myself for my new system.

taylormade, I don't get it: are You having troble with Mojo or plain firewire? FWIW I run vista 64 and drive a Mojo and am able to capture via firewire too, I'm on 3.5 however.

I don't get it either, Luca.  This is just plain old firewire - no Mojo.  I've never had this problem with any other Avid system.  The deck works fine on my other computer with Xpress Pro, I'm even using the same firewire cable.  As I said, my new computer recognizes the deck and I can capture in Windows Movie Maker, but MC4 can't find the deck.

This could be one of my old favs, Luca and myself are using Gigabyte boards with FW TI chipsets, works very well.

Your own board has a Via chipset for the fw, they are known not always to work well with editing apps.

Although you have bought yourself another fw card, I would also recommend to disable your onboard Via fw connection from Bios and see if that helps. 

Too late tonight, but I'll give it a try tomorrow and let you know how it works out.

Have a good nights sleep, I bet a couple of pennies that the via chipset is your prob, hopefully disabling it from Bios will fix your prob, you might have to remove the drivers for it, maybe the drivers should be uninstalled from windows before shutting down the sys and disabling it from Bios.