Medusa Panel › Stream › Add Stream
Medusa can offload decoding and encoding to a GPU, so one server carries far more channels at a far lower CPU cost. You turn it on per stream (or once in a reusable profile) by choosing a hardware encoder and deciding how much of the pipeline runs on the GPU.
bin/web --nvidia-driver-supported lists the driver versions that match the bundled FFmpeg.Supported backends
- Intel Quick Sync (QSV) — integrated and Arc GPUs. Encoders:
h264_qsv,hevc_qsv. - NVIDIA NVENC / NVDEC — GeForce, Quadro and RTX. Encoders:
h264_nvenc,hevc_nvenc, andav1_nvencon AV1-capable cards. - AMD (VAAPI) — Radeon GPUs. Encoders:
h264_vaapi,hevc_vaapi.
/dev/dri/renderD128).Choose the encoder and the acceleration
Open Medusa Panel › Stream › Add Stream and set the video codec to a hardware encoder (for example h264_nvenc or h264_vaapi). Then set:
- Hardware Acceleration Method —
Full,PartialorEncoding Only. Full runs decode and encode on the GPU; Encoding Only decodes on the CPU and encodes on the GPU; Partial sits between the two. - Hardware Device — which GPU to use when the server has more than one. For AMD this is the render node (such as
/dev/dri/renderD128).
Encoder settings
- Preset — NVENC uses
p1–p7(p1 fastest, p7 best quality) plus named presets such ashqandllhq. QSV and AMD VAAPI have no x264/x265-style preset; those presets (ultrafast…veryslow) apply only to the software encoderslibx264/libx265. - Profile and Level — apply to the hardware encoders too, by codec. See Codecs and passthrough.
- Rate control, bitrate and size — CBR or VBR, the target bitrate and the resolution work the same as on the CPU.
Deinterlacing on the GPU
When the source is interlaced, the engine can deinterlace on the same GPU: adaptive_cuvid or yadif_cuda on NVIDIA, advanced_qsv on Intel. Otherwise it falls back to yadif on the CPU. See Filters and overlays.
Verify it is working
Watch the stream statistics: with acceleration active the CPU stays low while the GPU rises, and the stream log names the device it opened.
libx264 / libx265, while the lower tiers stay on the GPU.Related
- Bitrate ladders — the ladder runs on the backend you bind here.
- Codecs and passthrough — which codecs each backend can encode.
- Filters and overlays — GPU deinterlace and scaling.