libobs: Fix debug spam from maxed buffering

When audio buffering is maxed, certain sources will always repeat the
same debug logging message of "render audio source [name] has gone
backwards", which shouldn't apply if the audio timestamp is 0 rather
than a valid audio value.
This commit is contained in:
jp9000 2022-04-24 07:51:43 -07:00
parent e3bdb4ca7b
commit 090613851e

View File

@ -577,7 +577,7 @@ bool audio_callback(void *param, uint64_t start_ts_in, uint64_t end_ts_in,
/* if a source has gone backward in time and we can no
* longer buffer, drop some or all of its audio */
if (audio_buffering_maxed(audio) &&
if (audio_buffering_maxed(audio) && source->audio_ts != 0 &&
source->audio_ts < ts.start) {
if (source->info.audio_render) {
blog(LOG_DEBUG,