-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
🐛 Cannot swap between cameras while recording on Android #1296
Comments
Should you try to pause the recording before switch camera and resume recording after that? |
Same issue here: #834 |
Hey!, |
Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3. I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here? Here's an instruction on how you can test that: #1674 (comment) If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉 Thank you! |
I am still unable to get recordings to work while switching the camera. I'm gonna try to spend a couple minutes looking at it, but the app doesn't crash, the recording just ends at the point where you switch cameras |
Hmm, actually the entire recording is kept, even the audio, the video just freezes at the point of the camera switch |
With the Camera2 rewrite you mean? In that PR? |
Yep! With the branch you recommended. |
What were you trying to do?
When recording a video on iOS, I am able to swap the camera and continue the recording with no issue. This seems to not be possible on android, instead the recording fails when this happens. This feature is supported on apps like Tiktok and Snapchat, and is also supported by the native camera application.
Reproduceable Code
What happened instead?
The recording fails with an inactive source error.
Relevant log output
Device
Samsung Galaxy S20
VisionCamera Version
2.15.0
Additional information
The text was updated successfully, but these errors were encountered: