# Plex Transcoder actual sources

**URL:** <https://forums.plex.tv/t/plex-transcoder-actual-sources/220847>\
**Category:** Plex Labs\
**Created:** [January 8, 2018, 11:08pm UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847 "2018-01-08T23:08:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![devrus](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@devrus](https://forums.plex.tv/u/devrus)\
**Post date:** [January 8, 2018, 11:08pm UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847/1 "2018-01-08T23:08:22Z")

</div>

Hi there. I’ve found some topics where Plex provided sources for Plex Transcoder. As it is a modified ffmpeg and ffmpeg is LGPL.  
Why dont you make a mirror repo on github?

Why I’m looking for it?

I’m and Raspbery Pi 3 user. Recently I’ve bought a new TV(Before it was and old one without Smart TV, DLNA etc). So mostly I was watching using direct stream to PC(connect pld tv via HDMI… argh paint…) and now I feel the power of Plex as it can diliver my content to any device.  
RPi3 have a GPU with h264 encding/decoding support. I’ve made some tests for ffmpeg build with --enable-omx-rpi(This swith enables ffmpeg to use GPU of rpi for h264 transcoding) and perfomance is pretty good. I have to switch to another simular software(there for i have a Plex Pass for Year) - Emby. The main reason it uses system installed ffmpeg. So I can watch 1080p video with transcoding without any buffering on rpi3. But I want to watch it in Plex as it much better than Emby.  
To prove that I’m not a liar here is some logs of transcoding from Emby:

720p h264 Hi10 4.3 Mb\s bitrate -\> 720p h264 4.3Mb\s bitrate [https://pastebin.com/0Qu50kkD](https://pastebin.com/0Qu50kkD)  
1080p h264 Hi10 12Mb\s bitrate -\> 1080p h264 10Mb\s bitrate [https://pastebin.com/tpP41084](https://pastebin.com/tpP41084)

So it will be nice to have a repo for transcoder or at least a link for tarball of actual version witch will be updated constantly.

---

<div class="post-metadata">

**Author:** ![elan](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/elan/32/5_2.png) [@elan](https://forums.plex.tv/u/elan)\
**Post date:** [January 9, 2018, 4:27am UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847/2 "2018-01-09T04:27:26Z")

</div>

Hey there, I’ve asked internally about that flag, but in the meantime, this is the latest source ~ [https://files.plexapp.com/elan/ffmpeg/plex-ffmpeg-2017-12-17.txz](https://files.plexapp.com/elan/ffmpeg/plex-ffmpeg-2017-12-17.txz)

---

<div class="post-metadata">

**Author:** ![elan](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/elan/32/5_2.png) [@elan](https://forums.plex.tv/u/elan)\
**Post date:** [January 9, 2018, 4:56am UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847/3 "2018-01-09T04:56:39Z")

</div>

(Basically, it’s not a trivial endeavor for us to enable rPI as a supported architecture for h/w acceleration. We’d need to build with those extra flags/headers, figure out the best scaling/decoding parameters, test, and support. Not saying we’d never do it, just explaining why we haven’t thus far.)

---

<div class="post-metadata">

**Author:** ![devrus](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@devrus](https://forums.plex.tv/u/devrus)\
**Post date:** [January 9, 2018, 10:09am UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847/4 "2018-01-09T10:09:10Z")

</div>

Great thx for tarball.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [January 8, 2020, 1:38am UTC](https://forums.plex.tv/t/plex-transcoder-actual-sources/220847/5 "2020-01-08T01:38:12Z")

</div>


