the frame data is important for realtime frame data processing.
thanks.
I agree with that idea :)
This is in the works now and coming soon. I want to do a bit on top of just passing the frame though. I've been adding a lot of NDK stuff lately to speed up processing and I'd like to structure that to be usable by CameraKit users. Especially with the frame callbacks where performance is incredibly important.
What sorts of things do you need to do with the frames?
@dwillmc
Possibly a support for a function where we could specify a frame processor function that gets each frame, and also the processed frame (maybe like color enhanced, filter effects) is returned to the camera View.....
in my case, i want to get each frame to use for JNI with opencv c++, and return preview!
@dwillmc In my case ,I have a lot of neural networks for real-time image processing锛宻uch as AR,robot vision
@dwillmc In my case, I need frame to use for real-time OCR.
@dwillmc In my case, I'm trying to detect motion (i.e., page turns) and take a photo for an automatic scan app.
Do you have any update on this? @dwillmc
@xymelon @monatis @benjaminbarbe Yes we plan to have this included in 1.0.0 release aimed for Jan 1, 2018. We hope to open a PR and Snapshot builds for this release, this week so you can comment, test, etc!
@dwillmc May have further input too
Do you have any update on this...? @dwillmc
We are hoping to issue a 1.0.0 PR soon for testing and a lot of this is included. @browningweb
@austinkettner Can you post a link here to the PR and/or feature docs?
Otherwise, shouldn't this issue remain in Open state?
any updates on this?
BUMP......? should we switch camera package from camerakit...?
@eviansplash @kunaldawn @edwardotis Here is the 1.0.0 PR: https://github.com/CameraKit/camerakit-android/pull/318 give it a try and let us know a bit more about your use case? We are adding in additional calls ahead of merging and can specifically address this.
Most helpful comment
any updates on this?