emby server transcoding on live playback

#Emby server transcoding on live playback how to
#Emby server transcoding on live playback movie
#Emby server transcoding on live playback install
#Emby server transcoding on live playback update
#Emby server transcoding on live playback software

The ones that matter are those that end with img.gz, which is used for brand new installations and tar, which is used to update an existing OpenELEC installation. When the build finishes, you’ll have a few files in the target directory.

#Emby server transcoding on live playback install

Yes, it takes at least eight hours to build on my system! Gak! Install OpenELEC

It’s not “get a cup of coffee” amount of time but more like “set it going before going to bed and it’ll be mostly done by the time you wake up”. On my VirtualBox instance running on a Mac Mini, it takes a staggering amount of time. So… how long should this take? Well, it massively depends on your system. Technically only the part up to ‘image’ is needed - the latter part is there to log everything, which is useful for debugging if something goes wrong. $ PROJECT=Generic ARCH=x86_64 make image 2>&1 | tee make.log Better have at least 300MB available for the source and then quite a bit more for the build.īuilding the disk image is exactly the same as doing so for the stock image, since I made the Emby build a default option: This will download a couple hundred megabytes of source bits and expand to use another hundred or so. Start out by cloning my forked version of the OpenELEC source code: If you have a dedicated Linux box then all the better since it will likely be much faster. I did mine the easy way and just installed VirtualBox and installed the lasted Ubuntu image onto it. We’ll be compiling OpenELEC from source so we need a Linux PC to do the build on. Here’s the video for those who prefer talking pictures to words:

#Emby server transcoding on live playback how to

That’s what this post is about - how to install Emby inside of the OpenELEC disk image to be part of the cohesive system. That means that for the Emby server to run locally, it will need to be included as part of the OpenELEC disk image. It runs off of a disk image in RAM and so anything running that’s not part of the image is typically wiped out on reboot.

#Emby server transcoding on live playback software

The problem here is that OpenELEC does not easily permit 3rd party software to be installed after the initial installation. Separating Kodi and Emby goes against that purpose. The power of a dedicated HTPC box is that everything runs locally, giving everything super fast reaction times and much tighter integration. Specifically, if you are okay with streaming or transcoding the movies over the network then you are likely better served with a Roku or FireTV box as the front-end running a Plex or Emby client. Unfortunately, that setup defeats the primary advantage of a dedicated HTPC, as far as I’m concerned. It is possible to run the Emby server on a separate computer and stream the content to Kodi - the addon does support that. This is in comparison to Plex, which exists sort of as a side-piece to Kodi and the two maintain separate databases. I tend to prefer Emby for Kodi integration partially because it is Open Source, partially because it is more flexible and more powerful when doing metadata management than Plex, but mostly because it completely takes over the Kodi database when the addon is installed.

#Emby server transcoding on live playback movie

Both are native remote streaming platforms both have excellent modern movie metadata management and both have addons that integrate their functionality with Kodi.

Handily, there are products that fill in those gaps, namely Plex and Emby. It’s so bad that it’s almost a deal-breaker for using Kodi! This console-style interface is now incredibly antiquated and is honestly one of the worst interfaces I’ve ever seen for managing information like this. The Kodi interface is stuck in the era from when it used to be XBMC and run on an XBox. This includes things like artwork and movie info and maybe trailers and all of the rest of the data bits associated with a movie file. Kodi has a terrible interface for movie metadata management. The second problem is the bigger one in my opinion. That is, say you are on a trip and want to watch a movie from your collection that is served up by Kodi. The first is that there is no way to do remote streaming. Kodi, in turn, is a pretty fantastic HTPC front-end, but it does have two notable issues. This results in super fast bootups and very simple setup, once installed. OpenELEC is an HTPC operating system that primarily runs the HTPC mediacenter Kodi off of a disk image in RAM. This post and accompanying video is all about installing Emby inside OpenELEC so I should first explain why I want to do that and what the issue is that justifies its own post.