Repository navigation
Visor Occlusion Detection / “LED Covered” Issue After First Capture #53
Sethinfinite
started this conversation in
General
Replies: 1 comment
|
Thanks, I'm glad Visor gave your glasses another chance. Occlusion detection is the glasses' own setting for something blocking the camera's view. The "LED covered" block is a separate check: the glasses won't record while the capture light is covered, so the people around you can always see it. It's in Meta's firmware, and I'm not going to work around it. Why it lets the first capture through, and why a hat now sets it off, also comes from the firmware, so I can't change it. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I just downloaded the APK, and so far I like it a lot more than the Meta app. Thanks for putting this together.
I do have one issue I'm trying to understand. I noticed the Occlusion Detection option under the camera settings, but testing it both on and off doesn't seem to change the behavior.
To clarify exactly what I'm seeing:
I disconnect/re-pair the glasses or delete/reinstall the app.
On the very first capture, I can intentionally cover the LED completely and the capture still works.
I then try another capture without changing anything.
From the second capture onward, I get the "LED covered" warning and the capture is blocked.
Turning Occlusion Detection on or off doesn't change this behavior.
If I disconnect/re-pair or reinstall again, the same sequence repeats: first capture works, then the LED-covered restriction starts triggering afterward.
I didn't really have this issue until a recent Meta update. Since then, the detection also seems much more sensitive in normal use, such as when wearing a hat.
Could you clarify what the Occlusion Detection setting in Visor actually controls? Is the "LED covered" restriction a separate check or firmware flag? If so, is there a way in Visor to override or change that behavior for testing?
The repeatable part that stands out to me is that the first capture after a fresh connection/setup works, but the restriction appears to kick in immediately afterward.
Thanks again for building this. I was honestly about ready to toss the Metas and accept that I had an expensive pile of circuits and plastic. The Meta app has been screwed up for so long that finding Visor actually gives me some hope for these things again. This app is seriously impressive, and I really appreciate the work you've put into it.
All reactions