Libra 2 Kobo Libra 2 first impressions

[frostschutz]

Originally Posted by Krios

What is that black tape on the sides in post #146, mine doesn't have it?

I can only guess it may be related to the front light which may be bleeding out the sides and visible on the Libra 2 hull (maybe something specific to the white edition?) Or maybe its supposed to dampen any creaking but then all Libra's should have it, not just the white ones. In any case it was like that from the get go, other than trying to remove the microsd card, I didn't modify anything at all.

[Krios]

Originally Posted by frostschutz

I can only guess it may be related to the front light which may be bleeding out the sides and visible on the Libra 2 hull (maybe something specific to the white edition?) Or maybe its supposed to dampen any creaking but then all Libra's should have it, not just the white ones. In any case it was like that from the get go, other than trying to remove the microsd card, I didn't modify anything at all.

Thank you, mine is black, and sorry you had to repeat yourself, now i see you already wrote that in post #146.

[NiLuJe]

FWIW, a device-tailored CBZ in KOReader should be as fast as the screen can be driven, which is basically as fast as a Kindle can go, because it's also doing device-tailored files by default .

(For a random unoptimized CBZ, you'll have to eat the (small) cost of an extra scaling pass, which will mostly always be hidden away, since we preload the next page).

I have no idea why this takes forever in Nickel, but it does, extra scaling pass or not.

[Almamida]

Originally Posted by NiLuJe

FWIW, a device-tailored CBZ in KOReader should be as fast as the screen can be driven, which is basically as fast as a Kindle can go, because it's also doing device-tailored files by default .

(For a random unoptimized CBZ, you'll have to eat the (small) cost of an extra scaling pass, which will mostly always be hidden away, since we preload the next page).

I have no idea why this takes forever in Nickel, but it does, extra scaling pass or not.

Yes, I tried with the non optimized CBZ (~250MB vs ~92MB) and performance is pretty similar. It's so impressive!
The only thing that seems to "slow" the Libra is the refresh at every page. I don't know Lua at all but I'm curious if I can force Koreader to not refresh at every page for mangas to see if the screen handles as well as the Kindle.

[NiLuJe]

@Almamida: The default should be set to something like a flash every 6 pages or so, not every page (although I *do* recommend flashing every page for that type of content), so I'm not quite sure what you're talking about.

Note that (some?) OG Libras had a weird bug where waiting for flashing updates was utterly broken and had to trip a 5s timeout, so, define "slow" .

[Almamida]

“Slow” is super fast (I’m assuming the Paperwhite has the edge on speed because it does not fully refresh the page)
I tried to change the refresh rate but no matter what I select, it happens every page. So I thought that was overwritten / bypassed by Koreader because the content type is a picture. Maybe it’s a bug then.

[NiLuJe]

You can't not refresh the full screen when the full screen has changed content, so I'm still mildly puzzled ;o).

If, on the other hand, you're talking about panning or scrolling, then, yeah, the Kindle does that slightly differently. A plain old full-page switch, not really.

[NiLuJe]

Okay, actually watching the video helped ;o).

The Kindle is using a different waveform mode (my guess would be a regal one, probably REAGLD). I don't recall anyone ever doing that before, because REAGLD used to not be worth it over GC16. IIRC, the Kindle reader used to do the same thing as for text content, which is REAGL until a flash (which is what we do in KOReader, too).

I haven't checked that in a while, though, and a Libra 2 might behave differently than a Sage/Elipsa, and/or differently than a PW5 on that front .

EDIT: My Elipsa behaves similarly (i.e., no switch to black/mini flash on white gutters), as long as I don't flash on every page. (Because that enforces GC16 instead of REAGL).

TL;DR: Double-check that you're not requesting a full refresh every page in KOReader (Gear > Screen > E-ink settings > Full refresh rate).

[Almamida]

Originally Posted by NiLuJe

Okay, actually watching the video helped ;o).

The Kindle is using a different waveform mode (my guess would be a regal one, probably REAGLD). I don't recall anyone ever doing that before, because REAGLD used to not be worth it over GC16. IIRC, the Kindle reader used to do the same thing as for text content, which is REAGL until a flash (which is what we do in KOReader, too).

I haven't checked that in a while, though, and a Libra 2 might behave differently than a Sage/Elipsa, and/or differently than a PW5 on that front .

EDIT: My Elipsa behaves similarly (i.e., no switch to black/mini flash on white gutters), as long as I don't flash on every page. (Because that enforces GC16 instead of REAGL).

TL;DR: Double-check that you're not requesting a full refresh every page in KOReader (Gear > Screen > E-ink settings > Full refresh rate).

I found the culprit : It's the .mobi file. For some reason it fully refreshes at every page turn, no matter what setting I chose.

On the other hand, I tried again with the original CBZ... It refreshes every 6 pages like I ask it to... and it's even faster.

So the Libra2 under KOReader is faster than the Paperwhite in this case
To put things in perspective, the mobi file is 93.4MB on the Kindle and the CBZ is 309MB :




Just to compare, same files this time without KOReader on the Kobo :

[koboy]

Originally Posted by Almamida

I found the culprit : It's the .mobi file. For some reason it fully refreshes at every page turn, no matter what setting I chose.

On the other hand, I tried again with the original CBZ... It refreshes every 6 pages like I ask it to... and it's even faster.

So the Libra2 under KOReader is faster than the Paperwhite in this case
To put things in perspective, the mobi file is 93.4MB on the Kindle and the CBZ is 309MB :




Just to compare, same files this time without KOReader on the Kobo :

well done for solving it. how does pinch to zoom compare on both devices with Koreader installed on the Libra 2?

best wishes koboy

[NiLuJe]

Huh. Best assume we do not actually support MOBI, because, err, what little support there is is... fairly subpar .

(@koboy: I don't actually think we support pinch to zoom, outside of the image viewer, that is. And even if we did, I'd assume it to be somewhat slower.).

[koboy]

Originally Posted by NiLuJe

Huh. Best assume we do not actually support MOBI, because, err, what little support there is is... fairly subpar .

(@koboy: I don't actually think we support pinch to zoom, outside of the image viewer, that is. And even if we did, I'd assume it to be somewhat slower.).

thanks for clarifying.

best wishes koboy

[NiLuJe]

On the other hand, there are seven billion zooming modes designed to ensure that, if you actually feel like you need to pinch to zoom for something, you're doing it wrong .

[Almamida]

Originally Posted by NiLuJe

Huh. Best assume we do not actually support MOBI, because, err, what little support there is is... fairly subpar .

(@koboy: I don't actually think we support pinch to zoom, outside of the image viewer, that is. And even if we did, I'd assume it to be somewhat slower.).

That’s what I figured when things were different in some menu. I wanted to be fair and compare with the same file but there was no need.
Now I’m going to try again on the Sage, hoping the battery does not drain too much.

Thank you for your input all along. And thanks for your work on KOReader, it’s so impressive.

[jasius]

Originally Posted by Almamida

I found the culprit : It's the .mobi file. For some reason it fully refreshes at every page turn, no matter what setting I chose.

On the other hand, I tried again with the original CBZ... It refreshes every 6 pages like I ask it to... and it's even faster.

So the Libra2 under KOReader is faster than the Paperwhite in this case
To put things in perspective, the mobi file is 93.4MB on the Kindle and the CBZ is 309MB :




Just to compare, same files this time without KOReader on the Kobo :

It’s pretty sad that a people outside Kobo make better firmware than Kobo, but I LOVE KO Reader, so much so that it’s swayed me from a Paperwhite to a Libra 2.

KO Reader let’s me have the margins and spacing EXACTLY how I want them.