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
After some time, the underlying audio system will call the callback again, and the algorithm will be executed again. This is an implementation detail that should not be observable, apart from the latency implications.
Actually, I think this implementation detail was always observable. If the main thread kept asking for currentTime, it can see that currentTime gets updated several times very close together, and then there's a pause of a few milliseconds before this burst of updates happen again
Can't quite delete the whole note because the next paragraph starts with
The system-level audio callback
So, maybe just delete most of the note, but leave the little bit about system-level callback. Or modify the next paragraph in some way. Also, an offline audio context doesn't have a system-level audio callback since there's no connected audio device.
Either way, more editing is required than just deleting the note.
The note about rendering in Section 2.4 says
Actually, I think this implementation detail was always observable. If the main thread kept asking for
currentTime
, it can see thatcurrentTime
gets updated several times very close together, and then there's a pause of a few milliseconds before this burst of updates happen againAlso, getOutputTimestamp can show this too.
Delete the sentence about not being observable?
The text was updated successfully, but these errors were encountered: