mirror of
https://github.com/shumaiOne/shumai.git
synced 2026-11-22 18:38:24 +00:00
35 lines
1.8 KiB
Plaintext
35 lines
1.8 KiB
Plaintext
---
|
|
title: Media Transcoding Settings
|
|
description: Configure video transcode strategies and preview proxy generation.
|
|
---
|
|
|
|
High-resolution camera formats and raw media files cannot be rendered natively in web browsers. Shumai transcodes these assets into web-friendly streaming formats in the background.
|
|
|
|
---
|
|
|
|
## Video Transcode Strategies
|
|
|
|
Team Owners can select how the transcoding engine handles uploaded files:
|
|
|
|
### 1. Best Match (`best_match`)
|
|
|
|
- **Behavior**: Shumai checks the parameters of the uploaded file.
|
|
- **Skip Transcoding**: If the file is already in a web-compatible format that browser engines can play directly (like standard MP4s), transcoding is skipped.
|
|
- **Transcode**: If the file format is incompatible, it is transcoded. This is the recommended option as it saves processing time and storage space.
|
|
|
|
### 2. Transcode All (`all`)
|
|
|
|
- **Behavior**: Every single uploaded video is sent through the transcoding pipeline.
|
|
- **Output**: Converts the file into a standardized, web-optimized MP4 profile. This ensures consistent streaming performance and compatibility across all client devices and browsers, regardless of the source.
|
|
|
|

|
|
_Placeholder: Web UI Settings screen displaying the Media Processing tab with the strategy toggle selectors._
|
|
|
|
---
|
|
|
|
## Processing Architecture
|
|
|
|
Transcoding is resource-intensive. Depending on your scaling needs, your administrator can run the transcode engine on the main server (Local Single-Server mode) or delegate tasks to specialized transcoding worker machines (Distributed High-Scale mode).
|
|
|
|
_Note: In all modes, the processing machine must have the standard system media utilities (`ffmpeg` and `ffprobe`) installed._
|