There seems to be no way to use scaletempo with speed parameter (and scaletempo2 lacks similar one)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Important Information
Provide following Information:
- 0.35.1
- Linux Mint 21
- mpv built from source
- No GPU card
Reproduction steps
mpv --audio-pitch-correction=no --af=scaletempo=speed=pitch --no-config --log-file=output.txt file_to_play
mpv --audio-pitch-correction=yes --af=scaletempo=speed=tempo --no-config --log-file=output.txt file_to_play
For above runs I've found no scaletempo2 in logs.
mpv --audio-pitch-correction=yes --af=scaletempo=speed=pitch --no-config --log-file=output.txt file_to_play
See in Log below.
Expected behavior
When scaletempo passed as an option use it instead of scaletempo2 always.
Actual behavior
When scaletempo passed as an option it is used instead of scaletempo2 if reaction to speed is set as default: tempo, but not for e.g. pitch.
Log file
[ 1.297][v][cplayer] Set property: speed -> 1
[ 1.343][v][autoaspeed] adding NOT scaletempo2
[ 1.343][v][autoconvert] inserting resampler
[ 1.343][v][swresample] format change, reinitializing resampler
[ 1.343][v][swresample] 48000Hz stereo float -> 48000Hz stereo floatp
[ 1.343][v][af] [userspeed] (enabled)
Related
Maybe related: https://github.com/mpv-player/mpv/issues/8705
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
Start by tracing the scaletempo and scaletempo2 selection from the autoaspeed log entry, comparing behavior with speed set to tempo versus pitch. Review the related issue #8705 for context and use the provided mpv reproduction commands and log output to verify that the requested filter choice is honored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100