Postby adrian » 31 Jul 2018 07:55
Hi Jean-Baptiste Kempf,
I had the same issue and disabling the hardware acceleration under the Preferences > Input/Codecs worked. Though it took me a few hours to find this thread using different keywords on Google.
So, my question now is, why? What is causing this issue? Is this a known issue? Is it caused by only certain types of hardware? Is there a list of known offenders? Does it matter what OS is being used? Maybe a verification step could be done in the code to check that the gamma has actually changed so that automatic detection can actually work? Or is that code already there but is failing?
Sorry for all the Qs. but I like VLC and it is a shame that this failure happens and wonder if anything can be done to stop this from happening or at the very least, warn the user that a problem could occur and proposing a possible solution, saving the user hours of frustration. Short term solution could be that a help balloon pop up saying this could be an issue the first time a user slides the gamma control after VLC startup, and proposing turning off hardware acceleration (specifying where that is since the preferences is a large beast of options). The balloon could have a "Don't show me again" checkbox as well.
Thoughts?
A