New Beta 3.2.98

mikelove

皇帝
Staff member
We've started rolling out a new beta version 3.2.98 on our beta channel on Play; we're worried enough that it might randomly crash on people that we haven't even distributed it to all testers yet, but will over the course of the next few days.

The big change here is that we're finally doing our long-awaited roll-out of new algorithms for OCR and handwriting; "New OCR" is now the default OCR interface, as is a new modern machine-learning-based OCR algorithm. A downside of newer OCR algorithms is that while they're generally more accurate, and better at pulling text out of weird places and distinguishing it from other random stuff, they aren't great at matching up detected characters to precise pixel locations in an image, so with the new algorithm, live OCR shows the detected characters above the box instead of overlaying it, and still/screen OCR covers characters with an opaque white rectangle rather than a transparent green overlay.

We also added a new 'snap OCR' screen, which is basically just 'pause video and then tap on characters to look them up.' But honestly, now that the text detection is more accurate we feel like this will be better than 'live OCR' for most of the applications for which people were using live OCR, and might even make 'live OCR' a hidden / off-by-default thing at some point depending on how people respond to 'snap OCR.'

Experimental handwriting has been available in various builds before, the only difference is that now it's the default.

You can go back to the old OCR interface and algorithm and the old handwriting algorithm via Settings / OCR and Settings / Input Methods / Handwriting. We're planning to phase out the old algorithms for new users over the next few months, but to continue allowing people who already paid for OCR or 'enhanced handwriting' (or a bundle, as all of them include enhanced handwriting) the option to use the old algorithms if they prefer them.

We also updated our PDF decoder to use the open-source PDFium library - which saves money / disk space and gives us the ability to make whatever arbitrary changes we like for it - and cleaned up PDF viewing a bit (scroll positioning is nicer and it lets you use volume buttons to scroll just like other readers). And we fixed a bunch of bugs too.

Also, for iOS people following this: the new handwriting algorithm is available in the current iOS build as an off-by-default instead of an on-by-default option in settings. We're making a similar break with our old OCR algorithms in the next 4.0 beta (and we already do offer the option to use a different OCR algorithm for still images) but debating whether to also bring a new algorithm to the old app.
 

stacktic

Member
Hi,
I just got this new version and I don't understand why this one is 3.2.98 when this version number was already used so you end up with two versions with the same version number but important changes in features. After checking on the settings, this old version is reported as 3.2.98 on the Android App Info but 3.2.97 in Pleco.

Regarding the new pdf reader:
- the first impression is that it is really slow, it takes at least 5 seconds to load a 2MB pdf and while it does not crash I still get a "pleco not responding" pop up each time I try to change page, there was no such thing on the previous version, no delay when changing page.
- it now forces the OCR even for pdfs with real texts, as I don't own the OCR add-on I can no longer see the definition of the words, is it possible to have a way to disable the use of the OCR and use the text directly from the pdf?

While I really want this feature to happen, the impact on performance is too high like this.
Having to buy the OCR add-on on top of the reader to be able to read a pdf even when it contains only text does not make much sense to me.

Have a nice day!

Edit: I hoped this was due to fact that the OCR add-on was not installed on my device but after installing the demo, it does not improve performances.
 
Last edited:

mikelove

皇帝
Staff member
Thanks!

By 'force OCR' do you just mean that it won't show you definitions because it says you don't own OCR? That's a bug - we merged the PDF viewer code from OCR and non-OCR into a single class in preparation for eventually adding a seamless toggle between OCR and non-OCR in a future update and it looks like we forgot to have it skip the 'have they purchased OCR yet' check for the non-OCR version.

As for the slow loading: so it takes about the same amount of time for each page change as it does for the first run? What brand / model of Android phone do you have and what version of Android is it running? We haven't seen any performance difference here but there may be some particular little thing that's very slow on some devices and hopefully we can work around it if so.
 

stacktic

