jellyfin-ffmpeg VS jellyfin-blog

Maybe my expectations for RPi 5 are too high, but it’s hard to imagine that an SBC manufacturer known as the industry standard removed the H.264 decoder & encoder from their latest product instead of adding VP9 and AV1, causing users to go crazy when YouTube playback dropped frames. Not to mention serving up transcoded content as a media server.

Good news is that I've been playing around with its competing products. For those users who want a normal media server experience in 2023, Jellyfin will support RK3588 full hardware accelerated transcoding, includes AV1 decode, subtitle burn-in and HDR tone-mapping. (WIP https://github.com/jellyfin/jellyfin-ffmpeg/issues/34#issuec...)

https://github.com/jellyfin/jellyfin-ffmpeg/issues/243 has the solution.

https://github.com/jellyfin/jellyfin-ffmpeg/issues/57 says jellyfin but same for emby. It will play but freezes after a bit randomly.

jellyfin-ffmpeg5 is updated to 5.1.3-1, which built against the llvm15. https://github.com/jellyfin/jellyfin-ffmpeg/releases/tag/v5.1.3-1

wget https://github.com/jellyfin/jellyfin-ffmpeg/releases/download/v5.1.2-8/jellyfin-ffmpeg5_5.1.2-8-bionic_amd64.deb

Hopefully the official Jellyfin documentation will be updated soon to reflect this newly available packaging.

The website is able to be edited through GitHub, so you can contribute with that you deem to be needed additionally. I've done a few changes in the past and they are normally very responsive. You can find it on: https://github.com/jellyfin/jellyfin-blog

Also, yes, I didn't write the blog post for 10.7. Although I did start it right after the release seeing that nobody took the mantle and wanting to have it done. However, I was in a bad place mentally at that point, after a year of being alone in a 75m² apartment (and ended up losing my job 3 months later in part due to that), so can you really blame me for not having the (mental) capacity to get it done?