MPR - Media Processor

Components

• Reverse Proxy (nginx)
• Application Layer (Django, FastAPI, UI)
• Worker Layer (Celery, Lambda)
• Data Layer (PostgreSQL, Redis, SQS)
• Storage (Local FS, S3)

Entities

• MediaAsset - Video/audio files with metadata
• TranscodePreset - Encoding configurations
• TranscodeJob - Processing queue items

Job States

• PENDING - Waiting in queue
• PROCESSING - Worker executing
• COMPLETED - Success
• FAILED - Error occurred
• CANCELLED - User cancelled

Input / Output Separation

• MEDIA_IN - Source media files to process
• MEDIA_OUT - Transcoded/trimmed output files

Why Relative Paths?

• Portability: Same database works locally and in cloud
• Flexibility: Easy to switch between storage backends
• Simplicity: No need to update paths when migrating

Local Development

MEDIA_IN=/app/media/in
MEDIA_OUT=/app/media/out

/app/media/
├── in/                    # Source files
│   ├── video1.mp4
│   └── subfolder/video3.mp4
└── out/                   # Transcoded output
    └── video1_h264.mp4

AWS/Cloud Deployment

MEDIA_IN=s3://source-bucket/media/
MEDIA_OUT=s3://output-bucket/transcoded/
MEDIA_BASE_URL=https://source-bucket.s3.amazonaws.com/media/

Database paths remain unchanged (already relative). Just upload files to S3 and update environment variables.

API Endpoints

• POST /api/assets/scan - Recursively scans MEDIA_IN and registers video/audio files
• POST /api/jobs/ - Creates transcoding job with source asset, preset, and optional trim times

Supported File Types:

Video: mp4, mkv, avi, mov, webm, flv, wmv, m4v
Audio: mp3, wav, flac, aac, ogg, m4a