-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black border around volume change bar and progress bar became much too thin #14501
Comments
|
Yes I realize there's an option to change it. I'm asking why it changed. This is a regression. |
It was changed because it looks better. |
Can you point to the commit/line that was changed? I want to know the manner of the change so I can precisely revert it. And no it doesn't look better. The bar border size is practically invisible now because it is so thin. The border exists for a reason, so that the OSD doesn't blend into the background on white images. Try viewing it from a good distance away on a 4k TV. |
What was the purpose of the Also, thank you, I set the value to 1 which seems to be a good match for the OSD and stats border thickness. Also, I really suggest watching on a 4k tv, sat a good distance away from you, especially if you're somewhat nearsighted. It doesn't look good at all. It just looks like it's almost gone. |
dent is the size of chapter markers and is proportional to the border. Giving them a minimum value makes them clearly visible even with a smaller border. |
It shouldn't be an issue here. |
mpv Information
Other Information
Reproduction Steps
Use on a 4k window. Use --no-config and change the volume level or seek. Observe that the border around the drawn OSD is much thinner than it used to be.
Expected Behavior
The bar should look something like:
Actual Behavior
Instead it looks like:
Log File
Not sure what log file would demonstrate this.
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: