Chris's F2F Notes
File submission
- Select (or use default?) preset/settings
- Generate MediaObject ID
- Save MediaObject
Move file to uploads directory (collection/uploads?) master_file/create
Characterize
Process (transcode)
Create job
Submit
- Input file (URL?)
- Output destination (URL?)
- Encoding options
Return
- Job ID
Background / Encoder
Poll (status?)
Submit
- Job ID
Return
- State
- %
- Current operations?
Finished (Details)
Submit
- Job ID
Return
- Status
- %
- URL
- Technical metadata
Failed (Details)
Submit
- Job ID
Return
- Status
- %
- Error messages
- Current operations?
Depend on encoder/encoder shim to transfer derivatives to streaming server/location
Avalon
Jobs
Create
Details
List by Status
Zencoder
Zencoder uses a 'Job' to transcode media. The Job specifies all settings in a single package.
API versioned by version number, e.g. 'v2'
Each Job, Input and Output is assigned an (independent) ID
Job states include pending, waiting, processing, finished, failed, and cancelled.
Input states include pending, waiting, processing, finished, failed, and cancelled.
Output states include waiting, queued, assigning, processing, finished, failed, cancelled and no input.
Jobs
Create
List
Details
Resubmit
Cancel
Finish (a Live Job)
Job Progress
Notifications
Register for a notification when a job is completed via HTTP POST, email, etc.
Returns:
- Job ID
- Status: 'finished', 'failed', 'cancelled'
- Output label (if applicable)
Amazon Elastic Encoder
Amazon uses a 'Pipeline' (queue) to transcode a 'Job' according to the settings specified in a 'Preset'.
API versioned by date, e.g. '2012-09-25'
The value of Job:Status is one of the following: Submitted, Progressing, Complete, Canceled, or Error.
Jobs
Create
List by Pipeline
List by Status
Read
Cancel
Notifications
Register for a notification when a Job changes state via HTTP, email, etc.
Returns:
- State: 'PROGRESSING', 'COMPLETED', 'WARNING', 'ERROR'
- Error code
- Message
- Version (API)
- Job ID
- Pipeline ID
- Input