SeaMauFive@lemm.eeOPtoJellyfin: The Free Software Media System@lemmy.ml•Hardware ClarificationEnglish
1·
11 months agoI’m not totally sure I get what you’re saying in 2, but I appreciate your endorsement of quick sync
I’m not totally sure I get what you’re saying in 2, but I appreciate your endorsement of quick sync
Much appreciated. I was worried I’d need a graphics card. It’s great to hear that some CPUs are overkill
Thanks! I feel much more confident hearing what people have that works
Thank you. That’s exactly the kind of answer I was looking for. It’s good to know that this is just a struggle for the pi and not something CPUs as a whole have an issue with
I skimmed the guide you sent and the top says that the portions in brackets are placeholders and need to be replaced with real values. If you change {{ lemmy_docker_image }}
to be the name of the image to use dessalines/lemmy:0.18.0
for example, do you get further
I’m assuming you mean the jellyfin server and not the Android TV client specifically.
Running the jellyfin server on an SBC is possible, I’m running it on a pi 4 right now. Personally, I’d recommend installing docker and running the service in a container. There’s official docs for how to do so https://jellyfin.org/docs/general/installation/container/
That being said, Jellyfin docs recommend against running on an SBC. I too, running it on an SBC, recommend against it. It can do the “happy path” well. But if the stored media is in a format that requires the server to transcode it for the current, it cannot handle it. The time it takes to transcode is several times longer than the actual run time of the media. You will have a bad time. I’m currently looking to change/upgrade the hardware to work around this