Jellyfin HW Acceleration Not Working

In this tutorial, you'll learn about Jellyfin HW Acceleration Not Working. We cover key concepts, practical examples, and best practices.

Hook

You enable hardware acceleration in Jellyfin Dashboard → Playback. You have an Intel CPU with Quick Sync or an NVIDIA GPU. But when you start a transcode, htop shows 100% CPU usage and the transcode log says "SW" (software). The GPU sits idle.

The Wrong Way

Installing every driver package available or enabling all acceleration options simultaneously (VAAPI + QSV + NVENC) creates conflicts that Jellyfin cannot resolve.

# BAD: Installing everything
sudo apt install intel-media-va-driver intel-media-va-driver-non-free i965-va-driver nvidia-driver-545 mesa-va-drivers

[FFmpeg] libva: Driver conflicts — multiple drivers registered
[FFmpeg] Falling back to software transcoding

Multiple VA-API drivers on the same system cause libva to pick the wrong one and fall back to software.

The Right Way

Select the correct driver for your hardware and verify it works before configuring Jellyfin.

# Intel: Install the right driver (12th-gen+ uses intel-media, older uses i965)
sudo apt install intel-media-va-driver  # For modern Intel
# sudo apt install i965-va-driver       # For old Intel (pre-10th gen)

# Test VA-API
sudo -u jellyfin vainfo 2>&1 | grep -i "driver\|profile"

libva: Driver name: iHD
vainfo: Supported profile: VAProfileH264Main
vainfo: Supported profile: VAProfileHEVCMain

In Jellyfin Dashboard → Playback:

• Hardware acceleration: VA-API
• VA-API device: /dev/dri/renderD128
• Enable hardware encoding: Checked

# Ensure Jellyfin user can access render nodes
sudo usermod -aG render,video jellyfin
sudo systemctl restart jellyfin

Test with a 4K file — nvidia-smi (NVIDIA) or cat /sys/class/drm/renderD128/device/vendor (Intel) should show load.

Prevention

• Install only the single driver matching your hardware generation.
• Add the Jellyfin user to render and video groups on every install.
• Test with vainfo before configuring Jellyfin.
• For Docker deployments, pass --device=/dev/dri and --group-add=44 --group-add=105.
• After every OS update, re-verify VA-API or NVENC still works.

Advanced Troubleshooting

Check the Logs

Most TOOL errors are logged to stdout or a dedicated log file. Check your logs first:

# Check system logs
journalctl -u tool --since "1 hour ago"

# Or check the application log
tail -50 ~/.tool/logs/error.log

Test with a Minimal Example

Create the simplest possible tool configuration to verify the base setup works:

tool --version
tool --help

If the minimal test passes, add configuration options one at a time until you find the breaking change.

Common Configuration Mistakes

• Using the wrong file path or URL in configuration
• Forgetting to restart TOOL after changing config files
• Mixing tabs and spaces in YAML configuration files
• Setting incorrect permissions on configuration directories

When to Reinstall

If none of the above resolves the issue, consider a clean reinstall:

# Backup your configuration
cp -r ~/.tool ~/.tool.bak

# Remove and reinstall
# Follow the official TOOL installation guide

This ensures you start from a known good state and can isolate the issue.

Common Mistakes with hwa transcode

1. Non-exhaustive pattern matches that compile with warnings then crash at runtime
2. Misunderstanding that String is [Char] with poor performance for large text operations
3. Using foldl instead of foldl' causing stack overflow on large lists

These mistakes appear frequently in real-world JELLYFIN code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

DodaTech — hardware acceleration that actually works.