[Shelley Moore]

Thanks, Ian. I finally found it the other night. Finally. Sony sure doesn’t make using their products very easy sometimes.

[Shelley Moore]

oops, “naming”, not name.

[Shelley Moore]

Thanks Ian… I do realize that it is a quirk with FCPX, but are you telling me you’ve figured out a shortcut that would negate name each individual mono track? Thanks…

[Shelley Moore]

I’ve spent hours, no days, trying to get a finished project back from FCPX to the desktop as an MXF file using Content Browser Exporter. I use Content Browser to import the MXF files from my Sony XDCAM 700, which are then wrapped or converted or whatever to MOV files to edit with. But it has been impossible to export the finished project back to the desktop as an MXF.

However, I talked at length to a fellow at Sony about six weeks ago. He, through much trial and error, finally figured out how to do it. But the process is so time-consuming there is no way it is usable for deadlines. He figured out that you have to assign a “role” to each of the 8 mono tracks of audio in order for Content Browser Exporter to accept it. It is a silly and finicky and time-consuming process even if you have just one audio track source. But if you’ve got more than one source, EACH one has to be expanded to its 8 mono tracks, then EACH one of those has to be assigned a “role” (which is what FCPX is calling them now.) Not even remotely usable. Unless there is a fix to that issue between Content Browser Exporter and FCPX, one that allows you to simply ‘share’ (export) the finished project with all video and audio tracks as is back to the desktop as an MXF, then it is unusable.