Is there a limit on OCR in Devonthink Pro?

DEVONthink
41

In Finder can you turn on the OCR logging, to do this:

  • Quit DEVONthink3
  • InFinder select the menu Go->Go to Folder, copy and paste the line below and press Go.
  • Copy the attached file to this folder
    OCR.plist (274 Bytes)
  • Restart DEVONthink3

The next time you get the error message can you send a copy of the OCRLog.txt file that will be in the same folder as above.

42

your instructions are missing the folder name…

43

Sorry it should be:
~/Library/Application Support/DEVONthink 3/Abbyy

44

I have the error log, where do you want me to send it?

45

Please hold the Option key and choose Help > Report Bug to start a support ticket. Add Attn: Alan in the body and attach the log. Thanks.

46

ok sent. thanks for your help.

47

I have the same issue … I’d love to see this fixed. I’ll share a log as well if needed. This has been happening for at least year.

48

Hello everyone,

I too am having this same issue. Didn’t have it on my MBP Intel, but I do have it on my Mac mini M1.

Best,
Dan

49

As suggested in the thread, probably best to now send them a support ticket.

50

Yes, I did, with the log.

51

Abbyy still has not fixed this issue. 3.7 gives the error after 24 pdfs or so… I am ocr’ing about 1000 pdfs of 100+ pages and it has taken me weeks of finding my process error’d out, quitting DT, restarting the app and the OCR process again. I would have loved to just start OCR’ing and forget about it until it’s done… I know it’s not DevonTech’s fault, but it is really frustrating.

1 Like
52

I can confirm that this is still an issue (Big Sure, m1, 3.72).

53

If you get this error, quit and restart DEVONthink, this will reset the ABBYY OCR. ABBYY is aware of the issue and we are awaiting the next update from them.

1 Like
54

Can confirm this still happens (Sonoma 14.1.1, m2, DTP3.9.4)

55

Thanks. Can confirm we’re still waiting on an update too :slight_smile:

56

The issue is still open (Sonoma 14.5, DT 3.9.6). I followed the instructions above and deleted the SDK folder which resulted in other errors. Finally I deleted only the file licenses.cnt in the folder SDK/licenses and OCRing seems to work again.

57

I am also having this issue

58

Delete the file licenses.cnt and you should be fine.

59

I just encountered the same issue today. Deleting License.cnt works.

What’s really frustrating is that I have to add the failed documents to the “OCR queue” again. The workaround itself required a mere 15 seconds. Recollecting the 50+ documents to OCR took me much longer, however. (I ended up creating multiple smart groups for that purpose.)

As a QoL change request: It is desirable to preserve the “OCR queue” in some way when this specific error message is logged.