Azure data corruption, scan merging, color problems, player crashing about livescan3d HOT 4 CLOSED

Hi Zachduer,

I also noticed the artifacts that you've been describing. A lot of the problems you have described have already been fixed, but are not yet on the Azure Kinect branch. I could offer to do a PR with fixes, when I have some time (Could take 1-2 weeks).

1: Are you using multiple Azure Kinects on one PC? Because I noticed corrupted files are happening when more than one Kinect is connected to a PC. The cause of this is that all Kinects write to the same temporary file on the client device before transmitting, which is corrupting the data. I already fixed this in PR #49 , but I'm now realizing I should have done a seperate PR for this.

2: I haven't experienced this one yet, but I can do a little investigation.

3: This should be an easy fix, I'll try to replicate this issue

Additionally to the issues you mentioned, there is the PR #38 which fixes problems with the PLY format. This has been fixed on the Default Kinect Branch, but not on the Azure Kinect branch yet.

I'll try to commit a PR soon which should fix most of the problems.

Regarding 4: This also happens for me, it always crashes and is not in a usable state. However I don't know if I'll have the time to figure this one out.

from livescan3d.

Hi Chris! Thank you for your response! Yes, I am using all 3 Azure Kinects on a single PC. I will take a look at PR #49 and work from there, thank you so much!!

from livescan3d.

Hi Zach,

yeah that should probably be the cause for most of your issues!

Let me know if #49 fixes the problems for you!
The pull request adds temporal synchronisation to LiveScan, but you can just leave it disabled.

from livescan3d.

Hi Chris!

Yes, confirmed, PR #49 fixes all of the issues I mentioned here. Thank you so much! The hard work of you all has saved me SO much time, so I get to skip to the fun parts! <3

from livescan3d.