# Fold

> Fit a horn path into a cabinet, read its geometry checks and compare the folded response before making the horn follow the fold.

Source: https://simulator.00aud.io/docs/reference/tiles/fold

**Fold** fits a horn into a cabinet and shows where the result differs from the intended path. Read its checks together with the dashed folded response before you build.

- **Shows:** A cabinet fold with boards, driver placement and checks against the intended horn.
- **Healthy when:** Geometry is buildable and the achieved path, taps, mouth and chambers are close enough to your design.
- **If it is not:** Open the warning chips, adjust the cabinet or fold, and compare the folded response.

## The tile

_Figure: The example tapped horn folded into a cabinet, showing the boards, air passage, centreline and unused spaces._

Computed from the tapped horn example. The cabinet outline is geometry; the comparison readouts describe the path used for simulation.

| Measurement | Folded | Target |
| --- | --- | --- |
| Path length | 2,500 mm | 2,500 mm |
| Modelled air volume | 363 L | 409 L |

Supported types: [Front-loaded horn](https://simulator.00aud.io/docs/horns/front-loaded-horn), [Back-loaded horn](https://simulator.00aud.io/docs/horns/back-loaded-horn), [Tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn), [Offset-driver horn](https://simulator.00aud.io/docs/horns/offset-driver-horn). Branches and multiple driver entries need an assembly layout that the folding tool does not yet provide.

## How to read it

| Readout or check | What to look for |
| --- | --- |
| **Length** | The folded path against the target. A difference beyond 0.5 % warns; beyond 3 % fails the check. |
| **Front tap**, **Rear tap** or **Driver entry** | The achieved position where the driver can actually sit. A small length error alone does not prove the taps match. |
| **Driver** | Clearance from boards and the shell, room for cone travel, and obstruction of the passage. |
| **Shape**, **Mouth** and **Chamber** | How the passage, outlet and any chamber differ from the acoustic target. |
| **Can't build** | A geometric conflict such as overlapping passages. Resolve it before treating the drawing as a cabinet proposal. |

Open a check chip for the discrepancy and available fixes. Passing geometry checks does not validate panel strength, joints or bend losses.

## What moves it

| Control | Effect |
| --- | --- |
| **Auto** and **Fold pattern** | Choose the path arrangement and its count before fitting the box. |
| **Draw** | Lay out the path yourself through the cabinet grid. |
| Cabinet **Height**, **Depth** or **Width** | Typing a dimension locks it. **Fit box** searches the unlocked dimensions around those constraints. |
| A held board | Keep a manual placement while the rest follows the horn. The **Held** chip can release it. |

## Compare, then adopt

1. **Read the dashed line.** The folded line on the response graphs uses the achieved path and taps. Compare SPL and excursion over the intended band, not only the headline length difference.
2. **Check why it is absent.** No separate line appears when the horn already matches the fold, the fold cannot be simulated, or stuffing or damping prevents carrying the design into the folded passage. Horn diagnostic graphs do not show this comparison.
3. **Keep a separate alternative.** In **Full screen**, **Fork as enclosure** makes an enclosure from an eligible fold so you can compare it as a separate design.
4. **Adopt deliberately.** **Use this fold** writes the achieved spans and taps into the horn, locks the cabinet and holds the boards. The pill then reads **Matches horn**. Undo restores the earlier design.

> **Before cutting boards** Inspect **Cut list** and the actual driver clearances. The model does not simulate bend scattering or motor obstruction. The geometry export is not a fabrication drawing.

## What to try

| Try | What it changes |
| --- | --- |
| [Fit around a real constraint](https://simulator.00aud.io/docs/horns/folding#cabinet) | Set the cabinet dimension that must fit your space, then use **Fit box**. |
| [Read the warning](https://simulator.00aud.io/docs/horns/folding#checks) | Open a check chip to see the discrepancy and available fixes. |
| [Compare before adopting](https://simulator.00aud.io/docs/horns/folding#folded-line) | Inspect the dashed folded response; **Use this fold** changes the horn itself. |

## Ask your AI

**Ask your AI**

> Using 00 Simulator, fold the horn in my open workspace without saving. Explain the geometry warnings and achieved taps, simulate the folded changes beside the target, and compare SPL and excursion before suggesting which fold to keep.