-
Notifications
You must be signed in to change notification settings - Fork 3
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
Alternative ways to match devices #21
Comments
I'll just list out the use cases for the other options than the "by device id" option. By Bus PathHere the device is mapped by looking at which bus adress it is connected via. Pros:
Cons:
By "Other" methodThis is the current default on Linux and freeBSD. Even if this is not as useful for physical devices as the "By ID" or "By bus path" methods, there is still some cases where this is useful or needed. This is because the virtual devices only gets put in Pros:
Cons:
|
This sparked from a discussion about how the V4L2 plugin matches capture devices (obsproject/obs-studio#9246). Matching devices by the bus / port might be interesting, but we need to consider this approach holistically, both for other platforms, and also for other device types. It's unclear how the UI would look like, if it's a global vs per device type vs per source, etc.
TODO: list use cases
The text was updated successfully, but these errors were encountered: