Dear,
I'm working on Realsense SDK and SR300,
1 - How to merge two PXCM3DScan or create multi PXCM3DScan in a PXCMSenseManager;
2 - Having two parts of an object, how to auto align?
3 - In PXCM3DScan, can you show me how to Reconstruct 2 PXCM3DScan to a file?
4 - Having *rssdk files of a model, how to merge?
Thanks!
链接已复制
The link below has a script for the old RSSDK RealSense SDK that combines RGB and depth streams into one image. The script was for the SR300's direct predecessor the F200.but should work with SR300.
https://mtaulty.com/2015/04/16/m_15794/ https://mtaulty.com/2015/04/16/m_15794/
Regarding the best conditions for scanning a 3D model with the R200: it is not something that can be described in words precisely, because each person's location is different. In general, you should scan in a location that has average lighting (not too dark, not too bright), avoid rooms with fluorescent lights like ceiling strip lights, and position the camera so that the object / person you are scanning fills as much of the camera's view as possible.
The same rules for getting good scan results that I mentioned earlier for R200 apply to scanning with SR300 too.
The SetIVCAMFilterOption instruction can be used in the 2016 R2 and 2016 R3 SDKs to re-balance the output of F200 and SR300 cameras according to accuracy and distance.
https://software.intel.com/sites/landingpage/realsense/camera-sdk/v1.1/documentation/html/index.html?setivcamfilteroption_device_pxccapture.html Intel® RealSense™ SDK 2016 R2 Documentation
Reading the 3DScan instructions, it looks like the Full option was the correct one for a full human body, as it provides the largest scanning area.
If the camera cannot see the whole body then you should move the camera further away from the body so the camera can see more of the body.
Sorry, I forgot you were using an SR300 and not a R200 with much longer range. The SR390 is not suited to scanning the full human body because of its limited range. The R200 is the best camera for full body scanning. Because of the SR300's range, it is better at just scanning the head.
The only way I can think of to get depth range on the SR300 like that of the R200 is to use IVCamFilterOption to give the SR300 longer range at the expense of scanning accuracy.
https://software.intel.com/sites/landingpage/realsense/camera-sdk/v2016r3/documentation/html/index.html?ivcamfilteroption_device_pxccapture.html Intel® RealSense™ SDK 2016 R3 Documentation
The 3D scanning function of the 2016 R2 SDK's AlertEvent system has a type of alert called ALERT_LOST_TRACKING
https://software.intel.com/sites/landingpage/realsense/camera-sdk/v1.1/documentation/html/index.html?alertevent_pxc3dscan.html Intel® RealSense™ SDK 2016 R2 Documentation
The script below shows an example of use of AlertEvent.
https://github.com/getnamo/realsense-ue4/blob/master/Plugins/RealSensePlugin/ThirdParty/RSSDK/Include/pxc3dscan.h realsense-ue4/pxc3dscan.h at master · getnamo/realsense-ue4 · GitHub
If you type 'camera explorer' into the text box at the bottom of your Windows screen (next to the button where you shut down the PC) then you can find the Camera Explorer program. This checks which RealSense cameras you have plugged in, if they can be detected, and lets you do tests with them.
In the 2016 R2 SDK, AcquireFrame can be used to check if a stream has 'timed out' because it has got stuck.
https://software.intel.com/sites/landingpage/realsense/camera-sdk/v1.1/documentation/html/index.html?acquireframe_pxcsensemanager.html Intel® RealSense™ SDK 2016 R2 Documentation
