You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2020. It is now read-only.
What would you like to submit? (put an 'x' inside the bracket that applies)
question
bug report
feature request
Issue description
Hello,
I'm attempting to use the Snapshot Maker sample on a Panasonic FZ-G1 Windows tablet. It has a front-facing camera as well as a rear-facing camera.
I just found out today that AForge.NET's Snapshot Maker sample has been superseded by by this librarie's sample of the same name. But I'm having the same issue in both versions of the sample.
Basically, when I connect to the front-facing camera, 100% of the time, it works as expected. When connecting to the rear-facing camera, it remains "connecting ..." indefinitely about 99.9% of the time. I say that this way because in debugging what I know how to debug, sometimes hitting breakpoints seems to alter the timing of things in such a way that a grand total of 3 times have I been able to use the rear-facing camera (see a video preview, trigger a snapshot capture, etc.).
I would really like to understand better how I can diagnose this myself. But any and all idea/suggestions are appreciated.
When I pull the source into Visual Studio and debug this, it seems that for the rear-facing camera, the NewFrame event doesn't fire like it does for the front-facing camera. Therefore the currentFrame is always null.
Anything I can add here to help you give suggestions/support?