Closed pasandal closed 3 weeks ago
Hi @pasandal You are welcome to modify the source code of the librealsense SDK and then build the SDK from the modified source code using instructions at one of the links below.
Linux https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
Windows https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md
Hi @MartyG-RealSense ,
Thank you for your response. I understand that modifying the SDK locally is an option, but I wanted to clarify if this issue could be addressed in the official SDK itself. Given that this affects initialization time and compatibility with valid device path formats like ven_
, it seems like it could impact other users too.
If yourself or another RealSense user is able to develop a solution then we would welcome it being submitted as a Pull Request (PR) for consideration by the RealSense team for inclusion in the official SDK.
Hi @pasandal Bearing in mind the recommendation in the above comment that a solution should be developed and submitted for inclusion in the SDK by a RealSense user, do you require further assistance with this case please? Thanks!
Case closed due to no further comments received.
Issue Description
parse_usb_path_multiple_interface
andparse_usb_path_from_device_id
function in your code assuming that HID device paths must contain avid_
prefixven_
(e.g.,ven_elas&dev_e551&subsys_17aa233c
), which is valid but not recognized by your parsing logic.Impact:
Recommendation:
ven_
anddev_
.vid_
andpid_
in the device path.Link to code: https://github.com/IntelRealSense/librealsense/blob/e1688cc318457f7dd57abcdbedd3398062db3009/src/win/win-helpers.cpp#L106