Application entry point

To perform a transcode application code, whether the worker or desktop, calls MFFactory.exportMovie(), but how this is initiated depends on the application:

· In the desktop ExportMovieDialog creates an ExportMovieJob, which is run by the JobRunner so it displays a progress dialog and can be interrupted (there is also a RebuildPreviewJob used by the Build Proxy Movies command).

· In the worker a Build Path-based Proxy or Export Standalone Movie processing step calls ClipProcessor.performConversion() to do the transcode.

MFFactory.exportMovie() calls MFDelegate.getExporter(), which now always returns SegmentExporter (the “Advanced Exporter”), then calls either buildPreview() or exportMovie(), depending on how the operation was initiated. The distinction between previews and exported movies is historical and can largely be ignored (it stems from when we had tape-based previews, where the movie for a clip could be built up from bits of different files, rather than file-based proxies that we use exclusively now).

For all practical purposes the top level entry point for all transcoding operations is therefore SegmentExporter.doExport().