Meanwhile, what does the following parameters mean? How would these parameters impact the tracking?
“CnnHPE”: {
“Filter”: {
“ThreshHold”: {
“MinDisplacement”: 30,
“SmoothCameraJointVelocity”: false,
“MaxDisplacement”: 200
}
}
Could you please record a dump(check Failure_Case_Recorder) so that we can reproduce the problem in your case study. Send it to mail(support-nuitrack@3divi.com) or in private messages on this forum.
Also when you turn on AI do you have depth image or only black screen?
Hmmmm I only see black screen on the GUI for depth camera. But when I was using Realsense Viewer, the depth image was great. I’ve sent the recording to support-nuitrack@3divi.com. Please take a look. Thanks!
I downloaded the recording, we’ll check it out next week.
Also, could you tell if you have any antivirus installed? For example McAfee, Kaspersky or something else.
I think the problem comes from the depth image. It seems like the nuitrack always set the depth sensor to “Short Range” or “Low Ambient Light” mode (as described in Realsense Viewer), no matter which number I put in “Preset” in my realsense2module. Out of my 100 tries, there are only two times that the depth image were correctly captured under “Max Range” preset and gives me very good skeleton tracking data. Could you look into this issue? Thanks!
Moreover, I found that no matter what preset value is set in nuitrack config, the mode will be automatically set back to “Low Ambient Light” for L515. The reason that sometimes (2 out of 277 tries) Nuitrack correctly works in “Max Range” mode is that it probably reads the cached data of Realsense Viewer/Depth Quality optimizer on “Max Range mode”. I believe this is the root cause of my issue.