Thread: Firmware 4.32.19501
View Single Post
Old 05-05-2022, 12:59 AM   #444
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Deobulakenyo View Post
I might have misread your post.

I thought word and page counts work while the time of read estimates are problematic
I have no idea where that would have come from. The reading estimates have to be calculated by you somehow. Though I suppose getting a sensible or useful value could be considered to be problematic.

Or are you referring to the estimates shown when reading? If so, this has absolutely nothing to do with those. As I originally stated, for purchased books, these estimates are the same as on the Kobo web site. They are just a guestimate they are showing based on reading rates someone has come up with for them. The time remaining estimate when reading is calculated while you are reading and does not use these numbers. I don't know how it is calculate, but, I believe it is affected by how fast you actually read. The accuracy has been discussed (with some amusement at time), but, I've never really tried to check it for myself.
Quote:
I need to study how to enable that.

Does the reading estmaites require new columns also?
Only if you need to store it in your library. This is why a template is used. The value can be calculated from other columns that you have. The obvious thing to do is to divide the word count by the number of words you read per minute. That was the intention of my example, but I don't know what my reading rate is so I plucked two numbers out of the air (Well, I used 10 because the division easy and 12 made because it gave enough of a difference in the values created). If you have another source for the reading estimates, you may need to store them as a column. Or you might use a completely different calculation. The Count Pages plugin can calculate some readability numbers for a book. I suppose they could be used to weight the reading speed somehow (but I have absolutely no idea how).

Or you could use the estimates for something completely different. Just remember that Kobo considers the numbers to be minutes and will display them as hours. I suppose you could use it for a rating from 1 to 10, but, you would need to send numbers between 60 and 600.



And for the record, there is also a column in the database called "Duration". Kobo uses that for the duration of an audiobook. I decided not to add this to the driver as the sideloading for audiobooks isn't good enough to make it worthwhile at this point. And the fact that I was going to end up with seven (KoboTouch) or eight (KoboTouchExtended) different templates in the driver configuration made me not want to do it. I will revisit this if there is demand.

And for those who opened the driver config and counted, I'm talking about the next release. See https://www.mobileread.com/forums/sh...d.php?t=346321 for details.
davidfor is offline   Reply With Quote