# High CPU on video playback (Anthias Docker on Raspberry Pi 5)

**URL:** <https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518>\
**Category:** Anthias\
**Created:** [August 20, 2025, 12:45am UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518 "2025-08-20T00:45:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![6\_HP\_9](https://avatars.discourse-cdn.com/v4/letter/6/b5e925/32.png) [@6\_HP\_9](https://forums.screenly.io/u/6_HP_9)\
**Post date:** [August 20, 2025, 12:45am UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/1 "2025-08-20T00:45:13Z")

</div>

Hi everyone! I’m looking for help and to know if anyone faced the same issue.

**Hardware**

- Raspberry Pi 5 Model B – 4 GB RAM
- Waveshare PCIe-to-M.2 Adapter with PoE
- Official Raspberry Pi NVMe SSD 256 GB

**OS & Setup**

- Raspberry Pi OS Lite (Bookworm), fully updated
- Anthias running in Docker (Pi5 images, latest tags)
- Followed `raspberry-pi5-ssd-install-instructions.md`

**Issue**

- Full HD videos are played by ffplay

- CPU usage jumps to constant 80–90% during playback

- The fan gets very loud when CPU maxes out

- Example process:

**What I tried**

- Converted assets to HEVC (hvc1)

**Comparison**

- Balena image: playback is smooth (no high CPU)
- Raspberry Pi 4 with Anthias Docker: playback is smooth
- Problem only on Raspberry Pi 5

How can I enable hardware-accelerated playback on Pi 5 with the Anthias Docker viewer?

Is there a way to force VLC, or recommended ffplay flags to use hardware HEVC decode on Pi 5?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![nicomiguelino](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@nicomiguelino](https://forums.screenly.io/u/nicomiguelino)\
**Post date:** [August 20, 2025, 1:17pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/2 "2025-08-20T13:17:29Z")

</div>

@6_HP_9, Anthias is currently using `ffplay` for the Raspberry 5 to play videos.

VLC is an option. However, a fair bit of work might be needed.

---

<div class="post-metadata">

**Author:** ![6\_HP\_9](https://avatars.discourse-cdn.com/v4/letter/6/b5e925/32.png) [@6\_HP\_9](https://forums.screenly.io/u/6_HP_9)\
**Post date:** [August 20, 2025, 1:56pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/3 "2025-08-20T13:56:17Z")

</div>

Thanks for the clarification.

I’m OK staying with ffplay on Raspberry Pi 5. I just need hardware decode so CPU (and the fan) don’t spike on 1080p. Not sure if it’s even possible.

I have a few questions though:

1. Is there a config or env var to pass extra ffplay args from docker-compose? For example, adding `-vcodec hevc_v4l2m2m` when the file is HEVC.

2. If not, is there a supported place to inject custom player flags (config file, hook, or override script) without forking?

3. For the VLC option, is there a dev tag/branch I can test? Also, could you elaborate on the “fair bit of work”? I might give it a try.

Thanks

---

<div class="post-metadata">

**Author:** ![nicomiguelino](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@nicomiguelino](https://forums.screenly.io/u/nicomiguelino)\
**Post date:** [August 20, 2025, 6:03pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/4 "2025-08-20T18:03:30Z")

</div>

@6_HP_9, I tried to get inside the `anthias-viewer` container and run videos via VLC but there’s no audio or video. By fair bit of work, I mean trying things like installing an X server and configuring VLC to start via the X11 by setting `DISPLAY` to `:0` (e.g., export `DISPLAY=:0`). Feel free to try ffplay with `X11` if you’d like to explore as well.

---

<div class="post-metadata">

**Author:** ![6\_HP\_9](https://avatars.discourse-cdn.com/v4/letter/6/b5e925/32.png) [@6\_HP\_9](https://forums.screenly.io/u/6_HP_9)\
**Post date:** [August 21, 2025, 1:43pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/5 "2025-08-21T13:43:46Z")

</div>

> [@nicomiguelino](#):
>
> rk, I mean trying things like installing an X server and configuring VLC to start via the X11 by setting `DISPLAY` to `:0` (e.g., export `DISPLAY=:0`). Feel free to try ffplay with `X11` if you’d like to explore as well.

Thanks again. I’ll give it a try and share it, if I’m successful.

---

<div class="post-metadata">

**Author:** ![vinividivici](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vinividivici/32/729_2.png) [@vinividivici](https://forums.screenly.io/u/vinividivici)\
**Post date:** [November 24, 2025, 5:04pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/6 "2025-11-24T17:04:12Z")

</div>

Was there ever a resolution to this? Have just a video on a Raspberry Pi 5 and its pinning CPU - exactly same results as above. Would currently make me want to only run static assets to avoid CPU/fan spikes.  
(Thanks in advance - otherwise an absolutely cracking bit of software and very appreciative)

---

<div class="post-metadata">

**Author:** ![nicomiguelino](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@nicomiguelino](https://forums.screenly.io/u/nicomiguelino)\
**Post date:** [November 24, 2025, 5:37pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/7 "2025-11-24T17:37:27Z")

</div>

@vinividivici, we’re still in the process of resolving other bugs that might be connected to or that might affect this issue. However contributions are always welcome if you have something in mind.

---

<div class="post-metadata">

**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\
**Post date:** [June 9, 2026, 3:18pm UTC](https://forums.screenly.io/t/high-cpu-on-video-playback-anthias-docker-on-raspberry-pi-5/6518/8 "2026-06-09T15:18:48Z")

</div>

This should be much better now. The high CPU during video came from the old way the player handled each frame, copying it through the CPU before showing it. The video path was rebuilt to draw frames directly on the screen instead ([#2975](https://github.com/Screenly/Anthias/pull/2975)), with frame pacing added in [#3006](https://github.com/Screenly/Anthias/pull/3006), which removes that heavy work. Please update to the latest release. Marking this as solved. If CPU is still high during video on the latest, let us know your setup.
