You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
frames_queued is in the TripleBuffer, but total_output_latency_frames is not (it's a separate atomic), so position() might be using two values from different invocations to the audio output callback. This is probably not a big problem in practice, because total_output_latency_frames probably does not vary very much if the audio callback is called at consistent times. But it's probably still worth fixing, by moving total_output_latency_frames into the TripleBuffer.
The text was updated successfully, but these errors were encountered:
mstange
changed the title
frames_queued and total_output_latency_frames may not update in a synchronized function
frames_queued and total_output_latency_frames may not update in a synchronized fashion
Jul 29, 2020
frames_queued
is in the TripleBuffer, buttotal_output_latency_frames
is not (it's a separate atomic), soposition()
might be using two values from different invocations to the audio output callback. This is probably not a big problem in practice, becausetotal_output_latency_frames
probably does not vary very much if the audio callback is called at consistent times. But it's probably still worth fixing, by movingtotal_output_latency_frames
into theTripleBuffer
.The text was updated successfully, but these errors were encountered: