Send-To-Playback Workflow: Long GOP Sequences
The following illustration shows a typical send-to-playback workflow for a Long GOP sequence (for example, XDCAM-HD or AVC LongG).
1. The user starts an STP process in MediaCentral UX.
2. The MediaCentral server, through the avid-central-service, checks media status through Media Indexer.
3. The avid-central-service creates an STP job and sends it to the MediaCentral Distribution Service (MCDS). MCDS performs an analysis of the sequence to determine if it needs mixdown or Long GOP encoding.
- If an audio mixdown or video mixdown is needed, the MCDS will send a Transcode mixdown job to the Production Services Engine, which sends the job to the Interplay Transcode provider.
- If no transcoding is required, the MCDS will send an STP Encode job to the Production Services Engine, which sends the job to the STP Encode provider.
4. The MCDS uses ASF and Media Indexer to dynamically relink the sequence to media in the target resolution.
5. The MCDS sends a request for any required mixdowns to the Production Services Engine, which then sends the jobs to the Interplay Transcode provider.
After sending the Transcode jobs, the MCDS periodically checks the Production Services Engine to determine when to send the encoding job to the STP Encode provider.
6. Interplay Transcode performs the required jobs and saves the media on the Avid shared-storage system.
7. When the transcode jobs are complete, MCDS sends an encoding job to the STP Encode provider.
8. STP Encode creates Long GOP OP1a media, stores it on the Avid shared-storage system, and initiates a transfer to the playout server, through Interplay Transfer.
9. Interplay Transfer transfers the sequence to the playback server.
Related Topics
