I'm using the v4l2sink plugin to stream into v4l2loopback and tell google Meet/zoom/whatever "hey, dummy 0x00002 is my webcam".
What distro? Nobody I know has been able to make that work!
Proposed bounty for adding virtual camera / microphone support natively to OBS
81–90 of 102 posts
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#82Earlier quoted context omitted.
I think bounties create an unhealthy incentive structure. The kind of thinking you expressed in your post that payments shouldn't be seen as "charity" leads to people trying to not "waste" their bounties. They'll add it to issues the maintainers won't do otherwise, which in turn leads maintainers to hold the code hostage, not doing something they'd have done had there been no bounty structure, hoping that someone pos…
I can't speak for others, but many of my company's open-source projects are not open-contribution (meaning I don't accept PRs unless I hire you). Features are added because funding comes from somewhere else, but it would be nice to have a second option for users to fund a feature directly .
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#83Earlier quoted context omitted.
I can't speak for others, but many of my company's open-source projects are not open-contribution (meaning I don't accept PRs unless I hire you). Features are added because funding comes from somewhere else, but it would be nice to have a second option for users to fund a feature directly .
Just curious, what do you gain from having your code be open-source if you do not accept outside contributions?
If you're asking what we benefit from doing this, not much. We could have released proprietary software, but as users of software ourselves, we enjoy having these freedoms, so we don't want to restrict users of the software we write.
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#84Earlier quoted context omitted.
I can't speak for others, but many of my company's open-source projects are not open-contribution (meaning I don't accept PRs unless I hire you). Features are added because funding comes from somewhere else, but it would be nice to have a second option for users to fund a feature directly .
Just curious, what do you gain from having your code be open-source if you do not accept outside contributions?
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#85Earlier quoted context omitted.
Just curious, what do you gain from having your code be open-source if you do not accept outside contributions?
Users can enjoy these four freedoms when using our software. https://www.gnu.org/philosophy/free-sw.en.html If you're asking what we benefit from doing this, not much. We could have released proprietary software, but as users of software ourselves, we enjoy having these freedoms, so we don't want to restrict users of the software we write.
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#86Earlier quoted context omitted.
Only some of the tech world lives on MAC and basically streamers use PC's.The other way of course is to use a second PC. What of course should be done is have this as part of the operating system and for audio too - id like to use Ableton live as the audio input into my Hangouts etc.
At least on Windows this has existed forever. On Windows 10 Config Panel -> Sound -> Manage sound devices -> Recording and choose your sound card to set as default input
And don't get me started on the total Goat Rope that Windows Audio seems to have turned into - for what ever reason a lot of laptop's using realtek sound has been broken since an update about 6 7 months ago
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#87This is right up my alley, but then I guess this isn't about paying one dev to do the job, is it? More like contribution to the whole OBS project. I'm not sure how this works (?)
(FYI, if you're interested in running my app, you'll need to disable SIP on 10.14+)
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#88Earlier quoted context omitted.
With 300 for a half-day, it would be 600 for a full day and 12000 for 20 days of work. In most parts of the world, that's an extremely high level salary and could easily fund most peoples month, granted they live outside of Silicon Valley. I'm sure many people would be more than happy to receive 300 or much less for half a day of work.
But my point was its not a quick half day fix for some minor formatting on a website - which you can out source offshore. Your talking windows audio /video internals which is not a common skill
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#89Earlier quoted context omitted.
This is about having OBS' output appear as a video source on the operating system. You're solving the wrong problem. :-)
I understand what it is, there is just no point to doing it. Its typical "i always use tool X to do Y, so now I want tool X to do Z when there is a tool B doing Z already." But whatever, go on.
I was actually trying to get this working for myself because I'm doing a presentation in a few days and I'd like to be able to swap between myself full screen, and then either the slides or another piece of software with my face in a smaller area. If a "virtual webcam" tool was available for OS X I would be able to pipe that into Zoom.
I could just do a screen share and switch back and forth but I want to do something a little more polished.
Re: Proposed bounty for adding virtual camera / microphone support natively to OBS
#90This makes me think. Is there a service that handles crowd-sourcing and processing payments a bit like Kickstarter but on a smaller scale? Say, if someone proposes a feature and the developer says "I'll do it for $300", users could donate until the goal is reached. With the promise of payment, the developer can go ahead and spend the time/effort, and everybody wins. But setting up a Kickstarter, IndieGogo, etc is too…
I think bounties create an unhealthy incentive structure. The kind of thinking you expressed in your post that payments shouldn't be seen as "charity" leads to people trying to not "waste" their bounties. They'll add it to issues the maintainers won't do otherwise, which in turn leads maintainers to hold the code hostage, not doing something they'd have done had there been no bounty structure, hoping that someone pos…