-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[RFC] vo_gpu: remove deprecated options --gamma-factor and --gamma-auto #14369
base: master
Are you sure you want to change the base?
Conversation
@@ -40,7 +40,7 @@ enum { | |||
VO_EVENT_ICC_PROFILE_CHANGED = 1 << 2, | |||
// Some other window state changed (position, window state, fps) | |||
VO_EVENT_WIN_STATE = 1 << 3, | |||
// The ambient light conditions changed and need to be reloaded | |||
// Deprecated. The ambient light conditions changed and need to be reloaded | |||
VO_EVENT_AMBIENT_LIGHTING_CHANGED = 1 << 4, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be removed too, no? It is not public API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, i wasn't sure how to handle this since we would get a 'hole' in that enum or would we want to renumber it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hole is fine, I think, to keep it simple. There are plenty of bits left for new values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If something new is added later, we can always just fill the hole in too.
Download the artifacts for this pull request: |
FWIW I wonder what is the alternative of |
#10699 (comment) #11153 |
Note that after deprecating Line 499 in 71d3f41
I suggest to undeprecate |
I'm not sure |
why was this option deprecated in the first place? |
https://github.com/mpv-player/mpv/wiki/GPU-Next-vs-GPU
Not sure if it was related. |
from the commits and the PR i could only gather "outdated information" and "--gamma-auto not working". though both aren't really a reason to deprecate the options. for the former update the info, for the latter fix it or open an issue (without knowing what exactly is broken, hard to judge). seems like the initial use case for then i am also of the opinion to undeprecate both options. |
I wonder what is "BPC"? I cannot find the word in any other places. |
black point compensation, is my guess. at least that's what i see when working with colour profiles and related. |
--gamma-factor and --gamma-auto were deprecated in 0.35 (ac39661 and 2207236). the latter was only used on macOS.
the equivalent client API functionality wasn't officially deprecated.
what i would like to discuss:
do we want to remove those options already?
if yes, how do we want to remove them? since the client API equivalent wasn't deprecated, removal of the functionality can't be done immediately?
do we want to deprecate the client API functionality first in the next release and remove the functionality in one of the releases after the next one?
the client API deprecation change should probably be taken separately?
hope i found all the dependent code and removed it properly.