- December 16, 2015 at 3:07 pm
I have recently had to export XDCAM MXF op-1a for a tv program. Just got note that the program has been rejected because of many video errors that were like tape clogs.
I am thinking I should now export DNxHD and take these files to a major post production house and get them to deal with the exporting.
Has anyone had problems exporting from avid to MXF OP-1a and has anyone any ideas how I can get these episodes to the broadcaster asap without errors?
- December 16, 2015 at 4:42 pm
What codec are you using when exporting? Without something more descriptive than “tape clogs” it is hard to tell if it is a render error, an mpeg encode error (depending on codec), etc. I would suggest trying a video mixdown to the delivery codec required, then try exporting again.
- December 16, 2015 at 11:09 pm
I did do video mixdowns with the resolution XDCAM HD 50Mbits MXF then exported to XDCAM MXF Op-1a. I had many crashes because of USB 3 conflicts, this is what Avid support said. I did get it to output to my c drive and thought everything was ok but recieved a rejection from channel 7 in australia.
All i was told that the files had severe vision faults that look like severe head clogs. And a few other severe vision faults.
Is this a common problem?
I read coming out of Avid in DNxHD is like coming out raw from the time line, so I hope these faults arent included in these files.
- December 16, 2015 at 11:12 pm
What does it look like when you AMA link your export back into the project? Load into the source monitor, gang it to your original timeline and see if you can see what they are claiming.
- December 17, 2015 at 1:31 pm
- December 17, 2015 at 1:37 pm
- December 17, 2015 at 1:38 pm
Is there a mix of interlace and progressive material?
- December 17, 2015 at 1:42 pm
No it was all shot on the same camera as progressive
- December 17, 2015 at 2:03 pm
Hmmm…. Seems like an export bug in the MXF OpAtom 1a file. Do you have Adobe Media Encoder by chance?
- December 17, 2015 at 2:14 pm
I’m even getting the same errors with a DNxHD output
Log in to reply.