Quote:
Originally Posted by mikea
Hey Jaya ... please don't think we've deleted your post, honestly! We actually just had a few logistical issues - turns out our CMS required someone to approve the comment before it get's posted. Anyhow, now that we know we have to approve comments, we are!
|
Ah, whew! Ok, that is good to hear. I was feeling a bit hurt about that. But I'm okay now. Glad to hear from you and nice to meet you. :-)
Quote:
Originally Posted by mikea
But just to clarify, the flashing is needed in every scenario that I've seen in which quality grayscale is required - otherwise you'll get ghosting (many of you have probably seen this before). Going black-to-white can be more responsive, as you've shown.
BTW I really like the eyes in your last video there ;-)
|
Thanks.
Yes, I agree but only partially. Flashing is required to get rid of buildup, fully agreed. But I believe quality grayscale is achievable without flashing as I show in this Fennec on E-Ink video (
http://www.youtube.com/watch?v=k4WBdagDgSg ) The driver and/or the frontend application can both make a runtime determination whether to use a full flashing update mode or a non-flashing mode. In the demos that I've been doing, I've found that buildup is minimal, so a full flash after every 200 iterations of activity (would be better if I was doing flash based on every 200 iterations of significant content change) is sufficient to achieve good 16-level grayscale.