Member
Exactly this, the "Demo version..." text instead of the definition.
I am using a redmi note 9 pro, it should be enough for this.

It takes a long time and a "Pleco not responding" popup on each page change.
The "funny" thing is that it happens only when using dark mode, as soon as I disable it the performance problem is gone.
 

mikelove

皇帝
Staff member
Thanks, that made the problem easy to find - we just uploaded a new build that should hopefully address both issues, though it might take Google a day or two to approve it.

Oh, and I forgot to respond to your point about version numbers - we had another beta called 3.2.98 out for a little while already, but that was mostly about privately shipping some of the new libraries without really meaningfully surfacing them, making sure there weren't any weird little stability problems. The current public release is still 3.2.97.
 

anhnha

举人
The OCR for screen readers for video in the new version 3.2.98 seems improved and better than the previous one. However, the OCR is still much worse compared to Google Lens. Google Lens is much more accurate, probably 100% even with blur or back background, while Pleco's OCR often fails or makes mistakes when the background is not perfect.
I'm wondering why Pleco doesn't use Google Lens or a similar technology?
 

mikelove

皇帝
Staff member
Thanks!

The OCR we're using is Google's, actually, which we adopted in part because we appreciate how well it works in Lens and Translate, but I don't think they offer their latest technology to developers right away - presumably at some point (maybe I/O? maybe next fall when they update Android?) they'll make it available to us and then we'll duly update it. We're using Apple's OCR in 4.0 beta on iOS and that appears to more closely mirror the capabilities of what they offer in their own apps, but with Google's, it's not built into the OS and seems to be awkwardly updated out-of-band from that.
 

kaine42

Member
Hello,
I don't know if this is a bug. In the ebook reader while reading an epub and selecting a word, then after pressing the view in dictionary button on the top right of the screen, and lastly, pressing the back button of my android device won't do anything anymore.
Before, it would take me back to the preceding dictionary entry if I opened another after the first one, or exit back to the ebook reader altogether, but now it doesn't do anything.
It didn't do that in 3.2.97.

Have a nice day !
 
Last edited:

anhnha

举人
Thanks!

The OCR we're using is Google's, actually, which we adopted in part because we appreciate how well it works in Lens and Translate, but I don't think they offer their latest technology to developers right away - presumably at some point (maybe I/O? maybe next fall when they update Android?) they'll make it available to us and then we'll duly update it. We're using Apple's OCR in 4.0 beta on iOS and that appears to more closely mirror the capabilities of what they offer in their own apps, but with Google's, it's not built into the OS and seems to be awkwardly updated out-of-band from that.
Thanks for the info. There is another app called Hanzii Dictionary, which offers very accurate OCR for videos (seems almost 100% accurate in bad background as well), but it's a bit slow. I'm not sure what technology they use.
 

mikelove

皇帝
Staff member
I don't know if this is a bug. In the ebook reader while reading an epub and selecting a word, then after pressing the view in dictionary button on the top right of the screen, and lastly, pressing the back button of my android device won't do anything anymore.
Before, it would take me back to the preceding dictionary entry if I opened another after the first one, or exit back to the ebook reader altogether, but now it doesn't do anything.
Thanks very much for bringing this to our attention - should be fixed in the next beta.

Thanks for the info. There is another app called Hanzii Dictionary, which offers very accurate OCR for videos (seems almost 100% accurate in bad background as well), but it's a bit slow. I'm not sure what technology they use.
Thanks - I figured out which one they're using and emailed the vendor. Performance is a concern - both for live and screen OCR (screen OCR is slow in the current beta due to a bug but the slowdown isn't OCR algorithm related) - but no reason we couldn't ship multiple algorithms as options if we can make the pricing etc work.
 

mikelove

皇帝
Staff member
(I should add that there are also some slower open-source OCR frameworks we could look at - we just kind of wanted to start off with something fast enough to act as a drop-in replacement for our old model)
 
Top