-
Notifications
You must be signed in to change notification settings - Fork 4.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
RS2_OPTION_EMITTER_ON_OFF not always working #9450
Comments
Hi @rolandgvc May I first confirm which model of RealSense camera you are using, please? The per-frame emitter on-off mode was designed for camera models with a fast global shutter. This would include D430, D435, D435i and D455. The link below, which provides information about this mode, contains a rapidly flashing image. |
Sorry, it's D455. #3066 this is the behaviour I am getting as well, just that it's not consistent. |
Thanks very much for the clarification about the camera model. It would be unnecessary to set RS2_OPTION_FRAMES_QUEUE_SIZE to 1 because '1' is the default value anyway. If you are using both depth and color streams then it may be worth setting it to '2' though, as described in the 'Latency Vs Performance' section of Intel's Frame Buffering Management documentation. Does setting the frame queue size to '2' provide any improvement in performance, please? |
Unfortunately not. Could it be from the kernel and realsense version? |
I do understand your situation, as I have handled a couple of past cases where the dot pattern has been visible on the "off" frame when using RS2_OPTION_EMITTER_ON_OFF, so only capturing frames where the emitter status was off did not prevent the chance of such frames having dots. My understanding is that it was related to the environmental lighting conditions at the time of capturing the image, and that the visibility could change at different times of day depending on the natural lighting level. |
I am not aware of a solution to this issue when using RS2_OPTION_EMITTER_ON_OFF, having studied the problem in the past cases where I have encountered this phenomenon. If the scene that the camera is being used in is well lit then an alternative may be to turn the projector off completely. The 400 Series cameras can alternatively use ambient light in a scene instead of the dot pattern to analyze surfaces for depth information when there is a good level of light present in the location that the camera is being used in. |
Hi @rolandgvc Do you require further assistance with this case, please? Thanks! |
Thanks very much @rolandgvc for the update! |
Issue Description
Having the depth sensor alternate on/off between frames is not always deterministic. Take for example the following code:
You would assume all the frames where the dot projections are visible would be skipped. Many times it happens that the
RS2_FRAME_METADATA_FRAME_LASER_POWER_MODE
flag will be a false negative.This can happen either at runtime (when none of the IR frames are hidden) or during operation (when some of the IR frames appear for a short periods of time).Any ideas why this is happening?
The text was updated successfully, but these errors were encountered: