Encoding/QSV - Current frame rate is unsupported
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv version and platform
Windows, git version, shinchiro scripts plus libmfx for QSV encoders
Reproduction steps
mpv.com any-video.mkv -o out.mkv --no-audio --no-sub --vf=fps=23.976 --of=matroska --ovc=h264_qsv --ovcopts=b=2000000
Actual behavior
Encoding fails:
[ffmpeg] h264_qsv: Current frame rate is unsupported
[ffmpeg] h264_qsv: some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
It fails the same way with or w/o "--vf=fps=23.976" part.
In earlier versions it used to work with --ofps=23.976.
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 reproducing the failure with the provided mpv command on Windows using the QSV encoder, then compare it with the earlier --ofps=23.976 behavior. Trace the mpv-to-FFmpeg QSV encoding path and check how the current frame rate is passed. Done means a 23.976 fps QSV encode succeeds without the unsupported-frame-rate error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100