Ballerburg9005 has quit [Ping timeout: 265 seconds]
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #linux-amlogic
tolszak has joined #linux-amlogic
camus has quit [Remote host closed the connection]
camus has joined #linux-amlogic
Daanct12 has quit [Read error: Connection reset by peer]
Daaanct12 has joined #linux-amlogic
zkrx has quit [Ping timeout: 268 seconds]
zkrx has joined #linux-amlogic
Daaanct12 has quit [Quit: Quitting]
tolszak has quit [Ping timeout: 268 seconds]
tolszak has joined #linux-amlogic
camus has quit [Quit: camus]
camus has joined #linux-amlogic
Ballerburg9005 has joined #linux-amlogic
shoragan has quit [Ping timeout: 240 seconds]
shoragan has joined #linux-amlogic
shoragan has quit [Quit: quit]
shoragan has joined #linux-amlogic
shoragan has quit [Client Quit]
shoragan has joined #linux-amlogic
shoragan has quit [Ping timeout: 268 seconds]
shoragan has joined #linux-amlogic
chewitt has joined #linux-amlogic
jernej has joined #linux-amlogic
<chewitt>
Cheaterman: reading the backlog .. the 'off by one' error you mentioned the other day has been noted before but I was never able to pin down a repeatable scenario for it
shoragan has quit [Quit: quit]
<chewitt>
it shows up in Kodi playback sometimes as a pink line on the bottom of the screen
shoragan has joined #linux-amlogic
<chewitt>
and occasionally when bringing up the OSD overlay.. if you keep toggling it on/off/on/off/etc. it keeps shifting and the black shadow of text keeps drifting by 1px
shoragan has quit [Ping timeout: 246 seconds]
<chewitt>
IIRC the OSD plane is in-front of the video output plane, so the pink line is probably alpha channel showing because the transparent object we write to the OSD plane (to punch a hole and expose the video plane) being incorrectly sized
shoragan has joined #linux-amlogic
<chewitt>
I have fuzzy recall that I don't see this on a proper TV, but I do see it with a 10" 1080p LCD which has more limited display capabilities
<chewitt>
(not sure any of that helps .. and apologies if any of it sounds like I understand what I'm talking about)
buzzmarshall has joined #linux-amlogic
<lvrp16>
chewitt: cyph84 had a simliar issue, it doesn't occur for me on any of the 1080P display in my possession. he said he had the issue with 59.94Hz screens and such so I assumed it was a timing issue.