From 090613851eb7b44dd798a79f76477a65a74bfe42 Mon Sep 17 00:00:00 2001 From: jp9000 Date: Sun, 24 Apr 2022 07:51:43 -0700 Subject: [PATCH] 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. --- libobs/obs-audio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libobs/obs-audio.c b/libobs/obs-audio.c index 68a933a67..391b1497c 100644 --- a/libobs/obs-audio.c +++ b/libobs/obs-audio.c @@ -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,