Cannot use user media devices without flag #146

Closed
opened 2019-01-25 15:23:34 -06:00 by hunterpollpeter · 2 comments
hunterpollpeter commented 2019-01-25 15:23:34 -06:00 (Migrated from github.com)

No way to get access to user media devices (webcams and microphones) without having to use flag. Added a flag in PR #143. Would love to see this in the next release.

No way to get access to user media devices (webcams and microphones) without having to use flag. Added a flag in PR #143. Would love to see this in the next release.
mnill commented 2020-03-11 00:16:09 -05:00 (Migrated from github.com)

Any chances to be merged?
I need this feature to make face masks plugin. (needs web cam access from browser plugin).
Shall I start to make native plugin or there chances to merge?

Any chances to be merged? I need this feature to make face masks plugin. (needs web cam access from browser plugin). Shall I start to make native plugin or there chances to merge?
RytoEX commented 2021-04-15 01:27:00 -05:00 (Migrated from github.com)

Chromium/Chrome/CEF by default will prompt users for permission to use audio/video devices. This permission prompt can be bypassed by passing the --use-fake-ui-for-media-stream flag to Chromium/Chrome/CEF. Since we pass all user-specified flags to CEF, users can pass this flag to OBS to bypass the permissions prompt.

As we regard this to be unsafe default behavior, we will not add this to OBS as the default behavior. Furthermore, we don't consider this to be a bug, so I'll be closing this issue. For more information on our reasoning, see comments on #143.

Chromium/Chrome/CEF by default will prompt users for permission to use audio/video devices. This permission prompt can be bypassed by passing the `--use-fake-ui-for-media-stream` flag to Chromium/Chrome/CEF. Since we pass all user-specified flags to CEF, users can pass this flag to OBS to bypass the permissions prompt. As we regard this to be unsafe default behavior, we will not add this to OBS as the default behavior. Furthermore, we don't consider this to be a bug, so I'll be closing this issue. For more information on our reasoning, see comments on #143.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-obsproject/obs-browser#146
No description provided.