The forward and backward searches are delayed and slow. Is this issue possible to fix?

[zhouxinghong]

mpv Information

mpv v0.40.0-dev-gb6c35b55a Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Nov 27 2025 21:56:38
libplacebo version: v7.357.0
FFmpeg version: git-2025-11-27-75b8567
FFmpeg library versions:
   libavcodec      62.21.100
   libavdevice     62.2.100
   libavfilter     11.10.101
   libavformat     62.6.103
   libavutil       60.19.101
   libswresample   6.2.100
   libswscale      9.3.100

Other Information

- Windows 10 19044 x64
- CPU i5 3210
- Memory 8G
- Graphics card:
-  4.1. Intel Integrated Graphics 4000
-  4.2. NVIDIA: GT610
- Western Digital mechanical hard drive 5400 rpm
- Windows version:10 19044 
- GPU model, driver and version: GT610
- Source of mpv:https://github.com/mpv-player/mpv/actions/runs/19823285266/artifacts/4726646641
- Latest known working version:
- Issue started after the following happened:

Reproduction Steps

The forward and backward searches are delayed and slow. Is this issue possible to fix?

Expected Behavior

Forward and backward searches are no longer delayed or slow; they are as smooth as playing a local video.

Actual Behavior

The forward and backward searches are delayed and slow.

Log File

The forward and backward searches are delayed and slow. Is this issue possible to fix?

Sample Files

No response

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

• [x] I tested with the latest mpv version to validate that the issue is not already fixed.
• [x] I provided all required information including system and mpv version.
• [x] 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.
• [x] I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• [x] I attached the full, untruncated log file.
• [x] I attached the backtrace in the case of a crash.

[dancingmirrors]

Have you tried --video-latency-hacks=yes and --hwdec=dxva2 or --hwdec=dxva2-copy? As I recall I used to use those on Windows with similar hardware. However video-latency-hacks has some other annoying side effects on other platforms.

[dancingmirrors]

Also --profile=fast because the defaults are too heavy for that hardware.

[zhouxinghong]

Also --profile=fast because the defaults are too heavy for that hardware.

Adding the --profile=fast parameter will cause a sharp drop in image quality, therefore, it is not an ideal solution.

When playing HLS content on the same PC using other media players, they can search forward and backward very smoothly, without any lag or slowdown. That's why I felt it necessary to report this issue.

[dancingmirrors]

I doubt you will get any help because you didn't provide a log.

[Jules-A]

Adding the --profile=fast parameter will cause a sharp drop in image quality, therefore, it is not an ideal solution.

But did it fix the issue???

If it did then maybe try --scale=robidouxsharp , it's way better quality than bilinear in the fast profile and is a lot faster than lanczos in the default profile.

[zhouxinghong]

I disagree with using the --profile=fast approach.

If it did then maybe try --scale=robidouxsharp , it's way better quality than bilinear in the fast profile and is a lot faster than lanczos in the default in the default profile.

This method requires further testing to determine whether the results are satisfactory.

[Jules-A]

I disagree with using the --profile=fast approach.

I wasn't asking if you disagreed with it... I was asking if back/forward seeking is no longer slow when using --profile-fast , in-case it's another issue like caching (since you also have a HDD). It's impossible to tell what is causing your issue if you don't tell us anything....

[zhouxinghong]

I wasn't asking if you disagreed with it... I was asking if back/forward seeking is no longer slow when using --profile-fast , in-case it's another issue like caching (since you also have a HDD). It's impossible to tell what is causing your issue if you don't tell us anything....

I will conduct detailed tests using --profile=fast and --scale=robidouxsharp in the next use, and then publish a detailed test report and log records.