Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KA10: Vidissector #96

Open
larsbrinkhoff opened this issue Mar 11, 2019 · 3 comments
Open

KA10: Vidissector #96

larsbrinkhoff opened this issue Mar 11, 2019 · 3 comments
Assignees
Labels

Comments

@larsbrinkhoff
Copy link
Contributor

larsbrinkhoff commented Mar 11, 2019

The vidissector is a video input device for the AI lab PDP-10. (Actually, there were two or three hardware iterations.)

I'd like to implement this with input from a host "webcam". Or whatever the camera device on a typical laptop is called.

@rcornwell, @markpizz, there may not be any cross-platform API to do this. What are your thoughts?

@rcornwell rcornwell added this to To Do in KA10 Simulator via automation Mar 15, 2019
@rcornwell rcornwell moved this from To Do to Future Work in KA10 Simulator Mar 15, 2019
@larsbrinkhoff
Copy link
Contributor Author

I'd like to look into OpenCV: https://opencv.org/

@rcornwell
Copy link
Owner

For this and the other video device I am leaving it up to you to implement. When you have it working we can talk to Mark about moving it into main simH tree if needed.

@markpizz
Copy link
Contributor

Well OpenCV might be OK, but there will probably be a complicated set of build dependencies.
On *nix hosts the makefile, as always, can detect and use what is available. On Windows, adding dependencies is dramatically more complicated. The complexity on Windows is worse by the fact that all the Windows binaries are statically linked. Static linking allows easy binary distribution packaging (which is common on Windows) without having long chains of related dependencies that need to be also installed. The windows building process pre-gathers the 'supported' dependencies into a repo which gets dropped 'next' to the simh directory tree. This allows the developer(s) to work out the complexities one time without it being a user barrier to adoption.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
KA10 Simulator
  
Future Work
Development

No branches or pull requests

3 participants