normcap VS D3DShot

The workflow feels a bit more polished (Though also not perfect) and the repo is still active.

[1] https://github.com/dynobo/normcap

https://github.com/dynobo/normcap#similar-open-source-tools

Some sort of OCR — NormCap bound to a hotkey for general OCR and obisidian-ocr-plugin for Obsidian. Vital for tracking down screenshots of stuff.

Just for completeness: There's normcap, an OCR tool to copy text from the screen. It works right out of the box from what I tested, both from Flatpak and the AUR.

but i just found this https://github.com/dynobo/normcap from their readme, using tesseract as its backend, looks like nice replacement for text extractor.

By using the Python package d3dshot, we can grab a screenshot of our RealFlight environment (we'll take just the part showing the downward-facing camera feed), and then send this image data (encoded using OpenCV) over UDP. On another computer we can have a script running with a UDP socket open and waiting to receive these messages. This script is representing the third-party peripheral, which in real life would be capable of obtaining the video footage on its own. Nonetheless, the peripheral now has its data to analyze. The important thing to note here is that this peripheral is self-contained. It is not part of the autopilot (it's written in Python, for one thing), and thus its hardware and software can be developed without any integration concerns, provided that it conforms to the autopilot's API. So while this "peripheral" currently exists on the same computer that is running the autopilot, this is by no means a constraint, and it will soon be moved to a separate piece of hardware. So what, you may ask, it the point of this peripheral? Well, that will just have to wait until next time. But I think it's pretty cool, so hopefully you'll come back to check it out. You're very patient, dear reader. That's what I appreciates about you. -Greg