Here's one for the technical boffins amongst us,
I have created an automated digital file delivery workflow for content
entering our building. We are experiencing some issues as we transition
our established SD workflow to HD.
The primary challenge is maintaining captioning data through the desired
workflow (cutting in Avid via Interplay).
In SD, I receive a custom OP1a MXF which is split into an OP-ATOM
essence and checked into Interplay via XFConverter. Captions are
maintained because we are ensuring the VBI is present. Files are
accessed via Media Composer through ISIS/Interplay.
In HD, we receive a custom MXF which can either be split into OP-ATOM
essence via XF or simply dragged into a Media Composer bin. Captions
are inserted as 708 with a 608 flag OR as 608 with a 708 flag (depending
on what is received from the customer), following the Avid import all
captions are lost.
Does Media Composer have any ability to decipher caption data on Import
that's embedded in the OP1a MXF file? Should it create a Data track as
is does during a Nitris or HD Multi Speed capture? Data track capture is
enabled in Interplay...
We notice that when Nitris hardware/Media Composer is used to capture HD
content, it appears to write the VANC caption data to a data track
(D1.mxf) but when we pull the Data MXF file apart there appears to be an
Avid proprietary encode used, it's not in a 608 or 708 standard.
Has anyone been able to get the Media Composer to work in this fashion
with a similar digital path like our file based workflow?
Tough one first thing Monday morning, but this is how I ended Friday and
not with much success!
Cheers
Pete
[Non-text portions of this message have been removed]
No comments:
Post a Comment