stats.lua when watching 3D. Incorrectly formatted info stats with gpu.next vs gpu #12462
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv Information
Other Information
- Windows version:
- GPU model, driver and version:
- Source of mpv:
- Latest known working version:
- Issue started after the following happened:
Reproduction Steps
Thanks for trying to fix this. It works fine for Over/Under. But looking at your stereo-in command you only have options for half sbs, not full sbs. So I'm guessing there isn't any code in mpv for full sbs which results in the problem below.
Expected Behavior
See screenshots
Actual Behavior
See screenshots
Log File
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
- I tested and confirmed that the issue exists with the latest release version or newer.
- 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
Start with stats.lua and trace how gpu.next and gpu are formatted while 3D playback is active; compare the displayed output for Over/Under and the half/full SBS cases described in the issue. Done means the GPU information is formatted correctly in the affected 3D mode, matching the expected screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100