-
Notifications
You must be signed in to change notification settings - Fork 31
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
Missing teardown logic that doesn't cause the video to stop #52
Comments
Hi @sveres, You're right. We don't have a teardown logic that doesn't cause the video to stop. I suppose this is something that will benefit your use case? Also, there is no Sincerely, |
hi @vjekoart Yes, in our use case, the barcode recognition is optional and our barcode reading implementation cannot stop the video, otherwise it interferes with an other, parallel capturing method. You are right, there is no method like that, sorry about the confusion. What I meant is the
|
Hi @sveres, Thank you for the explanation. We'll look into this behaviour and extend the functionality from our side if we don't find an alternative solution. Sincerely, |
Thank you as well, if there is anything else I can clarify, please just let me know. |
Hi @vjekoart |
Hi @sveres, We're currently not working on this feature. However, the task is defined and placed in the backlog, but we cannot tell the exact date when it's going to be implemented due to limited resources. Sincerely, |
Hi @sveres, if you are using If you also want to stop the video feed (i.e. "freeze" the video feed, without tearing down the camera), you can call |
Thanks @DoDoENT, this is great news, we will check pauseRecognition out. |
Hey,
I think there is no way to stop the video recognition without pausing the video feed.
If I VideoRecognizer.cancelRecognition(), it pauses the video feed.
If I call VideoRecognizer.deleteRecognizer() without calling cancel firs, it will result in an unexpected error: "Uncaught (in promise): Recognizer runner is deleted. It cannot be used anymore!"
I think that's because there is still a setTimeout alive that tries to call processImage().
If I am wrong and there is a way, could you point me to the right documentation/code piece, please?
The text was updated successfully, but these errors were encountered: