04-15-2008, 09:08 PM | #16 | |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Quote:
Dale |
|
04-15-2008, 10:05 PM | #17 |
Murderous Mustela
Posts: 10,151
Karma: 47366760
Join Date: Oct 2006
Location: The other land of schnitzel and beer
Device: iPad M1 Pro, Kindle Paperwhite
|
The screens do not appear to flash specifically to black. Rather they "invert". It only seems to go black because there are far more white pixels on your average page.
Last edited by Dylrob; 04-15-2008 at 10:14 PM. Reason: minor rewording |
04-16-2008, 12:54 AM | #18 |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
|
04-16-2008, 03:54 AM | #19 |
The Introvert
Posts: 8,307
Karma: 1000077497
Join Date: Jan 2007
Location: United Kingdom
Device: Sony Reader PRS-650 & 505 & 500
|
Dunno about black/white but I find flashing of prs-500 a lot more pleasant than of prs-505 (unfortunately).
|
04-16-2008, 06:00 AM | #20 | |
Connoisseur
Posts: 66
Karma: 918
Join Date: Dec 2007
Device: iRex Iliad
|
Quote:
It would be very beneficial if the controller supported arbitrary sub-area refreshes, and a few of those areas in parallel perhaps. For the first uses of e-Ink displays, it probably wasn't a big deal that you update the whole screen at once since you'd probably be displaying a whole new page anyway. Since it turns out that people want to use the displays for popup menus and even typing or scribbling, having partial screen updates is the next logical thing to implement. I noticed that in the iLiad displayManager there is an API for partial screen updates which is "not implemented", yet the scribble library offers "fast point updates" by directly talking to the driver. Perhaps some of the functionality is already in the current hardware. |
|
04-16-2008, 06:17 AM | #21 | |
Connoisseur
Posts: 58
Karma: 344
Join Date: Dec 2007
Device: Sony PRS-500, PRS-505
|
Quote:
|
|
04-16-2008, 07:15 AM | #22 | ||
Murderous Mustela
Posts: 10,151
Karma: 47366760
Join Date: Oct 2006
Location: The other land of schnitzel and beer
Device: iPad M1 Pro, Kindle Paperwhite
|
Quote:
Last edited by Dylrob; 04-16-2008 at 07:16 AM. Reason: typo |
||
04-16-2008, 08:00 AM | #23 |
Enthusiast
Posts: 43
Karma: 432
Join Date: Nov 2006
Location: Connecticut
Device: Sony PRS-500
|
You should be confused because that's marketing speak, or a confused tech journalists. The "electronic" refresh rate of the current panels and controllers is 50Hz, that being said, it takes several passes at 50Hz to get where you need to.
|
04-16-2008, 10:49 AM | #24 |
Zealot
Posts: 103
Karma: 269
Join Date: Aug 2006
Device: FBReader on Android
|
And my point was that of course those features are beneficial, but they should be implemented in software first (and that they should have been implemented in software years ago). Putting stuff in hardware is a form of optimization, and premature optimization is usually suboptimal at best and very counter-progress at worst.
|
04-16-2008, 11:41 AM | #25 | |
Enthusiast
Posts: 43
Karma: 432
Join Date: Nov 2006
Location: Connecticut
Device: Sony PRS-500
|
Quote:
As well, this isn't "premature optimization", this is the result of many years of research, engineering, and refinement. As I said before, I've seen what this controller is capable of, and I am certain this could not be achieved in software on a mobile device. |
|
04-16-2008, 12:21 PM | #26 | ||||
Zealot
Posts: 103
Karma: 269
Join Date: Aug 2006
Device: FBReader on Android
|
Quote:
Quote:
Quote:
Quote:
Still, that's beside the point. I've myself designed libs that did amazing things, yet it turned out that the devs wanted to do completely different things, for which my lib wasn't at all optimized or even designed for in the first place. The point is, you really don't know what the app devs will want before they actually want it. And even then much of it actually turns out to be wrong, since they often don't even know it themselves before they've implemented their stuff. Some stuff you can predict with a high level of certainty, but surprisingly much you can't. Therefore you want as much flexibility as possible as late in the game as possible. Committing optimizations to hardware before having all app devs try different software versions of it is not being flexible. It works to some degree for "old" fields, such as CPU, or even GPU, designers (but even there we've seen many, many failures), but not so much for new stuff like e-book interfaces on slowly refreshing displays. |
||||
04-16-2008, 12:32 PM | #27 |
The Introvert
Posts: 8,307
Karma: 1000077497
Join Date: Jan 2007
Location: United Kingdom
Device: Sony Reader PRS-650 & 505 & 500
|
So very complicated...
Anyway, just to dilute the tech discussion, I would like to say that I expected this announce or something similar. Last year, around the same time viziplex was announced that allowed eInk readers to make a new generation model. I though, that if something like that doesn't happen, how will they justify a new model (which is faster, better, whiter, sweeter, ...etc., you get the general idea?). Here we go, a new controller, means we get new generation readers soon and will spend more money for a whiter/faster/better brand new eInk screen with a super duper new controller. They know very well what they are doing |
04-16-2008, 01:09 PM | #28 | |
Grand Sorcerer
Posts: 19,832
Karma: 11844413
Join Date: Jan 2007
Location: Tampa, FL USA
Device: Kindle Touch
|
Quote:
BOb |
|
04-16-2008, 01:11 PM | #29 | ||||
Enthusiast
Posts: 43
Karma: 432
Join Date: Nov 2006
Location: Connecticut
Device: Sony PRS-500
|
Quote:
Not to mention most embedded processors have an LCD controller of some sort, so it's not like this is an unheard of even for simplier display technologies http://www.intel.com/design/embedded...ors/302302.htm look at that, an LCD controller built right on the die of the processor. This sort of controller is largely abstracted from the developer as just putting data into the frame buffer. Quote:
Quote:
Quote:
|
||||
04-16-2008, 02:04 PM | #30 | ||||
Zealot
Posts: 103
Karma: 269
Join Date: Aug 2006
Device: FBReader on Android
|
Quote:
Also, what you described takes neither memory (1-4 bytes/pixel seems enough) nor time (small LUTs seems enough). Quote:
Quote:
Quote:
OTOH, the optimizations might turn out to be very good, and in that fortunate case => happy happy joy joy Last edited by msundman; 04-16-2008 at 02:12 PM. |
||||
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Epson Controler for Color E Ink | wallcraft | News | 2 | 08-01-2010 11:02 AM |
Epson and E Ink Announce a New EPD Controller | Jason | News | 3 | 10-11-2009 11:00 PM |
Display or controller damaged | netseeker | Sony Reader | 16 | 01-08-2009 09:10 AM |
Seiko Epson produces hi-res E Ink display | Alexander Turcic | News | 38 | 11-23-2007 12:00 PM |
Next E Ink e-reader from Epson? (speculation) | TadW | News | 4 | 04-14-2007 03:25 PM |