0 false 18 pt 18 pt 0 0 false false false <!-- /* Font Definitions */ @font-face {font-family:Times; panose-1:2 0 5 0 0 0 0 0 0 0; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:Cambria; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Cambria; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p {margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ascii-font-family:Times; mso-fareast-font-family:Cambria; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Times; mso-bidi-font-family:"Times New Roman";} @page Section1 {size:595.0pt 842.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin;}

We are working in a cutting room with three PC based Avid Media Composers, all running v3.1.3.

Our Dell Precision T7400 workstation digitizes HD-SDI 1080p-24 material (from HDCAM) through our Mojo DX to DNxHD 36 MXF media no problem. It's running 32bit Windows XP Pro SP2, has dual Intel Xeon 2.6GHz Quad Core processors, 4GB RAM, Quadro FX 1700 graphics card and is capturing to internal SATA storage. Quicktime version 7.5.5 and everything works great.

However, we have a slightly older Avid Certified HP XW8200 workstation which we want to use for digitizing (because the editor would rather use the Dell all day for cutting). This is setup identically with a clean install of Windows XP Pro SP2 and internal SATA storage but has dual Intel Xeon 2.4GHz processors and only 2GB RAM with a Quadro FX 1400 graphics card. Same version of Quicktime.

So we moved the Mojo DX PCI interface card over to the HP.

But, when attempting to digitize on this HP system, after a few seconds we get a "Capture aborted due to video overrun" error message. We have tried all the different DNxHD resolutions and get the same error message. Also tried to capture to various the different SATA drives in the machine, all the same problem.

We also have a Dell Precision M6300 Avid certified laptop which has a PCMCIA interface card to link to the Mojo DX. This is again running Windows XP Pro SP2 but with an Intel Core 2 Duo 2.2GHz processor and 4GB RAM. This gives us the same error message if we try to use it for digitizing (although admittedly we are trying to capture to USB2 drives but that should be fine in my experience because DNxHD 36 is only 36Mbps). But according to the Mojo DX manual this exact laptop should work fine. Very confusing.

Interestingly both the HP and Dell laptop play back 1080p-24 HD media via the Mojo DX no problem at all DNxHD resolutions, it's just digitizing that causes our error message.

The only difference is that the Dell workstation (which captures no problem) has slightly faster processors and more RAM than the HP XW8200. Is this causing our problem? Is it purely a horsepower issue?

If we buy another 2GB RAM for the HP XW8200 will that solve the problem?

For now we are digitizing on the Dell workstation for a few hours each day, but this is not ideal as the editor would rather be cutting. We are really keen to figure out the problem with the HP XW8200 so we can digitize on that. In theory it should work fine, but at the moment we are stumped.

Had a hunt around the forums but can’t find an exact match for this problem.

Any help or ideas gratefully received.

Gary Scullion

Assistant Editor

Gary,

We all love brain teasers on a Friday.....  read this over a few times just to make sure I had it all. 

We know that the correct HIB card is critical and that you need different ones for different versions of the editor...

Media Composer and Symphony prior to version 4.0, one type of card works in both Macs and PCs while the other type only works in PCs. You can identify which card you have by checking the Avid Part Number on the label attached to the card, or from the pictures on this article:

http://avid.force.com/pkb/LegacySearch?DocId=283511&Hilite=video+overun+and+mojo+DX

But that theory shouldnt be it because you say that the card works in another almost identical PC. right? And you also said another system works and its card was also moved and that did the same thign Right?

What's the Mojo doing?  Power light amber or what?  What are you feeding into the Mojo when capturing?

Me thinks it maybe the bus on the system that is causing this....    I know that only universal PCI cards ( which can use 3.3 volts ) may be installed in the PCI-x slots.  Maybe there is a power issue here.

I do know that with the 8200 there are some funky things regarding the bus...

We have seen errors on 8200 systems that were using both integrated ethernet (ie. for internet or LANShare) & integrated FireWire/1394 (for Adrenaline hardware) together rather than a separate gig-e or FireWire/1394 card to properly segment the bus.
Please take note: you might even see this when only using a low bandwidth data connection such as ethernet traffic created by an internet connection.

Are you connected to the internet on nthis system while attempting to capture?

Are you able to access any event logs that might show the error completely - there is usually a bit more to the mesage that that.

marianna

Hi Marianna

Thanks so much for getting back to me so quickly. We've had a few days off for Easter, now back in the cutting room.

Your tips are interesting but it appears you may think the Mojo DX is not being recognised at all by our HP 8200 or our Dell Laptop. Actually both systems connect with the Mojo DX, all lights are on correctly. We are feeding the Mojo DX and HD-SDI signal from a HDCAM-SR deck running at 24p.

To summarise again...

-- The Dell Precision workstation captures DNxHD36 media perfectly, and plays back fine

-- The HP workstation (using same PCIe interface card) cannot capture (we get video overrun error), but plays back fine

-- The Dell Laptop (using PCMCIA Mojo DX laptop adapter) cannot capture (video overrun again), but plays back fine.

We are not connected to the internet on any machine, and have nothing connected to the firewire ports.

However, we may have some kind of answer which it would be great to get your thoughts on.

In the ReadMe PDF that comes with Avid v4, it mentions specifically that the HP8200 and the Dell Laptop will not capture at DNxHD resolution (but doesn't explain why?) However, the Dell workstation will. That seems to explain our problem. But it would be great to know WHY these systems won't capture.

Any thoughts?

Gary 

Gary,

I think I know why but I feel it is better for the engineer to explain it so I have pinged him for clarification.

stand by

marianna

Gary,

Back again....

I just had a thought......  after checking the Readme -  the 8200 doesn’t have that limitation, but the dual core 8400 does have the limitation but only with MojoDX and DNxHD. 

I also asked Matt and was right :)   The reason for this limitation is the MojoDX uses SW Codecs and needs a Dual Quad Core, and these systems don’t have dual quads.  I can ask Nora in tech pub's to add this to the ReadMe going forward if you think this will help....

marianna

Marianna, that must only apply to the 8200 because I am running a single Quad-Core Z-400 with a DX with no issues at all. Is that because of a different overall system archetecture?  Also used the DX on my Dual Dual-Core 6400 and it ran great. Don't know why it would work fine on a 6400 and not an 8400....

Hi Clement, do You mean that You can successfully capture DNxHD? As much as I could read it's the first time I hear of an eight core requirement for Mojo DX, moreover, it was my understanding that 8 cores are required for Nitris DX, but of course I may just have gotten this wrong, I can't afford the DX boxes for my own studio, and wherever I freelance it's either Adrenaline or Nitris DX, so I'm not that familiar with Mojo DX.