On Fri, May 22, 2015 at 1:45 PM, Tanu Kaskinen <tanuk at iki.fi> wrote: > On Mon, May 18, 2015, at 21:56, Sébastien Barthélémy wrote: > > In some cases our application fails to get the stream latency: our > > callback, which was set using pa_stream_update_timing_info(), is called > > (in > > stream_get_timing_info_callback [1]) with o->stream->timing_info_valid > > == > > FALSE. > > > > My guess is that, in the test a bit above ([2]). we have > > command==PA_COMMAND_TIMEOUT. > > > > Is there any way to test that hypothesis? > > The callback given to pa_stream_update_timing_info() has type > pa_context_success_cb_t, which has the "success" argument. If "success" > is false, you can get the error code with pa_context_errno(). If the > operation failed due to a timeout, the error code should be > PA_ERR_TIMEOUT. > Thank you, I did the change, and so far only got timeouts. Good news! I don't know (or remember) the reason. I would guess that it has to do > with maintaining a stable public API and avoiding unnecessary complexity > in the API. However, if there's need for enabling the rtclock stuff for > custom mainloops, I'd expect there to be some way to implement that > without breaking backwards compatibility. > Ok, I may give it a try (not sur I'll find the time). Thank you for your help so far! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20150522/330094aa/attachment.html>
