Bug Report Not Receiving Source Audio Despite Showing It

Triscy

Member
I'm currently using an Avermedia C985 Live Gamer HD capture card in my 2nd streaming PC. For the most part, the multiplatform OBS has been working great for my casts.

The main problem I've run into, however, is that on occasion it will not actually pick up audio. From my main PC I use an Nvidia GTX 970 to play my games, which is split via HDM into both my monitor and to the capture card to get picked up for the streaming PC. To get the audio over, I use Virtual Audio Cable to split a Line 1 source to my headset and to the NVIDIA audio output, which does the job.

However, on some occasions(not all the time but often enough that I felt it necessary to say here), it will be reporting in OBS that it is receiving audio while, in reality, it isn't getting anything. The peaks for the "Game" source(which is the capture card's source) will be showing peaks of the audio from the game and teamspeak chats I'm in on my gaming PC, but people in the stream will be hearing nothing from the game. When I check the recording after casts, I can't hear the game in the recordings either. It's telling me that it's picking it up when it isn't.

I included my DxDiag for my streaming PC along with the log file for the most recent cast where this issue occured(earlier today). I would add the log file, but it's 1.9 gigabytes... yea.
 

Attachments

I don't recall them asking for a copy of your video.
We're talking about the log file from obs.
 
notepad++ is much more likely to play nice than the built in notepad on windows.
Notepad just outright rejected opening it.

Thing is I didn't try very hard. The streaming PC doesn't have much installed. I had to download 7zip just to get this thing zipped, but for the most part it's as barebones of installs as possible.
 
...You're sure this is a log we're talking about? Not a minidump, not a video, just a text file? Yikes. How long were you streaming for?

Can you try opening it with Notepad++ and see what was spamming the log to make it so big?
 
...You're sure this is a log we're talking about? Not a minidump, not a video, just a text file? Yikes. How long were you streaming for?

Can you try opening it with Notepad++ and see what was spamming the log to make it so big?
Yea; it's a log. Went into OBS multiplatform, clicked help, then "view logs". Notepad++ says the file is too big to open.

Also it was about a 4-hour stream. Started 2 PM, went a little past 6 PM.
 
tumblr_nn4ghhbZAk1u26fako1_400.gif


Back on topic, for anyone who does not want to open the log, the log contains endless lines of

13:29:23: gs_vertexbuffer_flush (GL) failed
13:29:23: glMapBufferRange failed, glGetError returned 0x502
13:29:23: gs_vertexbuffer_flush (GL) failed
13:29:23: glMapBufferRange failed, glGetError returned 0x502
13:29:23: gs_vertexbuffer_flush (GL) failed
13:29:23: glMapBufferRange failed, glGetError returned 0x502
13:29:23: gs_vertexbuffer_flush (GL) failed
13:29:23: glMapBufferRange failed, glGetError returned 0x502
13:29:23: gs_vertexbuffer_flush (GL) failed

Suggestion: Please uninstall OBS MP and re-install, and make sure you get version 11.0 which just released.
 
Surprisingly compressed to like 300 KB, despite extracting to the original 1.8 some gig file.
Sounds like the 11mb 3.5" floppy my sister pulled of a while ago, except more epic.
 
Sounds like the 11mb 3.5" floppy my sister pulled of a while ago, except more epic.
The compression is not surprising. If you know how compression works, you know that it takes identical numbers/letters/whatever and groups them. Since this file is has the same line repeating, the compression is very effective.

This is how streaming compression works. If there is a lot of action and moving parts, the video will use the whole buffer and max bitrate you have assigned it. If there is no movement, since each frame is the same, the bit rate can go down(In this case, variable bit rate, which Twitch hates)
 
Thing is the log wasn't what I made the post about. I have had the audio issue again since, but can't recall which day it was or else I'd provide the(less broken-ly long) log file.
 
Back
Top