September 19, 2017

Filed under: Announcements,Scripting — Marcus Tettmar @ 11:29 am

Note: Macro Scheduler 14.4 with OCR was released in October 2017. This post was written prior to that.

A sneaky peak of some new Screen OCR functions we have in development:

Please note that this feature is currently in development and therefore the syntax and final implementation may differ on release.

4 Comments »

  1. I have been using Capture2Text for my OCR recently as I had to copy a bunch of details from a web system but as it was all JS & CSS it was a real hassle, even disabling scripting didn’t help (OpSYS Backup). I ended up using MS with Capture2Text to get the outcome, it will be create to see this in production soon.

    Comment by CyberCitizen — September 20, 2017 @ 5:32 am

  2. Capture2Text also uses the Tesseract OCR engine, so you should see similar results.

    Comment by Marcus Tettmar — September 20, 2017 @ 6:34 am

  3. Great stuff Marcus, built in OCR will be a very useful addition to Macro Scheduler.
    Recently I have found myself in a corner where only OCR can get the job done on more and more occasions. If a servers is blocking get requests, or a websites does not support IE things can get tricksy.

    I sometimes use Chrome Puppeteer (Node JS) via macro scheduler as an IE workaround (Check it out) but OCR is definitely quicker and more convenient for small tasks, since I don’t have to write an additional script in JS. I was using Textract, but then I switched to Capture2Text, (both programs support CLI and use the tesseract libraries, but Capture2Text is free.)

    I’m not sure if Chrome Puppeteer integration (or something like it) is viable, but it would be awesome.
    Any idea when the OCR update will land?

    Comment by NickD76 — July 4, 2018 @ 5:18 pm

  4. This post was published last September and 14.4 with the OCR functions “landed” in October 2017! It’s been out 9 months already and people are using OCR functions already (see the forums). 🙂

    Comment by Marcus Tettmar — July 4, 2018 @ 5:35 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment