-
Notifications
You must be signed in to change notification settings - Fork 174
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
DroidCamX forgets Exposure, Autofocus and Whitebalance Settings #151
Comments
Agree. Would be super nice if you could just leave and connect back into the device the next time without touching the settings again. |
Another nice persistent setting to store would be the anti-flicker |
Yes! The zoom level would also be very nice to remember! |
Yes please. I just bought the droidcam pro and manually changing this every time is a pain. These options should be available through the cli. |
Persistent settings would be a wonderful feature! For OBS users (streaming or otherwise), the video feed is reset if the media source is inactive. It would be excellent if, when activated, the IP cam would be in its prior state. Thank you! |
Hi, if you are using OBS I would highly recommend switching to the newer DroidCam OBS app. |
DroidCam OBS is far superior. thanks for the recommendation. |
Bumping this! I'd love to see zoom level either A) remembered, or B) configurable via a CLI flag or something of the sort. |
Describe the bug
Changing any of the Exposure, Autofocus or Whitebalance settings from a default value to another value is not saved.
Steps to reproduce:
Exposure, Autofocus and Whitebalance are set back to their default values.
Expected behavior
DroidCamX remembers Exposure, Autofocus and Whitebalance settings.
Alternatively, enable setting those from the Windows, Mac and Linux droidcam applications so they can be saved and enforced from that side.
Additional context
Used droidcam-cli version:
1.7.1
Used droidcam-cli command:
droidcam-cli -size=3840x2160 adb 4747
Phone: Samsung Galaxz S9 Plus Edge
The text was updated successfully, but these errors were encountered: