Here's a patch for this - issue was caused by the refreshxml method losing the current timeline position.
Here's a patch for this - issue was caused by the refreshxml method losing the current timeline position.