Breaking change in frame count between 3.0.6 and 3.1.0

[daiscog]

After upgrading to 3.1.0 some of our tests are now failing without any changes to the test code. For example, the following is showing the actual values being emitted 18 frames earlier than expected:

The tests pass again after dropping back to version 3.0.6, with no other changes.

I've not had time yet to look into this in detail, but I will at some point try to reduce it to a minimal reproducible example and post more detail below.

Sharing this here for the time being for awareness and so others can investigate in the mean time if they want.

[Romjkez]

Same for us, had to downgrade to 3.0.6

[just-jeb]

These are the two changes that made it to 3.1.0: #501, #502

I suspect that this change caused the issue (the only thing that possibly could have impact).

The question is indeed how we didn't catch it in the tests so a minimal repro would be very helpful, @daiscog.

@MillerSvt do you have any idea why this could happen?

[MillerSvt]

I need minimal repro. It seems some tests, was written incorrect. But I have no idea why.

Same for us, had to downgrade to 3.0.6

@Romjkez Have you also moved 18 frames in your project?