Page 1 of 2

MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Wed Feb 08, 2017 1:01 pm
by rdubo
1rst of all, gr8 job. This suite is amazing. Now, we're using a very cost efficient automated transcode/transwrap workflow for youtube-like material in our newsroom using this application, and that's so much good.

IDK if this was requested before but I think this forum represents a good chance to do it. Ok, what about to use the MXF OP-ATOM wrapper for, let's say XDCAM-HD or DNx material and also deliver an AAF file for the masterclip handle within the Avid environment. With that, we'll be so much near to the direct ingest into an Avid ISIS Workspace and then into Avid Mediacomposer rise the masterclip for the final checkin to Avid Interplay.

That part could be useful for the enhancement of a lot a expected file based ingest tasks (FTP, SD cards, Smartphones, etc) based on H264 codec material that would take a lot of time to import.

Thank you very much.

Best regards,

Rodrigo.

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Wed Feb 08, 2017 11:23 pm
by admin
Hi Rodrigo, thank you for using FFAStrans and welcome to the forum! :-)

I have limited experience with AAF and I'm trying to understand what you request: Do you mean AAF as an output-wrapper for encoded media?

You also mentioned MXF wrapper for XDCAM-HD an DNxHD: Are you thinking about a different mxf-wrapper than the ones implemented in the already supplied encoders?

-steinar

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Thu Feb 09, 2017 12:35 pm
by taner
Hi Rodrigo,

We also use Avid-products (ISIS, Interplay).
I assume you want to have a similar workflow like e.g. AI Direct Auto Ingest provides but as there is no Avid-Interplay-check-in-option in ffastrans you want to have in addition to the transcoded OP-ATOM-files a (linked) AAF which contains the (combined video and audio) masterclips of the OP-ATOM-files for importing the AAF in MediaComposer and afterwards check-in manually the masterclips to your Interplay-Database

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Thu Feb 16, 2017 11:40 am
by rdubo
That's right... I tried FFAStrans with DNx and yeah it delivers OP-ATOM files to an Avid-like folder structure (Only in that case, for XDCAM FFAStrans uses MXF OP1A), but the only way to handle that material is using Media Tool on Avid Mediacomposer (Creating local databases) in a non-Interplay environment otherwise we need to perform resync on Interplay to force the new files to be indexed to the centralized database system and then catalog the new masterclips... It would be a lot of more easier if the system can create the AAF file too pointing to the new media, in order to carry the matadata that will build the masterclip for the Avid environment and then check in to Interplay.

FFAStrans works incredible anyway. I'm very happy using the app and I have a lot of more ideas of simple workflows for our station thanks to this software (Datamoving, MTS file ingest prep, automated deletions, etc). Only I need to obtain more resources for repurposing hardware and improve performance.

Thank you guys for your input and I hope to have the chance to keep the info cycling with you.

Big hugs,

Rodrigo.

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Tue Feb 21, 2017 3:43 pm
by taner
Hi Rodrigo,

As you I'm also interested in a transcoding which would go hand in hand with interplay.
Today a demo of root6 Content Agent was shown to me.
As far as I have seen Content Agent creates besides the OP-Atom-files a linked AAF (importing it and check-in to the interplay-database works automatically).
It has a lot of more features but nevertheless an expensive system because I would need just a small part of it (the check-in-option).

Taner

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Thu Mar 02, 2017 9:26 am
by Duval
Hi,
I have a simple request , is it possible to have the same Avid structure feature(Atom files, structure ,etc..) in XDCamHD encoder than DNxHD encoder ?
Is there any chance to have a "generic" encoder for other purposes (ex : wav encoding , mp3 ,...) of do i have to do it with a FFmpeg command line ?
Great job i discovered last week,

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Tue Mar 07, 2017 8:24 am
by admin
Hi Duval, thank you for using FFAStans and welcome to the forum! :-)

I'm not sure Avid accepts all kinds of media in their file structure.... I doubt it but correct me if I'm wrong. I know XDCAM-HD is doable but I have not had the time to look into it yet, but I will.

About the AAF/Interplay request: I don't know how much work that would be and how much development it would take. Also, I don't have an Interplay-system to play with...
Being a free tool, FFAStrans is aiming to be as professional broadcast tool as it can be. But there will always be some limitations when it comes to interacting with specific brodcast equipment. Normally it means having the systems to test with and that's expensive. Big corporations can do that but FFAStans is not there...yet. That being said, i WILL take a look at what's feasible it but nothing is promised.

-steinar

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Mon Mar 27, 2017 12:59 pm
by Duval
Hi,
Yes Avid accept OpAtom files with XDCam HD codec. So...
Or a other way is to cut DNxHD encoder in two parts encoding in DNxHD with mxf OP1A wrapper and another "codec" will be just a demux from OP1a to OPAtom .
We will be able to make a workflow with XDCamHD and Avid proflie OPAtom.

Regards

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Mon Mar 27, 2017 1:19 pm
by Duval
HI,
I've got a problem with the Avid DNxHD encoder in version 8. THe result ,eiter the audo profile you choose , is a video file + 32 audio files....

My workflow is basic : watch folder -->> A/V media decoder (intelligent) -->>Avid DNxHD (audio layout 1x2 or 2x1) -->> delivery folder.

Strange isn'it ?

the ver 7 is working well with the same worflow....

Re: MXF OP-ATOM/AAF Delivery for Avid Workflows.

Posted: Mon Mar 27, 2017 2:08 pm
by admin
No, it's not strange cause it's a bug :-(
Expect a patch this evening.

-steinar.