Thefrank
Thefrank
That looks like it is not even trying to make any hw decoding. I do not have any hardware that does hardware acceleration so it is rather hard to debug...
@rbev DNS name resolution errors (and some other network errors) can be caused by jellyfin's library monitoring. Try turning that off The good news is that jellyfin DOES see a...
Hrm. I have no idea why it does not even bother to use hwaccel despite detecting it. For your opencl try `ffmpeg -v verbose -init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device opencl@va`
dotNET is built under FreeBSD 12.4 and 13.2. JF should work on 12.4 and 13.2 but will not work under 14 because of the new OpenSSL version. When 14.0-R releases...
This should be resolved in ports via workaround but I am keeping this open until I can get around to making ABI specific jellyfin builds
FreeBSD:14:amd64 "Latest" should have it. "Quarterly" does not.
@louwe you can try the FreeBSD14 version of my experimental binary. It should work with both base openssl3 and ports openssl3 under 14.0 https://github.com/Thefrank/jellyfin-server-freebsd/releases/tag/jellyfin-vaapi-test
@louwe Short: The port should be working. Better support from the binary will be in the next jellyfin build. Long: Direct detection and use of OpenSSL3 (3.0) on FreeBSD will...
@louwe + @spin24 With the conversion to a source build, this should be resolved.
The default location has not changed in some time. What version did you have installed and what version did you upgrade to?