We asking all new users to read the articles below, before creating their first posting or thread.
Please note, in this forum are only English threads and postings allowed, without any exception!
Please follow the forum rules, thank you for your understanding.
Good day! I have a question about AFR. I suspect that when it's on, it matches the output frame rate to that of the input.
But what is the default frame rate of the output when AFR is off?
I've seen (via INFO)
1920 @ 60 fps
1280 @ 60 fps
1280 @ 30 fps
1280 @ 24 fps
864 @ 30 fps
Does it upscale low frame rates and downscale high frame rates when AFR is off and match them when it is on? 
Thanks for any replies.
Just a bump to the thread. Do most users use AFR? The only place I seem to notice a benefit is a channel with a chyron like CNBC. But I find the 2 second black screen on channel changes annoying, too. Thanks again for any replies. 
But what is the default frame rate of the output when AFR is off?
Depends from stream/channel,category . Most EU have 25/50fps and USA for example 25/60fps.
I will jump in. Why on earth when I turn AFR on there is 50 FPS square on every single channel, but the info button bringing stream details show 25 FPS?
Info shows only the streamed details from provider to your box (how the signal/data comes in) and AFR shows you what the box generate after stream is received. Provider stream 25 FPS -> AFR do his job on the box -> box shows you 50 FPS. For directly streamed 50 or 60 FPS channels from Provider, the AFR recognise that and do nothing.
AFR (auto frame rate) – is function which designed to match the media player's output frame rate to the original frame rate of (video) content. This applies to content that's mastered at different frame rates, for example 24fps film-based content or other international video content encoded at 60, 50, 30, 25, and 24fps.
Media player output frame rates will also match (and switch) the display's refresh rate appropriate for your region. For example 29.97fps for NTSC. 25fps and 30fps content uses frame rate doubling to display at 50Hz and 60Hz when available, matching its original appearance while preserving a fluid user interface.
For TV Box is important to have AFR in the system to make sure all the content plays in high quality.
System AFR can be implemented both through separate StageFright and through MediaCodec libraries with output to SurfaceView, and for two at once. For example, in MX Player (HW) with any content, even with HLS (HTTP Live Streaming). In fact, it is a universal crutch. Software cannot even detect that AFR is working and the output mode is changing. Since this is a universal solution, this kind of AFR can cause problems in some cases. For example, in some software there can be an intermediate switching while rewinding. In IPTV-managers, there can be extra switchings while changing channels, etc.
Modern AFR (fully implemented in the Android 6+ API) for processing in Kodi 17+, ViMu (with ViMu Engine), Archos, Plex, etc.
That means software (video players) independently control the resolution and the frequency of the display in the necessary way, accordingly to software logic. At the same time, everything that APP does not going to spread beyond the software (i.e. when APP stopped, and the system itself restored to the standard parameters). This is the ideal AFR implementation and this is the future. The problem only few TV Box manufacturers implement such abilities for AFR.
The first frame is converted to two, the second to 3, the third to 2, the fourth to 3, and so on. So 24 frames become 60 frames. Simple, but it leads to the judder effect - unevenness – part of frames are displayed 1/30 of a second, and the other one’s 1/20 of a second. To get rid of the judder effect, the frequency of the display should match the frame rate in the video. Therefore, for 24p video you need a display frequency of 24 Hz. In this case, each frame will display an equal amount of time and will be perfect.
Hi-End TVs have a function, which helps to rebuild the input sequence of frames. For example, TV Box set HDMI out for these parameters: 60 Hz. During 23.976p / 24p video playing, TV Box does standard 3: 2 pull down conversion and outputs 60p framerate. The TV input determines this sequence and reassembles it back to the original 23.976p / 24p. With such a TV, in fact, it doesn’t matter whether TV Box has auto-frame support or not - uniformity will always be perfect when playing 23.976p / 24p.
Info shows only the streamed details from provider to your box (how the signal/data comes in)
How accurate this details are? Provider is sending me screenshots from his server side api showing a channel 50 FPS and streaming approx. 18.000 Kbps, while MOL2 is showing the same channel 25 FPS but confirming the streaming rate.
How accurate this details are? Provider is sending me screenshots from his server side api showing a channel 50 FPS and streaming approx. 18.000 Kbps, while MOL2 is showing the same channel 25 FPS but confirming the streaming rate.
Check with VLC.
How accurate this details are?
I can tell you only what i know, if you want to research deeper then you have to speak with some of the developers from used protocol and MOL2. AFR shows me what i expect from such setting and that is all i need as user.
So it is possible that the details are not really accurate. I have seen on another popular IPTV app that the 50 FPS means nothing, as the stream is 25 FPS.
Mevi that's for M3U lists only, on that particular provider I have MAC portal access.
So it is possible that the details are not really accurate.
It is also possible that the info about send 50fps from Provider also are not accurate 
