Question / Help Got another monitor capture black screen issue for yas. Pls help.

Sparktite

New Member
So i was messing around with different ways to capture my webcam to record separately and i think it may have done something to obs. Could also just have randomly broken its just sorta odd cuz obs was running fine the last time i tried it.
I poked around for different troubleshooting guides and tried steps to get my monitor capture to work again. Tried running as admin even though my shortcut is set to always do that i think. Tried poking around in the nvidia settings to make sure my gpu is selected for obs in the 3d settings, however there is no gpu selection drop down, probably cuz i only have 1 gpu and no idea if i have onboard graphics even.
Tried reinstalling graphics driver out of desperation.
Would really appreciate any help i can get, especially because this issue seems common and im sure ppl are tired of dealing with it :P
Included some log files wasnt sure which ones are/arent relevant.

As for the webcam stuff i was doing i was trying to set vlc media player to record my webcam following some instructions online, it did not work at all. If you guys want me to link the steps i followed i can but not sure if anyone is interested in that.

Thanks for your time <3
 

Attachments

Narcogen

Active Member
23:58:17.060: Windows Version: 10.0 Build 17134 (revision: 829; 64-bit)

Windows is very out of date and a broken Windows feature can hurt OBS performance. You should update to at least 1809.

https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions

23:58:17.655: Initializing D3D11...
23:58:17.655: Available Video Adapters:
23:58:17.658: Adapter 0: NVIDIA GeForce GTX 1080
23:58:17.658: Dedicated VRAM: 4176478208
23:58:17.658: Shared VRAM: 4263979008
23:58:17.658: output 0: pos={0, 0}, size={1920, 1080}, attached=true
23:58:17.658: output 1: pos={-1922, -2}, size={1920, 1080}, attached=true
23:58:17.658: output 2: pos={-2, -1080}, size={1920, 1080}, attached=true
23:58:17.706: Loading up D3D11 on adapter NVIDIA GeForce GTX 1080 (0)
23:58:17.810: D3D11 loaded successfully, feature level used: 45056


You only have 1 GPU. There should not be any issue making a display capture work if Windows, OBS, and your GPU drivers are all up to date.

Unfortunately for me your scenes are fairly complex and have multiple monitor and game sources in them, so it's impossible for me to tell if you're not seeing a working display capture because it's being obscured by another source.

It may be worthwhile to make a new, blank Scene Collection, and create a single scene with a single desktop capture in it, and see if that works or not, and upload that logfile.

23:58:27.242: adding 85 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Digital White Lines)

This is a definite sign that you're overloading your computer and that even if the capture worked, you would likely be experiencing poor performance.
 

Sparktite

New Member
23:58:17.060: Windows Version: 10.0 Build 17134 (revision: 829; 64-bit)

Windows is very out of date and a broken Windows feature can hurt OBS performance. You should update to at least 1809.

https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions

23:58:17.655: Initializing D3D11...
23:58:17.655: Available Video Adapters:
23:58:17.658: Adapter 0: NVIDIA GeForce GTX 1080
23:58:17.658: Dedicated VRAM: 4176478208
23:58:17.658: Shared VRAM: 4263979008
23:58:17.658: output 0: pos={0, 0}, size={1920, 1080}, attached=true
23:58:17.658: output 1: pos={-1922, -2}, size={1920, 1080}, attached=true
23:58:17.658: output 2: pos={-2, -1080}, size={1920, 1080}, attached=true
23:58:17.706: Loading up D3D11 on adapter NVIDIA GeForce GTX 1080 (0)
23:58:17.810: D3D11 loaded successfully, feature level used: 45056


You only have 1 GPU. There should not be any issue making a display capture work if Windows, OBS, and your GPU drivers are all up to date.

Unfortunately for me your scenes are fairly complex and have multiple monitor and game sources in them, so it's impossible for me to tell if you're not seeing a working display capture because it's being obscured by another source.

It may be worthwhile to make a new, blank Scene Collection, and create a single scene with a single desktop capture in it, and see if that works or not, and upload that logfile.

23:58:27.242: adding 85 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Digital White Lines)

This is a definite sign that you're overloading your computer and that even if the capture worked, you would likely be experiencing poor performance.
Wow thanks yeah i feel stupid, i guess i accidentally enabled my capture card which usually shows up invisible over my other display and ive been basically been brain dead the past week due to lack of sleep and forcing a really weird sleep schedule ive had to do, so i guess i didnt notice when i was trying to figure out the problem last night.

Im surprised to hear that my windows could be "very" out of date when no less than 3 weeks ago i had gone through all the possible updates to make sure its as up to date as possible. I frequently check for updates so ive never really ever been that out of date. Ill be updating again tonight but i cant imagine having missed many updates considering i did a full update within the past 3 weeks. I don't like the idea of my install ever being more than a few updates old.

Whats with the audio buffering thing? I dont really understand what the issue is or how an audio buffer can be overloading my system. My system doesnt usually ever drop frames and i basically never have the cpu/gpu pinned whenever im streaming. Could you elaborate on what you mean or whats going on there. Also since i dont use the audio from that source how is it still messing with my audio?

Thanks again for your time <3
 

Sparktite

New Member
You can try using the update assistant, https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

If it doesn't update it will at least tell you why (eg incompatible driver / software).
Thanks i got it to update fine im just surprised it could be so out of date if i updated not too long ago. Oh well. This update was hell to deal with it wiped all my sound settings in my sound card software, obs, voicemeeter, took me like an hour to get all fixed again lol.

Now im just worried about the white lines source that has some kinda audio buffer issue. I cant see any issues with it but if u guys are that makes me worry. Ive been having issues with my recordings in adobe premiere too, been hearing its just an incompatibility issue they have so it have to jump through hoops trying to edit, but i did have a hunch at one point that my recordings were recording as VFR? VBR? instead of CFR CBR. Which if that source is overloading my system might explain that issue.
 
Top