SoundPro.

We know this problem from the inside. At ST-LINE two competent acoustics technicians registered in the Italian National Register (ENTECA) routinely deliver acoustic surveys, impact assessments and expert reports. SoundPro is born from their daily field practice, not from a market study.

A mature acoustics engineering studio works with neither a single instrument nor a single software. Years of purchases, training and partnerships mean today’s instrument parks are heterogeneous, and the workflow is fragmented across three incompatible families of applications: the sound-level meter’s bundled software for post-processing, an expensive enterprise-grade predictive software for the propagation model, and Office for the final report. Data moves between them by copy-paste.

Everyone in the field knows the daily result: for every survey the technician opens several single-brand applications in parallel, exports the data one by one, and then re-merges everything by hand in a spreadsheet. Calculation consistency is lost, graphical representation is inconsistent, the audit trail is fragmented across closed ecosystems. The forensic chain is fragile and has to be reconstructed after the fact for every expert report.

On top of this, two systemic gaps remain in the existing software on the Italian front: national regulations are almost always treated as manual post-processing or report templates, not as a built-in computation engine; and AI features — by now standard in professional productivity — are still absent from sector stacks.

SoundPro is written by the same group that uses it for its own expert reports. ST-LINE is not a software vendor that studied acoustics from the outside: the product’s technical ownership lies with two competent acoustics technicians registered in the Italian national register (ENTECA), actively operating as technical experts.

Every SoundPro feature answers a frustration lived on site or at the desk: multi-source coding, bit-identical computation for adversarial defensibility, cryptographic chain of custody for court-mandated expert reports, native GIS integration that avoids going through an external CAD for the plates. The functional specification is written by the technicians who will perform expert reports with this software.

We use it ourselves, today, on our own expert reports: whatever does not work we find before anyone else does, on real work with a real deadline.

SoundPro is currently in active development. We are building the multi-format import core, the ISO 9613-2 predictive engine, the forensic layer with cryptographic chain of custody, and the Italian regulatory computation modules. The architecture is consolidated and the v1.0 functional specification is under approval.

Today we use it ourselves. Opening it to external users starts with those working with instruments from several makes, or producing expert reports regularly: those are the situations where the product has something to prove straight away. We will state dates when we know them, not before.

There is one thing your input really settles: which instruments you use. The order in which we add importers comes from the instruments Italian practices actually own, not from a catalogue. We start with the formats of the most common class 1 sound level meters — among them the HBK 2255 and the 01dB FUSION — and continue with the ones you tell us about. If you work in acoustics today, write to us with what you measure with and what you export: that is the information that moves the queue.