Gentoo MythTV

29. 08. 08

xine, why not?

Filed under: configuration — Tags: , , — niko86 @ 19:19

after fiddling around with mplayer and the openchrome overlay i did not get mplayer with xvmc to work.
i don’t think openchrome causes the problems, everytime i tried to play a video with -vo xvmc mplayer told me that this video_out device is not compatible with the codec.
I don’t know what this means or why mplayer says that and it did not matter what codec the video was encoded with, so i gave it up.
somewhere i read about xine so i emerged it with the xvmc USE Flag, quickly went over the setup of xine.
(just execute `xine` while in x session, right click -> settings)
configured mythfrontend to use xine -f for mythvideo (-f = start in fullscreen)
that’s it, no magic happens here, just the xorg-server from openchrome overlay, the driver from openchrome overlay and xine.
it works out of the box, has lirc support, nice osd and i can play back videos with ~60% CPU Utilization.
what do you want more, compared with the fiddling with mplayer this took me 20 minutes (inlcuding the compiling of xine-lib, xine and oxine) and simply worked.
I am sure that there is a simple way to get xvmc to work with mplayer, but i just did not figure it out.


27. 08. 08

if i only knew this many hours ago…

Filed under: configuration — Tags: , , — niko86 @ 15:15

there is an overlay for portage which includes all the openchrome patches to make xvmc work with mplayer.
you can find an article about it here: click
i will report about how this works out after the re-emerging has finished.

I did not do much yesterday, just came back home and evaluated the situation.
what i can say right now is that you should re-emerge every xorg module you got.
currently the X-Server is not able to start because of some x264 library which i did not recompile.
Since i got some kind of “failsafe” setup which makes X restart in case of a failure of X Server or mythfrontend, the system currently tries to restart X Server over and over again…
i will report on this later.
i will also wite a quick how-to about making X restart after a failure of mythfrontend.

second update
this is important to know:
since the article above suggests using ACCEPT_KEYWORDS=”~x86″ to install the ebuilds from the overlay (you might as well add the ebuild to /etc/portage/package.keywords), portage will pull in all ebuilds masked with the ~x86 keywords that are more up-to-date than the one installed right now.
this means that if there is a newer ebuild in the official portage tree masked with ~x86 than in the openchrome overlay you will end up installing a new masked ebuild which is not from the openchrome overlay.
to avoid this you should look in your openchrome overlay dir for the newest ebuild available and mask all newer ebuilds.
in my case i had to mask:
in /etc/portage/package.mask because this version is the newest in the openchrome overlay.

Create a free website or blog at