mr-hexen

Since you have linked back to this post from a few other threads, you should provide a link to the source of your information in this post. Actually, that was me linking it, I recall it being mentioned as an issue so wanted to ensure people knew about this discovery.

Anyone having Transcode to RAM issues on the latest plexpass might want to read this: http://lime-technology.com/forum/index.php?topic=37553.msg428525#msg428525

Make sure it's set to cache only in share settings.

Thanks for following up, i'll avoid the latest CP update that just announced itself.

Is your docker img full?

Try this file. sound.conf

Patience is a virtue

The Q25 is becoming harder and harder to find. When you find it, the price will be much higher then it used to be. Research this and go from there (you'll likely be switching which case you get).

As i hoped you two would.. just wanted to point it out for anyone else reading the thread and making adjustments. I could picture in like 2 days "My docker image is full and I have no idea why?!"... not like we've never seen those posts before!

hex, you are correct about Plex's behavior and it is why I advocated against moving transcoding to RAM in the past. I had the same problem as dirtysanchez, but it was only on long high bit rate videos (movie BD rips). All other stuff ran fine. When I dug into it I was basically juuuuuust not hitting the wall with the shorter lower bit rate stuff but the BD movie rips, at full bit rate, would fill /tmp in about 30-45 min. Crash. flush. restart. rinse. repeat. Frankly the concern over SSD wear is misplaced given all current evidence and most plex / unraid implementations I can guess at. Even with 24/7 streaming of a reasonable number of 20mbit streams the SSD will outlive most people, no less its likely useful life. I have moved transcoding back to the SSD and will leave it there. If you can transcode to RAM without issues, then I see no point in not doing so. But if you have issues with /tmp filling up, it's probably best to just move transcoding back to cache and be done with it. How did you get it back to the SSD? did you map it there or did you just remove the /transcode directory. I mention this as a caution that it does not transcode to the docker.img as it might fill it up!

/tmp is RAM so 93% used is expected (Linux caches all free RAM for other needs and freely gives it up to programs that require it). It IS entirely possible that /tmp uses nearly the full amount of RAM until it stops, how large are the source video files you are transcoding? I think Plex saves the full transcoded file until the viewer stops watching the video.

Yes, Kodi can download actor thumbs. Check your settings to turn on / off. I also believe it can store .actors in each movie folder or a central folder so it doesnt downloaed duplicates.

Why not use a KODI-Headless Docker to check things out (it has a webserver for minimalistic viewing of libraries). Using a good media fetcher like CouchPotato or Sonarr should be able to handle the metadata for you. Simply tell it to use a nfo file with the IMDB link for accuracy?

Been playing with PlexOE a little more. Now I remember an issue that was a deal breaker for me: hardware acceleration is not working. My CPUs are getting crushed. Which build did you use and how did you determine this?

Thanks, but I doubt a local (canadian) shop will match a US one I'm monitoring some eBay and kijiji ads for a i5-4690k for $220 right now.

Sorry, what I did was follow the instructions here: https://forums.plex.tv/discussion/88788/oe-install-and-package-status-thread Essentially, replicate the regular OE install method but use the files from OEPlex instead.

Could you not just use the OEPLEX ISO?

UPDATE: I just did this as POC and had PlexOE up and running in a matter of 15 mins. John If this is the Plex Plugin on an current OE install, i tried this and hated it.

Explain again why this would NOT be an issue? I'm not being critical, but just don't understand using such an old platform. There has to be a lot of newer technology being excluded. That being said, you can always perform a manual install in a VM as described here: http://wiki.openelec.tv/index.php/Manual_Installation This is what I did for all 3 of my OE VMs. Only thing you need to do is modify your XML and disk controller and NIC model type from virtio to sata and e1000 respectively since OE does not have virtio drivers included. John It only uses the OpenELEC as a base. The PHT install is current stable. Sort of like unRAID used to be (or still is?) on an older linux kernel btu the unRAID stuff was current and stable.

I use plex.

UPDATE TIME: I've added a couple more dockers lately, namely CrashPlan and CrashPlan-Desktop to get a centralized backup system for our household going. I've set it to backup all data from C:\Users as that is where the important information lies (docs, pictures, spreadsheets, taxes, etc.) I've excluded certain folders like favourites, searches, appdata, etc that I dont care about. Now, on the topic of CPU... I've spotted an i5-4570 used for $180, still seems steep for a used processor... I'll probably just wait out for a smokin deal.

Exactly. Its a fork of OpenELEC (3.2.x I believe) that has the current PHT installed on it instead of Kodi. It turns hardware into a plex appliance basically. Hmm, I will need to talk to Eric. Sounds like a good idea for us to considering that we already have done the bulk of the work in tuning OpenELEC. It might be as simple as pointing your OE unVM to a different image? I'd try, but don't have a vt-d CPU.

Exactly. Its a fork of OpenELEC (3.2.x I believe) that has the current PHT installed on it instead of Kodi. It turns hardware into a plex appliance basically.

Jonp, can you give OpenELEC+Plex a try in a VM? Images located here: http://plexrpms.markwalker.dk/OpenELEC/3.2/

No. Vtd is required to pass through physical devices such as a USB controller or video card. It may not be called iommu in the Bios. Look for virtualization or something along those lines.