<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 7, 2018, at 7:24 AM, Jim Abernathy <<a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
  
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
  
  <div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><br class="">
    </p>
    <br class="">
    <div class="moz-cite-prefix">On 10/06/2018 06:45 PM, Jerry wrote:<br class="">
    </div>
    <blockquote type="cite" cite="mid:CAO_Sck5gc7KdU7Rbwpc+sXvS+AXyy-nKvYfWy7a27wKm1Ex4dw@mail.gmail.com" class="">
      <meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
      <div dir="ltr" class="">
        <div dir="ltr" class="">
          <div class="gmail_quote">
            <div dir="ltr" class="">On Sat, Oct 6, 2018 at 6:37 PM James
              Abernathy <<a href="mailto:jfabernathy@gmail.com" moz-do-not-send="true" class="">jfabernathy@gmail.com</a>>
              wrote:<br class="">
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div style="overflow-wrap: break-word;" class="">
                <div class="">
                  <blockquote type="cite" class="">
                    <div class="">
                      <div bgcolor="#FFFFFF" class=""><br class="">
                        <div class="gmail-m_3413871183495599563moz-cite-prefix">On
                          10/06/2018 03:16 PM, Jerry wrote:<br class="">
                        </div>
                        <blockquote type="cite" class="">
                          <div dir="ltr" class="">
                            <div class="">
                              <div class="gmail_quote">
                                <div dir="ltr" class="">On Sat, Oct 6, 2018 at
                                  2:48 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank" moz-do-not-send="true" class="">jfabernathy@gmail.com</a>>
                                  wrote:<br class="">
                                </div>
                                <blockquote class="gmail_quote" style="margin:0px 0px 0px
                                  0.8ex;border-left:1px solid
                                  rgb(204,204,204);padding-left:1ex">So
                                  I now have my RP3+ and I used Etcher
                                  to install the RP Stretcher from
                                  2017-11-29.  However when I turn on
                                  the RP3+, I just get the multicolor
                                  screen and the board has a blinking
                                  Green LED in some pattern.<br class="">
                                  <br class="">
                                  Did I miss a step?  I just downloaded
                                  the .zip file for Stretcher, Flashed
                                  the microSD with Etcher, and plugged
                                  it in.<br class="">
                                  <br class="">
                                </blockquote>
                                <div class=""><br class="">
                                </div>
                                <div class="">
                                  <div class="">That sounds like a kernel
                                    problem.  I know that the 3B+ needs
                                    a newer kernel.  I don't think that
                                    was reflected in Raspbian until at
                                    least the RPi 3B+ release date of
                                    3/14/18.</div>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">There may be a way for you to
                                    only upgrade the kernel by chrooting
                                    into that distribution from another
                                    Raspberry Pi, perhaps by installing
                                    current Raspbian on another card and
                                    mounting the target 11/29/17
                                    Raspbian card with a USB reader.</div>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">It's a pain but I bet that will
                                    work.  I've done similar things with
                                    other single board computers.  The
                                    end will be 11/29/17 with an
                                    upgraded kernel.  Which version to
                                    pick is another story.  Perhaps the
                                    latest one, perhaps not.  You could
                                    try the oldest kernel made after
                                    3/14/18 I suppose.<br class="">
                                  </div>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">You might have to grab the actual
                                    .deb file and upgrade it manually
                                    with dpkg -i.  I'm not very familiar
                                    with Debian-based distributions. 
                                    Perhaps there is a limited upgrade
                                    apt command that will do it.<br class="">
                                  </div>
                                  <div class=""><br class="">
                                  </div>
                                  <div class="">Good luck.  If you get stuck I
                                    can do it in parallel here.  I have
                                    spare microSD cards and a RPi3B+.<br class="">
                                  </div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </blockquote>
                        <br class="">
                        So I downloaded the latest Raspbian for RP3+
                        (2018-06-27-raspbian-stretch.zip) and used
                        Etcher to flash it to a 32GB microSD and this
                        one booted fine.  I'm going to try and get
                        MythTV Lite running on it like I didn't know any
                        better and see what happens.<br class="">
                        <br class="">
                        Jim A<br class="">
                        <br class="">
                      </div>
                    </div>
                  </blockquote>
                  <div class=""><br class="">
                  </div>
                  Well this is interesting.  Mythtv light works okay on
                  the Raspbian  2018-06-27 and I did a full update. 
                  Then I install Mythtv Light.  I didn’t try much
                  performance tuning yet, but it seems to work fine. I’m
                  using HDMI video to a A/V receiver and the receiver
                  sends the audio to 5.1 speakers and video to my UHD
                  TV. Setting audio to OpenMAX:hdmi and Video Playback
                  profile to OpenMAX Normal.  </div>
                <div class=""><br class="">
                </div>
                <div class="">I can see some performance issues, but I still have
                  to play with tuning.</div>
                <div class=""><br class="">
                </div>
                <div class="">I did get my Harmony Smart Hub remote paired to the
                  bluetooth on the RP3+. No issues there.</div>
                <div class=""><br class="">
                </div>
                <div class="">I’ve bought a MPEG2 license but I don’t have the
                  code yet.</div>
                <div class=""><br class="">
                </div>
                <div class="">More later after I’ve had time to tune.</div>
                <br class="">
              </div>
            </blockquote>
            <div class=""><br class="">
            </div>
            <div class="">Good.  Chroot is a pain.  But doable.</div>
            <div class=""><br class="">
            </div>
            <div class="">It looks like the firmware in the older image is the
              culprit and not the kernel as I thought:</div>
            <div class=""><br class="">
            </div>
            <div class=""><a href="https://github.com/Debian/raspi3-image-spec/issues/12" moz-do-not-send="true" class="">https://github.com/Debian/raspi3-image-spec/issues/12</a>
              <br class="">
            </div>
            <div class=""><br class="">
            </div>
            <div class="">All I know is, there was a Raspbian image that was
              released before 3/14/18.  I tried it on my 3+ and it
              didn't work, blinked like you said.  2 days later, the fix
              was out.  It was a hot topic on the forums at the time.  I
              just had to do a full upgrade with an older Rpi 2 and then
              it booted.<br class="">
            </div>
            <div class=""><br class="">
            </div>
            <div class="">If you have problems, and it sounds like you don't have
              any glaring ones, my offer still stands.  I can try going
              through in the next day or so and give you the steps.  It
              won't take me long.<br class="">
            </div>
          </div>
        </div>
      </div>
      <br class="">
    </blockquote>
    <br class="">
    I did a little more playing late last night. On a fully updated
    2018-06-27-raspbian-stretch.zip on my new Canakit RP3+ using a <span id="productTitle" class="a-size-large">Samsung 32GB EVO Plus Class
      10 Micro SDHC I added the repo for Mythtv light for stretch
      version 29. Then I basically followed the wiki guide:<br class="">
    </span><font size="+1" class=""><tt class=""><span id="productTitle" class="a-size-large">1. </span></tt><tt class=""><span id="productTitle" class="a-size-large">Configure <code class="">gpu_mem=256</code>
          using <code class="">sudo raspi-config</code></span></tt><tt class=""><br class="">
      </tt><tt class=""><span id="productTitle" class="a-size-large"><code class="">2. I
            bought and configured a MPEG2 license.<br class="">
            3. I selected OpenMAX Normal and OpenMAX:hdmi<br class="">
            4. I do the </code></span></tt></font><br class="">
    <pre class="">echo "performance" |sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

