Mailing List Archive

On 16/11/2019 14:44, Paul Gardiner wrote:
> One thing I've always loved about MythTV on my nvidia ION based frontend
> and hated about using Netflix and Amazon Prime on my Fire TV is
> automatic frame rate matching (well that on my frontend, and the lack of
> it on Fire TV). However, I've recently read this:
> http://www.aftvnews.com/explanation-of-the-new-frame-rate-matching-feature-on-the-amazon-fire-tv/
> and realised that I may be seeing the problem partly because my Fire TV
> box is very old. Can anyone tell me if the Mythfrontend app supports
> this when running on modern Fire TV sticks?
>
> (I've lied a little: actually my nvidia ION based frontend has recently
> lost this feature. I'd also love to know how to correct that.)
>
> Cheers,
>     Paul.

My FireTVstick 4k says it has the framerate adjustment enabled, but
using the 31Pre539 build I don't see the 'Separate video modes for GUI
and TV playback' option that is offered in the 31Pre1232 2019-render
branch. It just says 'Use GUI size for TV playback'

I haven't looked at the log with this question in mind. Playing a
BBCFour HD recording with 6-channel sound and ffmpeg decoding, the
displayed A/V Sync value flickers around, usually in the +/- 20 ms
range. The 4 CPUs are often at around 90%, and stuttering can occur.

FWIW, the leanfront build won't play that recording at all, but I looked
at BBCOne HD's 'Earth from space' recordings last night and playback was
excellent. Some h264 content plays, some not...

John

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 16/11/2019 15:33, John Pilkington wrote:
> On 16/11/2019 14:44, Paul Gardiner wrote:
>> One thing I've always loved about MythTV on my nvidia ION based
>> frontend and hated about using Netflix and Amazon Prime on my Fire TV
>> is automatic frame rate matching (well that on my frontend, and the
>> lack of it on Fire TV). However, I've recently read this:
>> http://www.aftvnews.com/explanation-of-the-new-frame-rate-matching-feature-on-the-amazon-fire-tv/
>> and realised that I may be seeing the problem partly because my Fire
>> TV box is very old. Can anyone tell me if the Mythfrontend app
>> supports this when running on modern Fire TV sticks?
>>
>> (I've lied a little: actually my nvidia ION based frontend has
>> recently lost this feature. I'd also love to know how to correct that.)
>>
>> Cheers,
>>      Paul.
>
> My FireTVstick 4k says it has the framerate adjustment enabled, but
> using the 31Pre539 build I don't see the 'Separate video modes for GUI
> and TV playback' option that is offered in the 31Pre1232 2019-render
> branch.  It just says 'Use GUI size for TV playback'
>
> I haven't looked at the log with this question in mind.  Playing a
> BBCFour HD recording with 6-channel sound and ffmpeg decoding, the
> displayed A/V Sync value flickers around, usually in the +/- 20 ms
> range.  The 4 CPUs are often at around 90%, and stuttering can occur.

I found the 'System X-Ray' display: 1080P 59.93, IIRC

MythTV OSD shows Video 1920x1089@25.00fps, FPS reported around 25 but
seems to be varying over a wider range now than when I started writing
this, when it was usually between 24.9 and 25.1 +/- 0.1

The CPU overload stutter is the main problem here. It's probably worse
with an active playback data display. DLNA still gives me the best
linear playback experience, with less wobble in slow panning shots, then
nVidia, then the Firestick stutter. But see below:

>
> FWIW, the leanfront build won't play that recording at all, but I looked
> at BBCOne HD's 'Earth from space' recordings last night and playback was
> excellent.  Some h264 content plays, some not...
>
> John
>

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sat, 16 Nov 2019 at 14:45, Paul Gardiner <lists@glidos.net> wrote:
>
> One thing I've always loved about MythTV on my nvidia ION based frontend
> and hated about using Netflix and Amazon Prime on my Fire TV is
> automatic frame rate matching (well that on my frontend, and the lack of
> it on Fire TV). However, I've recently read this:
> http://www.aftvnews.com/explanation-of-the-new-frame-rate-matching-feature-on-the-amazon-fire-tv/
> and realised that I may be seeing the problem partly because my Fire TV
> box is very old. Can anyone tell me if the Mythfrontend app supports
> this when running on modern Fire TV sticks?

The myth code has no support for switching the display frame rate on
Android - although I'm sure it is possible. (and the relevant settings
should probably be disabled if frame rate switching isn't available on
any given device/platform).

What Android and/or MediaCodec do is a different question however.
MediaCodec is a bit of a black box when it come to functionality. You
don't really know what you are going to get back from the decoder.
Whether under the hood there is any display configuration is also a
relative unknown.

If your device is changing the display frame rate at any point, you
would mostly likely see the usual display blanking for a short period
of time while it resets. I've never seen this on the Shield.

Android/MediaCodec also has a different render path - can't remember
the name of it atm (something like protected path??). Using this
route, the OS effectively takes ownership of the media and handles
everything - so it is conceivable that apps using this path will see
different results (e.g. support for HDR material on Shield). MyhTV
does not use this approach.

> (I've lied a little: actually my nvidia ION based frontend has recently
> lost this feature. I'd also love to know how to correct that.)

Something changed with more recent Nvidia drivers and what is returned
by libxnvctrl. I couldn't pinpoint the issue exactly as I didn't have
a 'before' and 'after'.

Anyway - it is fixed in the 2019-render branch - and hopefully the new
code is a little more robust.

Regards
Mark
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 17/11/2019 11:16, Mark Kendall wrote:
> On Sat, 16 Nov 2019 at 14:45, Paul Gardiner <lists@glidos.net> wrote:
>> (I've lied a little: actually my nvidia ION based frontend has recently
>> lost this feature. I'd also love to know how to correct that.)
>
> Something changed with more recent Nvidia drivers and what is returned
> by libxnvctrl. I couldn't pinpoint the issue exactly as I didn't have
> a 'before' and 'after'.
>
> Anyway - it is fixed in the 2019-render branch - and hopefully the new
> code is a little more robust.

That's great news. Thanks for the information Mark.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, 17 Nov 2019 at 11:16, Mark Kendall <mark.kendall@gmail.com> wrote:
> (and the relevant settings
> should probably be disabled if frame rate switching isn't available on
> any given device/platform).

Actually - I see that they are disabled:) (Just working on some
DRM/KMS modeswitching code).
Mark
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org