Graphics card for background work
Add-ons and advanced → When Reelhost works → Use the graphics card for background work. It's on when the Video speed test found a graphics card that works with Jellyfin's ffmpeg (NVIDIA NVENC, Intel Quick Sync, AMD AMF, or VideoToolbox on a Mac). Without one, it's off and greyed out, and says why. Playback isn't changed: Jellyfin still plays your files as they are. Only Reelhost's background work moves to the card. Open What each job uses to see which part does each job.
- TV-friendly copies
- The graphics card makes them. If it fails on a title, the processor makes that copy in the same run, and Activity says so.
- Commercial skipping
- The graphics card reads (decodes) the recording; the processor takes over for any recording the card can't read. Captions for recordings stay on the processor: ffmpeg reads broadcast captions only that way.
- AI subtitles
- On Windows with an NVIDIA card, whisper.cpp's own NVIDIA (CUDA) build does the work; on a Mac with Apple silicon, Metal does. whisper.cpp publishes no build for AMD or Intel graphics on Windows, so those use the processor. With the switch off, subtitles are made on the processor.
- The DJ's AI voice
- Stays on the processor: the voice engine Reelhost downloads runs on the processor only.
- Jellyfin's scrubbing preview images
- Jellyfin makes the little pictures you see while scrubbing (trickplay) on the processor unless it's told to use the card. The check-up fix Make preview images on the graphics card turns on Jellyfin's own trickplay settings (Dashboard, Playback, Trickplay: hardware decoding, and hardware encoding on Quick Sync and VideoToolbox). If Jellyfin isn't using the card at all yet, the Video speed fix goes with it. You review the change first, your settings are backed up, and Jellyfin restarts once. Turning the switch off offers to put back exactly what was there before; settings you changed yourself in Jellyfin are left alone.
- In Docker
- Reelhost doesn't test or use a graphics card passed through to the container, so the switch is off and its background work uses the processor.
On a Mac all 13 checks appear, done the macOS way, and Network drives is called Start at login. In Docker, Firewall, Sleep settings and Network drives don't apply in a container, so they're hidden, and Antenna TV is set up on its own screen. More about Docker.