-
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
Applying a preset in pyrealsense2 #2577
Comments
[Realsense Customer Engineering Team Comment] Try below code to see how it works:
|
Thanks, this works |
Hi @RealSense-Customer-Engineering , Is there any intention to expose the preset symbols in the Python wrapper directly so that we can do something more like depth_sensor.set_option(rs.option.visual_preset, rs.rs400_visual_preset.high_accuracy) rather than looping through descriptions looking for a label just to set a preset? Or is this looping approach intended to be the way to apply a preset with the Python wrapper? It seems like it would simply require one line in Thank you, |
Hi @dibya-pati You should be able to set the preset with a simple number value if you know which number relates to which preset on your particular camera (the 400 Series and L515 models have different presets). A Python example of this simplified code would be:
On 400 Series cameras, presets start at '0' and correspond to the order in which presets are listed in the RealSense Viewer. So if you open the Viewer's preset list and count 0, 1, 2, 3, then '3' would be the fourth preset in the list, which is 'High Accuracy'. |
Hi @MartyG-RealSense , Thanks for your reply; I understand that I can use a plain number like this, however it would be valuable to have these values exposed symbolically in the library, so I'm just wondering if they have been omitted intentionally or just haven't been done yet. Thanks, |
It seems that |
Issue Description
I'm trying to apply a high accuracy preset while capturing depth using SDK, couldnt find any example for python. Would appreciate any lead
The text was updated successfully, but these errors were encountered: