![]() ![]() This issue was discovered in November of 2018 more or less, and the cause was not discovered until March/ April of 2020, when I was in the middle of a UI rewrite, then my idea was releasing all changes and fixes at once with Webcamoid 9, and I though it won't take that much for a new release, so I decided that the best solution was helping people with their problem and offering them to use the daily build mean while. What needs to be gently pointed out here is that keeping your release version with its current behaviour is irresponsible. This is not true, the camera is not physically damaged, and it can be fixed as said before. That if they use this software it may permanently affect their webcam in a way only finding a daily build will fix. Turning auto controls on, or reconnecting the camera, fix the problem.Ī pinned issue in the github tracker is not sufficient warning to peopleĪ pinned issue in the github tracker is like a notice in the bottom of a locked file cabinet in the back of a disused lavatory with a sign on the door saying "beware of the leopard". ![]() OBS actually has support for camera controls too. VirtualDub2 and OBS both couldn't fix the problem. ![]() Way the release version uses to turn off the auto-exposure does it in a way that some other software can't turn back on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |