Simple transcoding overview
When you add a source file to Compressor and apply output instructions (all done in Current view), you create a transcoding job. You can submit a single job for transcoding, or add more source files (and output instructions), then submit a batch of jobs for transcoding.
Each job in a batch has several parts:
Source file: The media file that you want to transcode.
Setting: The transcoding instructions that specify how the file will be processed. Compressor provides a variety of built-in settings that you can use to output files in common media formats. Additionally, Compressor provides a number of preconfigured destinations—one or more settings combined with an automated job action that’s performed after transcoding. For example, if you use the Publish to Facebook destination to transcode a source file, Compressor outputs a high-quality QuickTime movie file, then applies the destination’s job action to upload the transcoded file to your Facebook account.
Location: The place on your computer or a connected device where the transcoded file will be saved. You can use one of the built-in locations, or specify a new location.
Filename: The title of the transcoded file. You can use the default filename (the name of the source file) or type a custom filename.
Job action: Optionally, you can add a post-transcoding action to a job, such as burning a DVD, uploading to Vimeo or YouTube, and so on. Each of the built-in destinations already contains a job action.
In the example below, two jobs make up the batch:
The first job uses the built-in Create DVD destination to output a Dolby Digital audio file and an MPEG-2 video file. The transcoded files will be saved to the source folder (the folder where the source media is stored), and after the files are transcoded, they’ll be burned to a DVD (using the Create DVD job action).
The second job uses two built-in settings (Small and HD 720p) to create a small QuickTime file and a high-definition (HD) QuickTime file. The transcoded files will be saved to the desktop. Because there’s no job action, the user will have to manually move or otherwise distribute each file.