Max Audio Buffering

moodboosted

New Member

Log file above:

I currently stream on twitch and within 1 hour to an hour and a half i face audio buffering issues on various sources. This is sometimes on the game im playing, spotify, or sometimes my microphone. I am unsure how to proceed in fixing this since on OBS it says the best way to fix it is to restart the device which is what I do but it happens every single stream.

Here is a clip to show you guys what I am talking about:

Upon relaunching the game in this situation it is fixed, but I do not understand how this keeps happening in the first place. This issue has been persisting for months at this point.
I was thinking maybe the error has something to do with this line in the log file but can not find any information about it.

23:51:42.613: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' invalidated. Retrying (source: Dota Audio)
23:51:45.615: [WASAPISource::TryInitialize]:[[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]] Failed to find window
23:51:50.252: Max audio buffering reached!

Anybody have a fix for this?
 

Nuking

New Member
Are you using the new "Application Audio Capture" source?

I am currently having exactly the same issue, and it happens every time for specifically those sources. My microphone doesn't experience it whatsoever, and I've changed and done everything to try and fix this.

I hope its okay I add onto this post with my own experience; My Audio Problem

1675760442287.png
 

Attachments

  • 2023-02-06 19-28-43.txt
    149.9 KB · Views: 32

moodboosted

New Member
We have the same issue so doesn't hurt to link your same log as well:) In my situation it is not only the OBS audio source scene that faces the issue, I also use the voicemod audio driver so both of them sometimes face this error. I have received a few comments on the OBS discord on how to fix this including:

Install CoreAudio.
Use Simple Mode.
Change audio bitrate from 320kbps to 192kbps in OBS Settings > Output.
Set bitrate to 8000.
In OBS Settings > Stream make sure to link Twitch account.
Tick the box to ignore streaming service recommendations.
In OBS Settings > Video, downscale your output to 720p.

As well as if it happens again check my CPU usage in task manager to see if it is a computer bottleneck but I have a 3070 and ryzen 5
 

Nuking

New Member
We have the same issue so doesn't hurt to link your same log as well:) In my situation it is not only the OBS audio source scene that faces the issue, I also use the voicemod audio driver so both of them sometimes face this error. I have received a few comments on the OBS discord on how to fix this including:

Install CoreAudio.
Use Simple Mode.
Change audio bitrate from 320kbps to 192kbps in OBS Settings > Output.
Set bitrate to 8000.
In OBS Settings > Stream make sure to link Twitch account.
Tick the box to ignore streaming service recommendations.
In OBS Settings > Video, downscale your output to 720p.

As well as if it happens again check my CPU usage in task manager to see if it is a computer bottleneck but I have a 3070 and ryzen 5
Did anything work for you? I myself haven't tried any of those things and for me I doubt I'd have a CPU bottleneck or GPU, 9980xe with a 2080TI at like half use. Hoping this issue gets improved in a future version of OBS, as I'm still having the issue and am running 1080p 60fps, 8k bitrate with the recommendation off. Just haven't done the 720p as I would love to save the footage off twitch with the best quality.
 

Yasunaii_

New Member
Hello !
I wrote a post a little too fast I think ^^'

I saw yours only after :x

However I have the same problem as you and so I come to add my experience: https://www.youtube.com/watch?v=dFdKfdGB4-4

and I still add the message that I wrote in case he is interested I put more information ^^.

 

moodboosted

New Member
Did anything work for you? I myself haven't tried any of those things and for me I doubt I'd have a CPU bottleneck or GPU, 9980xe with a 2080TI at like half use. Hoping this issue gets improved in a future version of OBS, as I'm still having the issue and am running 1080p 60fps, 8k bitrate with the recommendation off. Just haven't done the 720p as I would love to save the footage off twitch with the best quality.
Honestly nothing has worked for me I still have the problem even though I don't really see my CPU spike, I think my problem is with is my computer can't handle so many audio drivers that I am requiring my GOXLR to use since that is when the problem started to occur.

I am going to test changing my audio quality like I wrote people suggested in the OBS discord and I will get back to you:)
 

moodboosted

New Member
We have the same issue so doesn't hurt to link your same log as well:) In my situation it is not only the OBS audio source scene that faces the issue, I also use the voicemod audio driver so both of them sometimes face this error. I have received a few comments on the OBS discord on how to fix this including:

Install CoreAudio.
Use Simple Mode.
Change audio bitrate from 320kbps to 192kbps in OBS Settings > Output.
Set bitrate to 8000.
In OBS Settings > Stream make sure to link Twitch account.
Tick the box to ignore streaming service recommendations.
In OBS Settings > Video, downscale your output to 720p.

As well as if it happens again check my CPU usage in task manager to see if it is a computer bottleneck but I have a 3070 and ryzen 5
After attempting these fixes this did not stop my audio buffering issues, I will go ahead and uninstall my GOXLR drivers to see if that resolves the problem and give an update.
 

moodboosted

New Member
My problems are still persisting after all changes. However I have found the following documentation:


I am starting to think I am sharing too many sources with my GOXLR and it is interfering with the Audio Application Beta source so I am going ahead to make a change and use the Audio output capture to capture my game sound and see if the error still occurs.
 

moodboosted

New Member
I have fixed the issue on my end. I removed the applciation audio source and made my goxlr gaming driver the default application. This can be done with voicemeter to have individual audio drivers if you do not have the program. But basically it will keep saying audio buffering because OBS will check the sources every few moments and sometimes it will have an access issue. When you add things to the default OBS sound it will always monitor it and never refresh it which will stop all audio buffering errors.

Hope that helps! Sorry I couldnt fix the exact issue but it is a good work around.
 

HugoWoods

New Member
Could you explain better how you solved it? I'm in a lot of trouble with that. I really didn't get it. I don't speak English very well and even with a translator I don't understand. Could you elaborate a bit more?

thks for the help!
 

batteryman

New Member
I have the same issue with "Max Audio Buffering" on my iMac using a GreenFeathers IP camera. OBS fails every time at 3:20am, which I don't understand and the issue is always "Max Audio Buffering" . The microphone on the camera is off and the iMac has no other programmes running. I am trying to soak test the camera before moving to a remote site. The iMac is 2013 running Catalina with 2.9 mHz Quad core and 8M RAM. This issue has plagued me for months now so I put the camera on my new iMac ( 2019 3.2 gHz 6 core etc etc) I can't get a more powerful computer and OBS failed on this one, same issue, same time, 3:20 am. Any thoughts?
 

AaronD

Active Member
I have the same issue with "Max Audio Buffering" on my iMac using a GreenFeathers IP camera. OBS fails every time at 3:20am, which I don't understand and the issue is always "Max Audio Buffering" . The microphone on the camera is off and the iMac has no other programmes running. I am trying to soak test the camera before moving to a remote site. The iMac is 2013 running Catalina with 2.9 mHz Quad core and 8M RAM. This issue has plagued me for months now so I put the camera on my new iMac ( 2019 3.2 gHz 6 core etc etc) I can't get a more powerful computer and OBS failed on this one, same issue, same time, 3:20 am. Any thoughts?
I doubt it's the wall clock that triggers it. It might be the total run time. If you start at a different time, do you get the error at a different time too?
 
Top