# Pi 4b HW accelerated transcoding

**URL:** <https://forums.plex.tv/t/pi-4b-hw-accelerated-transcoding/832723>\
**Category:** Feature Suggestions\
**Created:** [February 28, 2023, 2:14am UTC](https://forums.plex.tv/t/pi-4b-hw-accelerated-transcoding/832723 "2023-02-28T02:14:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Far-King-Jeebus](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/far-king-jeebus/32/194391_2.png) [@Far-King-Jeebus](https://forums.plex.tv/u/Far-King-Jeebus)\
**Post date:** [February 28, 2023, 2:14am UTC](https://forums.plex.tv/t/pi-4b-hw-accelerated-transcoding/832723/1 "2023-02-28T02:14:13Z")

</div>

ffmpeg supports hardware accelerated transcoding on the pi 4b so why doesn’t the plex fork of ffmpeg?

What advantages has plex gained by forking ffmpeg away from the origin branch? It seems like plex has lost a lot of ffmpeg functionality and gained nothing?

Could it be really difficult for the plex devs to patch in the pi 4 HW transcoding of mainline ffmpeg into the plex variant? Or is such a task too comPlex?

---

<div class="post-metadata">

**Author:** ![FordGuy61](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@FordGuy61](https://forums.plex.tv/u/FordGuy61)\
**Post date:** [February 28, 2023, 8:39am UTC](https://forums.plex.tv/t/pi-4b-hw-accelerated-transcoding/832723/3 "2023-02-28T08:39:16Z")

</div>



---

<div class="post-metadata">

**Author:** ![FordGuy61](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@FordGuy61](https://forums.plex.tv/u/FordGuy61)\
**Post date:** [February 28, 2023, 8:39am UTC](https://forums.plex.tv/t/pi-4b-hw-accelerated-transcoding/832723/4 "2023-02-28T08:39:47Z")

</div>

I see you’ve commented on the thread @flow mentioned. I’ll close this as a duplicate.