Question / Help Webcam Not showing on Startup
- Thread starter dynomation
- Start date
Interesting! That does seem to fix the bug!
Unfortunately, its not a "solution" persay - I need the webcam to be cropped in my scene.
However, now that we know the cause, it should be easier to find and fix the bug.
Can anyone else confirm this behavior exists with webcams other than the Logitech HD C310?
(i.e. Does having a scene with a cropped webcam not appear on a first boot of OBS?)
Unfortunately, its not a "solution" persay - I need the webcam to be cropped in my scene.
However, now that we know the cause, it should be easier to find and fix the bug.
Can anyone else confirm this behavior exists with webcams other than the Logitech HD C310?
(i.e. Does having a scene with a cropped webcam not appear on a first boot of OBS?)
FilthyRobot
New Member
I can confirm, this behavior is happening with me as well (logitech c920, windows 10, obs studio 64 bit).
Also with cropped camera settings.
Also with cropped camera settings.
Perhaps fixed by this commit?
darkpowrjd
New Member
Have this same issue, but with 610 (I THINK that's the number: it's 600-SOMETHING), and with a few other sources which decides that they just refuse to show anything, regardless of what I try to do to fix it, and it seems to be the issue that RytoEX's link is referring to. Sometimes, it's the display capture deciding to be at 0,0 without any hope for me to sort it out. Sometimes, it's the webcam that refuses to show. Sometimes, everything is fine, and sometimes, it's both. It seems to show what it wants, when it wants. What's even better is that while the webcam doesn't show in one scene, it'll show perfectly fine in another scene in the same window when I switch to it.
That link would be good for me if I knew what I was supposed to DO with it, too. It has the coding there, but I'm not even sure what I have to do to get it to be installed so this doesn't happen anymore. It's sort of a deal breaker for me, especially when things I do with it are time sensitive (I can't wait forever for a solution), and switch back to OBS Classic to get things done, which has half the functionality that Studio has, which would be used if I didn't have to fight to get anything to work the way I need it to Uploading the log so I can be of as much help as I can to help you identify the exact problem (hopefully it uploads).
Some help in finding out how to get that script shown in the link installed would be helpful, too.
That link would be good for me if I knew what I was supposed to DO with it, too. It has the coding there, but I'm not even sure what I have to do to get it to be installed so this doesn't happen anymore. It's sort of a deal breaker for me, especially when things I do with it are time sensitive (I can't wait forever for a solution), and switch back to OBS Classic to get things done, which has half the functionality that Studio has, which would be used if I didn't have to fight to get anything to work the way I need it to Uploading the log so I can be of as much help as I can to help you identify the exact problem (hopefully it uploads).
Some help in finding out how to get that script shown in the link installed would be helpful, too.
The link that I provided was just showing that it has been fixed in the main code repository for OBS Studio. That means that the fix will be part of the next release, whenever that will be. The only things you can do are:
You can always reset a source's transform settings by selecting it and pressing Control+R.
- Wait for the next release.
- Compile OBS Studio yourself.
- Get someone else to compile OBS Studio for you.
You can always reset a source's transform settings by selecting it and pressing Control+R.
darkpowrjd
New Member
Seems there was a way to download the files for that, but if I were to want to replace the broken files using that until an official release comes, what would I have to do to do that (in other words, can I just replace the broken file(s) with the new one(s) to get it to work right)?
The CTRL+R thing is doing nothing to fix the issue. The Display capture lets me resize it (webcam does not even let me do that much), but it only shows a blank screen when I resize it (and it doesn't fix the core issue anyway)
The CTRL+R thing is doing nothing to fix the issue. The Display capture lets me resize it (webcam does not even let me do that much), but it only shows a blank screen when I resize it (and it doesn't fix the core issue anyway)
As I said previously, you would have to compile the OBS source code to get the fix running on your computer. The link I provided just shows that it has been fixed in the main code repository. Unless you know how to compile the source code for OBS, there is nothing for you to do but wait. You cannot just drop the source code files onto your computer and have them work.
I only pointed out Control+R for resetting your source transform properties as a possible thing to try, as that does occasionally workaround certain issues. Are both of your Display Capture sources pointed at different displays, or are they pointed at the same display? If they're pointed at the same display, that could cause the issue that you're describing. You should use "Add Existing" for multiple sources that point to the same thing.
Again, a hotfix release is forthcoming. It's being discussed and prepared right now. All you have to do is wait.
Yep.
darkpowrjd
New Member
Not for me. As of 0.16.6, certain sources still seem to go completely blank randomly. Sometimes none at all, sometimes the monitor or window captures, or both. Though they can show in some scenes, but not in others. And if I do a complete restart of the program again without changing any settings, the sources that will work and won't might or might not change. Desktop audio appears to be working, but I won't know until I record or stream to see if that was addressed.
I might have a completely unique problem if the source fixes are working for everyone else but me. I'll try to provide a few logs. I've been seeing this in most of the logs: "DShow: Run failed, device already in use (0x8007001F): A device attached to the system is not functioning." This seems to be when I switch to a scene and the webcam doesn't come up. I'm thinking maybe a full reinstall is in order to see if that does anything to address this.
I might have a completely unique problem if the source fixes are working for everyone else but me. I'll try to provide a few logs. I've been seeing this in most of the logs: "DShow: Run failed, device already in use (0x8007001F): A device attached to the system is not functioning." This seems to be when I switch to a scene and the webcam doesn't come up. I'm thinking maybe a full reinstall is in order to see if that does anything to address this.
Suslik V
Active Member
When you add new source to the scene, use Add Existing option (cloning) instead of Create new one.
OBS Studio Help Guide: https://obsproject.com/forum/resour...ware-studio-multiplatform-help-guide-pdf.365/ , look for Add new video source to OBS Studio scene section.