Hi All,
I've been trying to find a solution to this all day, so I thought I'd put it out there and see what other people think.
Background is 2 avids, Rourke SAN storage with Tiger Technologies MetaLAN.
One Avid is xw8200 with MC5 Adrenaline the other (having issues with) is a z800 with MC5.5 Adrenaline HD.
Everything was working fine till this yesterday and this morning the the new avid would not capture at DV50 (from a DVCPRO50 VTR via SDI) and it would freeze for a second and say "Signal Present but not captured".
At any of the DV25 codecs its fine, still outputs DV50 and DNx120 to the monitors and VTRS, so I check the Databases, scaled them down from 5,000 files to 3,000 files per MXF directory, move the software back to MC5 recomended Nvidia drivers, Quicktime and even back to MC5.
Made both avids rescan there Databases, the xw8200 is fine, but the z800 is telling me there are damaged mxf files and to quarntine them or ignore them... and still won't capture any higher than DV25. Tried an internal array instead of the SAN too, but no luck.
Any thoughts?
I'd try the normal stuff.
New fresh user. New project. Trash MCstate etc.
Open the console while attemptingto capture and see if any extra infos shown there.
Broadcast & Post Production Consultant / Trainer Avid Certified Instructor VET (Retired Early 2022)
Still offering training and support for: QC/QAR Training - Understanding Digital Media - Advanced Files * Compression - Avid Ingest - PSE fixing courses and more.
Mainly delivered remotely via zoom but onsite possible.
T 07581 201248 | E [email protected]
We had this message today. We've found it was the disk drive. We swapt capture target to Unity and it's fine. Hope this helps...
Thanks for your help!
Trashing the MCsate fixed the issue. Hopefully it does not arise again.
Nope take it back again....
All old ready created projects work fine, but new projects no matter what account will not ingest any higher than DV25.
But if I make the project on the other avid and open it in the avid with the issue it is fine....
There are actually 5 settings that come into play. See this previous post.
"There are few technological barriers. You can fix almost anything if you throw enough money at it."*******************************Randall L. Rike, ACI, ACSR Mac*Win*Unity*ISIS*DSSystems Engineer @ BET Networks [a Viacom company](wwld)
Tried the other thread and it didn't help....
Any other ideas?
Hi
Same problems here... with 5.5.1 all new projects will create this error. but removing the HD DNxcel board fix the issue... hein???
So back to 5.0.3.8 and it work well.
System: Z400 rev 1 running win7 64 bit, 1394 legacy drivers, MC Adrenaline 5.0.3.8 with DNXcel board.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller