Nothings been upgraded (I wish). the workstation was wiped and reloaded about a month ago but I can't see that effecting the firmware. We made sure to follow all of avid's software specs (quicktime, nvidia, etc) for this particual workstation.

Hello, We're running Symphony nitris on an xw8200 turnkey system and have been getting this error every time we try to do our first output of the day: Exception: NitrisBase: Err: 0 | -991167 | apk_interruptobject.cpp | 853 | Error Code: kLPKerr_HEOL_VEOF_HardwareMismatchError Msg: "NitrisBase:RLE2:UnivMix input E sync error" This was taken

[quote user="BobbyMurcerFan"]Render tab of Media Creation settings,[/quote] Got it. So if i'm working offline in 20:1 MXF, and making a quicktime ref, the most efficient settings would also be 20:1, correct? If thats the case, selecting the "same as source" selection should keep me at the most efficient settings?

[quote user="camoscato"]the red line could be marking the portion of the effect that is unrendered.[/quote] Thats definitely it. It's not on V1 and when I change the render range in the timeline fast menu, the lines go away. Rendering in/out around the lines made my export go smooth as silk. Thanks for the help! One more question: Does

The effects manual says that if Avid dropped frames on playback (in my case, failed export to QT Reference) it will display red lines on the TC track. Well I've had a few situations where the red line appears on a portion of one of the video tracks. What does this mean? Same thing? Different?

[quote user="Marianna"]low bandwidth data connections etc... or a drive related issues -[/quote] Faulty ATTO card was the issue. Swapped it and haven't had a so much as a hiccup. Thanks for the lead! -Dan

Any sequence I play will eventually crash, usually within 10 minutes. I get the error "Exception: FILE_OTHER, Filename: G:\OMFI MediaFiles\Edit7\xxxxxxx.mxf". If I hit OK and try to play again, I immediately get a similar message, except with an aif extension. It will do this until I reboot the computer. Here is what my console spits out during

Two days ago one of our HP xw8200 got a blue screen during startup. Unfortunately I cant remember the exact error but it had something to do with a phisical memory dump. There was no way to start windows (safe mode, etc.). This morning I turned it on, and it started with no problem. I dove into the Event Viewer to get some detail. Here what I found