2016-12-26, 16:51
2016-12-26, 16:53
(2016-12-26, 16:47)goodton Wrote:(2016-12-26, 15:21)FernetMenta Wrote: That was mainly logging in this build. I kicked off another one that increases number of render buffers.
My hypothesis:
Your NVidia gfx uses 2 back references for rendering video. This reduces number of free buffers and number of queued video frames into renderer. As a result renderer can't drop late frames. Bringing up the OSD or some other UI elements for rendering slightly changes timing so an additional video frames can be queued.
Ok, good that there is at least a possible explanation to this issue. Assuming that your hypothesis proves to be true, what can we do? And is this only NVidia-specific problem?
Try new build. So far I haven't seen an intel system with that many back and forward refs. In general Intel does not have a single forward ref.
2016-12-27, 15:42
2016-12-27, 23:24
I have finally got v17 (latest beta) working.. Im not 100% sure what got it working, but I played around with the video driver (ubuntu) - changing from v304 to 340 (as suggested earlier in the thread), but that made it alot worse.. I then went back to 304 and it now seems to work fine.
I still have an issue when plugging in the VGA cable for my projector - setting "Adjust display refresh rate" to OFF improved this to the point where it is not a big problem, however there is occasional tearing.. I am sure this is down to the video driver on the machine, nothing to do with Kodi..
So, result for me, but I will be keeping an eye on this thread to see if you guys gets the issue resolved for @goodton.
Thanks for the help.
I still have an issue when plugging in the VGA cable for my projector - setting "Adjust display refresh rate" to OFF improved this to the point where it is not a big problem, however there is occasional tearing.. I am sure this is down to the video driver on the machine, nothing to do with Kodi..
So, result for me, but I will be keeping an eye on this thread to see if you guys gets the issue resolved for @goodton.
Thanks for the help.
2016-12-27, 23:58
(2016-12-27, 20:11)FernetMenta Wrote: could you post debug log please
Of course
http://pastebin.com/7eXByYRg
2016-12-28, 00:02
(2016-12-27, 23:24)runel Wrote: I have finally got v17 (latest beta) working.. Im not 100% sure what got it working, but I played around with the video driver (ubuntu) - changing from v304 to 340 (as suggested earlier in the thread), but that made it alot worse.. I then went back to 304 and it now seems to work fine.
I still have an issue when plugging in the VGA cable for my projector - setting "Adjust display refresh rate" to OFF improved this to the point where it is not a big problem, however there is occasional tearing.. I am sure this is down to the video driver on the machine, nothing to do with Kodi..
So, result for me, but I will be keeping an eye on this thread to see if you guys gets the issue resolved for @goodton.
Thanks for the help.
Great that you got your case solved. But I have a hunch, that if @FernetMenta is able to solve this puzzle, it will serve also bigger audience.
2016-12-28, 00:19
Regarding if this is Nvidia only problem, it's not. I have the same thing with an AMD APU in Windows 10 x64. I don't see the problem in LibreELEC though on the same system.
I made this ticket about it a little while ago: http://trac.kodi.tv/ticket/17100 . Didn't notice that bringing up the OSD helps until i saw this thread.
I made this ticket about it a little while ago: http://trac.kodi.tv/ticket/17100 . Didn't notice that bringing up the OSD helps until i saw this thread.
2016-12-28, 10:24
here is a new build for testing: http://mirrors.kodi.tv/test-builds/win32...erloop.exe
2016-12-28, 12:49
(2016-12-28, 10:24)FernetMenta Wrote: here is a new build for testing: http://mirrors.kodi.tv/test-builds/win32...erloop.exe
Build tested, no visual improvement. Debug log attached:
http://pastebin.com/5gr2ghPC
2016-12-28, 15:13
2016-12-28, 15:53
(2016-12-28, 15:13)FernetMenta Wrote: new build: http://mirrors.kodi.tv/test-builds/win32...erloop.exe
would be nice to see a debug log
As there is now much more information in the debug log, I exceeded the max. paste-size in paste.bin for a non-pro user The actual log session is little bit shorter now to fit. Debug log here:
http://pastebin.com/4R8aTtWZ
2016-12-28, 19:01
Here's a log with the latest test version: https://drive.google.com/open?id=0BzfYgu...1IxY09Od1E
What i noticed while logging is also that the debug info FPS keeps switching between 23.4 and 24.4 fps every second or so.
Thanks for trying to help!
What i noticed while logging is also that the debug info FPS keeps switching between 23.4 and 24.4 fps every second or so.
Thanks for trying to help!