Live data from Hacker News

DeepSeek OCR

github.com

171–180 of 252 posts

Re: DeepSeek OCR

#171
It says the conversation can reduce size with large compression, which basic make the image blur but still contaim import information.

This is indeed amazing. It's actually how human try to understand and remember things. BY VISUAL! And when memory fade out, the image are getting blurred.

Not sure if those close source multimodal models are already using this method.

Re: DeepSeek OCR

#172

Earlier quoted context omitted.

Vision is how humans see text. So text must have built in adaptations to protect from visual noise. For example, two words that look similar must never appear in similar contexts, or else they would be conflated. Hence we can safely reduce such words to the same token. Or something like that.

That also works purely on text and it's the trick I used in my German speech recognition engine ( https://arxiv.org/abs/2206.12693 ). "I'm studying at Oxford Univ" has basically no loss in meaning even though "University" was truncated to less than half its characters.

This is like how many CLIs accept the shortest unique version of commands.

Re: DeepSeek OCR

#173

Earlier quoted context omitted.

Yeah, if it was cross-platform maybe more people would be curious about it, but something that can only run on ~10% of the hardware people have doesn't make it very attractive to even begin to spend time on Apple-exclusive stuff.

10% of hardware is an insanely vast amount, no?

Well, it's 90% less than what everyone else uses, so even if the total number is big, relatively it has a small user-base.

Re: DeepSeek OCR

#174

Earlier quoted context omitted.

But this was very much the case with existing OCR software as well? I guess the LLMs will end up making up plausible looking text instead of text riddled with errors, which makes it much harder to catch the mistakes, in fairness

Existing ocr doesn’t skip over entire (legible) paragraphs or hallucinate entire sentences

This must be some older/smaller model.

Re: DeepSeek OCR

#176
post #65

Earlier quoted context omitted.

Maybe my imagination is limited or our documents aren't complex enough, but are we talking about realistic written documents? I'm sure you can take a screenshot of a very complex spreadsheet and it fails, but in that case you already have the data in structured form anyway, no?

Now if someone mails or faxes you that spreadsheet? You're screwed. Spreadsheets are not the biggest problem though, as they have a reliable 2-dimensional grid - at worst some cells will be combined. The form layouts and n-dimensional table structures you can find on medical and insurance documents are truly unhinged. I've seen documents that I struggled to interpret.

To be fair, this is problematic for humans too. My old insurer outright rejected things like that stating it's not legible.

(I imagine it also had the benefit of reducing fraud/errors).

In this day and age, it's probably easier/better to change the process around that as there's little excuse for such shit quality input. I understand this isn't always possible though.

Re: DeepSeek OCR

#177

For everyone wondering how good this and other benchmarks are: - the OmniAI benchmark is bad - Instead check OmniDocBench[1] out - Mistral OCR is far far behind most Open Source OCR models and even further behind then Gemini - End to End OCR is still extremely tricky - composed pipelines work better (layout detection -> reading order -> OCR every element) - complex table parsing is still extremely difficult [1]: http…

Wish someone benchmarked Apple Vision Framework against these others. It's built into most Apple devices, but people don't know you can actually harness it to do fast, good quality OCR for you (and go a few extra steps to produce searchable pdfs, which is my typical use case). I'm very curious where it would fall in the benchmarks.

Interesting. How do you harness it for that purpose? I've found apple ocr to be very good.

Re: DeepSeek OCR

#178

I tried this out on huggingface, and it has the same issue as every other multimodal AI OCR option (including MinerU, olmOCR, Gemini, ChatGPT, ...). It ignores pictures, charts, and other visual elements in a document, even though the models are pretty good at describing images and charts by themselves. What this means is that you can't use these tools yet to create fully accessible alternatives to PDFs.

I have a lot of success asking models such as Gemini to OCR the text, and then to describe any images on the document, including charts. I have it format the sections with XML-ish tags. This also works for tables.

Re: DeepSeek OCR

#179

Earlier quoted context omitted.

10% of hardware is an insanely vast amount, no?

Well, it's 90% less than what everyone else uses, so even if the total number is big, relatively it has a small user-base.

I don’t think 10% of anything would be considered relatively small even if we talk about 10 items: literally there’s only 10 items and this 1 has the rare quality of being among 10. Let alone billions of devices. Unless you want to reduce it to tautology, and instead of answering “why it’s not benchmarked” just go for “10 is smaller than 90, so I’m right”.

My point is, I don’t think any comparative benchmark would ever exclude something based on “oh it’s just 10%, who cares.” I think the issue is more that Apple Vision Framework is not well known as an OCR option, but maybe it’s starting to change.

And another part of the irony is that Apple’s framework probably gets way more real world usage in practice than most of the tools in that benchmark.

Post reply on HN