Jellyfin / Paperless-ngx on Raspberry Pi 4?
from frosch@sh.itjust.works to selfhosted@lemmy.world on 14 May 18:45
https://sh.itjust.works/post/60171250

Does anyone run one of the above on a Pi 4 and can share their experience how good or bad they run?

If course, transcoding won’t be any good and OCR probably cannot run in parallel, but aside from that - is it okay?

Currently running everything on a mini ITX with a i5-6600 which handles this easily for my small use cases, but also draws 20-30W idling most of the day… I’m eyeing a Pi 4b with 8gb RAM but don’t want to spend the money and then realizing that it doesn’t run smooth enough

#selfhosted

threaded - newest

IcedRaktajino@startrek.website on 14 May 19:00 next collapse

I run Jellyfin on a Banana Pi M4 Zero. It’s a little less capable than the Pi4 but runs JF just fine. Specs on this one are quad core 1.5 GHz, 4 GB RAM, 32 GB eMMC on Armbian.

The media files are all on the 1 TB SD card while the Jellyfin data directory (especially the SQLite DB) are on the eMMC. This seems to work much better as the DB file kept getting corrupted on SD. Should also help the SD card from wearing out since it’s pretty much only reading data from it most of the time.

As you guessed, transcoding is not going to work (JF is removing the v4l2 hardware support anyway), so I pre-transcode them to H264 + yuv420p in an mp4 container before moving them to the SD card. I also scale them down to 720p to fit more on there, but that’s because this is a travel server and isn’t my main media source.

Can’t speak for Paperless though.

northernlights@lemmy.today on 14 May 20:43 next collapse

Travel server? Now that’s an idea

frosch@sh.itjust.works on 15 May 07:49 collapse

A Pi as a travel server sounds like an awesome idea!

What are the use cases for taking it with you instead of just connecting to your homelab?

Edit: Your username made me thirsty, too bad I have to wait some hundred years to get one on earth…

mbp@slrpnk.net on 14 May 19:22 next collapse

I tried paperless years ago on my 4B and it did not work well enough to be usable.

Jellyfin was fine.

I’d say getting an x86 think centre or equivalent will cut your idle in half and give you enough overhead to run paperless and jellyfin.

Onomatopoeia@lemmy.cafe on 14 May 20:44 next collapse

I run a 2019 Dell OptiPlex SFF desktop as my ESXi box - it idles under 20w with multiple Linux and Windows VM’s (4 are standard, besides the ad-hoc ones for testing stuff).

Hard to beat the idle combined with performance when needed. Pi really doesn’t compare.

frosch@sh.itjust.works on 15 May 05:46 collapse

it did not work well enough to be usable.

Was it the overall performance or the OCR specifically?

I have run paperless some time on a pi 3b without OCR (manually doing it on a PC or when scanning with Apps like MakeACopy) and it was okay-ish. Not a lot documents though.

And I thought it was mainly the 1GB RAM limiting (starting Paperless started swapping right away…)

theorangeninja@sopuli.xyz on 14 May 20:44 next collapse

Consider papra as a more lightweight alternative for paperless-ngx. I have not used it yet unfortunately.

Teppichbrand@feddit.org on 14 May 20:58 next collapse

I tinkered for years with numerous Raspberry Pies but got tired of it. Bought a second hand Dell ThinClient Wyse 5070 for like 70€, installed DietPi and its awesome.

broodmother@discuss.tchncs.de on 15 May 07:22 next collapse

Zu Paperless-ngx auf dem Pi 4: Für leichte private Dokumentenmengen kann das funktionieren, aber OCR ist der Teil, der schnell zäh wird. Ich würde die Worker klein halten und OCR/Tika/Gotenberg eher auslagern, wenn regelmäßig größere PDFs reinkommen. Paperless selbst ist meist weniger das Problem als OCR + I/O; Jellyfin parallel ist ohne Transcoding deutlich entspannter.

KatherinaReichelt@feddit.org on 15 May 09:40 collapse

Als Privatnutzer bekommt man ja eher seltener gigantische Mengen an Papier per Post. Das sind dann maximal ein paar Briefe pro Woche und dann ist es auch total egal, ob die OCR 10 Minuten pro Brief braucht. Und wenn du als Firma wirklich noch eine größere Menge an Briefpost zu verwalten hast, dann ist ein Raspi definitiv die falsche Wahl

gedfromgont@piefed.ca on 15 May 09:58 collapse

I have a Pi 4B with 8 GB RAM and run Jellyfin plus some other stuff on it. Works great.

Had it first installed via repo but transcoding did not work at all. After switching to the Docker setup though, transcoding worked ok out of the box. Definitely takes a few seconds before the stream starts when having to transcode but no hiccups afterwards. Unless you jump around of course, and also I never had more than one stream trandcoding.