Repository navigation
API Changes
ev-mp edited this page Nov 22, 2017
·
88 revisions
No API changes introduced
- rs2_start_processing_queue - convenience function that lets the user target the output of a processing block (for example align) directly into a frame_queue. This helps in languages where function pointers are not available, such as LabView
Signature of rs2_is_option_read_only, rs2_get_option, rs2_set_option, rs2_supports_option, rs2_get_option_description and rs2_get_option_value_description was changed. First parameter used to be pointer to rs2_sensor and now is pointer to rs2_options. However, it is 100% safe to cast pointer to rs2_sensor to pointer to rs2_options.
See Pipeline Changes pull-request for explanation
- rs2_stop_pipeline is now available as rs2_pipeline_stop
- rs2_start_pipeline is now available as rs2_pipeline_start
- rs2_pipeline_get_device is now available as rs2_pipeline_profile_get_device
- rs2_pipeline_get_active_streams is now available as rs2_pipeline_profile_get_streams
- rs2_enable_pipeline_stream is now available as rs2_config_enable_stream
- rs2_enable_pipeline_device is now available as rs2_config_enable_device
- rs2_disable_stream_pipeline is now available as rs2_config_disable_stream
- rs2_disable_all_streams_pipeline is now available as rs2_config_disable_all_streams
- rs2_pipeline_start_with_config
- rs2_pipeline_get_active_profile
- rs2_delete_pipeline_profile
- rs2_create_config
- rs2_delete_config
- rs2_config_enable_all_stream
- rs2_config_enable_device_from_file
- rs2_config_enable_record_to_file
- rs2_config_resolve
- rs2_config_can_resolve
- rs2_config_disable_indexed_stream
- rs2_get_stream_profile_size - This function was intended to offer an estimate of USB bandwidth, however USB3 performance is affect by factors other then bytes/second, rendering this method useless
- rs2_open_pipeline - This function was offered to force pipeline configuration prior to streaming. This can be more effectively achieved by rs2_config_resolve and rs2_config_can_resolve
- rs2_start_pipeline_with_callback - and rs2_start_pipeline_with_callback_cpp - Pipeline is always performing synchronization at the moment. If you wish to get minimum latency you can use callback API of the individual sensors
- rs2_pipeline_get_selection_count, rs2_pipeline_get_stream_selection, rs2_pipeline_get_stream_type_selection, rs2_pipeline_delete_selection - These methods were redundant
- rs2_get_context_time is now available as rs2_get_time
- rs2_create_pipeline_with_device is now available as rs2_enable_pipeline_device
- rs2_enable_stream_pipeline is now available as rs2_enable_pipeline_stream
- rs2_pipeline_get_selection is now available as rs2_pipeline_get_active_streams
- rs2_can_enable_stream_pipeline - This method, while useful, was not 100% clearly defined. The same goal was more cleanly achieved in a later release - rs2_config_can_resolve
- rs2_pipeline_get_extrinsics - Extrinsics can be queried between stream profiles, and don't require the pipeline or context.
- rs2_pipeline_get_context - Context can be passed to pipeline constructor for dependency injection, but should not be required for anything useful later on.
- rs2_create_pointcloud used to accept 2 parameters but rs2_create_pointcloud accepts 1 parameters!
- rs2_create_processing_block used to accept 3 parameters but rs2_create_processing_block accepts 2 parameters!
- rs2_create_align used to accept 3 parameters but rs2_create_align accepts 2 parameters!
RealSense SDK Wiki
- Home
- Troubleshooting Q&A
- Release Notes
- API Changes
- API How-To
- Build Configuration
- Realsense Viewer Manual
- Overview of Depth from Stereo
- Post-Processing
- Sample Data for SDK examples
- D400 Series Visual Presets
- D400 Advanced Mode
- Projection in RealSense SDK 2.0
- API Documentation
- Record and Playback
- About Android Support
- RealSense with Raspberry Pi 3
- RealSense with Raspberry Pi 4
- RealSense with NVidia Jetson
- ROS 2 Wrapper
- Frame Buffering Management
- Supported Matrix
- Docker