MartyX Grover
- Total activity 2396
- Last activity
- Member since
- Following 0 users
- Followed by 1 user
- Votes 1
- Subscriptions 739
Comments
Recent activity by MartyX Grover-
1. The multiple camera white paper's high-speed LED panel example states that the camera exposure time shoud be set to < 3 ms rather than 312, otherwise the panel will just be a blur. 2. I cons...
-
I apologise for the delay in responding further. Metadata is not one of my specialist subjects, so I will refer you to the official documentation link below to ensure that you are provided with a...
-
You are very welcome Aatefi2 - thanks very much for the update and the sharing of your code wth the RealSense community!
-
It may be worth applying the High Accuracy visual preset in the Viewer (selectable from the drop-down near the top of the Viewer side-panel) instead of the default Custom to see whether it improves...
-
Not as a built-in feature in the RealSense SDK. The commercial skeleton tracking software Nuitrack SDK ( https://nuitrack.com/ ) that is compatible with the 400 Series cameras and has Unity inte...
-
Is the camera mounted to a fixed point or being held in the hand, please? I ask this because in the Viewer's measuring mode, once you define the measuring start point with the first left-click and ...
-
Hi Getirfanhabeeb In the RealSense SDK, converting 2D pixel coordinates to 3D world coordinates is called deprojection and is described in the SDK's Projection documentation. https://github.com/In...
-
Do you mean this align function in pyrealsense2: https://intelrealsense.github.io/librealsense/python_docs/_generated/pyrealsense2.align.html
-
I would say that whether the difference in FOV size is automatically taken into account would depend on how your application is programmed. If you are aligning depth and color using the SDK's alig...
-
Do you have to define the FOV manually with RANSAC? Because whilst D415 and D455 both have the same size FOV for RGB and depth sensors, the FOV of the two camera models is different.