RELEASED — 0.1.0 · WINDOWS AND LINUX
The map, and the answer.
Acustika computes the loudspeaker coverage of your room and shows it. And more to the point, it proposes where to put the boxes — not just a map you have to know how to read.
Describe the room, read the coverage
A room is not a rectangle. You draw its zones with the mouse, give each one its rake, place the boxes and aim them: the map recomputes on every move.
Freely drawn zones
Point by point, any shape, several per project. An L-shape properly excludes its notch, where a simple bounding rectangle would have taken it in.
With their rake, as a percentage: 8 m of seating at 15% rises 1.20 m, and the ears rise with the floor.
A coverage map
Recomputed on every move, on a 24 dB scale, with the mean and the spread of each zone.
What counts is the spread across the whole room, not the average of the spreads. A room with an even stalls and a balcony 12 dB down is not well covered, even if each zone taken alone is.
A loudspeaker library
You pick a model before placing it, instead of retyping everything on every project. Coverage angle is set band by band.
A loudspeaker is very directional at high frequencies and near-omnidirectional at low ones: a single-frequency calculation is misleading and would give bad advice.
Placement advice
The application tries several placements and keeps the one whose coverage is the most even — height, angle, spacing, delays.
Then it explains why. Without the explanation nobody will trust the result, and the tool will be of no use.
What it does not do
A colour map is very convincing, even when it is wrong. That is why this section exists, and why the application says the same thing on screen.
No reflections, no reverberation
Acustika computes a direct field. Walls, audience and furniture are not modelled. A real room never looks like the model.
No phase between boxes
The summation assumes uncorrelated sources: two equal sources give +3 dB, not +6. Two coherent sources can in reality reach +6 dB or cancel.
No ray tracing, no STI
EASE and its peers are decades of work by teams of acousticians. Promising the same would mean shipping wrong maps with the confidence of right ones.
What is reachable is already useful: coverage, sound pressure, delay times for fills, and placement advice. The advice will stay a proposal, never a certainty.
Open formats, and a project that is yours
A project is a file, not a row in a database: a simulation gets sent on, archived with the job folder, compared.
Readable JSON
In ten years it will still open in a text editor. That is exactly the complaint made about closed formats.
CLF, SOFA, or CSV
GLL is a closed format with no public specification. Acustika targets CLF, created as an open alternative, and SOFA (AES69).
Typing it in always works
Many manufacturers publish their polar data as CSV. A few angles and a few bands are enough for a useful map. CSV import already exists.
What we stand for
Acustika follows the ResonLab rules, the same ones as Ohmnia and Scenika.
No connection
No account, no subscription, no usage tracking. Your projects never leave your machine.
No server, on purpose
Acustika works on project files, not on shared company data. Two people do not edit one simulation at the same time.
Messages that explain
Precise, never a raw technical error. When the software refuses something, it says why.
Nothing you cannot reopen
Readable formats, simple code, no closed format. That is a commitment, not a preference.
What is not guaranteed is said
Acustika does not replace an acoustician. What is indicative is announced as such, on screen and not only in the terms.
Checked, not claimed
The physics is tested against values known by hand: −6 dB per doubling of distance, +3 dB for two equal sources, 2.9 ms per metre.