-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clamp offset in VisualPlayPosition with extra time of two vsync interval #12470
Conversation
It turns out that this is required to not clamp in all good conditions. Clamping causes a jittery waveform and must not happen under normal conditions
@m0dB can you confirm this fix? |
looks good to me, at least I don't notice any regression. |
Shouldn't we log a warning, if this clamping happens? |
the warning is now in place. |
LGTM! Thank you! |
Why might want to limit the logging of these warnings...
|
There is already a boolean intended to avoid log spam. Each warning is indicating a stucked waveform and a visible stutter. If you see them all the time without transport issues it indicates broken syncing. I have no idea how to remove this spam without removing the warning altogether. I think it is better to fix the root cause if we can. On Linux I was not able to produce a single warning. A first step would be to make this warning more verbose. |
It turns out that this is required to not clamp in all good conditions. Clamping causes a jittery waveform and must not happen under normal conditions.
This removes one cause of jittery waveforms, during my tests. All other tests where successful with reasonable values. So I guess that the remaining jitters are real vsync misses.
The clamping has been introduced to not move the waveform with a stalled audio engine. This still works, but is done one vsync cycle later.