conditional auto profiles may not be triggered if their properties in `profile-cond` change too fast
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv Information
mpv v0.40.0-dev-gdbd7a905b Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
built on Dec 4 2025 16:44:20
libplacebo version: v7.358.0
FFmpeg version: git-2025-12-04-e0845ec
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 version: Win10 22H2 [Version 10.0.19045.6456]
- GPU model, driver and version:
- Source of mpv: https://nightly.link/mpv-player/mpv/workflows/build/master
- Latest known working version:
- Issue started after the following happened:
Reproduction Steps
- config files
mpv.conf
log-file=log.txt
osd-msg1=${speed}
input-ar-rate=40
[clamp_speed_min]
profile-cond=speed < 0.1
speed=0.1
[clamp_speed_max]
profile-cond=speed > 4
speed=4
input.conf
UP add speed 0.1
DOWN add speed -0.1
- hold down the up arrow key and don't release it
Expected Behavior
speed reset to 4 when it exceeds 4, as the clamp_speed_max profile expected.
Actual Behavior
after holding down the up arrow key for a while, the speed exceeded 4.
https://github.com/user-attachments/assets/c9626659-4ad8-4bd9-9807-aff09e9b9308
the larger input-ar-rate is, the easier it is to reproduce this issue.
after reducing its value to 20, the issue will no longer reproduce.
Log File
Sample Files
N/A
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the shown mpv.conf and input.conf, holding the Up arrow with input-ar-rate=40 and observing the speed and log.txt. Trace how conditional profiles react to rapid speed changes, then verify that speed is clamped at 4 while repeated input continues; compare behavior with input-ar-rate=20.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100