You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Linux version: Arch
- Kernel Version:
- GPU Model:
- Mesa/GPU Driver Version:
- Window Manager and Version:
- Source of mpv: git
- Latest known working version: Yesterday's build
- Issue started after the following happened: Some recent commit
Reproduction Steps
Set sub-line-spacing to -15.
Expected Behavior
The renderer used to draw the lines closer together.
Actual Behavior
The option is ignored and the following error is printed:
The sub-line-spacing option is out of range: -15
Error parsing option sub-line-spacing (parameter is outside values allowed for option)
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.
The text was updated successfully, but these errors were encountered:
FLT_MIN is a small positive number (1.175494e-38), so the check v <
FLT_MIN introduced in 0e7f9c3 made all 0 and negative float option
values error, e.g. panscan=0 or video-align-y=-1.
Fixes 0e7f9c3, fixesmpv-player#15728.
mpv Information
Other Information
Reproduction Steps
Set
sub-line-spacing
to-15
.Expected Behavior
The renderer used to draw the lines closer together.
Actual Behavior
The option is ignored and the following error is printed:
Log File
output.txt
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.The text was updated successfully, but these errors were encountered: