Skip to content
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

slow seeking when using heavy filters #14974

Open
6 tasks done
luikaire opened this issue Oct 1, 2024 · 0 comments
Open
6 tasks done

slow seeking when using heavy filters #14974

luikaire opened this issue Oct 1, 2024 · 0 comments

Comments

@luikaire
Copy link

luikaire commented Oct 1, 2024

mpv Information

mpv 0.38.0-UNKNOWN Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Aug 20 2024 14:03:22
libplacebo version: v7.349.0
FFmpeg version: 7.0.git
FFmpeg library versions:
   libavcodec      61.11.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.34.100
   libswresample   5.2.100
   libswscale      8.2.100

Important Information

- Platform version:
- GPU model, driver and version:
- Source:
- Introduced in version: all

Reproduction Steps

Use a CPU/GPU compute heavy filter that runs in real-time under normal playback conditions. Example is a vapoursynth script that uses RIFE-gpu for frame interpolation
(styler00dollar/VapourSynth-RIFE-ncnn-Vulkan#29)
sample vapoursynth script is attached which uses styler00dollar/VapourSynth-RIFE-ncnn-Vulkan RIFE models
motioninterpolation_rife_sudo.vpy.txt

Expected Behavior

Normal seeking (without temporary "hanging")

Actual Behavior

When using heavy filters (like RIFE-vapoursynth for frame interpolation) mpv hangs for a few seconds before seeking . This behaviour is not seen when not using filters or using fast filters

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant