Artificial reason of ghosting in <1ms OLED. Why it was done like that?
Posted: 04 May 2020, 16:36
Hello BlurBusters! (Chief, I hope you will check this as I never saw someone talk about this).
First of all I've already read this https://blurbusters.com/faq/oled-motion-blur/ and my question is not about this:
We know that <1ms OLED still have motion blur because of high MPRT (16.6ms on 60Hz). However when I run ufo ghosting test on Meizu Pro 6 (AMOLED screen) it has very big ghosting (ghosting, not blur because of MPRT). It surprised me a lot, because accordingly to RTINGS measurements OLED has ~0.1-0.5ms of color transitions. I've wrote my own grey color changer (from 0 to 255 and other shades), run it on Meizu and recorded with 960fps camera (video attached).
On this video we see rolling scan (16.6ms because it's 60Hz) and this scan changes color instantaneously (camera has 1 frame per 1 ms of real life so transitions have <1ms). Still it doesn't explain why there is ghosting. But here is strange thing.
If you will check frame by frame (or at 0.25x speed) transition from 0 to 255 (4th square on top on the left side) you will see that scanout switch pixel not from 0 to 255, but from 0 to ~127 - wait 16.6ms for new scanout - ~127 to ~230 - wait 16.6ms for new scanout - ~230 to real 255 (pure white) and so here is reason of ghosting. With <1ms response time screen do not change 0 to 255, but stretches this transition in time and since it's done once per scanout - we have real response time of 3xscanout time ~ 50ms. (It does same thing for other big transitions, but 0-255 is easy to demostrate)
I hope you understood all this info (check picture for details please). My questions are: is it known? does this technique has some name? If so, then why it's needed? Why we split 1 transition across multiple scanouts and increase response time artificially?
My theory is that true 0.1ms response time on low Hz screen (like 60Hz) will introduce stutters that people do not like. Imagine you change your IPS phone with >20ms responce time to 0.1ms OLED which has no ghosting at all and so it amplifies stutters (RTINGS talk about this issue when they review OLED TVs, but since TV shows 24fps video content it's more clear why it's important) I don't understand why it's used on 60Hz phones. Or maybe I wrong and OLED tech is not designed to have so fast changes in brightness (like transition from off state to full bright 255 can reduce lifespan and so we better to split this transition to multiple transitions so pixel will not be overloaded). But from what I see in RTINGS OLED review - TVs do not use it, they change from 0 to 255 instantly - https://i.rtings.com/images/reviews/tv/ ... -large.jpg On the other hand I don't have other OLED phones so I can't check existence of this trick on other phones.
So overall what is true? If this tech has special name then I will be happy to google it, but so far I can't find answer.
Video: https://drive.google.com/open?id=1I73CE ... q2LtWJr6qi
If you don't want download this, here is example how 0-255 transition was splitted to multiple phases. It doesn't fade between scanouts like LCD. It changes color shade instantly when scanline triggers it.
Thanks
First of all I've already read this https://blurbusters.com/faq/oled-motion-blur/ and my question is not about this:
We know that <1ms OLED still have motion blur because of high MPRT (16.6ms on 60Hz). However when I run ufo ghosting test on Meizu Pro 6 (AMOLED screen) it has very big ghosting (ghosting, not blur because of MPRT). It surprised me a lot, because accordingly to RTINGS measurements OLED has ~0.1-0.5ms of color transitions. I've wrote my own grey color changer (from 0 to 255 and other shades), run it on Meizu and recorded with 960fps camera (video attached).
On this video we see rolling scan (16.6ms because it's 60Hz) and this scan changes color instantaneously (camera has 1 frame per 1 ms of real life so transitions have <1ms). Still it doesn't explain why there is ghosting. But here is strange thing.
If you will check frame by frame (or at 0.25x speed) transition from 0 to 255 (4th square on top on the left side) you will see that scanout switch pixel not from 0 to 255, but from 0 to ~127 - wait 16.6ms for new scanout - ~127 to ~230 - wait 16.6ms for new scanout - ~230 to real 255 (pure white) and so here is reason of ghosting. With <1ms response time screen do not change 0 to 255, but stretches this transition in time and since it's done once per scanout - we have real response time of 3xscanout time ~ 50ms. (It does same thing for other big transitions, but 0-255 is easy to demostrate)
I hope you understood all this info (check picture for details please). My questions are: is it known? does this technique has some name? If so, then why it's needed? Why we split 1 transition across multiple scanouts and increase response time artificially?
My theory is that true 0.1ms response time on low Hz screen (like 60Hz) will introduce stutters that people do not like. Imagine you change your IPS phone with >20ms responce time to 0.1ms OLED which has no ghosting at all and so it amplifies stutters (RTINGS talk about this issue when they review OLED TVs, but since TV shows 24fps video content it's more clear why it's important) I don't understand why it's used on 60Hz phones. Or maybe I wrong and OLED tech is not designed to have so fast changes in brightness (like transition from off state to full bright 255 can reduce lifespan and so we better to split this transition to multiple transitions so pixel will not be overloaded). But from what I see in RTINGS OLED review - TVs do not use it, they change from 0 to 255 instantly - https://i.rtings.com/images/reviews/tv/ ... -large.jpg On the other hand I don't have other OLED phones so I can't check existence of this trick on other phones.
So overall what is true? If this tech has special name then I will be happy to google it, but so far I can't find answer.
Video: https://drive.google.com/open?id=1I73CE ... q2LtWJr6qi
If you don't want download this, here is example how 0-255 transition was splitted to multiple phases. It doesn't fade between scanouts like LCD. It changes color shade instantly when scanline triggers it.
Thanks


