New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CALL SEEK #1086
Comments
@5opr4ni can you send me a good file to test with? |
Hi @ronag I will wetransfer a file 720p50 with framenumbers in it so that you easier can see the issue. Play the video: Pause it: Do a Call:
The thing that happens is that the video jumps a couple of frames forward although the CALL OK reports that it has jumped to the seeked frame. Do another Call: And then try this several times: Played around with these and the same strange behavior. The thing I can see clearly is that the first seek command absolutely don't do what it should but the second seek gets you close to what you want. If you do what Issue #1102 says, you still get time 0.0 in both OSC and in INFO 1-10, but you end up in the correct frame. Last thing: If you have reached the last frame, SEEK doesn't work. /o |
Now SEEK works as expected. |
Expected behaviour
CALL 1-10 SEEK 123 should go to frame 123
Current behaviour
If you fire off a call like the command above and do that in a sequence as if you joged a jogwheel and sent the values. (123, 124, 125, 126......) The result is a bit unpredictive, it advances but it jumps back and forth in time, and the other ways to do a seek, like rel, in, out is also unpredictive.
Have a look here!
https://youtu.be/rvsemtNNfvE
Steps to reproduce
CALL 1-10 SEEK 123
CALL 1-10 SEEK 124
CALL 1-10 SEEK 125
CALL 1-10 SEEK 126
v2.2 Beta 9 x64
Win10
The text was updated successfully, but these errors were encountered: