Hey all,
In trying out live review in some admittedly weird environments, I’m finding that there might be a need for some remote error handling. For instance, if a file for some reason (say a slow disk that times out) isn’t available during a synchronized session, it would be nice if the failing session could ask peers what the timeline duration is so that it can make the failed slug the same length, otherwise the timing on syncronization is entirely off since timelines are different lengths.
Is this something that you’ve exposed to developers (sending custom network signals so we can handle cases like this) or even better, is this something on your radar?
Thanks,
-Kessler