Hi
Our application (still 0.10.34 based) is polling queues for current-level-time properties on all queues, every second, for monitoring purposes.
After the pipeline runs for a while, it seems to be randomly reporting huge current-level-time properties on a specific queue placed right after a matroskamux.
max-size-* are untouched (default), and when polling i read the current max-size-time which is the default one (1000000000 / 1000 ms).
Example huge values are 20138760ms, 6433150ms, 34000ms...
Does it ring a bell to anyone ?
Btw, it doesn't seem to have an impact, but seems shady anyway ...
Cheers
Florent
_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
