Archives for posts with tag: RasPi

Honestly, it’s been a little bit since researching and trying new HTPC software has pulled me in, and recently I’ve been shown

just how wrong it was….

In previous posts, I talked about how the dream setup was to have a lightweight Plex client installed on the RasPi, so that it would just be a matter of the well-established Plex server serving content to any number of RasPis automatically.

Recent work, however, has blown this entirely out of the water!

In what seems like the blink of an eye, RasPlex has sprung up, bringing a complete port of the new codebase of Plex/HT to the RasPI version of OpenELEC.

Seriously; the entire (Next generation) Plex desktop  client is now on the Raspberry.

Even the site is flash, yet looks like it works with it’s hands – very nice.

Initial impressions: Fantastic.

One caveat: The FAQ warning at the bottom of this page mentions having to ‘warm up’ the cache in order to have a responsive UI, but it’s not a well-known fact, and the first boot of RasPlex had me thinking that my Raspberry was slacking – 3-4 second response times to the plex remote, taking over 7 seconds to start a video, grinding to a halt when AirPlay was tested…

With with size of our Plex library, it was still caching 30 minutes later, and was still fairly sluggish before getting up to this speed a while later (left it on all night).

TADA! Raspberry Pi and Plex; together in the future at last!

I’ve created a new page on Pseudo Parental Control with Plex.

This is currently a high-level overview of how we handle parental control with 4 kids, the Raspberry, a couple computers, iOS devices, and a Roku.

A quick AHA moment came today when I was witnessing how achingly slow the RasPi was browsing through TV shows (Choose title, count to 7, choose season, count to 7, choose episode, etc).

So, aha; Went straight to XBMC > Settings > Video > File and deselected ‘generate thumbnails’.
Note: If anyone with clout reads this; this should be default for RasPi installs.

XBMC does not use the GPU to process thumbnails, which means that every time you are browsing a folder, it’s using the underpowered CPU to read one file, render a frame, and compress that in to an image, then do that for every thing else on the screen.

Edit: I don’t have the coding skills to put in the work to make this happen, but what makes sense is to split off a thread that generates the thumbnails with absolute low priority and ability to be terminated instantly (when someone presses play, or changes folders). The UI should also stop caring altogether when the thread is sent off: it shouldn’t wait, but just check in passively later to see if it’s done.