Closed SBoudrias closed 9 years ago
Yikes! Sorry about that. The unit tests are still passing, so that's a little surprising. Do you have a test case that reproduces the issue?
If you don't have one, don't worry about it — I should have some time tomorrow to get to the bottom of this.
I don't have a reduced test case, but I can point you where the bug is.
It's these lines, since the code changed to do a check on the timestamp, the value of normalizedPosition
is always 0 when it's triggered from a seek
call.
Got it. It must be something to do with the recent "delay" functionality. I'll bet this can be demonstrated with a unit test that utilizes both the delay functionality as well as seek
.
I just pushed and released a fix(1.4.2). Careless mistake on my part. Sorry about that. Thanks for reporting!
Looks like the 1.4 release is breaking
seek
. Not sure what changed, and I haven't investigated the issue yet.