My audio crapped out again tonight in the middle of a live stream (log link included)

[AM_radi0]

I had been experiencing this problem, but the past two or so weeks - after some tests and troubleshooting - I though I had resolved it. Things were working fine. However, tonight, while the stream health was top notch, my audio crapped out again. I'm starting to get frustrated with not being able to find the cause. I never know when my music livestream is going to fall apart.

Log link: https://obsproject.com/logs/NRqON1R9rsFPfQdo

On analysis of the log file, this jumped out at me:

Audio buffering hit the maximum value. This can be an indicator of very high system load and may affect stream latency or cause individual audio sources to stop working. Keep an eye on CPU usage especially, and close background programs if needed.

Occasionally, this can be caused by incorrect device timestamps. Restart OBS to reset buffering.

Source affected (potential cause): Komplete Audio 6

My CPU load never went beyond like 8%. The Audio 6 has never given me problems in all the years I've used it. The only thing I can think of is that the only other thing running behind OBS is Chrome (for setting up the stream and monitoring stream health on ReStream). I know Chrome is a resource hog, but like I said before - my CPU resources never jumped above like 8%. My mac is new and has an M2 processor and runs Sequoia.

I'm at my wit's end with this problem. Any help or input would be greatly appreciated. I stream weekly, so I would really love to resolve this before next Wednesday.

Thanks in advance.

 

[AaronD]

My CPU load never went beyond like 8%.

Is that from OBS's report? Or from the OS?

OBS can't see anything beyond itself, so it can only report that. Take that number with a big grain of salt. The OS can see everything, so its number is accurate...with some more caveats:

What is the percentage actually of?

• Is it a single core, so that 2 cores running flat out would report 200%?
  Or is it the total of all cores, so that 2 cores running flat out on a 4-core machine would report 50%?
• Is it the theoretical performance of the maximum clock speed, so that thermal throttling causes it to peg at something less than 100% per core?
  Or is it the actual performance at the moment, so that thermal throttling causes the report to increase while doing the same amount of work?

Etc.