I just upgraded from Xpress Pro where the Mojo was working great.  So far it does not work with MC 3.  Did I miss something?  Is it not compatible with MC 3?

I get all kinds of strange behavior.  Right now it shows a 1/4 screen of what used to be the startup screen on the client monitor.  Although MC 3 shows the device used as DNA the Mojo does not respond.

Any ideas would be very welcome.

 my mojo works great with mc 3.0 what happins if you unplug the mojo from the computer  pull the power then repower the mojo with out the fw in the computer?

I've done that several times.  By itself the Mojo shows the startup screen just fine.  It's just when MC starts up it goes crazy.

When you installed MC3 did yours apply a firmware upgrade?  Mine did not and I find that strange but I'm not sure if it was supposed to.

 I just discovered that it captures video (component) just fine.  It's just output that seems to be not working.  In the MC "Special" menu I notice the "Using DNA Client Monitor" is ghosted.  Is that supposed to be that way?

 I've run the DNA diagnostics which came out fine.  I tried moving the Mojo to another suite and it works fine.

I tried uninstalling the Mojo driver again and re-installing following the procedure that came with it.

Still no output.

I'd have to say the the upgrade from Xpress Pro to MC 3 has been a rather hellish experience starting with the ridiculous dongle upgrade scheme.  I'm on my 3rd day of wasted time and seriously regret upgrading.

The Mojo is just the icing on the cake.

The Mojo and Mojo SDI definately are compatitable with MC3.  (I interchange both regularly without problem) Can you confirm that MC is connected to the Mojo (there should be a "DNA" button highlighted in green on the Timeline just like in Xpress Pro.)

If so, are you playing back SD or HD?  The neither Mojo will playback or record HD.

In the project Window, are the project settings set to SD?  Is it possible to have the SD footage in a HD timeline (and vice versa), however, this would prevent the Mojo from out putting video.

I hope this information is helpful.  If the Mojo can digitize, then I suspect this is a setting issue.

Good luck.

 Thanks for the help but yes, the DNA is displayed and I've switched back and forth several times.  It is an SD (NTSC 30i) project with SD footage.  I captured clips (works fine) and then tried to play them back in the preview window and on the timeline.  Just get black now.

I've checked the output tools and it is set to component (which I need for my monitor).  I can see the startup screen on the mojo when the system is started so the cabling is OK I think.

I even tried moving another Mojo from a Xpress suite and it does the same thing.  I also uninstalled everything including the Mojo driver and did a clean install but to no avail.

Uninstalled everything again.

Just for fun I hunted down all references to Flamethrower.sys and deleted them manually.

Re-installed AGAIN and still no go.   WTF!

Is NOBODY else having any issues with this or is it just lucky me?

 I checked the console, and there is a stack of these messages.

Error/Status [0x1003]Error/Status Reporting: Your hardware has detected a serious error.
Please quit the application and power cycle the hardware.
[Error: DMPort Error]
Error/Status [0x80001013]Error/Status Reporting: Hardware detected a host vsync error

I removed the sync input just to test but no help.  I don't think that's what it is refering to but I don't know what it IS refering too.

 Well, I think I finally found the problem.  Just to test I changed my firewire connection from a dedicated Avid approved TI 1394 card to the onboard 1394 controller.

It worked!

The onboard controler did not work well with Xpress Pro so I added the dedicated card but it seems to now work with MC and the added card no longer works!  Go figure!

 Hi

If your dedicated card is a PCIe card, there is a small known problem with some PCIe firewire card, as you can read about here

http://community.avid.com/forums/t/59545.aspx?PageIndex=2

It was fixed and it will be part on the next version

Thanks for the info!  That is likely my problem.