Comment 7 for bug 160447

>> It might be that lib-xine is not picking the best driver for you.
>> Please run `xine --help` to see a list of available video/audio drivers
>> (-V,-A options) and try playing around with those in the ~/.me-tv/me-
>> tv.config (hope you know XML). Let's see where that takes us.
>>
Some interesting results here. The only video drivers that worked at
all were xv, opengl, and xshm.

xv worked for whichever channel me-tv was started in (either HD or SD),
but changing to other channels while running generated the problem with
interlacing and apparent wrong scan lengths. Maybe there is some
dimension which is being initialised on startup but not re-initialised
on channel change? xv used about 13% of 1 cpu on SD and 4. Sometimes
channel changes crashed the xserver.

opengl worked well for all channels, with usage of 1 cpu at about 15% on
SD and 50% on HD.

xshm worked well for all channels, with usage of 1 cpu at 23% on SD and
75% on HD.

I'm guessing that the original "auto" setting was defaulting to xv, but
it looks like opengl would be the best choice.

The only audio driver I had installed was alsa. It provided normal
sound on all SD channels and on SBS HD, but no sound on any of the other
HD channels.

On a different issue, I've noticed that the EPG doesn't always seem to
respond properly to mouse inputs. Sometimes after a single click on a
channel or program the cursor will remain as a pointing hand, the
channel change will not take place (no message to terminal) and the
focus will not leave the me-tv window. The only way out is Alt-F9 to
minimise me-tv, then kill it from the terminal.

Hope all this helps, since me-tv seems a very good application if these
minor bugs can be sorted out.

Thanks,
Dan