Quote:
Originally Posted by Hyphen-ated
Nah. My comparison is with reading text on my computer, which has something like 0.05s or less page turn delay for an epub.
Oh really! I looked at Koreader's list of features in the past and saw no claims about improved performance, which I figured would be a big deal they would want to brag about. I'll have to check it out.
|
It really depends on system EPD controller as we don't talk to eink directly on most devices. On devices that we race against system controller we win by a huge margin so we introduce delays to let the system driver finish its job before us to prevent artifacts:
https://github.com/koreader/koreader...id.lua#L37-L39
That says little about our own loop and a lot about how these devices weren't designed for fast page turns.
Even on serious devices where we talk to the EPD using ioctls there's nothing to brag about it. Requesting a refresh takes a fixed amount of time (which varies depending on the waveform, the mode, the region of the screen to refresh, what's actually on screen...). If we're fast or not depends on what happens before the ioctl is triggered.