Comments (8)
Did you build a vaapi supporting version of the container?
from sonarr-sma.
You'll also need to pass your VAAPI device to the docker container
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
Device path may vary depending on your system
Also using just --hwaccel vaapi will only get you a decoder, you'll also need to choose a VAAPI enabled encoder as well for encoding
Getting full hardware level decoder to encoder passing without software abstraction gets even more complicated, see the HWAccel ffmpeg guide and the numerous issues on the main SMA repo for that but it will require you setting pretty much all the hwaccel related options
The radarr-sma repo also has some issues regarding VAAPI setup you can browse through
from sonarr-sma.
Yes I did both build as well as pass /dev/dri to the container...here is part of the docker-compose.yaml for Sonarr:
sonarr:
hostname: sonarr
container_name: sonarr
build:
context: https://github.com/mdhiggins/sonarr-sma.git#build
args:
sonarr-tag: develop
ffmpeg_tag: 4.4-vaapi2004
depends_on:
- nzbget
volumes:
- sonarr:/config
- downloads:/downloads
- sma:/usr/local/sma/config
- type: volume
source: tv
target: /tv
volume:
nocopy: true
environment:
- TZ=America/New_York
- PUID=1000
- PGID=1000
- SMA_PATH=/usr/local/sma
- SMA_UPDATE=true
- UMASK_SET=022
ports:
- 8989:8989
restart: unless-stopped
devices:
- /dev/dri:/dev/dri
from sonarr-sma.
I wonder if this is an issue of mixing mono and Ubuntu. I believe the developer branch of Sonarr has migrated to mono but the VAAPI build of FFMPEG is Ubuntu.
Does rolling back to an earlier tag of Sonarr that's still on Ubuntu fix the issue by chance?
from sonarr-sma.
I switched the tag to latest and have the same issue...
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Package 'libva' has no installation candidate
from sonarr-sma.
It looks like the 'latest' tag has also been rebased to mono at this point (as of April) so that switch back to latest probably didn't change anything, feel free to correct me if I'm mistaken here
mdhiggins/radarr-sma#34 (comment)
One option that might work is to not build FFMPEG or use the jrottenberg FFMPEG at all and instead use mono and pull FFMPEG from the repo, see that link for a radarr example but Sonarr should work too (at least on the develop tag which is definitely on mono)
from sonarr-sma.
i've done the update and the libva error is gone, how would i confirm that ffmpeg is using vaapi?
from sonarr-sma.
You would have to look at your CPU/GPU usage during a job being run and then compare it with the VAAPI options turned off. Remember, adding the hwaccel parameter only turns on the decoder not the encoder though and decoding isn't all that intensive and not all input codecs will have a hw decoder. For the most performance gains I would include a VAAPI encoder as well (by adding it to the video codec list as your first codec)
https://unix.stackexchange.com/questions/525473/vaapi-usage-monitoring
h264vaapi and h265vaapi are the most common encoder choices
from sonarr-sma.
Related Issues (20)
- SonarrPostProcess - ERROR - Unable to restore scene information. HOT 3
- Feature request: build branch/tag added to GHCR &/or updated at Docker Hub
- Unable to locate package libnppig10 in build HOT 1
- ffmpeg error? HOT 4
- Upgraded to latest version and no longer working:( HOT 8
- Learning and need help with installation HOT 4
- Requesting NVENC enabled script or environment variable. HOT 13
- No module named 'requests' HOT 2
- Error caused by log file ownership HOT 4
- QSV not working on 620slim HOT 10
- Sonarr V3 and Radarr V3 Connect/PostProcess Exit1 Using Script
- NVENC capable FFMPEG build for alpine HOT 27
- Error in "/usr/local/sma/resources/mediaprocessor.py", line 261, in videoStreamTitle HOT 4
- Unable to Perform Local Rename & Conversion Prior to Moving/Sorting on NAS HOT 1
- ffmpeg vaapi error HOT 3
- kubernetes HOT 1
- Script exited with error code: 1 HOT 4
- Latest stable version of sonaar v3.0.9.1549 HOT 3
- vaapi hardware encode not working HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sonarr-sma.