mdsh.com/wiki

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 nead to go through an import process.

With this incantation 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.

ffmpeg -i "input.mov"
-r 25 -pix_fmt yuv422p
-s 704x576 -padtop 32 -padleft 8 -padright 8
-aspect 16:9
-vcodec mpeg2video
-minrate 30000k -maxrate 30000k -b 30000k
-intra -top 1
-flags +ildct+low_delay
-flags2 +ivlc+non_linear_q
-dc 10 -ps 1 -qmin 1 -qmax 3
-bufsize 1200000 -rc_init_occupancy 1200000
-rc_buf_aggressivity 0.25
-acodec pcm_s16le -ar 48000 -ac 2
-f mxf_d10 -y "output.mxf"

The problem is that the import process is a forground blocking process that stops editors from being able to edit.

If we strip that MXF into seperate 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:
D:\Avid MediaFiles\MXF\2

(Avid always puts its files into <Drive:>\Avid MediaFiles\MXF\1 but it will add any files in <Drive:>\Avid MediaFiles\MXF\[123456789] into the media database)

See also:
http://ingex.sourceforge.net/libMXF/