When I built rem, I spent significant effort getting screenshot -> ocr + screenshot -> ffmpeg loop energy efficient, but it definitely is more expensive than accessibility API.
You also save a lot of disk space and writes to disk.
That being said, you lose the cool swipe to go back in time and search through history and visually see, features.
And situations where accessibility isn't supported.
And as others have mentioned, built in ocr is definitely better than tesseract.
Yes, I know. Like I said: “Project reasons aside”. I’m not suggesting OCR for this, I’m imparting the general information to be used in other situations that in macOS you can OCR without requiring third-party tools.
You definitely still would, but you need to pay the full input cost twice, so the equation really depends on how much first message vs repeat message matter.
reply