<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/03/2018 02:51 PM, Peter Bennett
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f525128c-1b3f-3f3d-37d5-5877f2c05662@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/03/2018 02:08 PM, jksj wrote:<br>
</div>
<blockquote type="cite"
cite="mid:52a97f8e-b1f3-894a-b7ce-c1ff9812d370@googlemail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div class="moz-cite-prefix">On 29/06/18 23:48, Peter Bennett
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4ff1b746-97f1-289d-bb24-8701eb0a396e@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 06/29/2018 05:42 PM, jksj
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:90af62d7-6fef-64fb-2b3a-a4347e7fd002@googlemail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div class="moz-cite-prefix">On 29/06/18 21:36, Peter
Bennett wrote:<br>
</div>
<blockquote type="cite"
cite="mid:613d7145-9a97-c9e9-2a55-fb8446145161@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 06/29/2018 01:40 PM, jksj
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9eace80d-9d87-f47f-ca25-722773c8a46d@googlemail.com">Thanks
- successfully compiled and ran. Startup performance and
menu handling is fine. Playback OK (not deinterlaced)
for SD, useless for 1080i. Not being offered hardware
decoding with the patches applied. </blockquote>
Did you try selecting the "mediacodec normal" playback
profile? How do you know it is not using hardware
deecoding?<br>
<br>
What happens with 1080i playback?<br>
<br>
<blockquote type="cite"
cite="mid:9eace80d-9d87-f47f-ca25-722773c8a46d@googlemail.com">Will
try again once the patches are issued in case I screwed
up. The only real issue for compilation - is <a
moz-do-not-send="true"
href="https://android.googlesource.com/platform/bionic/+/master/docs/32-bit-abi.md">32-bit
ABI bugs</a> which requires that the compilation
option _FILE_OFFSET_BITS=64 to be removed. Presumably
this will limit file sizes to 2GB so probably makes 32
bit a none starter.<a moz-do-not-send="true"
href="https://android.googlesource.com/platform/bionic/+/master/docs/32-bit-abi.md"><br>
</a></blockquote>
Not necessarily - files are remote and are read by your
backend so I expect the 2GB limit on the frontend would
not matter.<br>
</blockquote>
<p>None of the mediacodec profiles appear in the list.
Presumably you only show those that are available - so
either I screwed the patch or the platform is not offering
it. Kodi uses mediacodec and shows the decoder in use as
amc-h264. Will try again with a clean build as soon as you
push the changes to git. Great work - many thanks.<br>
</p>
</blockquote>
That indicates that probably mediacodec was not enabled in
your build. In the patches, mythtv configure has lines added
to enable mediacodec if buildung for android. Check for
mediacodec in configure, also check the FFMPEG configure
output to make sure mediacodec was enabled.<br>
<br>
Did you apply the latest patch from the ticket?<br>
<br>
Peter<br>
<br>
</blockquote>
<p>Sorry for the slow response but there is an issue with the
patch on my system. The links from the android packaging
directory to the two new files are created to
mythtv/libs/libmyth instead of mythtv/libs/libmythtv where
they should be. If I hand create them it builds ok. <br>
</p>
<p>The patch 20180629_ff_rew_fixed runs as before with SD ok. <br>
</p>
<p>HD (1080i 50Hz) was much improved by the new codec,
previously the picture was virtually a slide show. Now it runs
without crashing but is unacceptably jerky. Both CPU cores are
running at 100% using H.264 mediacodec. Its a 2 core 1GHZ CPU
running in 2GBytes memory. You can tell it starts to swap at
playback start so the memory is barely enough.</p>
<p>Did not try anything else as basic playback was unacceptable
due to the machine being underpowered.<br>
</p>
</blockquote>
I have in the works a patch to reduce memory usage, which may
help. It is not ready and at the moment I am struggling with
another playback issue on Shield.<br>
<br>
Peter<br>
</blockquote>
I have added a new patch to the ticket, which reduces memory usage
and fixes some other issues. It is possible that you may have a
crash on playing 1080 content, let me know if that happens. I made a
fix for Shield Oreo and I hope it did not break playback on others.<br>
<br>
Peter<br>
</body>
</html>