writeavidmxf One great feature of Avid MediaComposer 3.0 or above edit software is the ability to place MXF OP Atom files into its MXF MediaFiles store, and have those files appear in the Media Tool without any need to go through an import process.
With this incantation of FFmbc we can take almost any square-pixel video file and make an IMX30 MXF that broadcast video servers and broadcast edit packages, such as Avid MediaComposer 3.0 or above, can import.
ffmbc -i "input.mov" -vf "[in]scale=702:576,pad=720:608:9:32:black[out]" -r 25 -top 1 -aspect 16:9 -pix_fmt yuv422p -vcodec mpeg2video -minrate 30000k -maxrate 30000k -b 30000k -bufsize 1200000 -rc_init_occupancy 1200000 -flags +ildct+ilme+low_delay -flags2 +ivlc+non_linear_q -qscale 1 -ps 1 -qmin 1 -rc_max_vbv_use 1 -rc_min_vbv_use 1 -dc 10 -intra -acodec pcm_s16le -ar 48000 -ac 2 -f mxf_d10 -y "output.mxf"
Versions of ffmbc from 0.6 onwards, including the current release candidates have D10 targets built in, so the command line to invoke an IMX30 conversion would simply be
ffmbc -i inputfile -target imx30 output.mxf|mov
Similarly for imx50 you would use '-target imx50'
Remember, if your source is interlaced use the extra interlaced scaling parameter of FFmbc, as in:
The problem is that the import process into the Avid MediaComposer is a foreground blocking process that stops editors from being able to edit.
If we strip that MXF into separate M2V and WAV files then we can use writeavidmxf from the BBC OpenSource INGEX project to create Avid compatible OP Atom MXF files.
ffmpeg -i output.mxf -an -vcodec copy -y output.m2v ffmpeg -i output.mxf -vn -acodec pcm_s16le -y output.wav writeavidmxf --prefix "A_PREFIX" --IMX30 output.m2v --wavpcm output.wav
Then copy the resultant set of MXF OP Atom files into a media drive, such as:
(Avid always puts its files into <Drive:>\Avid MediaFiles\MXF\1 but it will add any files in <Drive:>\Avid MediaFiles\MXF\ into the media database)
writeavidmxf is mentioned on: Video | FFmbc 0.5