2023-09-15, 11:06 PM
So I wonder if this has to do with the fact that you're not adding your customffmpeg dir to the PATH in your container? I know the instructions I followed for compiling my own ffmpeg always included adding the dir where you compiled the bin to the PATH. Unsure whether that matters for how Jellyfin calls the tool for transcoding. The last part of my custom compile script that I developed and saved for future reference looks like this:
You might verify that your custom ffmpeg actually works by doing a docker exec into the container and trying to run it just to see the banner. If it doesn't run, there's something wrong with the compile.
Code:
PATH="$HOME/bin:$PATH" make -j$(nproc) && \
make install && \
hash -r
You might verify that your custom ffmpeg actually works by doing a docker exec into the container and trying to run it just to see the banner. If it doesn't run, there's something wrong with the compile.
Jellyfin 10.10.0 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage