slower page turning when tapping

[marp68]

I've had my Kobo Glo HD for about four months now and I'm really happy with reading on it. I have so far about 80 books.

But now I've noticed that every page turn have started to take longer time when tapping the screen, about 2 seconds. However, when sweeping, it goes faster and seems more normal.

Anyone experienced this and anyone knows how to speed up the page turn again when tapping?

I'm running 3.19 and have only epub files on it.

[GeoffR]

I've seen it happen with certain books.

I think the slow tap response compared to the fast swipe response is because with a tap the software has to check whether there is a link in the tap zone that it should follow, or else turn the page; whereas a swipe always means turn the page and so no check for links has to be done.

The books that I've noticed being especially slow are ones that have huge internal files (i.e. extremely long chapters, or the publisher has put multiple chapters in one file, or files with a very complicated internal structure that can result from automated conversions from formats such as PDF) and they get slower and slower the further you get into the chapter/file.

[Cinisajoy]

You might also try restarting the Kobo.

[marp68]

Originally Posted by GeoffR

I've seen it happen with certain books.

The books that I've noticed being especially slow are ones that have huge internal files (i.e. extremely long chapters, or the publisher has put multiple chapters in one file, or files with a very complicated internal structure that can result from automated conversions from formats such as PDF) and they get slower and slower the further you get into the chapter/file.

Interesting. Didn't know that this could effect the response. Thanks

[davidfor]

Originally Posted by marp68

Interesting. Didn't know that this could effect the response. Thanks

As a test of this, I have a thirty chapter book with about 500 pages. The code in the book is clean, there is a h2 for the chapter heading and paragraph tags for each paragraph. And rules separating sections. Each chapter is in a separate file. It works nicely all the way through.

I created two other versions. One I merged several chapters into one file to have different sized internal files. For this, the page turning slows down as the files get bigger and you get further through the file.

For the other version, I merged all the chapters into one file. It works, and at the start it turns pages reasonably quickly. But towards the end of the book, the page turns take several seconds.

[marp68]

This is good news, since it seems that it at least doesn't have to do with my specific device, but more of a general problem depending on how the books are generated. Thanks for testing, since I don't know how to reconstruct books. I've seen some differencies depending on for example between books, where in the book or chapter I am etc. Though it's hard to compare when time frame is short anyway. Either there seems to be a need of better structured books or devices with more power. Probably we'll see the latter...

This winter I will try to learn more about the book codes, structuring etc. Seems like a good thing to know. Right now I prefer to be outside, reading, in the nice late summer weather we have over here....

[mbovenka]

Originally Posted by davidfor

I created two other versions. One I merged several chapters into one file to have different sized internal files. For this, the page turning slows down as the files get bigger and you get further through the file.

For the other version, I merged all the chapters into one file. It works, and at the start it turns pages reasonably quickly. But towards the end of the book, the page turns take several seconds.

This is my experience as well. KindleUnpack can create epubs like that; AZW3s are pretty often like that internally. Kindles are less susceptible to the effect or do not suffer from it at all, it seems.

I have taken to using the Quality Check plugin to look for them (Epub Structure -> Oversize HTML Files) and do an epub-to-epub conversion to fix them.

[marp68]

Originally Posted by davidfor

As a test of this, I have a thirty chapter book with about 500 pages. The code in the book is clean, there is a h2 for the chapter heading and paragraph tags for each paragraph. And rules separating sections. Each chapter is in a separate file. It works nicely all the way through.

I created two other versions. One I merged several chapters into one file to have different sized internal files. For this, the page turning slows down as the files get bigger and you get further through the file.

For the other version, I merged all the chapters into one file. It works, and at the start it turns pages reasonably quickly. But towards the end of the book, the page turns take several seconds.

Is it easy to check which of the three my book is? Very clean, several chapters merged into one file or all chapters merged into one file? And is it easy and goes quick to clean it up a little?

Ah, sorry didn't see the next post. Is the way to go, to use "the Quality Check plugin to look for them (Epub Structure -> Oversize HTML Files) and do an epub-to-epub conversion to fix them"?

Tried the QC but it only found one book with oversized HTML files, and not the one I'm reading. So, maybe it's not that.