starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #6604] [CLOSED] Hardware acceleration for jetson #11050

New Issue
Closed
opened 2026-02-07 06:31:30 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:31:30 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/6604
Author: @mattangus
Created: 9/24/2021
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (7)

📊 Changes

2 files changed (+164 additions, -0 deletions)

View changed files

➕ Dockerfile.arm64-jetson (+72 -0)
➕ scripts/ffmpeg-jetson-wrapper (+92 -0)

📄 Description

Changes

Adds a docker file for building and installing jocover/jetson-ffmpeg to allow for hardware acceleration for the nvidia jetson.

I have tested this on the jetson nano. Please let me know if there is a better way to handle the jetson case. Currently you can find a built image on dockerhub (https://hub.docker.com/r/mattangus/jellyfin-jetson).

docker needs to be run with --runtime nvidia.

for some reason I could only get it to work with docker-compose by adding mkdir /usr/lib/jellyfin-ffmpeg; ln -s /usr/bin/ffmpeg /usr/lib/jellyfin-ffmpeg/ffmpeg to the entry point.

Issues

Implements: https://github.com/jellyfin/jellyfin/issues/5674 (or https://features.jellyfin.org/posts/1118/add-jetson-ffmpeg-nvmpi-support)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/6604 **Author:** [@mattangus](https://github.com/mattangus) **Created:** 9/24/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (7) - [`5f111c6`](https://github.com/jellyfin/jellyfin/commit/5f111c67ba4ff76beaf5294559a6236d39496aa8) initial commit for jetson - [`e8af6b0`](https://github.com/jellyfin/jellyfin/commit/e8af6b0a396112ec2f84c91ad992cd05c1008c9d) fixed ffmpeg path - [`517a380`](https://github.com/jellyfin/jellyfin/commit/517a380169c47bb565979a5f222a15695c069467) combined docker layers - [`d7626e8`](https://github.com/jellyfin/jellyfin/commit/d7626e86593d08fcbead4afc5a595b63bbf78e6d) moved ffmpeg build to jetson-ffmpeg - [`1ccc6d8`](https://github.com/jellyfin/jellyfin/commit/1ccc6d894f3de390a2e2d3e2a4a9acbb9b590a45) changed default ffmpeg to wrapper - [`3003d26`](https://github.com/jellyfin/jellyfin/commit/3003d26febaa23d00a90ce7f2d7db15582bfae0b) removed debugging prints - [`052a115`](https://github.com/jellyfin/jellyfin/commit/052a1155b7eb52fcd71f60124bb7a3a1e15caca4) updated file permissions ### 📊 Changes **2 files changed** (+164 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `Dockerfile.arm64-jetson` (+72 -0) ➕ `scripts/ffmpeg-jetson-wrapper` (+92 -0) </details> ### 📄 Description <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** <!-- Describe your changes here in 1-5 sentences. --> Adds a docker file for building and installing [jocover/jetson-ffmpeg](https://github.com/jocover/jetson-ffmpeg) to allow for hardware acceleration for the nvidia jetson. I have tested this on the jetson nano. Please let me know if there is a better way to handle the jetson case. Currently you can find a built image on dockerhub (https://hub.docker.com/r/mattangus/jellyfin-jetson). docker **needs** to be run with `--runtime nvidia`. for some reason I could only get it to work with `docker-compose` by adding `mkdir /usr/lib/jellyfin-ffmpeg; ln -s /usr/bin/ffmpeg /usr/lib/jellyfin-ffmpeg/ffmpeg` to the entry point. **Issues** <!-- Tag any issues that this PR solves here. ex. Fixes # --> Implements: https://github.com/jellyfin/jellyfin/issues/5674 (or https://features.jellyfin.org/posts/1118/add-jetson-ffmpeg-nvmpi-support) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 06:31:30 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#11050
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?