Reference

Reference · Tiles

TILEHORNS

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#

Side sectionSerpentine · 5 runs · 530 mm wide
Path length
2,500 mmtarget 2,500 mm · +0.0 %
Air volume
363 Ltarget 409 L
Computed from the tapped horn example. The cabinet outline is geometry; the comparison readouts describe the path used for simulation.

Supported types: Front-loaded horn, Back-loaded horn, Tapped horn, 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 checkWhat to look for
LengthThe folded path against the target. A difference beyond 0.5 % warns; beyond 3 % fails the check.
Front tap, Rear tap or Driver entryThe achieved position where the driver can actually sit. A small length error alone does not prove the taps match.
DriverClearance from boards and the shell, room for cone travel, and obstruction of the passage.
Shape, Mouth and ChamberHow the passage, outlet and any chamber differ from the acoustic target.
Can't buildA 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#

ControlEffect
Auto and Fold patternChoose the path arrangement and its count before fitting the box.
DrawLay out the path yourself through the cabinet grid.
Cabinet Height, Depth or WidthTyping a dimension locks it. Fit box searches the unlocked dimensions around those constraints.
A held boardKeep a manual placement while the rest follows the horn. The Held chip can release it.

Compare, then adopt#

  1. 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. 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. 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. 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.

What to try#

TryWhat it changes
Fit around a real constraintSet the cabinet dimension that must fit your space, then use Fit box.
Read the warningOpen a check chip to see the discrepancy and available fixes.
Compare before adoptingInspect 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.
or open it inClaudeChatGPT

Connect your assistant so it can open your designs.