This thread has more detail:
El, to answer your question "Thank you for reaching out regarding this issue. If we were to add this feature in the capture API logic, how would you like to see it implemented?" The answer is, just fix the recorded offset. Arguably it's a bug. Thanks, Chris