<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 3/14/2017 11:56 PM, Tom Harris
wrote:<br>
</div>
<blockquote
cite="mid:CAAme0Obx_UoyprPbR0DT+mkizB49v2p741i5N2-_hs+mdXPH6g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Mar 13, 2017 at 9:59 PM, Tom
Harris <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:thom.j.harris@gmail.com" target="_blank">thom.j.harris@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Mon, Mar
13, 2017 at 1:12 PM, Peter Bennett <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:cats22@comcast.net"
target="_blank">cats22@comcast.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px
0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF">
<div>
<div class="m_-9052440178675591822gmail-h5">
<p><br>
</p>
<br>
<div
class="m_-9052440178675591822gmail-m_6280151748738118325moz-cite-prefix">On
03/13/2017 01:04 AM, Tom Harris wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar
9, 2017 at 12:46 PM, Phill Edwards
<span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:philledwards@gmail.com"
target="_blank">philledwards@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="auto">
<div><br>
<div class="gmail_extra"><span
class="m_-9052440178675591822gmail-m_6280151748738118325m_5966011211832219938gmail-"><br>
<div class="gmail_quote">On
9 Mar 2017 16:23, "Tom
Harris" <<a
moz-do-not-send="true"
href="mailto:thom.j.harris@gmail.com" target="_blank">thom.j.harris@gmail.com</a>>
wrote:<br
type="attribution">
<blockquote
class="m_-9052440178675591822gmail-m_6280151748738118325m_5966011211832219938gmail-m_-1778664185637175462quote"
style="margin:0px
0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">There
are a bunch of
threads, files, etc.
for getting
mythfrontend running
on a Raspberry Pi.
But, some of them
appear no longer
maintained/updated.
<div>So, I'm
wondering what's
the current
recommendation for
a Pi frontend
deployment.</div>
<div><br>
</div>
<br>
</blockquote>
</div>
</span>This page says it's
up to date for 0.28</div>
</div>
<div class="gmail_extra"
dir="auto"><a
moz-do-not-send="true"
href="https://www.mythtv.org/wiki/Raspberry_Pi"
target="_blank">https://www.mythtv.org/wiki/Ra<wbr>spberry_Pi</a></div>
</div>
</blockquote>
<div><br>
</div>
<div>I had some time to set up a
new Pi3 frontend this weekend.
I basically replicated the same
experience from when I tried a
little more than a year ago.
1080i was still not usable for
me. It seems like others have
this working.. what am I
missing?</div>
<div><br>
</div>
<div>My experience was:</div>
<div><br>
</div>
<div>1. Spent a lot of time
debugging. This is a recurring
theme in my long experience with
MythTV. I got random frontend
hangs, which I thought were
related to video decoding. But,
after much debugging got it down
to the "query_cache" settings in
MySQL. Once I disabled that the
frontend became reliable.</div>
<div><br>
</div>
<div>2. US Broadcast MPEG2 @ 720P
works great.</div>
<div><br>
</div>
<div>3. US Broadcast MPEG2 @1080i
does not work well. I get
video playback, but with
frequent audio hiccups and some
video hiccups. The default
de-interlacer setting of
'Advanced (HW)' was quite bad.
When I changed it to "Fast (hw)'
it worked much better -- but
still had audio/video hiccups.</div>
<div><br>
</div>
<div>MythTV version: 0.28
(up-to-date frontend and
backend)</div>
<div>Video Settings: OpenMax
normal, Decoder: Openmax,
renderer: openmax, OSD Renderer:
OpenGL; Primary deinterlacer:
Fast(HW)</div>
<div>MPEG2 license enabled:
verified by command line and CPU
load during playback</div>
<div>Output: HDMI @ 1080P on 4K TV</div>
<div><br>
</div>
<div>Any tips on reliable 1080i
MPEG2 playback?</div>
</div>
</div>
</div>
<br>
<fieldset
class="m_-9052440178675591822gmail-m_6280151748738118325mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</div>
</div>
Did you look at the "System Performance"
section in the Raspberry Pi Page?<br>
<a moz-do-not-send="true"
class="m_-9052440178675591822gmail-m_6280151748738118325moz-txt-link-freetext"
href="https://www.mythtv.org/wiki/Raspberry_Pi" target="_blank">https://www.mythtv.org/wiki/Ra<wbr>spberry_Pi</a><br>
If you still have a problem, try running with
-v playback. See if there are any audio sync
errors or other messages displayed.</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
</span>
<div>
<div bgcolor="#FFFFFF">Thanks! I re-read that and
spent some more time getting the Alsa:Default
working. I had gotten static with that before
and switched to OpenMax:hdmi. I switched to
Stereo and made sure all the DD/DTS/etc. options
were disabled and Alsa:Default now works and
1080i MPEG2 playback is smooth.</div>
<div bgcolor="#FFFFFF"><br>
</div>
<div bgcolor="#FFFFFF">With the Pi3, the UI is
quite responsive. I'll definitely be giving
this a try to replace LibreElec/Kodi that I've
been using for the last year.</div>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>A couple more notes on further testing:</div>
<div><br>
</div>
<div>- I had a few crashes of the frontend - but, after
looking at the logs I found that it was actually the
kernel oom (out of memory) killer killing mythfrontend.</div>
<div> - I changed the GPU memory from 256MB to 128MB for
some more head room and playback is fine. Is there any
reason to believe this will be a limitation? The
performance tips in the wiki recommend 256MB and
increasing to 320MB if playback was not smooth.</div>
<div><br>
</div>
<div>- I tested several themes earlier and I'm guessing that
contributed to the oom kills. I switch to a simpler 720p
theme and the frontend memory usage seems reduced. </div>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mythtv.org/mailman/listinfo/mythtv-users">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a>
<a class="moz-txt-link-freetext" href="http://wiki.mythtv.org/Mailing_List_etiquette">http://wiki.mythtv.org/Mailing_List_etiquette</a>
MythTV Forums: <a class="moz-txt-link-freetext" href="https://forum.mythtv.org">https://forum.mythtv.org</a>
</pre>
</blockquote>
Not sure if this is relevant to the Pi3, but I ran into a recent
kernel bug with Ubuntu 16.04 that caused the OOM killer to do its
thing when there was plenty of RAM and swap space available (<a
class="moz-txt-link-freetext"
href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842</a>).<br>
Jay<br>
</body>
</html>