Closed dfeng777 closed 3 months ago
Looks like you're building a container using the latest sonarr container which has been rebased to alpine but then using an ffmpeg build from a non alpine based container which will not work
Thanks for the response. So how would I construct the compose file to make them consistent? I had commented out the image: mdhiggins/sonarr-sma:latest
line. Do I need to different ffmpeg build tag and/or specify a sonarr build tag?
Depend on what your specific end goals are
If its just vaapi encoding that you're after, the ffmpeg build included in the alpine repo supports vaapi, so just enable SMA_USE_REPO
and SMA_HWACCEL
by setting them to true. Doing this means you no longer need to build your own container and can just use the images. If you were building ffmpeg for another reason then it'll depend, but alpine ffmpeg build containers are somewhat limited
Thanks again. As you suggested, I switched back to the mhiggins/sonarr-sma
image with the SMA_USE_REPO
and SMA_HWACCEL
env variables enabled and the vaapi-enabled version of ffmpeg is working. My goals are simply to encode h265/hevc/mkv media to h264/avc/mp4/aac for maximum compatibility.
After fiddling around with autoProcess.ini options for a while and after reading various support threads, it seems like the only way I could get a 10-bit h265 file to encode to 8-bit h264 was to add the following line to postopts:
-vf scale_vaapi=w=1920:h=1080:format=nv12
This was as described in this post:
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/1666#issuecomment-1673404167
I'm not sure what this option does and if it's still the best way to get 10-bit encoding working, but would appreciate the latest direction. Let me know if a new issue/thread is appropriate.
That's probably not the best way to do it, the vaapi encoder will add the scalar automatically if you are decreasing your size
What you're going to want to do is set your pix_fmt to something 8 bit instead but which format is up to you
Describe the bug After building an image using the vaapi build option in the docker compose file, neither ffmpeg or ffprobe can be run from within the docker shell. Running a manual.py command also errors out with the message in the title ("No such file or directory: '/usr/local/bin/ffprobe).
Command or context you are trying to run
/usr/local/sma/venv/bin/python3 /usr/local/sma/manual.py -c /usr/local/sma/config/test.autoProcess.ini -i /data/Media/temp/InputFile.mkv
autoProcess.ini settings
Log files
FFMpeg headers
System Information
OS: Synology DSM 7.2
Python version
Docker config (if relevant) Docker compose:
Expected behavior Expected manual.py script to find and execute ffprobe and ffmpeg to start processing file.
Additional context Was able to successfully use the mdhiggins/radarr-sma:latest image to run ffmpeg from the container shell and to run a manual.py job (just without hardware acceleration).
Issues posted without any logs or autoProcess settings will be closed