Hey!
This is a weird one - could you let me know if it still happens when "ignore time scale" is true/false, and if "remember read position" is true/false?
It might just be a quirk of the editor if those don't effect it, since meshes reading out should be based on an internal timer, not Time.time.