https://docs.mumbli.app/benchmarks
It'll be interesting to see it on my coding evals as well. Can't do it yet but will try later.
41–47 of 47 posts
https://docs.mumbli.app/benchmarks
It'll be interesting to see it on my coding evals as well. Can't do it yet but will try later.
Amazing! I just tried the OCR capabilities with a photo of a DIN A4 page which was written with a typewriter. The image isn't the easiest to interpret. The text perspective is distorted because the page is part of a book and the page margin toward the spine of the book is very small. There are also many inline corrections due to typing errors while the page was written (backspace couldn't erase characters back then,…
New account created ~5 hours after this post, with a single comment specifically praising the model / product. I want to believe, but this sort of astroturfing isn't very encouraging.
Amazing! I just tried the OCR capabilities with a photo of a DIN A4 page which was written with a typewriter. The image isn't the easiest to interpret. The text perspective is distorted because the page is part of a book and the page margin toward the spine of the book is very small. There are also many inline corrections due to typing errors while the page was written (backspace couldn't erase characters back then,…
Have you tried this task using an actual OCR model like Google Cloud Vision AI? I am not sure if this is what Gemini uses under the hood but multi-modal LLMs are not designed to extract text like this so it should be no surprise it's not good at it?
I should retry the experiment because there has been a lot of progress since then and I could imagine that GCP improved there vision models since then.
Gave it a try for structured data extraction. Tested returning a JSON object from images. The output was correct, and seemed deterministic, although I ran it only 2-3 times on the same image. Main problem is response time: it took about 20-25 seconds for a simple structure of 5 fields. As such unusable at scale, let alone "real time" processing. Other problem is cost, it is considerably more expensive than more estab…
We're working a lot more on speed in the coming few weeks :) More GPUs and more optimizations.
Our has been focus on quality of output first and we'll make optimizations as we grow :)
The lite models are great for simple use cases but won't don well in more complex OCR use cases.
I was curious and compared STT on my bench https://docs.mumbli.app/benchmarks It'll be interesting to see it on my coding evals as well. Can't do it yet but will try later.
Excited to see the results
Earlier quoted context omitted.
Here’s the academic paper behind it: https://arxiv.org/abs/2602.04101
Thanks. Well this is fascinating. >Instead of a single transformer, we combine (i) a stack of heterogeneous DNNs paired with small language models as perception modules It seems that we're reinventing the brain's organs one by one from first principles. (Though Transformer + Common Crawl unintentionally builds a whole bunch of them we don't even understand yet.) I found some broader context and the whole thing is ind…
We see two types: workflows & agents.
Workflows are the most common, there's a pipeline like processing loan documents before data gets loaded to the next step or translating user comments before being stored in the database.
Agents are where you have a chat based system or a brain of sorts that calls many tools to achieve a user goal. The model doing this is a lot better at non deterministic task which then delegates to Interfaze for specific deterministic actions like OCR, Web extract then consumes that data. That's the article you referenced :)
I was curious and compared STT on my bench https://docs.mumbli.app/benchmarks It'll be interesting to see it on my coding evals as well. Can't do it yet but will try later.
Try it using run task mode when comparing to pure STT models: https://interfaze.ai/docs/audio/speech-to-text#long-audio-tr... Excited to see the results