tytan652

Note: On "Use Both" the button will not get stuck waiting for a PipeWire connection because it's V4L2 VCam that change the button state. But on PipeWire only, the button...

> Anything else blocking this? My PR did not get any reviews, so until mine is not merged, this one is stuck. Normally your PR should be drafted waiting for...

> Should your PR include a possible solution for the "stuck" start virtualcam button, or should this be added later? The "stuck button" can not be fixed on the UI...

This one should be updated too: https://github.com/obsproject/obs-studio/blob/master/plugins/rtmp-services/rtmp-format-ver.h

> I personally disagree with this. A user should not have to concern themselves with which Camera API OBS or the receiving app is using. The user should just be...

For now it will only affect Linux, after this PR is just a first step, the next could be add option like "All Windows API Virtual Camera Output" and "All...

> I don't see a practical application of limiting which camera API OBS outputs to. I just thought that at least on Linux, user may not want OBS to always...

~~Big change of director, no selector.~~ This PR now enable the use of V4L2 and PipeWire VCam implementations simultaneously. PS: It also allows to add something similar for Windows PS2:...

> Just to ask, we're assuming that outputting to all doesn't incur some kind of performance cost as opposed to one, is that accurate? Matt wanted both by default, this...

I added the selector, I you want I can remove it and keep it for another PR. This selector doesn't add third party virtual camera. ~~I think adding translation for...