Closed gresheff closed 3 years ago
Does rolling back to bionic for sonarr on the jrottenberg side of things make any difference? I believe I tested it on bionic with mono and it worked fine
Its mentioned in the readme you should try and match the versions for compatibility
4.3.2-vaapi1804
as your ffmpeg_tag
specifically
That did it, thanks!
Wasn’t aware you could pull older binaries with this kind of tagging.
On Mar 16, 2021 at 01:51, <Michael Higgins @.***)> wrote:
4.3.2-vaapi1804 as your ffmpeg_tag specifically
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/mdhiggins/sonarr-sma/issues/23#issuecomment-800074073), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAWYYHFURFRMFC7G5M77UZLTD4L2JANCNFSM4ZHRO7HQ).
So you're not actually even pulling an old binary. The jrottenberg container is building FFMPEG from source and you're just changing the build environment using docker tags and then copying the binaries from one container to another. Its the latest version of FFMPEG
Thanks for all of your great work on this project! I am a bit of a noob so please excuse me if my comments are too ambiguous.
I have been trying to use sonarr-sma and radarr-sma containers to transcode with VAAPI hardware acceleration (jrottenberg static images). I have been using the #build tag as per the README. This has worked well with radarr-sma but there are missing dependencies for sonarr-sma which causes ffmpeg to fail.
I believe the reason may be that the ffmpeg VAAPI binaries have been based off focal. Radarr has recently been rebased to focal which is why the multi stage build works (with all required dependencies). Sonarr is still on a bionic base (mono) and therefore there are missing dependencies.