-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can't pause/rewind/ff new depth-anything beta build videos #24
Comments
Weird, in my environment it works with See if the key is being pressed using |
Oh I am using mostly the large model with 4090 here, does it work on large model for you? I am once again out of town so I've been less active. |
Works for me. The model selected should not influence that behavior. |
Still doesn't work for me and did a fresh download, what keys should I be pressing? I did numberpad 5 for pause, etc. It works on older version when I test it with default mode and midas hmm. Do you have maybe a video of exactly how you are launching, loading the depth-anything model, then showing you can pause the video? Not sure if I am doing something wrong here. |
Well, it should be not different from loading a midas onnx file. Does the console output any error? Test if the key is pressed by changing here: //CHECK `Keymapper.Inst` is not null
if (Keymapper.Inst == null)
Debug.LogError("Keymapper.Inst is null");
else
Debug.Log($"Pause: {Keymapper.Inst.VideoPause}");
if (Input.GetKeyDown(Keymapper.Inst.VideoRewind))
Skip(-5f);
else if (Input.GetKeyDown(Keymapper.Inst.VideoPause)) {
//CHECK IF THE KEY IS BEING PRESSED
Debug.Log("Pause button pressed");
PausePlay();
}
else if (Input.GetKeyDown(Keymapper.Inst.VideoForward))
Skip(+5f); |
Sorry for delay, I will get back to this soon. I didn't see a console error. I will try what you wrote above soon. |
The new Unity beta build with depth-anything works great for me, the only issue I have is the numpad 5, 6, 4 no longer fast forward rewind or pause when using the depth-anything model when playing a video. Any way to fix this?
The text was updated successfully, but these errors were encountered: