[mythtv-users] Andoid mythfrontend schema changed again

[John]

On 06/02/2022 15:04, James Abernathy wrote:
>
>
> On Sat, Feb 5, 2022 at 9:06 PM David Engel <david at istwok.net> wrote:
>
>     On Sat, Feb 05, 2022 at 04:55:26PM -0500, James Abernathy wrote:
>     > On Sat, Feb 5, 2022 at 3:55 PM Peter Bennett
>     <pb.mythtv at gmail.com> wrote:
>     > > I have built the latest mythfrontend fixes/32 and master for
>     android.
>     > > Download from the usual place.
>     > >
>     > > Peter
>     > >
>     >
>     > Thanks, I just installed the v32 64 bits on a Nvidia Shield TV.
>     It works
>     > great with my fixes/32 backend.
>
>     If you use the mediacodec-dec decoder, please give the improved,
>     mediacodec decoder a try.  It's working very well for me but I'd like
>     some feedback from others.
>
>     David
>     -- 
>     David Engel
>     david at istwok.net
>
>
> This morning I got around to testing the v32 32bit version of 
> mythfrontend on a FireTV 4K and a FireTV 4K MAX. Mediacode-dec is 
> unusable on those devices with freezes and crashes. I can make opengl 
> usable with 4 CPUs and Low-quality deinterlacing. I also have the 
> Audio read ahead set to 800ms. Anything lower causes issues.
>
> I occasionally  see jumps in playback that are hard to describe. It's 
> like the picture instantly jumps forward a few tenths of a second.  I 
> don't know if this is a Mythfrontend issue or the network provider's 
> original signal.  I notice this same problem on streaming services 
> like DirecTV streaming service. I know the bit rate on OTA signals has 
> fallen since the FCC repack occured.
> I'll retest the Shield TV on both Mediacodec and OpenGL to see which 
> is better if I can tell. But on the FireTV I have to use OpenGL to 
> make it usable.
>
> Jim A
>
>
>
Noting Jim's experience as reported above, mine is completely different 
with UK H264 recordings, read ahead set to 1000ms

In general worked well but live tv not usable.

Again in general android playback can be erratic in both Leanfront and 
Mythfrontend, by which I mean that occasionally (1 in 10)

playbacks either stall or seek doesn't work. These are generally from 
secondary channels that may have weaker signals or very compressed streams.

These issues are however none repeatable, next day the same recording 
could be fine.

Its probably a network timing issue as previously discussed.

Hopefully the improved mediacodec implementation in the frontend may 
resolve the problem. I could not get it to fail today.

Remote frontend MythTV Version : v32-Pre-3519-g0caf3ac0ec

Backend & local frontend MythTV Version : v32-Pre-3519-g0caf3ac0ec

Android version -20220205-arm-v32-Pre-3518-g81063d4add.apk

The v32 32bit version of mythfrontend worked fine for me on UK H264 25Hz 
1920i recordings.

On Shield Tv with mediacodec

Fire Stick 4K Max with Mediacodec

Fire Stick 4k Opengl without de-interlacing (Mediacodec suffers from judder)

Live TV core dumped on a remote Intel Frontend .

022-02-06 15:28:38.249116 I  TV::StartTV(): Entering main playback loop.
2022-02-06 15:28:40.306297 I  Player(1): Opening 
'myth://tv/20681_20220206152839.ts'
Handling Segmentation fault
Segmentation fault (core dumped)

On a local Intel Frontend

Worked but live tv unwatchable due to stutter.

Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: I CoreContext 
mythplayervideoui.cpp:159 (ProcessCallbacks) PlayerVideo: Executing 
VAAPI context creation
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: I CoreContext 
opengl/mythvaapiinterop.cpp:140 (InitaliseDisplay) VAAPIInterop: Created 
VAAPI 1.7 display for GL-VAAPI-DRM (Intel iHD driver for Intel(R) Gen 
Graphics - 20.1.1 ())
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: I CoreContext 
mythvideoout.cpp:174 (SetDeinterlacing) VideoOutput: SetDeinterlacing 
(Doublerate 1): Single Medium|CPU|GLSL|DRIVER Double Medium|CPU|GLSL|DRIVER
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: I CoreContext 
mythvideoout.cpp:174 (SetDeinterlacing) VideoOutput: SetDeinterlacing 
(Doublerate 1): Single Medium|CPU|GLSL|DRIVER Double Medium|CPU|GLSL|DRIVER
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: E CoreContext 
opengl/mythvaapiinterop.cpp:301 (SetupDeinterlacer) VAAPIInterop: VAAPI 
deinterlacer config failed - 'motion_adaptive' unsupported?
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: E CoreContext 
opengl/mythvaapiinterop.cpp:412 (Deinterlace) VAAPIInterop: Failed to 
create VAAPI deinterlacer 2x VAAPI Adaptive - disabling
Feb  6 13:53:33 tv mythfrontend: mythfrontend[5978]: I CoreContext 
opengl/mythopenglvideo.cpp:477 (SetupFrameFormat) GLVid: New frame 
format: None:None 1920x1080 (Tex: 2D) -> VAAPI:NV12 1920x1080 (Tex: 2D)
Feb  6 13:54:24 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   31.52 Mean: 31729 
Std.Dev: 58287 CPUs: 7% 9% 8% 8%
Feb  6 13:54:25 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   24.14 Mean: 41422 
Std.Dev: 78987 CPUs: 21% 71% 13% 44%
Feb  6 13:54:26 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.32 Mean: 39498 
Std.Dev: 78278 CPUs: 26% 97% 17% 11%
Feb  6 13:54:27 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   23.31 Mean: 42896 
Std.Dev: 70182 CPUs: 19% 50% 56% 16%
Feb  6 13:54:28 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   27.24 Mean: 36707 
Std.Dev: 72168 CPUs: 15% 10% 98% 20%

The same recording viewed in playback

Feb  6 13:52:56 tv mythfrontend: mythfrontend[5978]: I CoreContext 
opengl/mythvaapiinterop.cpp:140 (InitaliseDisplay) VAAPIInterop: Created 
VAAPI 1.7 display for GL-VAAPI-DRM (Intel iHD driver for Intel(R) Gen 
Graphics - 20.1.1 ())
Feb  6 13:53:06 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.01 Mean: 39986 
Std.Dev:   238 CPUs: 7% 8% 8% 7%
Feb  6 13:53:07 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.02 Mean: 39967 
Std.Dev:   279 CPUs: 20% 23% 15% 12%
Feb  6 13:53:08 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.01 Mean: 39980 
Std.Dev:   163 CPUs: 14% 23% 20% 3%
Feb  6 13:53:09 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.00 Mean: 39994 
Std.Dev:   137 CPUs: 9% 11% 19% 17%
Feb  6 13:53:10 tv mythfrontend: mythfrontend[5978]: I CoreContext 
jitterometer.cpp:127 (RecordEndTime) PlayerFPS:   25.01 Mean: 39976 
Std.Dev:   173 CPUs: 10% 12% 24% 11%

Strangely Live tv was ok on the Android 32 bit frontend apart from 
channel change still failing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220206/bc80f5ad/attachment.htm>