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
Users are currently forced to choose between two modes of playback:
In play mode the time cursor increments smoothly. This is nice for offline playback when we already have the data, but is hard to use in live mode since you need to precisely match the offset and rate of data.
In follow mode the time cursor continuously jumps to the new data at the end of the timeline, but this lacks some of the smoothness of follow mode.
This is particularly noticeable in a windowed plot when viewing the data as part of a realtime stream. Any burstiness in the data, such as from network jitter, or from larger payloads like images in the data-stream cause the plot to feel stuttery.
It would be nice to have the option to turn on some degree of smoothing in follow mode at the cost of a bit of additional latency. We should be able to dynamically track both a max-latency and rate of progression of the current timeline in order to progress time forward as smoothly as possible while accounting for burstiness.
In the case of large outliers, we could then jump to the end and reset the estimator.
The text was updated successfully, but these errors were encountered:
I don't think it need to add latency if the "smoothed" value is set to alway over-estimate the time, i.e. be sightly ahead of the incoming time points. In fact, we HAVE to do that to always see the latest incoming data.
Users are currently forced to choose between two modes of playback:
This is particularly noticeable in a windowed plot when viewing the data as part of a realtime stream. Any burstiness in the data, such as from network jitter, or from larger payloads like images in the data-stream cause the plot to feel stuttery.
It would be nice to have the option to turn on some degree of smoothing in follow mode at the cost of a bit of additional latency. We should be able to dynamically track both a max-latency and rate of progression of the current timeline in order to progress time forward as smoothly as possible while accounting for burstiness.
In the case of large outliers, we could then jump to the end and reset the estimator.
The text was updated successfully, but these errors were encountered: