brentstaff
The four playback questions we see most, with the short answers. The troubleshooting docs go deeper.
Direct play, direct stream, converting
- Direct play: the file is sent untouched. Almost free. This is the goal.
- Direct stream: video copied, audio or container rebuilt. Cheap.
- Converting: video decoded and re-encoded. This is what makes a processor work hard.
The player shows which one it chose and why, and so does Settings, Activity.
Video plays but there's no sound
Usually the audio is DTS, TrueHD or E-AC3. Chrome plays those silently instead of showing an error. The server rebuilds that audio automatically, so you'll see Direct Stream. If it's still silent, turn Auto Convert back on in the player's settings, check you're on the right audio track, and check the browser tab isn't muted.
Everything converts
- You picked a quality (1080p, 720p, 480p). Resizing always converts. Set it back to Original.
- The file is HEVC and the browser can't prove it decodes it. Safari and recent Edge usually can, Firefox generally can't, Chrome depends on the machine. Use one that can, or the Android app.
Buffering or stuttering
- Too many conversions at once. One 4K conversion can fill a strong processor.
- Wireless. A 4K remux can pass 80 Mbps. Test on a wired device.
- The disk. Several streams from one spinning drive or a network share can starve playback while the processor looks idle.
Seeking is slow
On converted video, seeking restarts ffmpeg at the new point, so a pause of a second or two is expected. Direct play seeks instantly.
Still stuck? Start a thread with the reason the player shows.