timeInfo.currentTime passed to PaStreamCallback is not strictly conformant to spec
The PaStreamCallback documentation for timeInfo.currentTime reads:
"the time in seconds when the stream callback was called"
At the moment the buffer processor may call the stream callback multiple times without intervention from the calling host API, so what is currently happening is:
"the time the portaudio buffer processor started processing the host buffer which the callback is involved with filling".
I think an accurate "current time" should be passed to the callback when possible. This was the reason ticket #3 existed.
One resolution would be to change the buffer processor to return after each call to PaStreamCallback so the host api implementation could update the currentTime field.
"the time in seconds when the stream callback was called"
At the moment the buffer processor may call the stream callback multiple times without intervention from the calling host API, so what is currently happening is:
"the time the portaudio buffer processor started processing the host buffer which the callback is involved with filling".
I think an accurate "current time" should be passed to the callback when possible. This was the reason ticket #3 existed.
One resolution would be to change the buffer processor to return after each call to PaStreamCallback so the host api implementation could update the currentTime field.
Leave a comment