# Horn Editor

> Shape the unfolded horn path in Drawing or Table view, then check what the change does to response, cone travel and local air motion.

Source: https://simulator.00aud.io/docs/reference/tiles/horn-editor

Use **Horn Editor** to change the acoustic path: its lengths, areas, flares, stuffing and driver entries. The response graphs update from those same values.

- **Shows:** The unfolded horn path as a drawing or a table, including spans, flares, stuffing and driver entries.
- **Healthy when:** Each path and driver connection matches your intended acoustic design.
- **If it is not:** Choose the correct path, edit its spans or entries, and watch SPL, excursion and diagnostics.

## The tile

_Interactive walkthrough in the page: the simulator's own tiles running a short demo._

The front-loaded example, with an unchanged reference beside it. Play the steps or take over the controls to see each path edit affect the response.

Choose the horn and its path before editing. Horns with branches or more than one path have separate path chips. **Drawing** and **Table** edit the same design; the table is useful for exact values and starts as the phone view.

## How to read it

| Part | What it means |
| --- | --- |
| A span between stations | One length with an area at either end and its own flare. Its H label identifies that span. |
| Driver and tap markers | Where a diaphragm face or extra driver joins the path. Which markers can move depends on the horn type. |
| Stuffed region | The part of a span carrying porous fill. Its position, extent and resistivity affect the loss model. |
| **Length**, **Mouth Ø** and **Area ratio** | Readouts for the selected path, rather than the outside dimensions of a cabinet. |
| **Mode spacing** | An approximate spacing for the path. It is not a substitute for the simulated response or a usable-band specification. |

Each path supports 1 to 8 spans. Use the [full editor guide](https://simulator.00aud.io/docs/horns/editor#markers) for the markers each topology supports.

## What each edit changes

| Edit | Check beside it |
| --- | --- |
| Length or station area | SPL, impedance and excursion across the intended band. A local narrowing also deserves a Horn Particle Velocity check. |
| Flare | The whole response: the area between stations changes even when the endpoints stay put. |
| Driver or rear tap position | Output summation and the resulting peaks and dips. Moving a tap changes which part of the path each diaphragm face drives. |
| Stuffing | Resonances and output together. Reducing a peak can cost useful level elsewhere. |

> **The path is not the cabinet** An unfolded drawing does not prove the horn fits into boards. **Fold into cabinet** opens the **Fold** tile for supported types. Compare its achieved path and response before adopting it.

## What to try

| Try | What it changes |
| --- | --- |
| [Use exact values](https://simulator.00aud.io/docs/horns/editor) | Choose **Table** to type lengths and areas. **Drawing** edits the same values. |
| [Check a narrow section](https://simulator.00aud.io/docs/reference/tiles/horn-particle-velocity) | Read **Horn Particle Velocity** at the stations either side of it. |
| [Try a cabinet](https://simulator.00aud.io/docs/horns/folding) | Use **Fold into cabinet** when the current topology supports folding. |

## Ask your AI

**Ask your AI**

> Using 00 Simulator, read the horn in my open workspace and explain its path lengths, station areas, flares and driver entries. Try a small change to its mouth area without saving, then compare SPL and excursion with the original.