DonF •⚡
New Member
I'm not here to pick a fight, and I'm not asking anyone to reopen anything. I'm trying to understand one thing: why a report backed by measurements was rejected, because that's the only part I couldn't get answered.
OBS 33.0.0, Linux, 60 fps, no stream, no recording, no replay buffer. "Skipped frames" increases by exactly 1 every 30.0 s, indefinitely, with a stable phase.
I spent about four hours measuring before reporting anything, with an AI assistant helping me structure the results — the measurements are mine. I eliminated, one by one and each time by measurement: an empty scene (same result), the cameras, the capture filters, the 24 browser sources tested individually in an isolated Chromium, the docks, the audio clock, the PipeWire capture, the GPU (no throttling, no Xid), the refresh rate, CPU affinity, the workqueues and vsync. Over 300 s: 10 increments, exactly 30.0 s apart, 10/18000 = 556 ppm. The counter maps to `video->lagged_frames`, which has a single writer, `libobs/obs-video.c:825`, reached only when `os_sleepto_ns()` returns false.
I filed that as GitHub issue #14165 with the code chain and the numbers, and asked which evidence would be accepted. The account was blocked before any technical exchange, the issue was closed in one line, and a reply from another account asking the same question was locked as spam 13 minutes later.
So my question is a simple one, and a one-line answer is all I need: is this behaviour by design — the counter reporting the video thread re-synchronising its clock — or is it something you would consider a defect? If it's by design, I'll write it in my own notes and stop there. I'm not looking for a winner here, just for the reason.
OBS 33.0.0, Linux, 60 fps, no stream, no recording, no replay buffer. "Skipped frames" increases by exactly 1 every 30.0 s, indefinitely, with a stable phase.
I spent about four hours measuring before reporting anything, with an AI assistant helping me structure the results — the measurements are mine. I eliminated, one by one and each time by measurement: an empty scene (same result), the cameras, the capture filters, the 24 browser sources tested individually in an isolated Chromium, the docks, the audio clock, the PipeWire capture, the GPU (no throttling, no Xid), the refresh rate, CPU affinity, the workqueues and vsync. Over 300 s: 10 increments, exactly 30.0 s apart, 10/18000 = 556 ppm. The counter maps to `video->lagged_frames`, which has a single writer, `libobs/obs-video.c:825`, reached only when `os_sleepto_ns()` returns false.
I filed that as GitHub issue #14165 with the code chain and the numbers, and asked which evidence would be accepted. The account was blocked before any technical exchange, the issue was closed in one line, and a reply from another account asking the same question was locked as spam 13 minutes later.
So my question is a simple one, and a one-line answer is all I need: is this behaviour by design — the counter reporting the video thread re-synchronising its clock — or is it something you would consider a defect? If it's by design, I'll write it in my own notes and stop there. I'm not looking for a winner here, just for the reason.