VoxelStudio

Product revisions

CloudCutter revision history

The product began as a focused E57 cutter and developed into a streaming point-cloud viewer, spatial cutter, batch splitter and converter for E57, XYZ ASCII and LAS.

Maintained by VoxelStudioPublic and development-line changes
Open CloudCutter pageBrowse performance tests

This history records user-visible changes and important engineering changes. It avoids assigning unverified features to a release and distinguishes current public functionality from experimental development work.

Current beta line

CloudCutter_E57 V1.1 beta

Windows x64 · Trial and commercial delivery

Current

Formats and conversion

  • Added LAS input and output support.
  • Expanded the primary supported formats to E57, XYZ ASCII and LAS.
  • Added direct conversion between supported formats, including E57 → LAS, E57 → XYZ, LAS → E57, LAS → XYZ, XYZ → E57 and XYZ → LAS.
  • Kept geometry as the primary transferable content; RGB, intensity, scan structure, photographs, classifications and other metadata depend on the active reader/writer path.

Selection and preview workflow

  • Added interactive 3D inspection of the lightweight preview alongside the top view.
  • Added a Select all tiles action for preparing a complete-cloud selection in one operation.
  • Added Adjustable preview tile size so that the coarse spatial grid can be adapted to the dataset and task.
  • Expanded saved-selection handling for top-view tiles and vertical Z ranges.
  • Added clearer controls for saving and clearing top-view and vertical selections.

Export workflow

  • Added one-command export of multiple saved selections.
  • Added two main output modes: one combined output or separate files for the saved selections.
  • Extended the same selection workflow across the supported input and output formats where the corresponding reader/writer path is available.
  • Continued the low-memory and streaming approach so that source-file size does not directly determine required RAM.

Measured limitation: Benchmark E57-01 showed that the current safe E57 split exporter creates many files from one user command but rereads the source point stream for each output. Single-pass multi-output E57 export is therefore a development target, not a current performance claim.

Trial and distribution

  • Added the 30-day organization Trial workflow with registration at first launch.
  • Supports up to 10 fixed devices for the organization Trial.
  • Commercial builds are delivered by direct request after agreement and licensing terms are confirmed.

Developer Edition benchmark instrumentation

  • Added separate First Run and Repeated Run records.
  • Added read, operator-preparation and export timing.
  • Added hardware, memory, CPU, process I/O and storage identification to benchmark reports where available.
  • Added HTML and JSON report generation and automatic E57 output metadata/point-count validation.

Benchmark controls are part of the development and validation workflow and are not necessarily included in every public Trial package.

Original product scope

CloudCutter_E57 V1.0

Initial E57-focused foundation

  • Established the original E57 reading and cutting workflow.
  • Built a lightweight preview instead of loading the complete source cloud into memory.
  • Provided top-view spatial tile selection for choosing the required regions.
  • Supported saved selections and controlled export of selected E57 data.
  • Established the streaming/low-memory design principle used by later versions.

The V1.0 entry describes the confirmed original product scope. Smaller internal build changes will be added only when their branch records are reviewed and can be assigned accurately.

Current development target

Correspondence export optimization

Planned work; not yet a released feature

  • Replace repeated source traversals with indexed routing during one sequential point-stream pass.
  • Use bounded per-output buffers and backpressure to keep memory controlled.
  • Preserve required XYZ, RGB, intensity and E57 schema fields where supported.
  • Use transactional temporary outputs and validate every completed file before commit.
  • Repeat the same benchmark datasets and selections after optimization and publish regressions as well as improvements.
← All benchmarks and recordsRead Benchmark E57-01 →