Additional board variants to workaround the Quest Pro's IRLED flicker effect#35
Open
OrendCross wants to merge 1 commit intoEyeTrackVR:mainfrom
Open
Additional board variants to workaround the Quest Pro's IRLED flicker effect#35OrendCross wants to merge 1 commit intoEyeTrackVR:mainfrom
OrendCross wants to merge 1 commit intoEyeTrackVR:mainfrom
Conversation
…ing effect By default, using the OpenIris firmware on a ESP32S3 paired with a Quest Pro results in the camera witnessing a strobing/flickering effect of the Quest Pro's IR LED Array, preventing applications from gaining meaningful data from the camera feed. Downsampling the XCLK_FREQ to '10500000' resolves this issue on my Seeed Studio ESP32S3-Sense. While there is no flicking, the resulting image is locked to 30FPS and ~30ms in my testing. I cannot test if this will resolve the issue with other boards; but I believe it is safe to assume this will work with Project Babble as it uses a ESP32S3, so I have included it as well. I believe some ESP32 supported cameras have a 'Strobe Sync' pin available on their pinouts, but whether the camera modules are able to interact with it, or if using those supported cameras is viable is beyond me.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default, using the OpenIris firmware on a ESP32S3 paired with a Quest Pro results in the camera witnessing a strobing/flickering effect of the Quest Pro's IR LED Array, preventing applications from gaining meaningful data from the camera feed.
Downsampling the CONFIG_CAMERA_USB_XCLK_FREQ to '10500000' resolves this issue on my Seeed Studio ESP32S3-Sense. While there is no flicking, the resulting image is locked to ~30FPS in my testing. I cannot test if this will resolve the issue with other boards as I only have the Seeed Studio ESP32S3; but I believe it is safe to assume this will work with Project Babble as it uses a ESP32S3, so I have included it as well.
I believe some ESP32 supported cameras have a 'Strobe Sync' pin available on their pinouts, but whether the camera modules are able to interact with it, or if using those supported cameras is viable is beyond me.