Posts: 23,232
Joined: Aug 2011
Reputation:
1,069
fritsch
Team-Kodi Developer
Posts: 23,232
If your TV is dump and Limited Range there won't be a difference between xrandr: Full + kodi limited and xrandr: Video 16:235 and kodi limited.
xrandr: Limited Range 16:235 we have discussed now a lot does scaling by itself. This in combination with kodi's limited will produce gray for black and light gray for white.
Video Limited 16:235 xrandr setting will set Limited Infoframe _but_ won't scale colors and just let them passthrough.
As you see in my patch the (limited && !video_range) -> don't scale
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
2015-12-01, 22:24
(This post was last modified: 2015-12-01, 22:26 by FernetMenta.)
I would rather disable triple buffers than making it worse with tearfree. Throwing away frames at a different stage just to see the silly fps counter lying is no solution at all.
EDIT: also note that the introduced latency of frametime DOES harm. You notice on a/v sync and on GUI responsiveness.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
2015-12-01, 22:34
(This post was last modified: 2015-12-01, 22:35 by FernetMenta.)
It cures a/v sync because Kodi assumes double buffers NOT triple. Your work around sacrifices a/v sync for the sake of a more or less unimportant use case. There ore only a few dialogs where fps drops down and only when playing SD on lower end systems. Do you really think this is more important than a/v sync?
btw: I noticed improvement on my 1820T with double buffers. System Info does not drop to 25 fps.
Posts: 23,232
Joined: Aug 2011
Reputation:
1,069
fritsch
Team-Kodi Developer
Posts: 23,232
2015-12-01, 22:44
(This post was last modified: 2015-12-01, 23:11 by fritsch.)
Intel driver does default TRIPLE buffering NOT Double. You had TripleBuffers on, on your system enabled - until I told you about the defaults two days ago.
And your "Do you really think" - comment is fully out of context. The "Tearfree" was a blind test - as the developer told me: it does not influence full screen swaps at all - the blind test told us now otherwise ... and it will be off again.
Also: Users need solutions for running a browser next to kodi - for watching amazon prime / netflix / whatever ... choose between TearFree and compositing :-).
TripleBuffering is default on windows (Aero) and will be default on everything wayland - we can make a double buffer dance when this happens - but we need to cope with that in the future.
Edit: Yeah, just tested all combinations. If a browser is relevant to you - you won't get the tearing fixed at all, when TearFree is off. TearFree On instead will harm kodi (as seen above). So there is no nice solution available to get both, e.g. perfect kodi playback and DRM content via external providers through browser.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 98
Joined: Jun 2015
Reputation:
2
yes, if the chromium is used under openelec "tearfree on" is necessary. sadly i have also to switch to limited colors when browser is started because otherwise the browser is outputting in full range color.
btw: with OE r21585 audio are on many tv channels with dolby 2.0 not synced with picture. also is audio dolby 2.0/5.1 not in sync if there are errors in streams. on satellite this sometimes happend. is that already known or are logs necessary?
Posts: 23,232
Joined: Aug 2011
Reputation:
1,069
fritsch
Team-Kodi Developer
Posts: 23,232
Currently uploading new builds:
Changelog:
- Disable Tearfree as it failed and was proven to introduce sync errors
- Disable TripleBuffer as kodi uses a double buffer by default
For the future, everyone with sync problems also provide Xorg.0.log please - if TearFree is used - we already know it's the driver that is causing it.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.