at reboot.

What is the best way to automate the echo "performance" command on each boot?

The only strange thing I see is with playing back recorded mpeg2 TV shows. The video seems to occasionally speed up and slow down like when a person is walking across the screen.  It's like then the sport replay guy is messing with the speed of replaying a touchdown run.
The audio does not sound different and there is no pitch change. It's also is correct lip sync.

I also installed Kodi 17.6. I works very well with no playback audio or video issues.  But I hate the user interface of Kodi 17, so I'm hoping to tweak Mythtv Frontend to fix the last few things.

So the latest Raspbian works on the latest RP3+ with Mythtv frontend.

Jim A
 
</pre>
    <font size="+1" class=""><tt class=""><span id="productTitle" class="a-size-large"><code class=""></code></span></tt></font><span id="productTitle" class="a-size-large"><code class=""></code></span><span id="productTitle" class="a-size-large"><code class=""><br class=""></code></span></div></div></blockquote><div><br class=""></div>I have a question about the MPEG2 license.  I put the “decode_MPG2=0x999999” code statement in my /boot/config.txt file.  After I rebooted I did the test statement “vcgencmd codec_enabled MPG2” which says “enabled”</div><div><br class=""></div><div>I wanted to test with no MPG2 so I removed that decode_MPG2 statement in /boot/config.txt file, but after rebooting my "vcgencmd codec_enabled MPG2” command still returned “enabled”.  Is the MPEG2 codec turned on in the firmware permanently now????</div><div><br class=""></div><div>Jim A</div><div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><span id="productTitle" class="a-size-large"><code class="">
      </code></span>
    <blockquote type="cite" cite="mid:CAO_Sck5gc7KdU7Rbwpc+sXvS+AXyy-nKvYfWy7a27wKm1Ex4dw@mail.gmail.com" class="">
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br class="">
      <pre wrap="" class="">_______________________________________________
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>
    <br class="">
  </div>

</div></blockquote></div><br class=""></body></html>