[jonscaife]

I just updated from a nightly (KodiSetup-20180728-17729f35-master-x64) to Beta 2 on my windows machine and noticed the micro-stutter, rolled back and problem went away.  Found this posting afterwards hoping I wasn't the only one.  I really hope whatever causes this doesn't get wrapped into final release.

 Assuming we're experiencing the same problem it seems the nightly from 28th July didn't have it, but the nightly from 30th july does have it.  I don't know how to see what changes were made between these dates, no can I find an installer for the 28th july nightly to test on my system.  But I'm willing to bet that it is "smooth motion" that is responsible.

I'm tempted to git clone the source code, undo the smooth motion changes that I found and then build it myself as a test.  But it seems like a lot of faffing about

[fritsch]

I did that already, but you obviously won't find that in the Android forum where you highjacked a user's bugreport: https://forum.kodi.tv/showthread.php?tid...pid2764033 Build 2

[jonscaife]

I did that already, but you obviously won't find that in the Android forum where you highjacked a user's bugreport: https://forum.kodi.tv/showthread.php?tid...pid2764033 Build 2

 Thank you for the information and the build but the deint3 and deint4 builds are no longer available to download.  I would have liked to try the deint4 build.

Also I'd call it more "have the same problem on a different OS" than "hijacked".  The thread you linked to refers to a problem with deinterlacing - I have had no problem with deinterlacing so it would have been pretty difficult for me to associate that thread with my issue.  I did the best I could to post somewhere relevant, even if it doesn't "fit" neatly into the way the forums are structured.

[jonscaife]

Rather than wait I eventually gave in and compiled a modified kodi for myself.  I removed the smooth motion code.  And lo and behold I have no more horrible judder, just beautifully smooth TV again.

[fritsch]

Jep - @afedchin  spotted the issue. Problem was understood, but fix is pending. In short: smooth picture uses certain deinterlaced frames in a wrong way, reducing / removing previous / advancing frames used for post processing.

[jonscaife]

Jep - @afedchin  spotted the issue. Problem was understood, but fix is pending. In short: smooth picture uses certain deinterlaced frames in a wrong way, reducing / removing previous / advancing frames used for post processing.

 Great stuff - thanks for the update.  I look forward to a version with the fix included

[Eddie Strike]

Great work guys, can't wait to ttest the fix. Please post in here when you've commited it

[dcol]

The mico-stutter is very annoying. Just have an option in settings>display for turning off the smooth picture feature. Obviously it should be called 'jitter picture'. Using nightly build 9/24

[Martijn]

The mico-stutter is very annoying. Just have an option in settings>display for turning off the smooth picture feature. Obviously it should be called 'jitter picture'. Using nightly build 9/24

 or we actually try to fix the issue instead of adding pointless settings. likely a fix is already found and will be included at some point

[outcave]

Try this night build (kodi-20180924), the problem seems to be solved, see also here: https://github.com/xbmc/xbmc/pull/14470

[Nanomani]

Try this night build (kodi-20180924), the problem seems to be solved, see also here: https://github.com/xbmc/xbmc/pull/14470

This post become little confuse betweem android user and windows user. Same issue but not same fix.

for Windows user If I all understand the night build fixe also this isssue but with this PR :
https://github.com/xbmc/xbmc/pull/14472 

Kodi seems very tricky to keep him stable.
In all case thanks to all people who give their times for community and dev.

[outcave]

Try this night build (kodi-20180924), the problem seems to be solved, see also here: https://github.com/xbmc/xbmc/pull/14470

This post become little confuse betweem android user and windows user. Same issue but not same fix. 

Since this thread is on Android Forum, I refer to Android :-)

[Maelor]

Have you enabled/selected the whitelist resolutions in the Settings/System/Display section?

How many resolutions should appear in the list in settings?

On my HiMedia Q10 I'm only being offered one: 1920x1080p 60.00 Mhz.
On my Samsung Galaxy Tab S3 I'm only being offered one: 2048x1536p 60.00 Mhz.
Is this normal?

[outcave]

Have you enabled/selected the whitelist resolutions in the Settings/System/Display section?

How many resolutions should appear in the list in settings?

On my HiMedia Q10 I'm only being offered one: 1920x1080p 60.00 Mhz.
On my Samsung Galaxy Tab S3 I'm only being offered one: 2048x1536p 60.00 Mhz.
Is this normal?

You should find all the resolutions available on your system.
On Android mobile phone it's quite normal to have only one in the list.

[atc98092]

I haven't observed any stutter with my Shield, including some UHD rips. I'm using Beta 2 and have every available resolution white-listed. TV is a 55" Samsung JU7100, fed through a Yamaha AVR. HDR and all lossless audio codecs work fine, including Atmos and DTS:X.