timing of point cloud rendering

[alexandervakhitov]

Hi!

Thank you for the nice library.

Experimenting with the visualizer's function _custom_draw_geometry_with_cameratrajectory, I get the following timings:

• capture nothing in the callback, 20ms to render;
• capture rgb, 40 ms;
• capture depth, 60 ms;
• capture depth and rgb, 80 ms.

Why is the time for depth capture so big compared to the time for rgb capture? Can I make it faster?

In general, I'm looking for a way to render point clouds as fast as possible.

Thank you!

[Fred3D-tech]

same problem.. then following the topic.

[sammo2828]

When capturing, are you saving as PNG images? Generally saving as PNG is a slow operation.

If you don't need the data on disk, capture a float buffer instead.

If you do need the data on disk and timeliness is important, still capture a float buffer and write it as raw binary to disk (at the cost of more space).

[alexandervakhitov]

Thank you. The timings are only for capturing, saving is not performed at all. For my application, I need streaming rather than saving to disk. So, I'd like to know if there are ways to improve the time needed to capture the buffers.

[germanros1987]

We have been moving to a new visualization module based on Filament. Right now our transference times are not much better than they were before, but we are working on improving that. So, I am not closing this issue yet...