[mythtv-users] 0.25 frontend on raspberry pi?

Evuraan evuraan at gmail.com
Tue Sep 17 23:36:20 UTC 2013


> To summarize, it's not going to happen until someone writes OpenMAX support in MythTV, and then it's still not going to happen (on the 256MB version) until someone cleans up memory usage in the frontend, and then it still may be slow rendering things like Watch Recordings or the channel guide on larger systems.
>

thank you for explaining.

//
there are two major hurdles preventing use of mythfrontend on a Raspberry Pi.

Mythfrontend will not run happily at high resolutions on a system with
somewhere less than 200MB of system memory, which is what you have
after the graphics core gets its fill.  A second generation unit has
512MB total (again minus the graphics core's take), which should
alleviate this issue.

Mythfrontend will not be useful on a system unless it can actually
play back video, which either means sufficient CPU, or a usable
hardware decoder.  The Raspberry Pi has nowhere near the former, and
will not have the latter until someone spends the time writing an
OpenMAX implementation for MythTV.
//

If the mountain doesn't, I am hoping cmyth gets much needed  deletion
fu.. (Will settle for THAT!)

but *why* is the FE so taxing?


More information about the mythtv-users mailing list