Problem with current version of Depthkit producing very noisy renders

Depthkit
,
1

Hi everyone,

I have just gone back to using DepthKit after a 2 year break. I’m using the same Azure Camera and workflow as before. This involves capturing a 3D obj sequence using the Azure Camera, importing the OBJ sequence into AfterEffects, and rendering with different effects using the Plexus plugin.

My problem is that the updated version of DepthKit appears to be generating a completely different mesh decimation style. The points used to be on a grid, but now they zoom about like buzzing insects. The resulting image is much harder to see, and the visual noise is distracting.

I don’t know what the problem is, but my best guess is that the new method of reducing the point cloud is stripping out random points, rather than reducing the density of points on a grid. So when I bring the stripped down obj sequence into After Effects, Plexus renders the points and connecting lines, producing this noisy image. I’ve experimented with the DepthKit capture settings, but no matter what I try I always get this noisy image.

Can anyone suggest how to get a cleaner / less noisy point cloud out of Depthkit? Or am I stuck with this new, noisy image because Depthkit has a new method for reducing mesh decimation?

Finally, if there’s nothing that can be done, is it possible to install and run an older version of DepthKit?

I’ve attached links to two different files. This is what I would like to do - made using the older version of DepthKit.
Older version of depth kit = desired render style

This is what I am currently getting out of the current version of Depth Kit
Current version of Depthkit = Noisy render style

2

@GrahamPlumb - Depthkit version 0.8.1 introduced a new option for textured geometry sequence export: WebXR-ready Draco meshes. In implementing this, the existing mesh export library was replaced with one which supported both OBJ’s as well as Draco files, which is why the export options and simplified mesh topology have changed. Unfortunately, this means that the old style of decimation is no longer available in the Depthkit app, but something similar is achievable by exporting unsimplified meshes, then before importing into After Effects / Plexus, using PyMeshLab’s Clustering Decimation process: ms.meshing_decimation_clustering()

3

Thanks for the reply Cory.

The issue with this approach is that it will create huge files, and slow down down my workflow significantly. Is there any way I could install the older version of DepthKit, a version before this decimation update? It would save a lot of work and spending extra money on new new hard drives.

Thanks so much.

Graham

4

@GrahamPlumb - Please check your email.