[Placeholder Topic Title: Emby Performance Issues on Raspberry Pi 4]

Hi everyone,

I've been running Emby Server on my Raspberry Pi 4 (4GB RAM) for a few months now, and recently I've noticed a significant drop in performance. Transcoding is extremely slow, sometimes taking minutes to start, and the web interface has become quite laggy. I've checked my network, and it's not the bottleneck. My storage (a USB 3.0 SSD) is also performing well.

Here are some details about my setup:

• Emby Server Version: 4.7.12.0
• Raspberry Pi 4 Model B (4GB RAM)
• OS: Raspberry Pi OS (64-bit)
• Media storage: External USB 3.0 SSD
• Network: Gigabit Ethernet

I'm not sure what could be causing this. Has anyone else experienced similar issues with Emby on a Raspberry Pi lately? Any suggestions on how to diagnose or fix this would be greatly appreciated!

# Example command or snippet if relevant
                        echo "Checking CPU usage..."
                        top -bn1 | grep "Cpu(s)"
                        

Hello JohnDoe,

Thanks for reporting this. We've seen a few reports of performance degradation on ARM-based devices like the Raspberry Pi with recent Emby versions. This is often related to changes in how certain codecs are handled or increased resource demands from new features.

Could you try a few things for us:

1. Check the Emby Server logs: Look for any recurring errors or warnings, especially around the time you notice the slowdowns.
2. Disable hardware acceleration temporarily: Go to Settings -> Playback and disable "Enable hardware acceleration" for transcoding. See if this makes a difference.
3. Monitor CPU/RAM usage: Use `htop` or a similar tool on your Pi to see what processes are consuming the most resources when Emby is under load.

If you can provide the relevant log snippets, that would be very helpful for our developers.

Hey JohnDoe,

I had a similar issue a while back. For me, it turned out to be related to some background services or scheduled tasks on the Pi that were hogging resources. Try checking `cron` jobs or any other system daemons that might be running unnecessarily.

Also, have you considered using the official Emby Docker image? It can sometimes offer better isolation and easier management of dependencies.

Let me know what you find with the logs!