# 00 Simulator docs, in full
> 00 Simulator is a loudspeaker enclosure simulator that runs in the browser. It models sealed, vented, passive-radiator, bandpass and horn enclosures from a driver’s T/S parameters, and assistants such as Claude and ChatGPT can use it through its connector.
Every page of https://simulator.00aud.io/docs as Markdown, in reading order. Each page starts with its title, a one-line summary and its address. The index of pages is https://simulator.00aud.io/llms.txt.
---
# Your first design
> Build a vented subwoofer in 00 Simulator step by step: pick a driver, set the box, read the response and see what breaks at 200 W.
Source: https://simulator.00aud.io/docs/start/first-design
Build a vented subwoofer for a real 12-inch driver, read the graphs that matter most, and see what breaks when you turn it up. Every graph here is the simulator’s own output for the same design.
## Pick a driver
Open [the simulator](https://simulator.00aud.io/app). A first visit starts as a guest, so there is nothing to sign up for. The **Welcome to 00 Simulator** dialog offers ready-made examples; choose **Start from scratch** and it opens **Add enclosure**. Later, **Add new enclosure** at the foot of the enclosure list opens the same dialog.
- Click the **Driver** box (it reads **Select a driver** until you pick one) and type `12.00SW`. The search matches manufacturer and model.
- Results under **Catalogue** show each driver’s model, brand, nominal impedance and size. The star makes it a favourite, listed under **Your drivers** next time.
- **Browse all** opens **Advanced driver search**: filters, and a table of size, impedance, Fs, Qts, Vas, Bl, Sd and Xmax for every driver. **Create custom driver** adds one of your own ([Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers)).
Pick the Ciare 12.00SW. These four of its parameters shape this design; [T/S parameters in five minutes](https://simulator.00aud.io/docs/start/ts-parameters) covers the rest.
- **Fs:** 29 Hz: where the cone resonates in free air.
- **Qts:** 0.29: how damped that resonance is.
- **Vas:** 55 L: the suspension’s stiffness, as a volume of air.
- **Xmax:** 13.5 mm: how far the cone travels, one way, before it distorts.
With a driver chosen, the dialog suggests a type from the driver’s EBP (Fs divided by Qes) under **Suggested starting point**. For this driver it reads: _EBP 88 points toward a vented starting alignment at 82.5 L, tuned to 26 Hz._ Keep **Vented**, leave **Name** and **Colour** as they are, and click **Add enclosure**.
## Make it vented
The new enclosure starts from the suggestion. Its settings are in the **Enclosure** section under the enclosure list, and **Type** already reads **Vented**. Set **Volume** to 55 L and **Tuning** to 32 Hz, the box from the app’s Vented example. Then open **Port** and set **Diameter** to 100 mm, with **Number of ports** at 1.
_Figure: The Enclosure panel for this design: Type Vented, Volume 55 L, Tuning 32 Hz, Port length 356 mm, and the Port section open with one circular 100 mm port._
| Field | Value |
| --- | --- |
| Type | Vented |
| Volume | 55 L |
| Tuning | 32 Hz |
| Port length | 356 mm (follows from the tuning) |
| Port › Number of ports | 1 |
| Port › Diameter | 100 mm |
- **Port length** follows from the tuning and the port’s size: 356 mm here. It works both ways: type a port length and the tuning follows instead. The panel holds whichever you set last.
- **Results**, under the port, lists its cross-sectional area and **Port volume**, the space the port itself takes up inside the box.
- Prefer to skip the typing? [Open the finished example](https://simulator.00aud.io/app?template=vented) and carry on from the next step.
> **Not sure about the type?** [Choose an enclosure type](https://simulator.00aud.io/docs/start/enclosure-types) shows a starting example for each type and when each one is worth using.
## Read the response
A new workspace opens with the **SPL (dB)** tile: level against frequency, one curve per enclosure in its colour. This one is flat to within 1.7 dB from 40 Hz to 200 Hz and falls away below the 32 Hz tuning. Its F3, where it falls 3 dB below its loudest octave, is 30.3 Hz; F10 is 24.9 Hz.
_Figure: The SPL tile for this design at 200 W: flat from about 40 Hz up, falling below the 32 Hz tuning, with F3 marked at 30.3 Hz and F10 at 24.9 Hz._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built. At 1 W the curve has the same shape, 23 dB lower.
| Frequency | SPL at 200 W |
| --- | --- |
| 20 Hz | 93.1 dB |
| 24.9 Hz (F10) | 101.0 dB |
| 30.3 Hz (F3) | 107.9 dB |
| 40 Hz | 110.0 dB |
| 100 Hz | 109.9 dB |
- Click **F3** in the tile’s header to mark F3 and F10 on each curve. **F-point settings** beside it choose which points show and the level they are measured from; the default is **Auto · loudest octave average**.
- The level is at 1 m in half space until you change **Environment**, in the Driver panel. [Reading a response](https://simulator.00aud.io/docs/start/reading-a-response) covers what the shape tells you.
## Turn it up
Power is set per enclosure. Open **Power** in the Driver panel and set **Input power** to 200 W; the numbers under the slider are clickable. The curve rises 23 dB and keeps its shape, to about 110 dB. Two limits break first, on the **Excursion** and **Port Velocity** tiles (the example opens with both; otherwise add them with **Add tile**):
- **Excursion**: below about 19 Hz the cone travels past its 13.5 mm Xmax, the dashed line on the tile. Under the tuning the port no longer holds the cone back.
- **Port Velocity**: at the tuning the port does the work, and its air peaks at **28.4 m/s** near 30 Hz, over the 17 m/s warning line.
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The app’s own SPL, Excursion and Port Velocity tiles running this design in your browser, as the power goes from 1 W to 200 W. Nothing here is saved.
> **Fix one thing at a time** A high-pass filter below the tuning keeps the cone in check: [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters). The port needs more area: [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port). [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) explains each limit.
## Keep it
As a guest the design lives in this browser, and the header reads **Guest project**. To keep it, click **Save** in the header:
- **Create free account** signs you in, and your guest project comes with you as a cloud workspace (an account that already has workspaces asks first: **Import guest workspace?**). A free account keeps up to 250 workspaces, saved as you go, with their revision history, on any device you sign in on.
- **Download .00sim** keeps a file instead, which **Export** › **Open 00sim project…** opens again.
> **Guest share links are public** **Share** in the header makes a link. Made as a guest, **Create share link** publishes it at once and lists it in the **Gallery**, and you cannot manage it or take it out of the Gallery later. Signed in, **Create draft** keeps it private until you publish. [Share and publish](https://simulator.00aud.io/docs/guides/sharing) has the details.
**Or ask your AI to build it**
Your assistant runs the same solver through the 00 Simulator connector and saves the design to your account.
> Using 00 Simulator, build a 55 L vented box tuned to 32 Hz with one 10 cm port for the Ciare 12.00SW, simulate it at 200 W, and tell me its F3 and where excursion and port velocity go over their limits.
---
# The workspace
> A tour of the 00 Simulator workspace: the header, the enclosure list and panel, the Driver panel, tiles, layouts and the phone dock.
Source: https://simulator.00aud.io/docs/start/workspace
Where everything is in 00 Simulator, and what it is called. Your enclosures are on the left, the graphs in the middle, and the selected enclosure’s driver, power, EQ and environment on the right.
_Figure: The 00 Simulator workspace on a desktop, numbered: 1 the header, 2 the enclosure list, 3 the enclosure panel, 4 the layout bar with Add tile, 5 the tiles, 6 the Driver panel._
The vented example from [Your first design](https://simulator.00aud.io/docs/start/first-design) at 200 W, as a guest. The tiles show the solver’s curves for that design.
1. Header
2. Enclosure list
3. Enclosure panel
4. Layouts and Add tile
5. Tiles
6. Driver panel
## The header
| Part | What it does |
| --- | --- |
| **Undo** and **Redo** | Step back and forward through your edits (⌘/Ctrl+Z and ⌘/Ctrl+Shift+Z). The arrow between them lists recent steps, and **History and saved versions…** at its foot shows the rest. When the graphs carry notes or an assistant’s marks, a third button shows or hides them. |
| The workspace name | Signed in, **Workspaces** › the name: click the name to switch (**Recent**, **All workspaces**), the star pins it, and **Workspace actions** has **New workspace**, **Duplicate workspace**, **Rename workspace**, **Delete workspace…**, **Workspace history** and **Show info**. As a guest it reads **Guest project**, with **Save**. |
| **AI** | Connects your own AI assistant to your account: [Connect your AI assistant](https://simulator.00aud.io/docs/ai/connect). |
| **Share** | Makes a link to the enclosures you pick: [Share and publish](https://simulator.00aud.io/docs/guides/sharing). |
| **Export** | Files out (**Hornresp…**, **WinISD…**, **00sim project…**) and in (**Open 00sim project…**, **WinISD…**, **From another workspace…**, and measured traces): [Import and export](https://simulator.00aud.io/docs/guides/import-export). |
| **Settings** | **Display…**, **Appearance…**, **Simulation…**, **Drivers…** and **Passive radiators…**: [Settings and themes](https://simulator.00aud.io/docs/guides/settings). |
| **Log in** | Signs you in; once you are, your avatar holds the account menu. |
| **Info** | **Docs**, **Gallery**, **About**, **Roadmap** and **Changelog**, with the app’s version. |
## The enclosure list
The left panel lists every enclosure in the workspace, one row each in its own colour. A row shows the name, the driver, then the type, size, power and tuning; the dot beside the power is its thermal load.
- Click a row to select it. The enclosure panel below and the Driver panel both edit the selected enclosure.
- The eye on a row takes it off the graphs. The count in the **Enclosures** header says how many are shown, and opens a menu with **Hide all**, **Swap shown and hidden**, **Select all** and **Sort once by**.
- ⌘-click (Ctrl-click on Windows and Linux) or Shift-click selects several. The header becomes a selection bar to show, hide, move or delete them together.
- Right-click a row for **Solo**, **Rename**, **Duplicate** and **Delete**, and, signed in, **Move to workspace** and **Copy to workspace**. Solo draws only those enclosures until you end it.
- **Add new enclosure**, at the foot of the list, opens **Add enclosure**: **Type**, **Driver**, **Name** and **Colour**, or **Pick an example**.
- **Measured traces**, below, holds measurements you import: [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements). Most list actions have a key: [Keyboard shortcuts](https://simulator.00aud.io/docs/guides/shortcuts).
## The enclosure panel
Under the list, **Enclosure** holds the selected enclosure’s box. **Type** comes first and decides the rest. A vented box shows **Volume**, **Tuning** and **Port length**, each with a slider, then these sections:
| Section | What is in it |
| --- | --- |
| **Port** | **Shape** (round, slot or a custom area), **Number of ports** and the port’s size. **Advanced**, inside it, holds **End correction** and **Port model**. |
| **Results** | Values worked out from the box, such as the port’s **Cross-sectional area** and **Port volume**. |
| **Baffle step** | **Simulate baffle step** adds the loss from a front baffle of a given **Width** and **Height**, with the driver where you place it. |
| **Box volume adjustments** | **Driver displacement** and **Bracing / other**: the space they take up inside the box. |
Each type has its own fields: [Boxes](https://simulator.00aud.io/docs/boxes) and [Horns](https://simulator.00aud.io/docs/horns) cover them, and [Controls and fields](https://simulator.00aud.io/docs/reference/controls) lists every one.
## The Driver panel
The right panel edits what drives the selected enclosure. With nothing selected it reads **Select an enclosure to edit**.
| Section | What is in it |
| --- | --- |
| **Driver** | The driver picker and **Edit T/S**; **Number of drivers**, from 1 to 50, with **Wiring** once there are several; **Voice coil wiring** for dual-coil drivers. [Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers). |
| **Power** | **Input power**, from 0.01 W to 100 kW, on a slider whose numbers you can click; **Series resistance**; a **Series capacitor**; and the voltage that power takes. [Power and limits](https://simulator.00aud.io/docs/guides/power-and-limits). |
| **EQ / filters** | The enclosure’s filters. **Add** gives high-pass and low-pass filters, parametric EQ, shelves and a Linkwitz transform. [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters). |
| **Environment** | **Radiation space** (Full space, Half space, Quarter space, Eighth space) and **Listening distance**, for the whole workspace. |
Both side panels fold to a narrow rail with a button per section, drag by their grip to either side of the tiles, and resize from their inner edge. **Reset panels**, in the layout menu, puts them back.
## Tiles
Every graph and tool on the dashboard is a tile, and every visible enclosure draws its own curve on it in its colour. A tile’s header carries its name and its controls:
- ⓘ, **How to read this tile**, opens help beside the workspace, or as a sheet on a phone. **Full page** opens its reference page under [All tiles](https://simulator.00aud.io/docs/reference/tiles).
- Controls of its own: **F3** marks on **SPL (dB)**, the warning value on **Port Velocity**, **EQ** to edit filters on the graph, and settings for the tile and its axes.
- **Expand to 2 columns** widens a tile, and **Remove graph** takes it off the dashboard.
- Drag a tile by its title to move it (**Drag to move graph**) or by its corner to resize it (**Drag to resize**). The other tiles make room, and a placeholder shows where it will land.
## Add tile
**Add tile**, at the right of the layout bar, lists every tile with a search box (**Search tiles...**). A tick marks the tiles already on the dashboard, and choosing one of those scrolls to it. A new workspace starts with just SPL (dB).
| Group | For example |
| --- | --- |
| **Editor** | EQ Editor, Horn Editor, Fold, Baffle Layout |
| **Graphs · core** | SPL (dB), Max SPL (dB), Headroom, Excursion, Port Velocity, Impedance |
| **Graphs · advanced** | Phase, Group Delay, Cone Velocity, Amplifier Load (VA), Compare |
| **Info** | Metrics, Insights, Schematic, T/S Parameters |
## Layouts and pinned tabs
A layout is a set of tiles and where they sit. The switcher at the left of the layout bar names the current one, or reads **Custom layout** when the tiles match none; a lime dot means changes that are not saved. The app has three:
| Layout | Tiles |
| --- | --- |
| Basic | SPL (dB), Impedance, Excursion |
| Headroom | Headroom, Max SPL (dB), Excursion |
| Horn Design | Horn Editor, SPL (dB), Impedance, Excursion, Group Delay |
- Pinned layouts sit beside the switcher as tabs, one click each. Basic, Headroom and Horn Design start pinned, and up to 5 can be; tabs that do not fit fold into a +N tab. Pin from a layout’s row in the switcher’s menu, or right-click a tab to **Unpin**, **Move left** or **Move right**.
- **Save as…** keeps the current tiles as a layout of your own, up to 20, saved in this browser for your account. Change a saved layout’s tiles and **Revert** and **Save** appear beside it.
- **Manage layouts…** lists every layout, pinned or not. The layout menu (⋯) at the far right also has **Shrink charts**, **Reset tiles to default** and **Reset panels**.
- More in [Layouts and pinned tabs](https://simulator.00aud.io/docs/guides/layouts).
## On a phone
_Figure: The workspace on a phone: the workspace menu at the top, one tile, and the dock with a pill per tile, the add button, the power chip and the layout button._
The same design on a phone. On a narrow screen the tiles page one at a time: swipe sideways or tap a pill.
1. Workspace menu
2. The tile on screen
3. A pill per tile
4. Add or choose a graph
5. Input power
6. Layout
- The menu at the top right (**Open workspace menu**) opens **Enclosures**, **Driver**, **Power**, **EQ** and **Environment** as drawers. The cloud at the top left goes back to your workspaces.
- The dock at the bottom has a pill per tile (the one on screen shows its name), **+** to add or choose a graph (**Add or choose a graph**), the power chip, and the layout button.
- The power chip opens **Input power** as a sheet over the dock, and the layout button opens the layouts, the list of tiles and **Add tile**. Selecting an EQ filter on a graph opens its editor the same way.
- One sheet opens at a time, and a sheet never resizes the graph above it, so EQ handles stay where they are.
- More in [On a phone](https://simulator.00aud.io/docs/guides/phone).
## Ask your AI
**Ask your AI**
With the 00 Simulator connector, your assistant can arrange your open tab’s tiles while it explains them.
> Using 00 Simulator, arrange the dashboard of my open workspace around SPL, Excursion and Port Velocity, and tell me what each one shows for every enclosure in it.
---
# Choose an enclosure type
> The six enclosure types in 00 Simulator, from sealed to horn, compared on the app’s own examples: what each one gives and what it costs.
Source: https://simulator.00aud.io/docs/start/enclosure-types
00 Simulator has six enclosure types: Sealed, Vented, Passive Radiator, Bandpass 4, Bandpass 6 and Horn. Each one trades box size, how deep the bass goes, how loud it plays and which limit you meet first. This page shows the trade on real designs so you can pick one to start with.
_Figure: The six enclosure types on one graph, each drawn relative to its own level so their roll-offs compare: sealed, vented, passive radiator, bandpass 4, bandpass 6 and a tapped horn._
Each design at its example’s power, half space, 1 m, drawn relative to its own loudest one-octave average (0 dB). Simulated when this page was built.
| Type | Design | −3 dB |
| --- | --- | --- |
| Sealed | Dayton Audio DCS205-4, 15 L | from 62.2 Hz |
| Vented | Ciare 12.00SW, 55 L, tuned to 32 Hz | from 30.3 Hz |
| Passive Radiator | Dayton Audio DCS165-4, 10 L, one radiator | from 63.8 Hz |
| Bandpass 4 | B&C 18SW115, 70 L sealed rear, 50 L front at 59 Hz | 38.9–92.2 Hz |
| Bandpass 6 | B&C 18SW115, 224 L rear at 30.6 Hz, 112 L front at 47.6 Hz | 29.7–56.8 Hz |
| Horn | B&C 21SW152, 2.5 m path | from 37.2 Hz |
## The six types
You pick the type in the **Type** list when you add an enclosure, and you can change it later in the enclosure panel. The graph above draws one design of each type. They use different drivers and powers, so it compares shapes, not loudness: where each one starts to roll off and how steeply it falls.
−3 dB is measured the way the SPL tile measures F3: against the loudest one-octave average. [Reading a response](https://simulator.00aud.io/docs/start/reading-a-response) explains it.
| Type | How it works | Example | −3 dB |
| --- | --- | --- | --- |
| **Sealed** | The driver in a closed box. The trapped air acts as a spring behind the cone. | [Dayton Audio DCS205-4, 15 L](https://simulator.00aud.io/app?template=sealed) | from 62.2 Hz |
| **Vented** | A closed box with a port. The air in the port resonates with the box at the tuning frequency and adds to the output there. | [Ciare 12.00SW, 55 L, tuned to 32 Hz](https://simulator.00aud.io/app?template=vented) | from 30.3 Hz |
| **Passive Radiator** | A vented box with a second cone, with no motor, in place of the port. Its mass sets the tuning. | [Dayton Audio DCS165-4, 10 L, one radiator](https://simulator.00aud.io/app?template=passive-radiator) | from 63.8 Hz |
| **Bandpass 4** | The driver between a sealed rear chamber and a front chamber loaded by a port or a passive radiator. Only that front outlet radiates. | [B&C 18SW115, 70 L sealed rear, 50 L front at 59 Hz](https://simulator.00aud.io/app?template=bandpass) | 38.9–92.2 Hz |
| **Bandpass 6** | Both chambers are loaded, each by a port or a passive radiator with its own tuning. Only those outlets radiate. | B&C 18SW115, 224 L rear at 30.6 Hz, 112 L front at 47.6 Hz (no example) | 29.7–56.8 Hz |
| **Horn** | A path that widens from the driver to a mouth, instead of a box. There are eight horn types, from front-loaded and tapped to multiple-entry. | [B&C 21SW152, tapped, 2.5 m path](https://simulator.00aud.io/app?template=tapped-horn) | from 37.2 Hz |
The Bandpass 6 row has no example of its own: it is the starting point the **Add enclosure** dialog fills in when you choose Bandpass 6 for the B&C 18SW115. The second horn example, three B&C 10PS26 drivers on a [multiple-entry horn](https://simulator.00aud.io/app?template=multi-entry-horn), is −3 dB from 70.4 Hz to 366 Hz: horns are not only for subwoofers.
## What each one trades
| Type | Gives you | Costs you |
| --- | --- | --- |
| [Sealed](https://simulator.00aud.io/docs/boxes/sealed) | A small, simple box. A gentle roll-off that room gain can fill in. The air spring holds the cone below resonance, and there is no port to fit or to make noise. | Less deep bass for its size than a vented box, so the cone travels further and needs more power for the same low notes. |
| [Vented](https://simulator.00aud.io/docs/boxes/vented) | More output low down from the same driver. Near the tuning the port does the work and the cone barely moves. The example is −3 dB at 30.3 Hz. | A steeper roll-off below the tuning, where the cone is no longer held and its travel climbs fast. A port that has to fit in the box and can chuff when the air in it moves too fast. |
| [Passive radiator](https://simulator.00aud.io/docs/boxes/passive-radiator) | Vented-style tuning with no port noise and no long port to fit, useful in small boxes. | A second cone to buy, with its own travel limit to check on the **PR Excursion** tile. The tuning moves with its added mass. |
| [Bandpass 4](https://simulator.00aud.io/docs/boxes/bandpass-4) | High output over one band, with the driver hidden inside. The example covers 38.9–92.2 Hz. | A narrow band, a large box for it, and one port that carries all the output, so check its air speed. |
| [Bandpass 6](https://simulator.00aud.io/docs/boxes/bandpass-6) | A band set by two chamber tunings. The starting point above covers 29.7–56.8 Hz. | Two chambers and two ports to size. Their tunings must stay apart: close together, their outputs cancel. |
| [Horn](https://simulator.00aud.io/docs/horns) | High efficiency and output over the band the path loads. The tapped horn example's loudest octave averages 121 dB at 1 m from 100 W. | Size: the tapped horn's path is 2.5 m long, folded into a cabinet. Ripple and extra lobes from the path's own resonances: above its band this one drops to −30 dB near 221 Hz, then comes back within 3 dB up to 249 Hz. More to design. |
> **Compare them in one workspace** Every enclosure in a workspace draws on the same tiles. Add a second type for the same driver and the difference in extension, excursion and port speed shows on one graph. See [Compare designs](https://simulator.00aud.io/docs/guides/compare).
## Where to start
When you choose a driver in the **Add enclosure** dialog, 00 Simulator suggests Sealed or Vented from its efficiency-bandwidth product, EBP = Fs / Qes. Above 75 it suggests Vented, otherwise Sealed, and it fills in a starting size you can accept or change.
- The Ciare 12.00SW from the vented example has an EBP of 88. The dialog suggests Vented and starts from 82.5 L (1.5 × Vas) tuned to 26.1 Hz (0.9 × Fs).
- The Dayton Audio DCS205-4 from the sealed example has an EBP of 81, so it too is suggested Vented. Choose Sealed anyway and the dialog starts from 10.2 L, the size for a Qtc of 0.707. The example itself uses 15 L.
- Passive radiator and horn designs start from the app’s own defaults. For those, open an example and change it.
The suggestion is a starting point, not a verdict. Beyond the driver, choose by what you can build and where it will play:
- Little space, or a room that adds bass of its own: start **Sealed**.
- The most bass from one driver in a box you can fit: start **Vented**, or **Passive Radiator** if a port will not fit.
- Loud over one narrow band: try **Bandpass 4**.
- Output and efficiency matter more than size: open the horn examples and read the [horn types](https://simulator.00aud.io/docs/horns).
[T/S parameters in five minutes](https://simulator.00aud.io/docs/start/ts-parameters) explains the driver numbers behind the suggestion, and [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) shows the limits every design runs into.
## Ask your AI
**Ask your AI**
Your assistant uses the same suggestion logic and solver through the 00 Simulator connector.
> Using 00 Simulator, suggest a sealed and a vented enclosure for the Dayton Audio DCS205-4, add both to a new workspace, and compare their F3, box size and peak excursion at 50 W.
---
# T/S parameters in five minutes
> The few Thiele/Small parameters that shape a speaker box, what each one does, and their values for the drivers in 00 Simulator’s examples.
Source: https://simulator.00aud.io/docs/start/ts-parameters
A driver’s Thiele/Small (T/S) parameters are the numbers 00 Simulator models it with. You need only a handful to choose a box: three set its size and tuning, two set how much air the cone can move, and four describe the motor and the power it takes.
- **Fs · Qts · Vas:** The box: its size, its tuning and the shape of the roll-off.
- **Sd · Xmax:** The air the cone can move, and so how loud it can play low down.
- **Re · Le · Bl · Pe:** The motor, the load the amplifier sees and the power rating.
## Fs, Qts and Vas: the box
- **Fs**, the resonance: the frequency where the cone’s moving mass bounces on its suspension, measured in free air. A box changes it: the air in a sealed box stiffens the suspension and raises the resonance.
- **Qts**, how damped that resonance is. It combines the electrical damping of the motor (Qes) and the mechanical losses of the suspension (Qms). Low Qts means a tightly controlled cone.
- **Vas**, the volume of air that is as springy as the suspension. A large Vas means a soft suspension, which needs a larger box for the same result.
In a sealed box of volume Vb the resonance rises to Fc = Fs × √(1 + Vas / Vb) and the Q to Qtc = Qts × √(1 + Vas / Vb). The Dayton Audio DCS205-4 in the 15 L [sealed example](https://simulator.00aud.io/app?template=sealed) has Fs 32.3 Hz, Qts 0.37 and Vas 27 L, so it settles at Fc 54.0 Hz with Qtc 0.62. The flattest response, Qtc 0.707, would take 10.2 L with Fc 61.7 Hz.
In this ideal sealed-box relation, Qtc stays above Qts. As Qts approaches 0.707 from below, the volume needed to reach that target becomes very large. At or above 0.707, no finite sealed volume reaches it.
For a rough enclosure suggestion, 00 Simulator uses the efficiency-bandwidth product, EBP = Fs / Qes. The **Add enclosure** dialog suggests **Vented** above 75 and **Sealed** below it. The **T/S Parameters** tile reads it more loosely: sealed below 50, vented above 100 and either in between.
The drivers in 00 Simulator’s examples. The suggestion only picks between Sealed and Vented, and it is a starting point: the sealed example’s driver, for one, is suggested Vented.
| Driver | Example | Fs | Qts | Vas | EBP | Suggested |
| --- | --- | --- | --- | --- | --- | --- |
| Dayton Audio DCS205-4 | [Sealed](https://simulator.00aud.io/app?template=sealed) | 32.3 Hz | 0.37 | 27 L | 81 | Vented |
| Ciare 12.00SW | [Vented](https://simulator.00aud.io/app?template=vented) | 29 Hz | 0.29 | 55 L | 88 | Vented |
| Dayton Audio DCS165-4 | [Passive Radiator](https://simulator.00aud.io/app?template=passive-radiator) | 35.7 Hz | 0.34 | 12.1 L | 99 | Vented |
| B&C 18SW115 | [Bandpass](https://simulator.00aud.io/app?template=bandpass) | 34 Hz | 0.30 | 149.1 L | 110 | Vented |
| B&C 21SW152 | [Tapped Horn](https://simulator.00aud.io/app?template=tapped-horn) | 32 Hz | 0.36 | 200 L | 84 | Vented |
| B&C 10PS26 | [Multiple-Entry Horn](https://simulator.00aud.io/app?template=multi-entry-horn) | 54 Hz | 0.29 | 38 L | 164 | Vented |
## Sd and Xmax: the air it can move
- **Sd**, the cone’s effective area.
- **Xmax**, how far the cone can travel one way before its motor and suspension stop behaving linearly. It is the maker’s figure for clean travel, not the point where the driver breaks.
Their product, Vd = Sd × Xmax, is the air one stroke can push. It sets how loud a driver can play low down: for the same level, a radiator has to move four times the air for every octave lower. In a sealed box the cone moves all of it; in a vented box the port takes over near the tuning. The B&C 21SW152 moves 34 times the air of the Dayton Audio DCS165-4 in one stroke.
| Driver | Sd | Xmax | Vd = Sd × Xmax |
| --- | --- | --- | --- |
| Dayton Audio DCS205-4 | 214 cm² | 8.8 mm | 188 cm³ |
| Ciare 12.00SW | 523 cm² | 13.5 mm | 706 cm³ |
| Dayton Audio DCS165-4 | 125 cm² | 6 mm | 75 cm³ |
| B&C 18SW115 | 1,210 cm² | 14 mm | 1,694 cm³ |
| B&C 21SW152 | 1,680 cm² | 15 mm | 2,520 cm³ |
| B&C 10PS26 | 320 cm² | 5.5 mm | 176 cm³ |
The **Excursion** tile draws each driver’s Xmax as a dashed line, and the **Max SPL (dB)** tile caps the level where the cone reaches it. [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) covers both, with the travel figures beyond Xmax.
## Re, Le, Bl and Pe: motor and power
- **Re**, the voice coil’s DC resistance. It sits a little below the nominal impedance (Znom), and the impedance dips close to it above resonance.
- **Bl**, the motor’s strength: force per amp of current. More Bl lowers Qes, so the motor damps the cone harder.
- **Le**, the voice coil’s inductance. It raises the impedance as frequency rises and trims the top of a woofer’s response.
- **Pe**, the rated power handling from the maker’s power test. It is a test rating, not the heat the coil can shed.
| Driver | Re | Znom | Le | Bl | Pe |
| --- | --- | --- | --- | --- | --- |
| Dayton Audio DCS205-4 | 3.9 Ω | 4 Ω | 1.78 mH | 10.7 T·m | 300 W |
| Ciare 12.00SW | 3.3 Ω | 4 Ω | 1.60 mH | 19.5 T·m | 2,000 W |
| Dayton Audio DCS165-4 | 3.4 Ω | 4 Ω | 1.43 mH | 9.2 T·m | 200 W |
| B&C 18SW115 | 3.3 Ω | 4 Ω | 1.36 mH | 26.0 T·m | 3,400 W |
| B&C 21SW152 | 6.0 Ω | 8 Ω | 2.20 mH | 39.0 T·m | 4,000 W |
| B&C 10PS26 | 6.0 Ω | 8 Ω | 1.20 mH | 14.1 T·m | 700 W |
> **Where Le shows up** The **Impedance** tile always includes Le. For SPL, box designs use **Settings › Simulation… › Non-horn upper response**. The default, **Estimated · BITS frequency limit**, assumes a flat driver and rolls off at the driver’s published upper frequency limit when the library has one. **Physical model** uses Le instead.
Pe feeds the heat limit on the Max SPL tile, which can read it three ways. [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) explains them.
## Where to find them in the app
- The **T/S Parameters** tile lists the selected enclosure’s driver under **Electrical**, **Mechanical** and **Physical**, then **Interpretation** (EBP and the suggested type) and **Sealed targets**: the box for a Qtc of 0.58, 0.71 or 0.90 and its Fc.
- Turn on the tile’s **T/S adjust sliders** to nudge a parameter and watch every graph move. They are temporary tweaks for exploring and do not change the driver.
- **Edit params** opens the driver’s values to change them and save over the driver or as a new one. [Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers) covers entering a driver from a datasheet.
Every parameter the app stores, with its unit and range, is in the [T/S parameters reference](https://simulator.00aud.io/docs/reference/ts-parameters).
## Ask your AI
**Ask your AI**
Your assistant reads the same driver library and suggestion logic through the 00 Simulator connector.
> Using 00 Simulator, look up the B&C 18SW115 and tell me its Fs, Qts, Vas, Xmax and EBP, which enclosure type the suggestion logic picks for it, and the sealed box volume for a Qtc of 0.707.
---
# Reading a response
> How to read an SPL curve in 00 Simulator: how F3 and F10 are measured, what radiation space and distance do, and what bumps and dips mean.
Source: https://simulator.00aud.io/docs/start/reading-a-response
A response is the level a design plays at each frequency. The **SPL (dB)** tile draws one for every visible enclosure, at its input power, the listening distance and the radiation space you set. This page reads one curve from end to end.
_Figure: The SPL tile for the vented example at 1 W, with its reference level and the −3 dB and −10 dB lines that set F3 and F10._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 1 W, half space, 1 m. Simulated when this page was built.
| Point | Level | Frequency |
| --- | --- | --- |
| Reference: loudest octave average | 88.1 dB | 249–499 Hz |
| F3 | 85.1 dB | 30.3 Hz |
| F10 | 78.1 dB | 24.9 Hz |
## The curve
- Frequency runs left to right on a log scale, so every octave is the same width: 20 to 40 Hz takes as much room as 200 to 400 Hz.
- Level is sound pressure in dB at the listening distance. The [vented example](https://simulator.00aud.io/app?template=vented&power=1) at 1 W is flat at about 88 dB and rolls off below 32 Hz, its tuning.
- Level follows power: ten times the power adds 10 dB and twice the power about 3 dB. The shape does not change, because the model is linear.
- Hover the tile to read the level at a frequency. Each visible enclosure draws its own curve in its colour.
## F3 and F10
F3 and F10 are where the curve has fallen 3 dB and 10 dB below its reference level. 00 Simulator takes the reference from the loudest one-octave stretch of the curve, averaged: for the vented example that is 88.1 dB between 249 and 499 Hz. With the default Auto reference, it uses the outer crossings across the simulated range. An internal dip does not set an edge, but a separate lobe above the threshold can move one.
- Turn on **F3** in the SPL tile’s header to mark F3 and F10 on every visible enclosure. The **F-point settings** cog beside it adds F6 or a custom level.
- Bandpass boxes and horns pass a band, so they get two marks for each level: a low edge (F3L) and a high edge (F3H).
- Under **Advanced** in the same settings, **Auto · loudest octave average** is the default reference. **Selected band average** averages a band you choose, and **Response peak** measures down from the highest point. Summary tiles always use Auto.
- The **Metrics** tile compares visible designs by one measure at a time; choose F3 or F10 to compare their extension.
Each example at its own power, half space, 1 m, with the default Auto reference. Bandpass and horn rows show both edges where both fall between 10 Hz and 500 Hz.
| Example | Power | F3 | F10 | Reference level |
| --- | --- | --- | --- | --- |
| [Sealed](https://simulator.00aud.io/app?template=sealed) | 1 W | 62.2 Hz | 33.8 Hz | 85.4 dB |
| [Vented](https://simulator.00aud.io/app?template=vented) | 1 W | 30.3 Hz | 24.9 Hz | 88.1 dB |
| [Passive Radiator](https://simulator.00aud.io/app?template=passive-radiator) | 1 W | 63.8 Hz | 34.9 Hz | 83.1 dB |
| [Bandpass](https://simulator.00aud.io/app?template=bandpass) | 100 W | 38.9 and 92.2 Hz | 27.2 and 134 Hz | 111.9 dB |
| [Tapped Horn](https://simulator.00aud.io/app?template=tapped-horn) | 100 W | 37.2 and 249 Hz | 32.8 Hz | 121.4 dB |
| [Multiple-Entry Horn](https://simulator.00aud.io/app?template=multi-entry-horn) | 50 W | 70.4 and 366 Hz | 59.3 Hz | 127.3 dB |
> **When the high edge jumps** The tapped horn’s F3H lands at 249 Hz because a second lobe above its band comes back within 3 dB. With **Selected band average** set to 40–110 Hz, F3 reads 37.3–117 Hz. For horns and narrow bandpass boxes, pick the band you mean to use.
## Radiation space and distance
The **Radiation space** setting represents how much space the speaker radiates into. For boxes it applies the level offsets below; for horns it also changes the mouth loading, so the response can change shape. It is in the **Environment** section of the Driver panel and applies to every enclosure in the workspace; the default is half space.
Box-model level offsets relative to full space. These are idealised boundary conditions; the model does not include room modes, reflections or the speaker’s directivity.
| Radiation space | Box-model gain | Where the speaker is |
| --- | --- | --- |
| **Full space** | +0 dB | Away from every surface, such as a speaker flown outdoors. |
| **Half space** | +6 dB | On the floor, or flush in one large surface. |
| **Quarter space** | +12 dB | On the floor against one wall. |
| **Eighth space** | +18 dB | In a corner: the floor and two walls. |
**Listening distance** in the same section sets where the level is read, from 0.1 to 50 m. Level falls 6 dB each time the distance doubles, so 2 m reads 6 dB below 1 m. Distance moves the SPL and Max SPL curves up and down without changing how hard the driver or the port works.
> **Compare like with like** The example curves on this page use half space at 1 m; other figures state their own settings. When comparing a datasheet or measurement, match space and distance first. In the box model, full space reads 6 dB below half space at the same distance. For horns the difference varies with frequency because the mouth loading changes too.
## Bumps and dips
_Figure: The vented example tuned to 32 Hz and the same box tuned to 45 Hz, which adds a hump above the roll-off._
The same 55 L box and driver at 1 W, half space, 1 m. Simulated when this page was built.
| Tuning | F3 | Hump above the level at 200 Hz |
| --- | --- | --- |
| 32 Hz | 30.3 Hz | none |
| 45 Hz | 40.3 Hz | +4.2 dB at 48.7 Hz |
- _A hump above the roll-off_ means the box is underdamped: a vented box tuned high, or a sealed box that is too small for its driver. Tuned to 45 Hz, the vented example gains a 4.2 dB hump at 48.7 Hz and loses its deepest bass: F3 rises from 30.3 Hz to 40.3 Hz.
- _Ripple and dips inside a band_ come from resonances along a horn’s path, or from two tunings set too far apart in a sixth-order bandpass box. Small ripple is normal; a deep dip is a hole in the band.
- _A dashed line marked PR_ on a vented box is the port’s first pipe resonance, where a real port can add a narrow peak of its own. For the vented example it sits at 482 Hz, well above the band a subwoofer uses.
- Peaks on the **Impedance** tile mark the tunings. The vented example has peaks at 19.1 Hz and 49.9 Hz with a dip at 31.6 Hz, close to its 32 Hz tuning. The sealed example has one peak, at 53.6 Hz: its resonance in the box, not the driver’s Fs.
A room adds peaks and dips of its own, often larger than any here. The simulation shows the speaker, not the room: [From simulation to a build](https://simulator.00aud.io/docs/start/simulation-to-build) covers what it leaves out and how to compare with a measurement.
## Ask your AI
**Ask your AI**
Your assistant reads the same curves through the 00 Simulator connector.
> Using 00 Simulator, simulate my open workspace and tell me each enclosure’s F3 and F10, the level of its loudest octave, and any dip deeper than 3 dB inside its band.
---
# Limits: travel, heat and air
> The three limits that stop a speaker getting louder (cone travel, voice coil heat and port air speed) and where 00 Simulator shows each one.
Source: https://simulator.00aud.io/docs/start/limits
Three things stop a speaker getting louder: the cone runs out of travel, the voice coil gets too hot, or the air in the port moves too fast. 00 Simulator draws each one. Max SPL combines travel and thermal limits; Headroom also checks port air speed. Which comes first depends on the design and the frequency.
- **Travel:** Cone excursion against Xmax, on the **Excursion** tile. Worst below the tuning of a ported box.
- **Heat:** The power into the voice coil against its rating, Pe, on the **Max SPL (dB)** tile.
- **Air:** Air speed in the port against 17 m/s, on the **Port Velocity** tile.
## Travel: Xmax, Xmech and Xdamage
_Figure: The Excursion tile for the vented example at 200 W, with and without a 25 Hz high-pass, against the driver’s 13.5 mm Xmax._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Excursion | Peak | At |
| --- | --- | --- |
| No filter | 21.2 mm | 10 Hz |
| 25 Hz high-pass | 6.3 mm | 24 Hz |
At 200 W the [vented example](https://simulator.00aud.io/app?template=vented&power=200) passes its 13.5 mm Xmax below 18.7 Hz, reaching 21.2 mm. At the 32 Hz tuning the port does the work and the cone moves only 2.5 mm. Below the tuning the box stops holding the cone, which is why a high-pass there helps: with a 25 Hz high-pass the peak falls to 6.3 mm.
The lines hide when **Show Xmax reference lines** is off in **Settings › Simulation…**.
| Figure | What it means | On the Excursion tile |
| --- | --- | --- |
| Xmax | Maximum linear excursion, one way. Past it the motor and suspension stop behaving linearly and distortion rises. A clean-playing limit, not damage. | Dashed line in the enclosure’s colour |
| Xmech | The mechanical limit, where the surround or spider bottoms. Optional in the driver’s data. | Dotted line |
| Xdamage | Travel that can physically damage the driver. Optional in the driver’s data. | Finely dotted line |
Passive radiators have their own Xmax, on the **PR Excursion** tile, and it caps Max SPL too. A passive radiator can run out of travel while the driver is still inside its own.
## Heat: Pe and the thermal rules
Pe is the power the maker rates the driver for, 2,000 W for the Ciare 12.00SW. What damages a voice coil is heat, and a loudspeaker is not a resistor: its impedance swings with frequency, so the same watts mean a different voltage, current and heat at every frequency. The Max SPL tile reads the rating one of three ways, chosen under **Thermal limit** in its settings:
| Rule | What it holds at the limit | For the Ciare 12.00SW |
| --- | --- | --- |
| Real input power, the default (as in Hornresp) | The real power going into the driver, at its rating. The voltage climbs at impedance peaks. | 2,000 W |
| Constant voltage (as in WinISD) | One amplifier voltage at every frequency: by default √(Pe × Re), the rated power into the coil’s resistance. | 81.2 V |
| Coil heating (an estimate) | The heat in the voice coil, at a budget: the heat the driver took in its own rating test, re-created in the model with pink noise over 30–300 Hz. | 1,029 W, 51% of the rating |
The coil heating budget is well under the rating because a power rating counts watts against the lowest impedance in its test band, while most of the band sits at higher impedance. **Voice coil temperature** (20–300 °C) raises Re for every rule: at 150 °C a copper coil’s resistance is 51% higher, which lowers the output where the impedance is close to Re. It applies to Max SPL only; the SPL tile stays cold.
_Figure: The Max SPL tile for the vented example with Limits on: the Max SPL line and the two ceilings it follows, the power limit dashed and Xmax dotted._
The same vented example, half space, 1 m. Max SPL does not depend on the input power you set. Simulated when this page was built.
| Frequency | Max SPL | Power limit ceiling | Xmax ceiling |
| --- | --- | --- | --- |
| 20 Hz | 93.7 dB | 111.3 dB | 93.7 dB |
| 32 Hz | 120.7 dB | 120.7 dB | 123.6 dB |
| 50 Hz | 117.9 dB | 127.4 dB | 117.9 dB |
| 100 Hz | 122.4 dB | 122.4 dB | 125.4 dB |
| 200 Hz | 121.3 dB | 121.3 dB | 137.1 dB |
Turn on **Limits** in the Max SPL tile’s header to draw both ceilings; the line is the lower of the two. In this box it follows Xmax below 30.9 Hz, heat from 30.9 to 34.8 Hz, Xmax from 34.8 to 86.6 Hz and heat above 86.6 Hz: heat takes over around the tuning, where the cone barely moves. Your input power and EQ do not move the line: they change what you send, not what the speaker can take. Port air speed is not part of Max SPL.
## Air: port velocity
Air through a port gets noisy when it moves too fast: it chuffs and whistles. The **Port Velocity** tile draws its peak speed at each frequency against a dashed warning line, 17 m/s by default. At 200 W the vented example’s port peaks at 28.4 m/s near 30.1 Hz, over the line. Air speed follows the square root of power: at a quarter of the power, 50 W, it peaks at 14.2 m/s.
- Change the warning line with **Port velocity** under **Settings › Simulation…**, from 10 to 30 m/s. The app’s hint puts the typical limit at 15 to 20 m/s, higher for flared ports.
- More port area lowers the speed; the port then gets longer to keep the tuning. [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port) walks through it.
- A sixth-order bandpass box has a second port, on the **Port Velocity (Rear Chamber)** tile.
## All three at once: Max SPL and Headroom
In this example the port is the tightest limit in the band the box plays: at 200 W it is over its line at the tuning, while the cone passes Xmax only below 18.7 Hz, beneath the box’s 30.3 Hz F3, and the power is 10% of Pe. Another design can be the other way round, which is why two tiles combine the limits:
- **Max SPL (dB)** shows the loudest each design can play at each frequency, a sine at a time, before Xmax or the thermal rule stops it. It ignores port air speed.
- **Headroom** starts from a listening target, an average level plus a crest factor for the peaks (85 dB and 12 dB by default), and colours each frequency **Clean**, **Threshold** or **Over max** against all the limits, port air speed included.
The Headroom tile’s default limits. Change them under **Limits** in its settings.
| Limit | Clean up to | Over max above |
| --- | --- | --- |
| Driver excursion | 1 × Xmax | 1.125 × Xmax |
| Port velocity | 17 m/s | 30 m/s |
| Thermal power | 0.5 × Pe | 1 × Pe |
| PR excursion | 1 × PR Xmax | 1.25 × PR Xmax |
> **What the limits leave out** The model is linear. A real driver’s motor and suspension soften as it nears Xmax, a hot coil compresses the output, and a port compresses before it chuffs. Each frequency is checked as a steady sine, while music spreads its energy and shares one thermal budget. Treat the lines as warnings to design away from, not ratings to run up to.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver at other powers through the 00 Simulator connector, without changing your design.
> Using 00 Simulator, for each enclosure in my open workspace, find the input power at which the cone first reaches Xmax and the power at which the port passes 17 m/s, without saving, and tell me which limit comes first and at what frequency.
---
# From simulation to a build
> What 00 Simulator’s model assumes and leaves out, what to enter so the box you build matches it, and how to check the build with a measurement.
Source: https://simulator.00aud.io/docs/start/simulation-to-build
A simulation is a model of the box you describe. It is close enough to choose a design and size a box, as long as you describe the box you will actually build. This page covers what the model assumes, what it leaves out, and how to measure the finished box and compare.
## What the model is
- _Boxes are lumped._ The driver, the air in each chamber and the air in each port are treated as single masses, springs and losses. That holds while the box and port are small next to the wavelength, which is 3.4 m at 100 Hz and shrinks as frequency rises.
- _Horns are paths._ Sound travels along the path as a plane wave, segment by segment, so the model follows the path’s length and area. It does not see its bends and folds.
- _It is linear._ Output scales with power and the shape never changes. Nothing compresses, except the voice coil temperature you can set for the Max SPL tile.
- _The driver is its T/S parameters:_ datasheet values, as the library holds them. Real samples differ from the datasheet and from each other.
## Enter the box you will build
**Volume** in the enclosure panel is the net internal volume: the air the driver works against, “excluding ports, bracing, and driver displacement”. Enter the driver and the bracing under **Box volume adjustments** (**Driver displacement** and **Bracing / other**) and the panel’s **Results** show the **Gross volume**: the space to build inside the walls, port included.
For the [vented example](https://simulator.00aud.io/app?template=vented), 55 L net with one 100 mm port 35.6 cm long, the port itself takes 2.8 L, so the gross volume is at least 57.8 L before you add the driver’s own displacement from its datasheet.
| What to enter | Where | Why it matters |
| --- | --- | --- |
| Driver displacement | **Box volume adjustments** | The magnet and basket take air from the box. Leave it out and the built box is smaller than the model. |
| Bracing and anything else inside | **Bracing / other** | Same: every litre of wood is a litre less air. |
| Port size and number | **Port** | **Port length** follows from the tuning, the port area and the end correction. Check it fits the box before you cut. |
| How the port ends | **End correction**, under the port’s **Advanced** | A port acts longer than it is, and a flanged end, such as one flush with the baffle, acts longer again. With “Two flanged ends” instead of “WinISD default”, the example’s port shrinks from 35.6 cm to 33.1 cm for the same tuning. |
| A finite front baffle | **Baffle step**, **Simulate baffle step** | Off by default. On, it adds the smooth loss that a baffle of your width and height causes as frequency falls, 6 dB at the bottom. It does not draw diffraction ripple. |
**Port model** under the same **Advanced** is **Lumped** by default. **Distributed** treats the port as a duct, which matters when its pipe resonance comes near the band you use. [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports) goes further.
## The top of the response
Above the bass, a real driver’s response is set by its cone and voice coil, which a lumped model describes only roughly. **Settings › Simulation… › Non-horn upper response** chooses how box designs handle it:
- **Estimated · BITS frequency limit**, the default, assumes a flat driver with a 24 dB/octave roll-off at the driver’s published upper frequency limit, when the library has one. The box’s own response and your EQ still apply. Impedance, excursion and phase use the physical model.
- **Physical model** uses the driver’s T/S parameters, including its voice coil inductance, all the way up.
- Horns always use the physical model.
**Upper frequency** under **Settings › Display…** sets how far up the solver runs. Auto is 400 Hz, or 2 kHz when the workspace has a horn.
## What it leaves out
- The room. Its modes and reflections add peaks and dips, often larger than the differences between designs. **Radiation space** uses idealised boundary conditions: a level offset for boxes, and a change in mouth loading for horns. It does not model a room.
- The cabinet itself: panel resonances and standing waves inside a box. A lumped box has the same pressure everywhere inside it.
- Where the sound goes. The model gives one level at the listening distance, not how the sound spreads with angle.
- Behaviour at the limits: a softening suspension and motor near Xmax, a port that compresses and chuffs, a coil that heats up. [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) shows where each one starts.
- Your driver. Measured T/S parameters of your own sample beat the datasheet; enter them with **Edit params** on the **T/S Parameters** tile.
The full list, with how the solver is checked against other tools, is in [Model and limits](https://simulator.00aud.io/docs/reference/model-and-limits), with the [WinISD](https://simulator.00aud.io/validation/winisd) and [Hornresp](https://simulator.00aud.io/docs/horns/hornresp#validation) comparisons.
## Measure the build and compare
1. **Measure.** Measure the finished box with a measurement microphone and a tool such as REW. An impedance sweep is worth taking too: it shows the real tuning without any room in it. Note the distance and where the box stood.
2. **Import.** Drop a REW export, an .frd or a .zma file on a graph, or paste a table. Or open **Measured traces**, below the enclosure panel on the left, and choose **Add measured trace**.
3. **Link it.** In the trace’s details set **Linked to** to the enclosure it measures, then fill in **Distance** and **Space**. A linked trace takes a shade of the enclosure’s colour and hides with it.
4. **Line up the level.** **Align…** matches the trace’s average level to the design over a band you choose. Only the offset changes, and **Residual after aligning** says how far the shapes still differ.
5. **Read the difference.** Compare the impedance first: on a vented box the dip between its two peaks is the real tuning, and it tells you whether the port and volume came out as modelled. Then compare the SPL shape, remembering the room.
[Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements) covers the import formats, smoothing and display options.
## Ask your AI
**Ask your AI**
Your assistant can import and compare measurements through the 00 Simulator connector.
> Using 00 Simulator, compare the measured SPL trace in my open workspace with the enclosure it is linked to, over 30 to 200 Hz: tell me the level offset, the RMS residual once the offset is removed, and the frequency of the largest remaining difference.
---
# Boxes overview
> The box types in 00 Simulator compared with one driver in one 10 L box: sealed, vented, passive radiator and bandpass, and what each is for.
Source: https://simulator.00aud.io/docs/boxes
Every enclosure in 00 Simulator that is not a horn is a box: sealed, vented, passive radiator, bandpass 4 and bandpass 6. What sets them apart is where the air behind the cone can go. This page puts one driver in the same box four ways, so the differences you see are the box’s alone.
## One driver, four boxes
The Dayton Audio DCS165-4 in 10 L, built as each box type in turn, at 1 W:
_Figure: SPL of the Dayton Audio DCS165-4 in the same 10 L as a sealed, a vented, a passive radiator and a bandpass 4 box._
Dayton Audio DCS165-4 in 10 L, every box at 1 W, half space, 1 m. The passive radiator is an SB Acoustics SB15SFCR-00 with 50 g added; the port is tuned to the same 35.4 Hz; the bandpass front is tuned to 60 Hz. Simulated when this page was built.
| Box | −3 dB |
| --- | --- |
| Sealed | from 77.5 Hz |
| Vented, 5 cm port | from 35.9 Hz |
| Passive radiator, 50 g added | from 35.6 Hz |
| Bandpass 4, 5 L + 5 L | 41–90 Hz |
- **Sealed** rolls off first and most gently: −3 dB from 77.5 Hz, falling about 12 dB per octave below that. The air in the box is a spring behind the cone, and only the cone radiates.
- **Vented** and **Passive radiator** both tune the box to about 35.4 Hz and reach down to 35.9 Hz and 35.6 Hz: at 35 Hz they are 6.9 dB and 7.0 dB louder than the sealed box. The port that does it is 43.7 cm long, twice the inside of a 10 L cube (21.5 cm a side); the radiator needs only a hole in the baffle.
- Below the tuning the two part ways: the port’s output keeps falling steeply, the radiator’s drops into a notch at 15.4 Hz, near the radiator’s own resonance with its added mass.
- **Bandpass 4** passes a band, 41–90 Hz. The driver sits between a sealed rear chamber and a ported front one, and only the port radiates, so the upper bass is filtered out: at 200 Hz it is 19.4 dB below the sealed box.
> **One comparison, not a ranking** These four share a driver and a volume so the curves compare fairly. Each type does its best with a box chosen for it: for this driver, the Add enclosure dialog starts a sealed box at 3.6 L and a vented one at 18.2 L. The passive radiator here was picked to match the port. Each type’s page shows what its own settings do.
## The box types
Choose the type in **Type** at the top of the enclosure panel. The two bandpass types show there as **4th-order BP** and **6th-order BP**.
| Type | The air behind the cone | Choose it for |
| --- | --- | --- |
| [Sealed](https://simulator.00aud.io/docs/boxes/sealed) | Trapped in a closed box, as a spring. | Small, simple boxes, a gentle roll-off and tight timing. |
| [Vented](https://simulator.00aud.io/docs/boxes/vented) | Leaves through a port tuned with the box. | Deeper bass from the same box, when the port fits. |
| [Passive radiator](https://simulator.00aud.io/docs/boxes/passive-radiator) | Moves a second cone with no motor, tuned by its mass. | A low tuning in a small box, with no port to chuff. |
| [Bandpass 4](https://simulator.00aud.io/docs/boxes/bandpass-4) | Fills a sealed rear chamber; the front chamber radiates through a port or a passive radiator. | A band of bass with the range above it filtered out. |
| [Bandpass 6](https://simulator.00aud.io/docs/boxes/bandpass-6) | Both chambers are loaded by a port or a passive radiator, each with its own tuning, and only those outlets radiate. | A band shaped by two tunings. |
A horn loads the driver with a path that widens to a mouth instead of a box. The eight horn types have their own tab: [Horns overview](https://simulator.00aud.io/docs/horns).
## In every box
- [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports): Port shapes, several ports, end correction and the port model.
- [Several drivers and wiring](https://simulator.00aud.io/docs/boxes/multiple-drivers): More than one driver in a box, and how they are wired.
- [Losses and damping](https://simulator.00aud.io/docs/boxes/losses): The losses a real box has, and what the model includes.
## Where to start
- [Choose an enclosure type](https://simulator.00aud.io/docs/start/enclosure-types) compares the app’s own examples, one of each type, from sealed to horn.
- When you add an enclosure with a driver chosen, 00 Simulator suggests **Sealed** or **Vented** from the driver’s EBP (Fs divided by Qes): vented above 75, sealed at 75 or below.
- The [Sealed box calculator](https://simulator.00aud.io/calculators/sealed-box) and [Ported box calculator](https://simulator.00aud.io/calculators/ported-box) size a first box for a driver before you open the simulator.
## Ask your AI
**Ask your AI**
Your assistant builds and compares the boxes with the same solver, through the 00 Simulator connector.
> Using 00 Simulator, add a sealed and a vented box of the same volume to my open workspace, both with the driver from my first enclosure. Simulate them at its set power and compare their F3, peak excursion and, for the vented box, peak port air speed.
---
# Sealed
> How a sealed box works in 00 Simulator: the air spring behind the cone, what the volume does to Qtc, F3 and excursion, and its fields.
Source: https://simulator.00aud.io/docs/boxes/sealed
A sealed box is the driver in a closed, airtight box. The air trapped behind the cone is a spring, so the size of the box decides where the bass rolls off and how sharply. It is the simplest box to design and build, and the one to compare every other type with.
_Figure: The sealed example as the Schematic tile draws it: the Dayton Audio DCS205-4 on the baffle, its rear loading a closed 15 L chamber._
The [sealed example](https://simulator.00aud.io/app?template=sealed) in the [Schematic](https://simulator.00aud.io/docs/reference/tiles/schematic) tile: the Dayton Audio DCS205-4 in 15 L. Only the cone reaches the room.
The cone radiates directly; the rear face loads a sealed chamber.
## How it works
When the cone moves in, it squeezes the air in the box; when it moves out, it stretches it. That air pushes back like a spring, added to the driver's own suspension, so the driver resonates higher in the box than it does on its own. The Dayton Audio DCS205-4 resonates at 32.3 Hz in free air and at 54 Hz in the example's 15 L.
Two numbers describe the result, and the enclosure panel shows both: Fsc, the box's resonance (the **system resonance**), and Qtc, how sharply the response turns at it (the **system Q**). The example's Qtc is 0.62, and its F3 is 62.2 Hz.
Below the resonance the output falls at close to 12 dB per octave: the example loses 12.0 dB from 20 Hz down to 10 Hz. That is half the slope of a vented box, and it is the whole of the low end: only the cone radiates, so there is no port to tune or to hear.
## What the volume does
The same Dayton Audio DCS205-4 in four sealed boxes, from 6 L to 40 L:
_Figure: SPL of the Dayton Audio DCS205-4 in four sealed boxes, 6 L, 10.2 L, 15 L, 40 L: the smaller the box, the higher and sharper the knee._
Dayton Audio DCS205-4 at 1 W, half space, 1 m. Simulated when this page was built.
| Box | Qtc | F3 |
| --- | --- | --- |
| 6 L | 0.87 | 69.5 Hz |
| 10.2 L, suggested | 0.71 | 63 Hz |
| 15 L, the example | 0.62 | 62.2 Hz |
| 40 L | 0.48 | 64.9 Hz |
- A smaller box is a stiffer spring. In 6 L the resonance rises to 75.8 Hz and Qtc to 0.87, so the knee is higher and sharper.
- A bigger box is a softer spring. In 40 L Qtc falls to 0.48 and the curve starts to droop earlier, so F3 barely moves: 63 Hz in 10.2 L, 64.9 Hz in 40 L.
- What a bigger box does buy is the very bottom: at 20 Hz the 40 L box is 8.6 dB louder than the 6 L one.
> **Qtc 0.707 is the usual start** A Qtc of 0.707 is the flattest response that does not peak (a Butterworth alignment); above it the knee turns into a small hump. When you add a sealed enclosure with a driver chosen, 00 Simulator starts it at the volume that gives 0.707 (or 1.15 × Qts, for a driver whose Qts is above 0.68). For the Dayton Audio DCS205-4 that is 10.2 L.
## Excursion: a smaller box holds the cone
In a sealed box the cone does all the work, and its travel keeps rising as the frequency falls until it levels off below the resonance. The box's air spring is what holds it back, so the bigger, softer box lets it travel further.
_Figure: Cone excursion of the Dayton Audio DCS205-4 at 50 W in the same four sealed boxes, against its Xmax: the bigger the box, the further the cone moves at low frequencies._
Dayton Audio DCS205-4 at 50 W, half space, 1 m, with its 8.8 mm Xmax. Simulated when this page was built.
| Box | At 20 Hz |
| --- | --- |
| 6 L | 4.0 mm |
| 10.2 L, suggested | 5.7 mm |
| 15 L, the example | 7.0 mm |
| 40 L | 10.0 mm |
At 50 W and 20 Hz the cone moves 7.0 mm in the example, inside its 8.8 mm Xmax, and 10.0 mm in 40 L, past it. A sealed box runs out of travel at its lowest notes first, so read the [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) tile at the power you plan to use, and add a **High-pass** filter below the band you need if it crosses the line.
## What you set
Choose **Sealed** in **Type** at the top of the enclosure panel. The sealed fields are:
| Field | What it sets |
| --- | --- |
| **Volume** | The net internal volume: the air behind the cone, not counting the driver, bracing or anything else inside. Type a value from 0.01 L up, or drag the slider under it (1 to 1,000 L). Click the unit to change it. |
| Fsc, **system resonance** | The box’s resonance with the chosen driver. Type a frequency and the volume changes to give it. It cannot go below the driver’s Fs. |
| Qtc, **system Q** | How sharply the response turns at that resonance. Type a Q and the volume changes to give it. It cannot go below the driver’s Qts. |
| **Results › Gross volume** | Shown once you add volume under **Box volume adjustments**: the net volume plus what sits inside, which is the box to build. |
| **Box volume adjustments** | **Driver displacement** and **Bracing / other**: volume taken up inside the box. |
Fsc and Qtc appear once the enclosure has a driver, and count every driver in it: two drivers in the same volume behave like one driver with twice the Vas. **Baffle step** sits below, as it does for every type; see [Controls and fields](https://simulator.00aud.io/docs/reference/controls).
## When to use it
### Good for
- Simple builds: one closed box, nothing to tune and no port to fit or to hear.
- A gentle roll-off that EQ can reshape: the **Linkwitz transform** filter retunes a sealed box’s response.
- Tight timing. With the same Dayton Audio DCS165-4 in the same 10 L, the sealed box delays 40 Hz by 4.0 ms and the vented box by 13.6 ms (the [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay) tile).
### Watch for
- Less deep bass than a vented box of the same size: in that 10 L comparison the sealed box is 6.9 dB quieter at 35 Hz ([one driver, four boxes](https://simulator.00aud.io/docs/boxes#one-driver-four-boxes)).
- Excursion at the bottom. The cone does all the work and travels furthest at the lowest notes, so that is where it meets Xmax first.
- A bigger box is not a lower F3 with a low-Qts driver like the Dayton Audio DCS205-4 (Qts 0.37): Qtc falls and the response droops sooner instead.
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The sealed example at 50 W in the app’s own tiles, as the box grows to 30 L and shrinks to 8 L.
To keep going, [open the sealed example](https://simulator.00aud.io/app?template=sealed) in the simulator: the Dayton Audio DCS205-4 in 15 L, as on this page. Change **Volume** or type a **system Q** and watch the curves follow, or [open it at 50 W](https://simulator.00aud.io/app?template=sealed&power=50) to read the excursion.
## Tiles to watch
- [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl): Where the box rolls off, and its F3.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): How far the cone travels against Xmax, most at the bottom.
- [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance): One peak, at the box’s resonance: 53.6 Hz in the example.
- [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl): How loud it can play before excursion or heat stop it.
- [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay): The timing a sealed box is known for.
## Ask your AI
**Ask your AI**
Your assistant sizes and simulates the box with the same solver, through the 00 Simulator connector.
> Using 00 Simulator, add a sealed box to my open workspace with the same driver as my first enclosure, sized for a Qtc of 0.707. Simulate it at the same power and tell me its F3 and the frequency below which the cone passes Xmax.
---
# Vented
> How a vented (bass reflex) box works in 00 Simulator: the port and its tuning, what the tuning does to F3 and port length, and its fields.
Source: https://simulator.00aud.io/docs/boxes/vented
A vented box is a closed box with a port: a tube that lets the air inside out. The air in the port bounces on the air in the box at one frequency, the tuning, and adds its output to the cone there. You get deeper bass from the same box, and a port to size.
_Figure: The vented example as the Schematic tile draws it: the Ciare 12.00SW on the baffle, its rear loading a 55 L chamber that radiates through a 10 cm port tuned to 32 Hz._
The [vented example](https://simulator.00aud.io/app?template=vented) in the [Schematic](https://simulator.00aud.io/docs/reference/tiles/schematic) tile: the Ciare 12.00SW in 55 L, tuned to 32 Hz. The cone and the port both reach the room.
The rear face loads the chamber, which radiates through a port. Cone and port both reach the room.
## How it works
The air in the port is a small mass; the air in the box is a spring. Together they resonate at the tuning frequency, Fb, the way a bottle hums when you blow across it. Around Fb the port moves most of the air and the cone barely moves; well above it the port hardly matters and the box acts much like a sealed one.
Below Fb the port and the cone work against each other and the output falls fast, close to 24 dB per octave: the example loses 22.8 dB from 20 Hz down to 10 Hz, twice the slope of a sealed box. The cone also loses the port's support there, which is the thing to watch.
## What the tuning does
The same 55 L box and 10 cm port, tuned from 28 Hz to 40 Hz. Only the port length changes.
_Figure: SPL of the 55 L vented example tuned to 28, 32, 36, 40 Hz: a lower tuning sags, a higher one humps._
Ciare 12.00SW in the 55 L vented example with its 10 cm port, at 1 W, half space, 1 m. Simulated when this page was built.
| Tuning | F3 | Port |
| --- | --- | --- |
| 28 Hz | 29.6 Hz | 48.3 cm |
| 32 Hz, the example | 30.3 Hz | 35.6 cm |
| 36 Hz | 32.6 Hz | 26.8 cm |
| 40 Hz | 35.9 Hz | 20.6 cm |
- Tune lower and the response sags into a long slope: F3 only moves from 30.3 Hz to 29.6 Hz, but the port grows from 35.6 cm to 48.3 cm.
- Tune higher and the response humps above the tuning: 3.1 dB over the level at 100 Hz at 40 Hz, against 0.5 dB for the example. F3 rises to 35.9 Hz and the port shrinks to 20.6 cm.
- A bigger box or a narrower port shortens the port for the same tuning; a wider port lengthens it. [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports) has the details.
## Excursion: low at the tuning, high below it
_Figure: Cone excursion of the vented example at 200 W: lowest near the 32 Hz tuning, rising steeply below it past Xmax._
Ciare 12.00SW in the 55 L vented example at 200 W, half space, 1 m, with its 13.5 mm Xmax. Simulated when this page was built.
| Design | Least | At 20 Hz |
| --- | --- | --- |
| 32 Hz tuning at 200 W | 2.5 mm at 32.4 Hz | 12.5 mm |
At 200 W the cone moves least near the tuning, 2.5 mm at 32.4 Hz, because the port is doing the work. Below it the cone is unloaded and its travel climbs past the 13.5 mm Xmax below 18.7 Hz. If you do not need output below the tuning, a **High-pass** filter just under it keeps the cone in check.
The port has its own limit: at 200 W its air speed peaks at 28.4 m/s near 30.1 Hz, above the default 17 m/s warning line. This flags a risk of noise; the actual onset depends on the port’s shape and ends. The [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) tile shows it, and [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port) shows what to change.
## What you set
Choose **Vented** in **Type** at the top of the enclosure panel. The vented fields are:
| Field | What it sets |
| --- | --- |
| **Volume** | The net internal volume: the air in the box, not counting the ports, the driver or bracing. |
| **Tuning** | The box’s tuning frequency, Fb, from 15 to 1,200 Hz. |
| **Port length** | The physical length of each port for that tuning. Tuning and port length are a pair: set one and the other follows. The one you set last is held when you change the port’s size: with the tuning held, a wider port gets longer; with the length held, the tuning moves instead. A warning beside it means the port is too narrow for the tuning: make it wider or add ports. |
| **Port › Shape** | A round port, a slot, or a custom **Cross-sectional area**. |
| **Number of ports** | From 1 to 10 identical ports, each as long as **Port length**. |
| **Diameter**, or **Width** and **Height** | The size of each port: a diameter for a round port, width and height for a slot. |
| **Advanced** | **End correction** and **Port model**, under **Port**. See [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports). |
| **Results** | **Cross-sectional area** (all ports together), **Port volume**, **Gross volume** (net volume plus ports and anything under **Box volume adjustments**) and **1st port resonance**. |
> **Check the port fits** The example’s port is 35.6 cm long inside a 55 L box. **1st port resonance** under **Results** is the pipe resonance of that length (482 Hz here); a long port puts it lower, closer to the band you use.
## When to use it
### Good for
- Deeper bass from the same box. With the same Dayton Audio DCS165-4 in 10 L, the vented box reaches F3 35.9 Hz and the sealed one 77.5 Hz ([one driver, four boxes](https://simulator.00aud.io/docs/boxes#one-driver-four-boxes)).
- Little cone travel around the tuning, where the port does the work: more level for the same excursion.
- Drivers with a high EBP (Fs divided by Qes). When you add an enclosure, 00 Simulator suggests **Vented** for an EBP above 75; the Ciare 12.00SW’s is 88.
### Watch for
- The cone below the tuning, where it has no support: use a **High-pass** filter and read the [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) tile at full power.
- Port noise: keep the air speed under the 17 m/s line at the power you plan to use, or make the port bigger.
- Port length: a low tuning or a wide port makes a long port. In a small box it may not fit; the [comparison](https://simulator.00aud.io/docs/boxes#one-driver-four-boxes) needs a 43.7 cm port in 10 L, where a [passive radiator](https://simulator.00aud.io/docs/boxes/passive-radiator) is the usual answer.
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The vented example at 100 W in the app’s own tiles, as the tuning drops to 28 Hz and a second port goes in.
To keep going, [open the vented example](https://simulator.00aud.io/app?template=vented) in the simulator: the Ciare 12.00SW in 55 L tuned to 32 Hz, as on this page. [Open it at 200 W](https://simulator.00aud.io/app?template=vented&power=200) to see the limits.
## Tiles to watch
- [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl): The tuning, the roll-off below it and F3.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): The dip at the tuning and the climb below it.
- [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity): Air speed in the port against the 17 m/s line.
- [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance): Two peaks, at 19.1 Hz and 49.9 Hz in the example, with a dip near the tuning between them (31.6 Hz).
- [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl): How loud it can play before excursion, heat or the port stop it.
## Ask your AI
**Ask your AI**
Your assistant tries the changes with the same solver, through the 00 Simulator connector, and saves nothing unless you ask.
> Using 00 Simulator, for the vented box in my open workspace, try the tuning 4 Hz lower and 4 Hz higher without saving. Tell me each option’s F3, port length and peak port air speed at its set power, and which one you would build.
---
# Passive radiator
> How a passive radiator box works in 00 Simulator: tuning with added mass, choosing a radiator, PR Excursion, and the fields to set.
Source: https://simulator.00aud.io/docs/boxes/passive-radiator
A passive radiator box is a vented box with a cone in place of the port: a driver with no motor, moved by the air in the box. Its mass does the port’s job, so you can tune a small box low without a port that will not fit, and with no port to chuff.
_Figure: The passive radiator example as the Schematic tile draws it: the Dayton Audio DCS165-4 on the baffle, its rear loading a 10 L chamber that radiates through the Dayton Audio E150HE-PR._
The [passive radiator example](https://simulator.00aud.io/app?template=passive-radiator) in the [Schematic](https://simulator.00aud.io/docs/reference/tiles/schematic) tile: the Dayton Audio DCS165-4 and one Dayton Audio E150HE-PR in 10 L. The cone and the radiator both reach the room.
The rear face loads the chamber, which radiates through a passive radiator. Cone and passive radiator both reach the room.
## How it works
The radiator sits in the baffle where a port would go. When the cone pushes the air in the box, the air pushes the radiator. Its moving mass on the box’s air spring resonates like the air in a port, and that resonance is the box’s tuning: **Box tuning (Fb)** under **Results**, 36 Hz in the example.
Unlike the air in a port, a radiator has a suspension of its own, so it also has its own resonance. Below the tuning the output falls into a notch near that resonance, where the radiator and the cone cancel. That, and the radiator’s own travel, are what a port does not have.
## Tune it with added mass
Adding mass to the radiator is how you tune the box. The example with 25, 50, 100 g added:
_Figure: SPL of the passive radiator example with 0, 25, 50, 100 g added to the radiator: more mass tunes the box lower._
Dayton Audio DCS165-4 and one Dayton Audio E150HE-PR in the 10 L passive radiator example, at 1 W, half space, 1 m. Simulated when this page was built.
| Radiator | Fb | At 30 Hz |
| --- | --- | --- |
| No added mass, the example | 36 Hz | 65.7 dB |
| 25 g added | 31.2 Hz | 71.3 dB |
| 50 g added | 28 Hz | 73.6 dB |
| 100 g added | 23.7 Hz | 73.3 dB |
Each gram lowers the tuning: 50 g takes it from 36 Hz to 28 Hz, and makes the box 7.9 dB louder at 30 Hz. The price is a little of the upper bass: 0.6 dB at 60 Hz.
| Change from the example | Box tuning (Fb) |
| --- | --- |
| None | 36 Hz |
| 50 g of **Added mass (tuning)** | 28 Hz |
| Two radiators (**Number of PRs** 2) | 41.4 Hz |
| Twice the volume, 20 L | 32.9 Hz |
A second radiator doubles the moving area and raises the tuning, like a second port; add mass to bring it back down. A bigger box is a softer spring and lowers it.
## Choose a radiator that suits the box
Two radiators can give a box the same tuning and very different bass. Here the example’s Dayton Audio DCS165-4 and 10 L are tuned to about 35.4 Hz by a port, by a soft radiator with mass added, and by the example’s own radiator:
_Figure: SPL of the same driver and 10 L box tuned to about 35.4 Hz three ways: a port, the soft SB Acoustics SB15SFCR-00 with added mass, and the stiff Dayton Audio E150HE-PR._
Dayton Audio DCS165-4 in 10 L at 1 W, half space, 1 m. Simulated when this page was built.
| Design | Fb | F3 |
| --- | --- | --- |
| 5 cm port | 35.4 Hz | 35.9 Hz |
| SB Acoustics SB15SFCR-00, 50 g added | 35.4 Hz | 35.6 Hz |
| Dayton Audio E150HE-PR, the example | 36 Hz | 63.8 Hz |
- The SB Acoustics SB15SFCR-00 resonates at 21 Hz on its own (the Fs the radiator list shows beside its name), and its suspension is soft: its Vas is 41.8 L, far more than the box. With mass added it follows the port down to F3 35.6 Hz, then drops into its notch: 26.4 dB below the port at 15.4 Hz.
- The Dayton Audio E150HE-PR resonates at 30 Hz, close to the tuning, and its Vas is 4.8 L, stiffer than the 10 L of air behind it. At the same tuning its F3 is 63.8 Hz.
- The port matches the soft radiator, but it has to be 43.7 cm long, about twice the inside of a 10 L cube (21.5 cm a side).
> **A soft radiator with added mass tunes deep** As a rule, pick a radiator whose own resonance sits well below the tuning you want and whose Vas is larger than the box, then add mass to bring the tuning down. Pick one with enough area and travel too: it has to move the air a port would.
## Two things move: the cone and the radiator
The radiator moves most around the tuning, where it does the work, and has its own Xmax. The [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion) tile draws its travel with a dashed **PR Xmax** line; read it beside the cone’s [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) tile. The example at 20 W:
_Figure: The cone's excursion and the radiator's PR Excursion for the passive radiator example at 20 W, each against its own Xmax._
| Case | Peak | At | Note |
| --- | --- | --- | --- |
| Cone, Dayton Audio DCS165-4 | 8.1 mm | 10 Hz | 8.1 mm at 10 Hz · Xmax 6.0 mm |
| Radiator, Dayton Audio E150HE-PR | 6 mm | 33 Hz | 6.0 mm at 33.2 Hz · PR Xmax 19.0 mm |
The passive radiator example at 20 W, half space, 1 m. Simulated when this page was built.
Below the tuning the radiator stops holding the cone back, as a port does, and the cone passes its 6.0 mm Xmax below 25.5 Hz. The radiator peaks at 6.0 mm near 33.2 Hz, 32% of its 19.0 mm. Which one runs out first depends on the pair: a radiator with less area or travel can be the limit.
## What you set
Choose **Passive radiator** in **Type** at the top of the enclosure panel. Its fields are:
| Field | What it sets |
| --- | --- |
| **Volume** | The net internal volume: the air behind the cone, not counting the driver or bracing. |
| **Added mass (tuning)** | Grams added to each radiator, from 0 to 500 g. More mass, lower tuning. |
| **Passive radiator** | Which radiator. Click **Select a passive radiator…** and type a brand or model, or choose **Browse all with mechanical filters**. **Add** makes a radiator from its own parameters. |
| **Number of PRs** | How many identical radiators, from 1 to 50. It appears once a radiator is chosen. |
| **Results** | **Box tuning (Fb)**, **Total PR mass** (every radiator with its added mass) and, when you add volume under **Box volume adjustments**, **Gross volume**. |
## When to use it
### Good for
- A low tuning in a small box, where a port would not fit: the 10 L box above needs a 43.7 cm port, a radiator only a hole in the baffle.
- No port noise: there is no jet of air to chuff.
- Tuning you can change after the build, by adding or removing mass.
### Watch for
- The notch below the tuning, near the radiator’s own resonance: the output falls away faster there than with a port.
- A stiff radiator, or one whose own resonance is close to the tuning: it loses the deep bass a port would give.
- Two limits instead of one: the cone below the tuning and the radiator around it. Check both at the power you plan to use.
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The passive radiator example at 20 W in the app’s own tiles, with 50 g added and then 2 radiators.
To keep going, [open the passive radiator example](https://simulator.00aud.io/app?template=passive-radiator) in the simulator: the Dayton Audio DCS165-4 and one Dayton Audio E150HE-PR in 10 L, as on this page. Change **Added mass (tuning)** and watch **Box tuning (Fb)** follow.
## Tiles to watch
- [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl): The tuning, the notch below it and F3.
- [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion): How far the radiator travels, against its own Xmax.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): The cone, which still unloads below the tuning.
- [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance): Two peaks, at 30.1 Hz and 54.9 Hz in the example, with a dip near the tuning between them.
- [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl): How loud it can play before excursion or heat stop it.
## Ask your AI
**Ask your AI**
Your assistant tries the changes with the same solver, through the 00 Simulator connector, and saves nothing unless you ask.
> Using 00 Simulator, for the passive radiator box in my open workspace, try 25 g and 50 g of added mass without saving. Tell me each option’s tuning, F3, and peak passive radiator excursion at its set power against the radiator’s Xmax.
---
# Bandpass 4
> How a fourth-order bandpass box works in 00 Simulator: a sealed rear chamber, a front chamber loaded by a port or a passive radiator, and what each one changes.
Source: https://simulator.00aud.io/docs/boxes/bandpass-4
A fourth-order bandpass puts the driver in the wall between two chambers: a sealed one behind the cone and a ported one in front (a passive radiator can take the port’s place). Only the front outlet reaches the room, so the box plays one band of bass and rolls off both sides of it. This page shows what each chamber does, on the app’s bandpass example.
_Figure: The bandpass example drawn by the simulator’s schematic: the driver between a sealed rear chamber and a front chamber with one port to the room._
The bandpass example as the **Schematic** tile draws it: 70 L sealed behind the cone, 50 L in front tuned to 59 Hz.
The driver sits between a sealed rear chamber and a front chamber that radiates through a port. Only the chamber outlets reach the room.
## How it works
Behind the cone, the sealed rear chamber is a spring, as in a sealed box. In front, the cone drives the air in the front chamber, and that chamber’s port is the only way out: the chamber and the air in its port resonate at the front tuning, the middle of the band. Below the band the output falls as a sealed box’s does. Above it the air in the port is too heavy to follow, so the box rolls off the top of the band on its own.
_Figure: The bandpass example's SPL at 100 W, with the level 3 dB under its loudest octave marked._
B&C 18SW115 in the bandpass example (70 L sealed rear, 50 L front), at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Band | Peak |
| --- | --- | --- |
| Bandpass example | 38.9–92.2 Hz | 112.7 dB at 59 Hz |
- **Passband (−3 dB):** 38.9–92.2 Hz, 1.2 octaves
- **Loudest:** 112.7 dB at 59 Hz, from 100 W
- **Chambers:** 70 L sealed rear, 50 L front tuned to 59 Hz
- **Front port:** One 15 cm port, 21.3 cm long
The **SPL** tile marks both edges of a bandpass box’s band, F3L and F3H, measured against its loudest one-octave average as F3 is for any box. [Reading a response](https://simulator.00aud.io/docs/start/reading-a-response) explains the reference.
## What you set
Choose **Bandpass 4** as the **Type** when you add an enclosure, or switch an existing one: the enclosure panel lists the same type as **4th-order BP**. The panel then shows one chamber at a time, picked with the **Front** and **Rear** tabs beside **Chamber**.
| Control | What it sets |
| --- | --- |
| **Front** › **Loading** | **Port**, or **Passive radiator** to replace the front port with a radiator, as in a passive radiator box. |
| **Front volume** | The net air in the front chamber. With the port, it sets how wide and how loud the band is. |
| **Tuning** | The front chamber’s tuning: where the band sits. |
| **Port length** | The front port’s length. Change the tuning and the length follows, or type a length and the tuning follows. See [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports#tuning-and-length). |
| **Port** | The front port’s **Shape**, **Number of ports**, **Diameter** and, under **Advanced**, its **End correction**. |
| **Rear** › **Loading** | Always **Sealed** in a fourth-order box. |
| **Rear volume** | The sealed air behind the cone. |
| **Results** | The front port’s **Cross-sectional area** and **Port volume**. On the rear tab, the **Gross volume** once **Box volume adjustments** add to it. |
With a driver chosen, the **Add enclosure** dialog fills in a starting point for **Bandpass 4**: a sealed rear chamber sized as a sealed box for that driver would be, and a front chamber tuned to the resonance that rear chamber gives the driver. For the example’s B&C 18SW115 that is 32.7 L sealed and 26.3 L in front tuned to 80.1 Hz, which covers 49.3–137 Hz at 100 W. The example trades that for a bigger box and a lower band.
## The front chamber sets the band
The front tuning places the band. Tune it lower and the whole band moves down with it, a little quieter.
_Figure: The bandpass example's SPL with its front chamber tuned to 50 Hz, 59 Hz, 68 Hz: the passband moves with the tuning._
B&C 18SW115 in the bandpass example (70 L sealed rear, 50 L front), at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Band | Peak |
| --- | --- | --- |
| Front tuned to 50 Hz | 31.8–80.7 Hz | 110.3 dB |
| Front tuned to 59 Hz | 38.9–92.2 Hz | 112.7 dB |
| Front tuned to 68 Hz | 46.5–103 Hz | 115.0 dB |
The front volume sets how wide the band is, and width costs level. Shrinking the front chamber from 80 L to 30 L widens the band from 1.0 to 1.7 octaves, and its loudest octave falls from 114.0 dB to 108.8 dB.
_Figure: The bandpass example's SPL with a 30 L, 50 L, 80 L front chamber, all tuned to 59 Hz: the smaller the chamber, the wider and quieter the band._
B&C 18SW115 in the bandpass example (70 L sealed rear, 50 L front), at 100 W, half space, 1 m. Simulated when this page was built. Level is the loudest one-octave average.
| Design | Band | Level |
| --- | --- | --- |
| 30 L front | 33.2–111 Hz | 108.8 dB |
| 50 L front | 38.9–92.2 Hz | 111.9 dB |
| 80 L front | 42.2–83.9 Hz | 114.0 dB |
## The rear chamber holds the cone
The sealed rear chamber hardly moves the band: from 40 L to 120 L its lower edge moves by only 1.1 Hz. It sets how the bass under the band falls, and how far the cone travels there. A bigger chamber is a softer spring: the output reaches −10 dB lower, at 25.2 Hz instead of 30.3 Hz, and the cone moves further for it.
_Figure: Cone excursion of the bandpass example with a 40 L, 70 L, 120 L sealed rear chamber, against the driver's 14.0 mm Xmax._
B&C 18SW115 in the bandpass example (70 L sealed rear, 50 L front), at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Band | −10 dB at | Cone |
| --- | --- | --- | --- |
| 40 L rear | 39.9–90.8 Hz | 30.3 Hz | 3.3 mm |
| 70 L rear | 38.9–92.2 Hz | 27.2 Hz | 4.6 mm |
| 120 L rear | 39–92.5 Hz | 25.2 Hz | 6.1 mm |
## What to check
- **Port Velocity**: the front port carries all the output. At 100 W the example’s port peaks at 11.2 m/s near 48.7 Hz, under the 17 m/s warning line. Air speed grows with the square root of power, and a narrower port speeds it up.
- **Excursion**: below the band the rear chamber keeps holding the cone, so its travel levels off instead of climbing. The example’s cone peaks at 4.6 mm at 10 Hz, 33% of the driver’s 14.0 mm Xmax.
- **Port length**: the front port has to fit inside the front chamber. The example’s is 21.3 cm long; a lower tuning or a wider port makes it longer.
- [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity): The front port’s air speed against the warning line.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): The cone’s travel against Xmax.
## When to use it
### Good for
- Loud bass over about an octave, from a driver hidden inside the box. The example covers 38.9–92.2 Hz.
- A cone held in check below the band: the sealed rear chamber works as a sealed box’s air spring.
- Rolling off the top of the band in the box itself.
### Watch for
- Size for the band you get: the example is 120 L of chambers for 1.2 octaves.
- Bandwidth costs level: a smaller front chamber widens the band and makes it quieter.
- One port carries everything, so check its air speed at the power you will use.
- To set the bottom of the band with a tuning of its own, port the rear chamber too: [Bandpass 6](https://simulator.00aud.io/docs/boxes/bandpass-6).
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The bandpass example at 100 W in the simulator’s own tiles: the front tuning, then the front volume.
To keep going, open the example in the simulator. It opens as a fourth-order bandpass with its tiles set up.
- [Open the bandpass example](https://simulator.00aud.io/app?template=bandpass&power=100): 70 L sealed rear and 50 L front at 59 Hz, 100 W.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, for each fourth-order bandpass box in my open workspace, try the front chamber tuned 10 Hz lower and 10 Hz higher, and a front chamber a third smaller, without saving. Tell me the −3 dB band, the peak level and the front port’s peak air speed for each option at its saved power.
---
# Bandpass 6
> How a sixth-order bandpass box works in 00 Simulator: two ported chambers, two tunings, and what porting the rear chamber adds and costs.
Source: https://simulator.00aud.io/docs/boxes/bandpass-6
A sixth-order bandpass ports both chambers, and either port can be a passive radiator instead. The driver sits between them, each chamber has its own port and tuning, and both ports reach the room. This page shows what the second port adds, what each tuning does and which limits it brings, on the bandpass example with its rear chamber ported.
_Figure: A sixth-order bandpass drawn by the simulator’s schematic: the driver between two chambers, each with a port to the room._
The design this page uses, as the **Schematic** tile draws it: the bandpass example’s 70 L rear chamber tuned to 30 Hz through a 10 cm port, and its 50 L front chamber tuned to 70 Hz.
The driver sits between a rear chamber vented through a port and a front chamber that radiates through a port. Only the chamber outlets reach the room.
## How it works
Each chamber and the air in its port is a resonator. The rear one, tuned low, holds up the bottom of the band, as a vented box’s port does. The front one, tuned higher, holds up the top and rolls off above it. Both ports radiate, and the room hears their sum.
- **Passband (−3 dB):** 41.9–98 Hz
- **Loudest:** 115.4 dB at 66.5 Hz, from 100 W
- **Rear chamber:** 70 L, tuned to 30 Hz: one 10 cm port, 31.2 cm long
- **Front chamber:** 50 L, tuned to 70 Hz: one 15 cm port, 12.5 cm long
> **Keep the two tunings apart** The cone pushes the air in one chamber as it pulls the air in the other. Two identical chambers would make equal and opposite outputs that cancel, and the box would be silent.
## What porting the rear adds
Seal the rear chamber of this box and it is a fourth-order bandpass with the same chambers and front tuning. Porting the rear lowers the bottom of the band from 48.2 Hz to 41.9 Hz.
_Figure: The same 70 L and 50 L chambers, front tuned to 70 Hz, with the rear chamber sealed and with it ported: the ported rear lowers the bottom of the band._
B&C 18SW115 in 70 L rear and 50 L front chambers, at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Band |
| --- | --- |
| Rear sealed (Bandpass 4) | 48.2–105 Hz |
| Rear tuned to 30 Hz (Bandpass 6) | 41.9–98 Hz |
The cost is below the rear tuning. There, as in a vented box, the port no longer holds the cone back: at 100 W the cone reaches 12.5 mm at 10 Hz, against 4.6 mm with the rear sealed and the driver’s 14.0 mm Xmax.
_Figure: Cone excursion of the same two boxes against the driver's 14.0 mm Xmax: below the rear tuning the ported box's cone is no longer held._
B&C 18SW115 in 70 L rear and 50 L front chambers, at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Peak |
| --- | --- |
| Rear sealed (Bandpass 4) | 4.6 mm at 10 Hz |
| Rear tuned to 30 Hz (Bandpass 6) | 12.5 mm at 10 Hz |
## The two tunings
The front tuning moves the band, as in a fourth-order box, and a higher one is louder.
_Figure: The 6th-order box with its front chamber tuned to 55 Hz, 70 Hz, 85 Hz and its rear chamber at 30 Hz: the band follows the front tuning._
B&C 18SW115 in 70 L rear and 50 L front chambers, at 100 W, half space, 1 m. Simulated when this page was built.
| Design | Band | Peak |
| --- | --- | --- |
| Front tuned to 55 Hz | 34.4–70.7 Hz | 113.7 dB |
| Front tuned to 70 Hz | 41.9–98 Hz | 115.4 dB |
| Front tuned to 85 Hz | 54.5–118 Hz | 118.6 dB |
The rear tuning moves the band much less. It sets where the rear port stops holding the cone: tuned lower, the cone moves less at 20 Hz.
B&C 18SW115 in 70 L rear and 50 L front chambers, at 100 W, half space, 1 m. Simulated when this page was built. Front chamber tuned to 70 Hz.
| Rear tuning | Band (−3 dB) | Rear port, peak | Cone at 20 Hz |
| --- | --- | --- | --- |
| 25 Hz | 43.1–100 Hz | 19.6 m/s at 15.4 Hz | 3.3 mm |
| 30 Hz | 41.9–98 Hz | 19.8 m/s at 19.6 Hz | 5.7 mm |
| 40 Hz | 43.9–91.2 Hz | 21.0 m/s at 37.4 Hz | 7.1 mm |
## What you set
Choose **Bandpass 6** as the **Type** when you add an enclosure; the enclosure panel lists it as **6th-order BP**. Pick a chamber with the **Front** and **Rear** tabs beside **Chamber**. Both tabs now have the same controls:
| Control | What it sets |
| --- | --- |
| **Loading** | **Port**, or **Passive radiator** to load that chamber with a radiator instead of a port. |
| **Front volume** / **Rear volume** | The net air in the chamber. |
| **Tuning** | The chamber’s own tuning. |
| **Port length** | Its port’s length: change the tuning and the length follows, or type a length and the tuning follows. |
| **Port** | **Shape**, **Number of ports**, size and **Advanced** › **End correction**. The two ports share one end correction: change it on either tab and both follow. |
| **Results** | **Cross-sectional area** and **Port volume** for that chamber’s port, and its **1st front-port resonance** or **1st rear-port resonance**. |
- Switch between **4th-order BP** and **6th-order BP** and the front chamber stays as it is: only the rear chamber changes. The bandpass example switched to sixth order gets a rear port tuned to 40 Hz through a 7.6 cm port, the rear settings it already carried.
- A box with no front chamber yet gets one at half its volume, tuned 1.4 times higher, so the two chambers never start out identical: the vented example becomes 55 L tuned to 32 Hz behind the cone and 27.5 L tuned to 44.8 Hz in front.
- With a driver chosen, the **Add enclosure** dialog starts **Bandpass 6** from the driver itself: 1.5 times its Vas behind the cone, tuned to 0.9 × Fs, and half that volume in front, tuned to 1.4 × Fs. For the B&C 18SW115 that is 223.6 L and 111.8 L.
## What to check
- **Port Velocity (Rear Chamber)**: the rear port carries the deep bass. At 100 W it peaks at 19.8 m/s near 19.6 Hz, over the 17 m/s warning line. Two rear ports keep the tuning and bring it to 9.9 m/s, each 68.3 cm long.
- **Port Velocity**: the front port. It peaks at 12.3 m/s near 59 Hz.
- **Excursion** below the rear tuning, as for a vented box. A high-pass filter below 30 Hz keeps the cone from moving for output the box does not make. See [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters).
- Port resonances, under **Results**: the rear port’s first resonance is at 551 Hz and the front one’s at 1,373 Hz, far above the band. Longer ports resonate lower: with two rear ports it falls to 251 Hz.
- [Port Velocity (Rear Chamber)](https://simulator.00aud.io/docs/reference/tiles/rear-port-velocity): The rear port’s air speed against the warning line.
- [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity): The front port’s air speed.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): The cone’s travel against Xmax.
## When to use it
### Good for
- A lower bottom to the band from the same chambers: here 41.9 Hz instead of 48.2 Hz with the rear sealed.
- Setting each edge of the band with its own tuning.
- Loud bass with the driver hidden inside, from ports on both chambers.
### Watch for
- Two ports to size and fit. In this design the rear one is the first over the warning line.
- The cone is let go below the rear tuning: use a high-pass filter.
- Tunings too close together cancel.
- For a cone held by a sealed rear chamber instead, see [Bandpass 4](https://simulator.00aud.io/docs/boxes/bandpass-4).
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
This page’s design at 100 W in the simulator’s own tiles: the front tuning, then a second rear port.
There is no sixth-order example yet. Open the bandpass example and set **Type** to **6th-order BP**, then on the **Rear** tab set **Tuning** to 30 Hz and the port’s **Diameter** to 10 cm, and on the **Front** tab set **Tuning** to 70 Hz. That is this page’s design.
- [Open the bandpass example](https://simulator.00aud.io/app?template=bandpass&power=100): The fourth-order example at 100 W, to switch to sixth order.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, for each sixth-order bandpass box in my open workspace, check both ports' peak air speed at the saved power. For any port above 17 m/s, try a second port of the same size without saving, and tell me the new air speed, each port's length and whether the −3 dB band changed.
---
# Ports and end correction
> Every port control in 00 Simulator: tuning and port length, shape, size and count, end correction, the lumped and distributed port models and port resonance.
Source: https://simulator.00aud.io/docs/boxes/ports
A port is a tube or slot whose air resonates with the box at the tuning frequency. You choose its shape, size and count; 00 Simulator works out the length that gives your tuning, or the tuning a length gives. This page covers every port control, what end correction does, and when the port starts to resonate on its own.
## Where you find ports
| Enclosure | Ports |
| --- | --- |
| [Vented](https://simulator.00aud.io/docs/boxes/vented) | One chamber and its port. |
| [Bandpass 4](https://simulator.00aud.io/docs/boxes/bandpass-4) | The front chamber’s port. |
| [Bandpass 6](https://simulator.00aud.io/docs/boxes/bandpass-6) | A port on each chamber, each with its own tuning, on the **Front** and **Rear** tabs. |
| [Horns](https://simulator.00aud.io/docs/horns) | The rear chamber of a [front-loaded](https://simulator.00aud.io/docs/horns/front-loaded-horn), [offset-driver](https://simulator.00aud.io/docs/horns/offset-driver-horn) or [stubbed](https://simulator.00aud.io/docs/horns/stubbed-horn) horn, set to **Port** instead of **Sealed**. |
The controls are the same everywhere a port appears, apart from **Port model**, below. The examples on this page use the vented example.
## Tuning and port length
**Tuning** and **Port length** sit under the chamber’s volume, and both are always editable. Whichever you changed last is held, and the other is worked out from it:
- Change **Tuning** (the usual way) and the length follows. A different port size or count, chamber volume or end correction then changes the length, never the tuning. The example’s 10 cm port is 35.6 cm long for 32 Hz.
- Type a **Port length** and it is held instead: the tuning follows, and changing the port’s size moves the tuning. Cut the example’s port to 30 cm and the box tunes to 34.4 Hz.
The length comes from the port’s effective length: the length of air that resonates with the chamber at the tuning, less the end corrections.
```
effective length = port area × c² / ((2π × tuning)² × volume)
port length = effective length − (inside + outside) × r
c = 343 m/s; port area is all the ports together; r is one port’s radius
```
> **When the length comes out negative** A small port area with a high tuning can need less length than the end corrections already give. A warning then shows beside **Port length**, and the **Port** section opens with “Port volume is 0 L.” Use a wider port, more ports or a lower tuning.
## Size, count and shape
Every port below tunes the 55 L example to 32 Hz, so the SPL is the same for all of them. What changes is how long the port is, how much of the box it takes and how fast its air moves at 200 W.
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port | Length | Port volume | Peak air speed | 1st port resonance |
| --- | --- | --- | --- | --- |
| One 7.5 cm | 18.9 cm | 0.8 L | 50.5 m/s | 909 Hz |
| One 10 cm (the example) | 35.6 cm | 2.8 L | 28.4 m/s | 482 Hz |
| One 12.5 cm | 57.4 cm | 7 L | 18.2 m/s | 299 Hz |
| Two 10 cm | 77.1 cm | 12.1 L | 14.2 m/s | 222 Hz |
| One 20 cm × 3.9 cm slot | 35.6 cm | 2.8 L | 28.4 m/s | 482 Hz |
- More port area means slower air and a longer port. Two 10 cm ports take the example from 28.4 m/s to 14.2 m/s, and each is 77.1 cm long; a 7.5 cm port is short but far over the 17 m/s warning line, at 50.5 m/s.
- The port’s air is not part of **Volume**, the net air the driver works against. It shows as **Port volume** under **Results** and adds to the **Gross volume**, the box you build: 67.1 L with the two ports against 57.8 L with one.
- **Shape** has three buttons: a circle for a round port (**Diameter**), a square for a slot (**Width** and **Height**) and a dashed square for a custom **Cross-sectional area** per port. A slot’s end correction uses the radius of a round port with the same area, so the 20 cm × 3.9 cm slot is the same 35.6 cm long as the 10 cm round port.
- **Number of ports** runs from 1 to 10. **Diameter**, **Width** and **Height** take 1 to 100,000 mm, and **Tuning** 15 to 1,200 Hz.
## End correction
Air just beyond each end of a port moves with the air inside it, so the port acts longer than it is. End correction adds that length back: a factor for each end, times the port’s radius. The more correction, the shorter the port you build for the same tuning.
Set it under **Port** › **Advanced** › **End correction**. The menu offers WinISD’s presets, each shown with its average factor, or **Custom**, which opens **Inside** and **Outside** fields from 0 to 3. The default is 0.6 at both ends, as in WinISD.
The 10 cm port of the vented example, held at 32 Hz.
| Preset | Inside | Outside | Shown as | Example port length | 1st port resonance |
| --- | --- | --- | --- | --- | --- |
| WinISD default | 0.6 | 0.6 | 0.6 | 35.6 cm | 482 Hz |
| Two free ends | 0.614 | 0.614 | 0.614 | 35.4 cm | 484 Hz |
| One flanged end | 0.85 | 0.614 | 0.732 | 34.2 cm | 501 Hz |
| Two flanged ends | 0.85 | 0.85 | 0.85 | 33.1 cm | 519 Hz |
Because the tuning is held, the response does not move: only the length does, from 35.6 cm to 33.1 cm. A bandpass box’s two ports share one end correction: change it on either tab and both follow.
## Port model and port resonance
A port is also a pipe, open at both ends, with its own resonance where its length is half a wavelength. **Results** shows it as **1st port resonance**, worked out from the physical length: 482 Hz for the example’s 35.6 cm port. If it sits too low the port lets through sound above the bass and colours the response, so keep it well above where the box plays.
**Port model**, under **Advanced** on a vented box or a horn’s ported rear chamber, decides how the solver treats the port. **Lumped**, the default, moves the port’s air as one mass, so the resonance is only a number in **Results**. **Distributed** treats the port as a duct that sound travels along, so the resonance shows in the graphs, and adds a **Distributed duct resonance** row worked out from the length with its end corrections.
_Figure: The vented example with two 10 cm ports, each 77.1 cm long, with the lumped and the distributed port model. The distributed curve shows the ports' own resonance near 206 Hz._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Design | Resonance |
| --- | --- |
| Lumped | 222 Hz (1st port resonance) |
| Distributed | 206 Hz (distributed duct resonance) |
With two 10 cm ports, each 77.1 cm long, the distributed model puts a peak of 10.2 dB over the lumped curve at 210 Hz and a dip of 8.4 dB just above, at 215 Hz, where real ports this long resonate too.
- **Duct loss**, in Np/m, damps the duct. It starts at 0.02 and goes up to 2. At the maximum the ports barely work: the two-port example’s F3 rises from 30.2 Hz to 75.5 Hz.
- Bandpass ports have no **Port model** control.
## Air speed
Fast air chuffs and whistles. The **Port Velocity** tile draws the peak air speed in the port against a warning line, 17 m/s by default; a sixth-order bandpass has a second tile for its rear port. At 200 W the example’s one port peaks at 28.4 m/s.
- [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity): How to read the tile and what moves it.
- [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port): Get under the line, and what each fix costs.
- [Bass-reflex port calculator](https://simulator.00aud.io/calculators/bass-reflex-port): Port length for a tuning, outside the simulator.
## Try it
[Open the vented example](https://simulator.00aud.io/app?template=vented&power=200) at 200 W, open **Port** in the enclosure panel and change **Number of ports** to 2: the **Port length** grows from 35.6 cm to 77.1 cm, and the peak on the **Port Velocity** tile falls from 28.4 m/s to 14.2 m/s.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, for each vented box in my open workspace, try one, two and three ports of the current diameter without saving. Tell me each option's port length, port volume, first port resonance and peak air speed at the saved power.
---
# Several drivers and wiring
> Several identical drivers in one 00 Simulator enclosure: what the box, the power and the load share, how wiring changes the impedance, and dual voice coils.
Source: https://simulator.00aud.io/docs/boxes/multiple-drivers
One enclosure can hold several identical drivers. Set **Number of drivers** and they share the box’s air and its power; set **Wiring** and only the load the amplifier sees changes. This page shows both on the sealed example, and how dual voice coils work.
## Number of drivers
**Number of drivers** sits under **Driver** in the enclosure panel and takes 1 to 50. Every driver is the model you chose, all in the same box. The **Input power** under **Power** is the total: 00 Simulator gives each driver an equal share, and adds up what their cones move.
_Figure: The sealed example with one Dayton Audio DCS205-4, with two in the same 15 L and with two in 30 L, all at 50 W in total._
Dayton Audio DCS205-4, sealed, 50 W in total, half space, 1 m. Simulated when this page was built. Level is the loudest one-octave average.
| Design | F3 | Level |
| --- | --- | --- |
| One driver, 15 L | 62.2 Hz | 102.4 dB |
| Two drivers, 15 L | 65.2 Hz | 105.5 dB |
| Two drivers, 30 L | 60.8 Hz | 105.2 dB |
Dayton Audio DCS205-4, sealed, half space, 1 m, wired in parallel. Simulated when this page was built.
| Design | Power | F3 | Level | Each cone at 20 Hz |
| --- | --- | --- | --- | --- |
| One driver, 15 L | 50 W | 62.2 Hz | 102.4 dB | 7.0 mm |
| Two drivers, 15 L | 50 W | 65.2 Hz | 105.5 dB | 3.2 mm |
| Two drivers, 30 L | 50 W | 60.8 Hz | 105.2 dB | 4.9 mm |
| Two drivers, 30 L | 100 W | 60.8 Hz | 108.2 dB | 6.9 mm |
- Double the drivers and the box together and the shape stays: F3 moves from 62.2 Hz to 60.8 Hz. At the same 50 W the pair is 2.8 dB louder while each cone moves 0.70 times as far, because each gets half the power.
- Give the pair twice the power too and it is 5.8 dB louder, with each cone moving as far as the one did.
- Two drivers in the same 15 L share its air, so each sees half the box: the level rises 3.1 dB, but the deep bass gains less and F3 rises to 65.2 Hz.
- Limits are per driver: the **Excursion** tile shows one cone’s travel against its Xmax.
- In a sealed box the **system resonance** and **system Q** fields count every driver. **Driver displacement**, under **Box volume adjustments**, is one figure for the box: enter all the drivers’ displacement together.
## Wiring
**Wiring** appears once there are two or more drivers. It lists the balanced ways to wire the count you set: S is drivers in series, P is parallel strings, so 2S2P is two series pairs wired in parallel. Each option shows the nominal load the amplifier sees. For four of the example’s drivers:
| Wiring | Strings | Drivers per string | Shown as |
| --- | --- | --- | --- |
| 4P | 4 | 1 | 1.00 Ω |
| 2S2P | 2 | 2 | 4.00 Ω |
| 4S | 1 | 4 | 16.0 Ω |
The acoustic output is the same for every option: 00 Simulator drives each driver from its share of **Input power**, so the wiring only changes the voltage and current the amplifier supplies. **Load voltage** under **Power** shows the voltage: 9.9 V for two drivers in parallel at 50 W, 19.7 V in series.
_Figure: The impedance the amplifier sees from two Dayton Audio DCS205-4 drivers in 30 L, wired in parallel (2P) and in series (2S)._
Dayton Audio DCS205-4, sealed, 50 W in total, half space, 1 m. Simulated when this page was built.
| Design | Lowest | Load voltage |
| --- | --- | --- |
| 2P | 2.1 Ω | 9.9 V |
| 2S | 8.0 Ω | 19.7 V |
> **Series resistance is the exception** **Series resistance**, the cable and amplifier’s own resistance, sits at the amplifier’s terminals, so it takes a bigger share of a lower load. At the default 0.1 Ω the parallel pair above is 0.3 dB quieter than the series pair, and its F3 is 60.8 Hz against 63 Hz.
Changing **Number of drivers** to a count the current wiring does not divide sets the wiring back to all in parallel. The **Impedance** and **Amplifier Load (VA)** tiles show what the amplifier sees across the band.
## Dual voice coils
**Voice coil wiring** appears when the driver has two voice coils: **Series** or **Parallel**, each shown with its resistance. The simulation treats a dual-coil driver’s stored Re, Le and Bl as values for the coils in series. **Parallel** divides the resistance and the inductance by 4 and the force factor by 2, so the load is a quarter and the output at the same power is the same, again apart from series resistance.
Dayton Audio UM10-22 in the 60.8 L sealed box the **Add enclosure** dialog starts it in, at 50 W, half space, 1 m. Simulated when this page was built.
| Voice coil wiring | Shown as | Lowest impedance | Level |
| --- | --- | --- | --- |
| **Series** | 3.70 Ω | 3.8 Ω | 97.4 dB |
| **Parallel** | 0.93 Ω | 1.0 Ω | 97.0 dB |
With several dual-coil drivers the two settings multiply: the coil wiring sets each driver’s load, and **Wiring** combines the drivers.
## Different drivers
A box holds one model of driver. A multiple-entry horn is the exception: each of its drivers can use a different model, with its own count, wiring, power and EQ. To compare different drivers in boxes, give each its own enclosure in the workspace. Passive radiators have their own count, **Number of PRs**, also up to 50.
- [Multiple-entry (MEH)](https://simulator.00aud.io/docs/horns/multiple-entry-horn): Several drivers on one horn path.
- [Compare designs](https://simulator.00aud.io/docs/guides/compare): Several enclosures on the same tiles.
- [Power and limits](https://simulator.00aud.io/docs/guides/power-and-limits): Input power, series resistance and the limits it runs into.
## Try it
[Open the sealed example](https://simulator.00aud.io/app?template=sealed&power=50) at 50 W, set **Number of drivers** to 2 and **Volume** to 30 L, then switch **Wiring** between 2P and 2S and watch the **Impedance** tile.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, take the sealed box in my open workspace and, without saving, try two of its driver in twice the volume, wired in parallel and in series. For each option tell me the F3, the level at 100 Hz, each cone’s peak excursion and the lowest impedance at the saved power.
---
# Losses and damping
> The losses 00 Simulator assumes in every box: leakage, absorption and port loss, where each applies, and how much they change a design.
Source: https://simulator.00aud.io/docs/boxes/losses
Every real box loses a little energy: air leaks through joints, the air inside is damped, and the air in the port rubs on its walls. 00 Simulator models these as three fixed losses, the same in every box, with no setting to change them. This page says what they are, where they apply and how much they matter.
## The three losses
Each loss is a Q value: the higher the Q, the smaller the loss. Leakage and absorption are set against the chamber’s own tuning, so the same Q damps a small box as much as a big one.
| Loss | Q | Where | What it stands for |
| --- | --- | --- | --- |
| Leakage, Ql | 10 | Every chamber: sealed, vented, passive radiator and both bandpass chambers | Air escaping through joints, gaskets and the driver. It is set against the chamber’s tuning; in a sealed box, against its resonance with the driver. |
| Absorption, Qa | 100 | Chambers with a port | Damping of the air inside the chamber as it is squeezed and let go. |
| Port loss, Qp | 100 | Ports with the **Lumped** port model | Friction in the port. A port with the **Distributed** model uses its **Duct loss** instead: see [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports#port-model). |
- There is no control for them in the enclosure panel, and the 00 Simulator connector cannot change them for boxes either.
- Air that leaks from a sealed or vented box is added to what the box radiates. A passive radiator box leaves it out.
- Boxes have no stuffing or lining setting: damping material in a box is not modelled beyond these fixed losses.
## How much they matter
Leakage matters most, and most near the tuning, where the port does the work. To show it, the figures run the vented example through the same solver with a leakier and a tighter box. You cannot set these in the app; they show how far a real box could sit from the model.
_Figure: The vented example's SPL with a leakage Q of 5, 10 and 20: the leakier the box, the less output near the 32 Hz tuning._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 100 W, half space, 1 m. Only the leakage Q differs; the app always uses Ql 10. Simulated when this page was built.
| Design | F3 | At 32 Hz |
| --- | --- | --- |
| Ql 5, leakier | 33.5 Hz | 104.2 dB |
| Ql 10, as the app models it | 30.3 Hz | 106.1 dB |
| Ql 20, tighter | 29.4 Hz | 107.3 dB |
From Ql 5 to Ql 20 the level at 32 Hz rises from 104.2 dB to 107.3 dB, and F3 falls from 33.5 Hz to 29.4 Hz. The air in the port speeds up with it: 16.2 to 22.8 m/s at 100 W. With next to no losses at all (every Q at 1,000) the example would play 3.0 dB louder at the tuning; the leakage alone accounts for 2.5 dB of that.
_Figure: The vented example's impedance with a leakage Q of 5, 10 and 20: the leakier the box, the lower its two peaks._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 100 W, half space, 1 m. Only the leakage Q differs; the app always uses Ql 10. Simulated when this page was built.
| Design | Peaks | Dip |
| --- | --- | --- |
| Ql 5, leakier | 20.3 Ω and 18.2 Ω | 5.6 Ω at 31.6 Hz |
| Ql 10, as the app models it | 22.8 Ω and 21.0 Ω | 4.6 Ω at 31.6 Hz |
| Ql 20, tighter | 24.4 Ω and 22.8 Ω | 4.1 Ω at 31.6 Hz |
Impedance shows losses most clearly. A vented box has two peaks either side of the tuning and a dip between them; the leakier the box, the lower the peaks and the shallower the dip. The example’s peaks are 22.8 Ω and 21.0 Ω.
A sealed box feels its leak too. Without it, the sealed example’s F3 at 50 W would fall from 62.2 Hz to 59.7 Hz, and its impedance peak would rise from 40.4 Ω to 63.7 Ω.
## Check it against your box
Measure the impedance of the box you built and import it as a measured trace: it draws over the **Impedance** tile beside the simulation. Peaks taller than the simulated ones point to a tighter box than Ql 10, lower ones to a leakier box or more damping. Expect the response near the tuning to differ the same way.
- [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements): Import a measurement and compare it with a design.
- [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance): How to read the Impedance tile.
## Horns and the air
- Horns work differently: their paths can be stuffed segment by segment. See [Stuffing](https://simulator.00aud.io/docs/horns/stuffing).
- The air in every design is at 20 °C: sound travels at 343 m/s and its density is 1.201 kg/m³.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, compare the measured impedance trace in my open workspace with the enclosure it belongs to, and tell me where the measured peaks and the dip between them differ from the simulation.
---
# Horn loudspeakers in 00 Simulator
> How 00 Simulator models horns: the eight horn types, how a horn path is described, and the route from Horn Editor to stuffing, folding and Hornresp.
Source: https://simulator.00aud.io/docs/horns
00 Simulator models eight horn types with the same solver as its boxes, so a horn can sit next to a sealed or vented design in one workspace. This section explains how each type is connected, how to shape a horn path, and how to check it before you build.
## How a horn is described
A horn is one or more _paths_. Each path is a chain of _spans_, and each span runs between two _stations_: it has a length, an area at each end and a flare. Neighbouring spans share a station, so the path stays continuous while you edit it. The **Horn Editor** names spans H1, H2 and onward from the start of the path.
Positions along a path, such as where a driver enters or a stub joins, are markers you drag or type in centimetres from the start of the path. The design keeps each one as a fraction of the path’s length. Chambers sit between the diaphragm and the path, and every open end radiates: a mouth, a port or the cone itself.
- **Flares:** Conical, Exponential, Parabolic, chosen per span
- **Spans per path:** 1 to 8
- **Span length:** 2 cm to 6 m
- **Station area:** 5 cm² to 2 m²
- **Model:** One-dimensional waves in each span, coupled to the driver’s Thiele/Small model
- **Not modelled:** Bend losses, directivity and thermal power compression
## The eight horn types
Every type differs in where the two faces of the diaphragm meet the path. The schematics are drawn by the simulator from the designs on each type’s page.
_Figure: The eight horn types, each with the schematic of the design its page draws._
- [Front-loaded horn](https://simulator.00aud.io/docs/horns/front-loaded-horn): A driver at the throat feeds one horn.
- [Back-loaded horn](https://simulator.00aud.io/docs/horns/back-loaded-horn): The rear diaphragm face feeds the horn, while the front radiates directly.
- [Tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn): Both diaphragm faces enter one horn at separate positions.
- [Offset-driver horn](https://simulator.00aud.io/docs/horns/offset-driver-horn): One diaphragm face enters partway along the horn.
- [Stubbed horn](https://simulator.00aud.io/docs/horns/stubbed-horn): A closed side branch joins the main horn.
- [Compound horn](https://simulator.00aud.io/docs/horns/compound-horn): Each diaphragm face feeds its own horn path.
- [Multiple-entry horn (MEH)](https://simulator.00aud.io/docs/horns/multiple-entry-horn): Independently amplified drivers enter a shared horn.
- [Paraflex horn](https://simulator.00aud.io/docs/horns/paraflex-horn): Two resonator paths couple the diaphragm faces and reconnect before one shared mouth.
## Which type should I start with?
| Type | Good for | Folds into a cabinet | Hornresp record |
| --- | --- | --- | --- |
| [Front-loaded horn](https://simulator.00aud.io/docs/horns/front-loaded-horn) | Midbass and upper-bass horns where efficiency and output matter more than size. | Yes | Nd |
| [Back-loaded horn](https://simulator.00aud.io/docs/horns/back-loaded-horn) | Full-range and wide-band drivers that need help in the bass. | Yes | Nd |
| [Tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn) | High-output subwoofers in a compact, foldable cabinet. | Yes | TH or TH1 |
| [Offset-driver horn](https://simulator.00aud.io/docs/horns/offset-driver-horn) | Front-loaded designs whose first upper peak needs taming without stuffing. | Yes | OD, OD1 or OD2 |
| [Stubbed horn](https://simulator.00aud.io/docs/horns/stubbed-horn) | Front-loaded horns with a single troublesome peak that the stub can be tuned against. | Not yet | SH |
| [Compound horn](https://simulator.00aud.io/docs/horns/compound-horn) | Getting horn loading on both sides of the cone. | Not yet | CH, CH1, CH2 or CH3 |
| [Multiple-entry horn (MEH)](https://simulator.00aud.io/docs/horns/multiple-entry-horn) | Wide-band horns where one driver cannot cover the whole range. | Not yet | Throat record plus ME1 and ME2 |
| [Paraflex horn](https://simulator.00aud.io/docs/horns/paraflex-horn) | Deep bass designs where you want to try four connection layouts on the same spans. | Not yet | PH1 to PH4 |
If you are new to horns, open the [tapped horn example](https://simulator.00aud.io/app?template=tapped-horn) and follow the [tapped horn cookbook](https://simulator.00aud.io/docs/cookbook/tapped-horn). It walks through power, excursion and a high-pass filter on a real design.
## From idea to cabinet
1. **Pick a type.** Start from an example, or add an enclosure, set its type to **Horn** and choose a **Horn type**. Each type’s page says what it is good for. [The horn types](#types).
2. **Shape the path.** Drag spans, stations and entry markers in the **Horn Editor** tile, or switch it to its **Table** to type exact values. The graphs follow as you edit. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
3. **Look inside.** Particle velocity, pressure and acoustic impedance at any station, and each mouth or direct radiator as its own output. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
4. **Damp it.** Fill part of any span with fibre of a measured airflow resistivity, and watch what it does to the peaks above the band. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
5. **Fold it.** Pack the path into a cabinet you can build, see the folded horn on every graph, and get a cut list. [Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding).
6. **Cross-check it.** Export horns that fit Hornresp’s layouts as native records, and compare the two simulators on the same design. [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp).
The horn model is regression-tested against 122 native Hornresp cases across 8 horn families. 109 of 109 agreement checks meet their tolerances. These compare two simulators, not built cabinets.
## Work on horns with your AI
[Connect 00 Simulator](https://simulator.00aud.io/docs/ai/connect) to Claude, ChatGPT or another MCP client and your assistant can read, edit and simulate every horn type in your workspaces, try changes without saving them, and fold a horn into a cabinet. The numbers it quotes come from the same solver as the graphs.
_Figure: A scripted assistant session: the prompt, the 00 Simulator tools it calls, its reply and the simulated SPL of the tapped horn example with and without stuffing._
The conversation above is illustrative. The tool names are the server’s own, and the curve and numbers are solver output from when this page was built.
You: Using 00 Simulator, try filling the first half of H1 in my tapped horn with 10,000 Pa·s/m² fibre and tell me what it changes. Don’t save it.
The assistant calls `get_workspace` (Tapped Horn · B&C 21SW152), `get_enclosure_schema` (horn stuffing fields), `simulate_workspace` (empty and stuffed · 100 W · not saved), `render_simulation_graphs` (SPL).
Assistant: Filling H1 50 % from the closed end at 10,000 Pa·s/m² changes the response by at most 1.0 dB between 25 and 120 Hz, so the working band barely moves. Above 200 Hz it does more: the highest peak goes from 119 dB at 243 Hz to 116 dB at 301 Hz. I haven’t saved it.
| Result | Value |
| --- | --- |
| Largest change, 25–120 Hz | 1.0 dB |
| Top peak above 200 Hz, empty | 119 dB |
| Top peak above 200 Hz, stuffed | 116 dB |
| Fill | H1 · 50 % |
**Ask your AI**
With 00 Simulator connected, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, look at the horns in my open workspace. For each one, tell me its type, its −3 dB band and peak excursion at the power it is set to, and the one change you would try first.
---
# Front-loaded horn
> How to model a front-loaded horn in 00 Simulator: throat and rear chambers, a sealed or ported rear chamber, the Horn Editor, diagnostics, folding and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/front-loaded-horn
The driver sits at the throat and its front face drives the horn. Its rear face loads a rear chamber, which you can leave sealed or port like a bass-reflex box. This is the classic horn: high efficiency over the band the horn loads, in return for size.
_Figure: The front-loaded horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default horn path the simulator starts a new horn with, with a B&C 10PS26. Rear chamber volume: 15 L. Drawn by the simulator when this page was built.
## How it connects
The front of the cone feeds the throat, usually through a small throat chamber. The throat chamber and the throat act as an acoustic low-pass filter, so they set how the top of the band rolls off.
The back of the cone faces the rear chamber. Like a sealed box, the rear chamber adds stiffness, which shapes how the driver is loaded at the bottom of the band.
Choose **Port** for the rear chamber and it becomes a vented chamber: the port radiates beside the mouth and adds output around its tuning.
## When to use it
### Good for
- Midbass and upper-bass horns where efficiency and output matter more than size.
- Comparing a horn against a vented or sealed box for the same driver in one workspace.
### Watch for
- The horn only loads the driver where the mouth is big enough and the path is long enough. Below that band, output falls quickly.
- A small rear chamber lifts the upper bass but costs the lowest octave. Check the **SPL** and **Excursion** graphs together when you change it.
- With a ported rear chamber, check the **Port Velocity** graph and the port resonance readouts, as you would for a vented box.
## What you set
Set the enclosure type to **Horn**, then choose **Front-loaded** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume** only. 0 L connects the driver directly to the horn. |
| **Rear chamber** | **Loading**: **Sealed** or **Port**, and **Volume**. At 0 L the chamber adds no stiffness. Choosing **Port** on an empty chamber starts from 50 L with one round 100 mm port tuned to 40 Hz. |
| **Port** (**Port** loading only) | **Tuning**, **Port length**, **Shape**, **Number of ports** and the port size, as for a vented box. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the throat, then up to eight spans, each with a **Flare**, a **Length** and the **Area** where it ends. |
The driver marker is fixed at the throat. Drag the arrows and the dividers between spans to reshape the path, or click a value to type it. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the rear chamber volume does
Only the rear chamber changes between the lines. The smallest chamber gives the steepest low-frequency roll-off and a flatter upper bass; the largest keeps the most output below about 60 Hz. Above about 200 Hz the three lines are nearly the same, because the rear chamber hardly matters there.
_Figure: Simulated SPL of the front-loaded horn for 3 values of rear chamber volume: 5 L, 15 L, 40 L._
The default horn path the simulator starts a new horn with. Only the rear chamber volume changes between the lines. Simulated when this page was built.
Rear chamber volume, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Rear chamber volume | −3 dB |
| --- | --- |
| 5 L | 90 Hz |
| 15 L (the design drawn above) | 99 Hz |
| 40 L | 100 Hz |
## Diagnostics and stuffing
Locations run along the Main path, named by span and end, such as Main H1 throat. **Horn Radiating Outputs** shows the Main mouth, plus the Rear port when the rear chamber is ported. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Any span of the main horn can be stuffed. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Available. The **Fold** tile opens the throat into the dead space behind the throat cap. Its **Chamber** chip compares the throat and rear chambers the fold leaves with your targets, and a rear port’s tube volume comes out of the rear chamber.
- **Hornresp export · Nd:** Up to four spans export as a native record. A ported rear chamber is written as Hornresp’s Rear Vented chamber, a mapping that has not yet been checked against a native Hornresp capture. With no rear chamber, the export warns that Hornresp adds an exposed rear radiator.
- **Checked against Hornresp:** 26 native Hornresp cases of this type are re-simulated in the regression tests. 20 of 20 agreement checks meet their tolerances, and 6 more track stuffing-model differences without claiming agreement.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Front-loaded** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add a front-loaded horn to my open workspace for the driver I am using now. Compare a 15 L sealed rear chamber with a ported one tuned to 45 Hz, simulate both at 50 W, and show me SPL and excursion.
---
# Back-loaded horn
> How to model a back-loaded horn in 00 Simulator: the direct front radiation and the horn mouth, the throat chamber, the Horn Editor, diagnostics, folding and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/back-loaded-horn
The front of the cone radiates straight into the room while the back of the cone drives a horn. The horn adds bass below the point where the driver alone would fall away, and the two outputs add up at the listener.
_Figure: The back-loaded horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default horn path the simulator starts a new horn with, scaled in length, with a B&C 10PS26. Horn length: 1.2 m. Drawn by the simulator when this page was built.
## How it connects
The rear face of the diaphragm feeds the throat through a throat chamber. The horn’s mouth and the front of the cone are two separate outputs.
Because they are two outputs, they add with their phase. Where they arrive in step, the horn reinforces the bass; where they arrive out of step, they cancel.
## When to use it
### Good for
- Full-range and wide-band drivers that need help in the bass.
- Designs where the direct radiator carries the midrange and the horn only has to cover the bottom octaves.
### Watch for
- The two outputs can cancel just above the horn’s working band. Check **Horn Radiating Outputs**, not only the total SPL.
- There is no sealed rear chamber in this type: the throat chamber is the only chamber.
## What you set
Set the enclosure type to **Horn**, then choose **Back-loaded** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume**, and its **Cross-section** under **Advanced**. The cross-section sets the length of the coupling path: volume divided by cross-section. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the throat, then up to eight spans, each with a **Flare**, a **Length** and the **Area** where it ends. |
The rear-of-driver marker is fixed at the throat. Drag the arrows and the dividers between spans to reshape the path, or click a value to type it. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the horn length does
Only the horn length changes. The shortest horn adds little below 150 Hz, and each longer horn carries the output lower. Its peaks and dips start lower too, because the path’s resonances move down with its length.
_Figure: Simulated SPL of the back-loaded horn for 3 values of horn length: 0.6 m, 1.2 m, 1.8 m._
The default horn path the simulator starts a new horn with, scaled in length. Only the horn length changes between the lines. Simulated when this page was built.
Horn length, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Horn length | −3 dB |
| --- | --- |
| 0.6 m | 177 Hz |
| 1.2 m (the design drawn above) | 101 Hz |
| 1.8 m | 74 Hz |
## How the outputs add up
The dashed lines are the horn mouth and the front of the cone on their own. The solid line is what you hear: the horn dominates the low end and the direct radiator the top, and they interact where they overlap.
_Figure: Back-loaded horn, horn length 1.2 m: the total response and main mouth and direct radiator on their own._
The outputs are pressures, so they add with their phase: where the dashed lines are close in level and opposite in phase, the total drops below both.
Back-loaded horn, horn length 1.2 m. Solid: the total. Dashed: Main mouth and Direct radiator on their own.
## Diagnostics and stuffing
**Horn Radiating Outputs** shows the Main mouth and the Direct radiator separately, with their coherent total. When the throat chamber has both a volume and a cross-section, the coupling path shows as Main coupling. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Any span of the horn can be stuffed. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Available. The **Fold** tile mounts the driver on an outer wall facing out, opens the throat into the dead space and compares the throat chamber the fold leaves with your target.
- **Hornresp export · Nd:** Up to four spans export as a native record. Hornresp needs the two diaphragm faces at opposite polarities, and the export notes that absolute phase may be inverted and that you should use its combined acoustic output with Path = 0 cm.
- **Checked against Hornresp:** 13 native Hornresp cases of this type are re-simulated in the regression tests. 13 of 13 agreement checks meet their tolerances.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Back-loaded** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add a back-loaded horn to my open workspace for the driver I am using now, with a 1.5 m horn. Simulate it at 10 W, show me SPL, and use the radiating outputs in the results to tell me where the horn mouth and the direct radiator cancel.
---
# Tapped horn
> How to model a tapped horn subwoofer in 00 Simulator: front entry and rear tap positions, the throat chamber, the Horn Editor, diagnostics, folding and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/tapped-horn
Both faces of the diaphragm tap into the same horn at two points, and the horn has one mouth. Tapped horns give a lot of low bass from a cabinet that is small for the band it covers, which makes them a common subwoofer choice.
_Figure: The tapped horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The tapped horn example, with a B&C 21SW152. Front entry position: 14 % · 35 cm. Drawn by the simulator when this page was built.
## How it connects
The path starts at a closed end. The front of the cone enters at the front entry position and the back of the cone at the rear tap position, further along.
There is no box behind the cone: the path itself loads both faces, so its length and the two entry positions set where the output peaks and where it cancels.
## When to use it
### Good for
- High-output subwoofers in a compact, foldable cabinet.
- Drivers with a strong motor, a low Qts and plenty of excursion.
### Watch for
- Below the working band the horn stops loading the cone and excursion climbs. Use a high-pass filter and check excursion at the power you plan to use.
- Above the working band the response has deep notches and peaks. A subwoofer’s low-pass filter normally sits below them.
## What you set
Set the enclosure type to **Horn**, then choose **Tapped** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume**, and its **Cross-section** under **Advanced**, for a front coupling chamber. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the closed end, then up to eight spans, each with a **Flare**, a **Length** and the **Area** where it ends. |
| Driver marker | Where the front of the cone enters: the front entry position, in cm from the closed end toward the mouth. |
| Rear tap marker | The same, for the back of the cone. |
The driver and rear-tap markers can both be dragged along the path. The drawing starts at the closed end. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the front entry position does
Only the front entry moves. The working band barely changes, and the simulator reports the same −3 dB point for all three. What moves is the region above the band: with the entry furthest from the closed end, the first deep notch falls much closer to the top of the band.
_Figure: Simulated SPL of the tapped horn for 3 values of front entry position: 6 % · 15 cm, 14 % · 35 cm, 30 % · 75 cm._
The tapped horn example. Only the front entry position changes between the lines. Simulated when this page was built.
Front entry position, SPL: B&C 21SW152, Half Space · 1.0 m · 100 W.
| Front entry position | −3 dB |
| --- | --- |
| 6 % · 15 cm | 37 Hz |
| 14 % · 35 cm (the design drawn above) | 37 Hz |
| 30 % · 75 cm | 37 Hz |
## Diagnostics and stuffing
The one output is the Main mouth. Locations include the closed end, both entry points and the span ends. When the throat chamber has both a volume and a cross-section, it shows as Front coupling. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Any span of the horn can be stuffed, including the closed section before the front entry. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Available. The **Fold** tile keeps the closed end capped and leaves clearance for the cone near it. Its **Front tap** and **Rear tap** chips show where the driver lands on the folded path, and its **Hornresp** tab gives TH or TH1 values.
- **Hornresp export · TH or TH1:** The front tap must be at S2 and the rear tap at S3 or S4; otherwise the export stops with that reason. Taps at either end of the path are refused. The two faces need opposite polarities.
- **Checked against Hornresp:** 22 native Hornresp cases of this type are re-simulated in the regression tests. 19 of 19 agreement checks meet their tolerances, and 3 more track stuffing-model differences without claiming agreement.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
To keep going, open the example in the simulator. It opens with this type already set up, so you can change it and watch the graphs follow.
- [Open the tapped horn example](https://simulator.00aud.io/app?template=tapped-horn)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, open my tapped horn and try moving the front entry position to 10 %, 14 % and 25 %. Simulate each at 100 W without saving, then show me SPL and excursion and tell me which keeps the cleanest response above the band.
---
# Offset-driver horn
> How to model an offset-driver horn in 00 Simulator: the driver entry position, throat and rear chambers, a sealed or ported rear chamber, diagnostics, folding and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/offset-driver-horn
One face of the diaphragm enters the horn partway along, rather than at the throat. The section of path behind the entry is closed, and it works as a side branch that cancels a band of frequencies you choose.
_Figure: The offset-driver horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default horn path the simulator starts a new horn with, with a 15 L sealed rear chamber, with a B&C 10PS26. Driver entry position: 20 % · 24 cm. Drawn by the simulator when this page was built.
## How it connects
The path starts at a closed end. The front of the cone enters at the driver entry position; the back of the cone loads the rear chamber.
The closed section between the end and the entry puts a notch in the response. Designers use it to cancel an unwanted peak above the working band.
## When to use it
### Good for
- Front-loaded designs whose first upper peak needs taming without stuffing.
- Subwoofer horns that would otherwise have a strong resonance just above the band.
### Watch for
- The further the entry sits from the closed end, the lower the notch. Move it too far and the notch lands inside the working band.
- With the rear chamber at 0 L, the back of the cone radiates directly and shows as a Direct radiator output.
## What you set
Set the enclosure type to **Horn**, then choose **Offset-driver** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume**, and its **Cross-section** under **Advanced**. |
| **Rear chamber** | **Loading**: **Sealed** or **Port**, and **Volume**. At 0 L the back of the cone radiates directly. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the closed end, then up to eight spans, each with a **Flare**, a **Length** and the **Area** where it ends. |
| Driver marker | The driver entry position, in cm from the closed end. Switching to this type from a horn whose entry sits at the closed end moves it a fifth of the way along. |
The driver marker can be dragged along the path. The drawing starts at the closed end. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the driver entry position does
Only the driver entry moves. Near the closed end there is no notch below 500 Hz. Further along, a deep notch appears and moves down as the closed section grows, while the bottom of the band extends a little.
_Figure: Simulated SPL of the offset-driver horn for 3 values of driver entry position: 10 % · 12 cm, 20 % · 24 cm, 35 % · 42 cm._
The default horn path the simulator starts a new horn with, with a 15 L sealed rear chamber. Only the driver entry position changes between the lines. Simulated when this page was built.
Driver entry position, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Driver entry position | −3 dB |
| --- | --- |
| 10 % · 12 cm | 100 Hz |
| 20 % · 24 cm (the design drawn above) | 91 Hz |
| 35 % · 42 cm | 85 Hz |
## Diagnostics and stuffing
The one horn output is the Main mouth. The Rear port appears when the rear chamber is ported, and a Direct radiator when it is 0 L. Locations include the closed end and both sides of the entry point. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Any span of the horn can be stuffed, including the closed section behind the entry. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Available. The **Fold** tile keeps the closed end capped. Its **Driver entry** chip shows where the driver lands on the folded path, and its **Hornresp** tab gives OD, OD1 or OD2 values and the rear chamber volume.
- **Hornresp export · OD, OD1 or OD2:** The driver must enter at S2, S3 or S4. A ported rear chamber is written as Rear Vented, a mapping that has not yet been checked against a native Hornresp capture.
- **Checked against Hornresp:** 16 native Hornresp cases of this type are re-simulated in the regression tests. 13 of 13 agreement checks meet their tolerances, and 3 more track stuffing-model differences without claiming agreement.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Offset-driver** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add an offset-driver horn to my open workspace for the driver I am using now, with a 15 L sealed rear chamber. Try driver entry positions of 10 %, 20 % and 35 % without saving, simulate each at 50 W and show me where the notch lands.
---
# Stubbed horn
> How to model a stubbed horn in 00 Simulator: the stub junction position, the closed stub path, throat and rear chambers, diagnostics and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/stubbed-horn
A closed side branch, the stub, joins the main horn partway along. The stub cancels a band of frequencies set by its own length, which lets you notch out a resonance without moving the driver.
_Figure: The stubbed horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default horn path the simulator starts a new horn with, with a 15 L sealed rear chamber and the stub junction at 40 %, with a B&C 10PS26. Closed stub length: 0.45 m. Drawn by the simulator when this page was built.
## How it connects
The driver feeds the main horn at its throat, with the back of the cone in the rear chamber.
The stub is a second path that branches from the stub junction and ends closed. It has its own spans, so you set its length and taper like any other path.
## When to use it
### Good for
- Front-loaded horns with a single troublesome peak that the stub can be tuned against.
- Experiments with side-branch damping before committing to a cabinet.
### Watch for
- The stub length sets where the notch falls; the junction position changes how deep it is and how it interacts with the horn’s own peaks.
- With the rear chamber at 0 L the back of the cone radiates directly, as a Direct radiator output.
## What you set
Set the enclosure type to **Horn**, then choose **Stubbed** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume**, and its **Cross-section** under **Advanced**. |
| **Rear chamber** | **Loading**: **Sealed** or **Port**, and **Volume**. At 0 L the back of the cone radiates directly. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the throat, then up to eight spans. |
| Stub junction marker | Where the stub joins the main horn, in cm from the throat. |
| **Closed stub** | Under the **Stub** chip in the path bar: the area at the junction, then its spans. The table’s **End Ø** is the closed end’s. |
The driver marker is fixed at the throat and the stub junction marker can be dragged. Use the **Main** and **Stub** chips in the path bar to switch which path you are editing. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the closed stub length does
Only the stub length changes. Each stub puts its notch at a different frequency, lower for the longer stub, while the bass below the notch stays close to the same.
_Figure: Simulated SPL of the stubbed horn for 3 values of closed stub length: 0.3 m, 0.45 m, 0.6 m._
The default horn path the simulator starts a new horn with, with a 15 L sealed rear chamber and the stub junction at 40 %. Only the closed stub length changes between the lines. Simulated when this page was built.
Closed stub length, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Closed stub length | −3 dB |
| --- | --- |
| 0.3 m | 87 Hz |
| 0.45 m (the design drawn above) | 91 Hz |
| 0.6 m | 88 Hz |
## Diagnostics and stuffing
The one horn output is the Main mouth, with the Rear port when the rear chamber is ported and a Direct radiator when it is 0 L. The stub has its own locations, named Main stub. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
The main horn and the stub can both be stuffed. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Not yet. Folding handles one horn path, so the **Fold into cabinet** button is disabled for stubbed horns and the **Fold** tile says the type does not fold yet.
- **Hornresp export · SH:** Up to three main spans and one stub span export as a native record. A ported rear chamber is written as Rear Vented.
- **Checked against Hornresp:** 9 native Hornresp cases of this type are re-simulated in the regression tests. 9 of 9 agreement checks meet their tolerances.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Stubbed** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add a stubbed horn to my open workspace for the driver I am using now. Try closed stub lengths of 30, 45 and 60 cm without saving, simulate each at 50 W and tell me which one best cancels the largest peak above the band.
---
# Compound horn
> How to model a compound horn in 00 Simulator: separate front and rear horn paths, coupling chambers, rear tuning, diagnostics and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/compound-horn
Each face of the diaphragm drives its own horn, so the cabinet has two mouths. The rear horn can extend the bass while the front horn covers the upper band.
_Figure: The compound horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default front and rear horn paths, with a B&C 10PS26. Rear horn length: 1.5 m. Drawn by the simulator when this page was built.
## How it connects
The front of the cone feeds the front horn and the back of the cone feeds the rear horn, each through an optional coupling chamber.
The two mouths are separate outputs that add with their phase at the listener, like the horn and direct radiator of a back-loaded horn.
When the rear horn is short enough to act as a vent, the horn card shows its **Rear tuning**.
## When to use it
### Good for
- Getting horn loading on both sides of the cone.
- Designs where a short rear path should behave like a port.
### Watch for
- The two mouths can cancel where their outputs overlap. Check **Horn Radiating Outputs**.
- Switching a horn to compound moves both entries to the throat. If you switch back to tapped, set the rear tap again.
- The diagnostics graphs call the front path Main.
## What you set
Set the enclosure type to **Horn**, then choose **Compound** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Front coupling chamber** and **Rear coupling chamber** | **Volume** for each, and a **Front cross-section** and **Rear cross-section** under **Advanced**. |
| **Rear tuning** | A readout, shown only when the rear horn is short enough to act as a vent. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Front horn** | The area at the throat, then up to eight spans. |
| **Rear horn** | Under the **Rear** chip in the path bar, the same. A new rear horn is one 1.5 m exponential span. |
| Driver marker | On the front horn, where the front of the cone joins it; on the rear horn, where the back of the cone does. Each in cm from that horn’s throat. |
The driver marker can be dragged along either path. Use the **Front** and **Rear** chips in the path bar to switch which horn you are editing. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the rear horn length does
Only the rear horn length changes. Each longer rear horn carries the output lower, and the ripple through the band changes as the two mouths interact differently.
_Figure: Simulated SPL of the compound horn for 3 values of rear horn length: 0.75 m, 1.5 m, 2.25 m._
The default front and rear horn paths. Only the rear horn length changes between the lines. Simulated when this page was built.
Rear horn length, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Rear horn length | −3 dB |
| --- | --- |
| 0.75 m | 106 Hz |
| 1.5 m (the design drawn above) | 83 Hz |
| 2.25 m | 62 Hz |
## How the outputs add up
The dashed lines are the front and rear mouths on their own. The total follows whichever is louder, and dips where they are close in level and out of step.
_Figure: Compound horn, rear horn length 1.5 m: the total response and main mouth and rear mouth on their own._
The outputs are pressures, so they add with their phase: where the dashed lines are close in level and opposite in phase, the total drops below both.
Compound horn, rear horn length 1.5 m. Solid: the total. Dashed: Main mouth and Rear mouth on their own.
## Diagnostics and stuffing
**Horn Radiating Outputs** shows the Main mouth and the Rear mouth with their total. Main coupling and Rear coupling appear when their chambers have a cross-section. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Spans on both horns can be stuffed. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Not yet. Folding handles one horn path, so the **Fold into cabinet** button is disabled for compound horns and the **Fold** tile says the type does not fold yet.
- **Hornresp export · CH, CH1, CH2 or CH3:** Entries must be at the throat or the first junction. A rear coupling chamber cannot currently be exported, and the export says so. The two faces need opposite polarities.
- **Checked against Hornresp:** 13 native Hornresp cases of this type are re-simulated in the regression tests. 12 of 12 agreement checks meet their tolerances, and 1 more track stuffing-model differences without claiming agreement.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Compound** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add a compound horn to my open workspace for the driver I am using now. Try rear horn lengths of 1, 1.5 and 2 m without saving, simulate each at 50 W and show me SPL. For the best one, use the radiating outputs in the results to tell me where the two mouths work against each other.
---
# Multiple-entry horn (MEH)
> How to model a multiple-entry horn (MEH) in 00 Simulator: extra drivers with their own power and EQ, entry positions, chambers and ports, diagnostics and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/multiple-entry-horn
Several independently amplified drivers share one horn: D1 at the throat and the others entering along the path. Each driver has its own power, EQ, polarity and delay, so the horn can cover a wider band than one driver could.
_Figure: The multiple-entry horn (meh) drawn by the simulator's schematic, with its chambers, paths and outputs._
The multiple-entry horn example, with a B&C 10PS26. Entry position of D2 and D3: 13 % · 15 cm. Drawn by the simulator when this page was built.
## How it connects
D1 drives the throat. Each further driver, D2 onward, joins the path at its own entry position through its own front chamber and, optionally, an entry port.
All the drivers share the horn’s acoustic load and its one mouth. Where their outputs arrive in step they add; where they do not, the top of the band falls away.
## When to use it
### Good for
- Wide-band horns where one driver cannot cover the whole range.
- Point-source designs that combine drivers in one mouth.
### Watch for
- Entries far from the throat pull the top of the band down. Keep the entry positions short compared with the wavelengths you want the drivers to share.
- Drivers, power and EQ are set in the **Drivers** panel, not in the horn controls.
## What you set
Set the enclosure type to **Horn**, then choose **MEH** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Throat chamber** | **Volume**, and its **Cross-section** under **Advanced**, for D1. |
| **Rear chamber** | **Volume**, for D1. It is sealed. |
| D2, D3 … | A row for each extra driver, with its badge and name. It shows the entry’s two chamber volumes and opens to set them. |
| **Front chamber** and **Rear chamber** | Inside a driver’s row: that entry’s own chambers. |
| **Entry port area** (cm²) and **Entry port length** (cm) | Under the row’s **Advanced**, beside the **Front cross-section**: an optional port between the entry’s front chamber and the horn. |
| **Driver, power and EQ for** D2… | Opens that driver in the **Drivers** panel. A horn takes up to eight drivers in total. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main horn** | The area at the throat, then up to eight spans. |
| D2, D3 … markers | Where each extra driver enters, in cm from the throat. |
D1 is fixed at the throat. D2 and later markers can be dragged, and clicking one selects that driver. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the entry position of d2 and d3 does
Only the entry position of the two extra drivers changes. The bass is the same for all three. Moving the entries from near the throat to a quarter of the way along cuts the top of the band steeply.
_Figure: Simulated SPL of the multiple-entry horn (meh) for 3 values of entry position of d2 and d3: 6 % · 7 cm, 13 % · 15 cm, 25 % · 30 cm._
The multiple-entry horn example. Only the entry position of d2 and d3 changes between the lines. Simulated when this page was built.
Entry position of D2 and D3, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Entry position of D2 and D3 | −3 dB |
| --- | --- |
| 6 % · 7 cm | 71 Hz |
| 13 % · 15 cm (the design drawn above) | 70 Hz |
| 25 % · 30 cm | 70 Hz |
## Diagnostics and stuffing
The one output is the Main mouth. Each entry with a front chamber cross-section or a port gets its own coupling path in the location list, named after the entry. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
Spans can be stuffed in the simulation, but the Hornresp export refuses stuffed MEH designs. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Not yet. Folding does not handle multiple driver entries yet, so the **Fold into cabinet** button is disabled for multiple-entry horns.
- **Hornresp export · Throat record plus ME1 and ME2:** Two or three drivers in total, with entries at S2 and, for a third, S3. Amplifier delay, an entry port without a front chamber and stuffing are refused with a reason.
- **Checked against Hornresp:** 10 native Hornresp cases of this type are re-simulated in the regression tests. 10 of 10 agreement checks meet their tolerances.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
To keep going, open the example in the simulator. It opens with this type already set up, so you can change it and watch the graphs follow.
- [Open the multiple-entry example](https://simulator.00aud.io/app?template=multi-entry-horn)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, open my multiple-entry horn and try moving D2 and D3 to 10 %, 20 % and 30 % of the path without saving. Simulate each and show me SPL, then tell me how far out the entries can go before the top of the band falls away.
---
# Paraflex horn
> How to model a Paraflex horn in 00 Simulator: subtypes PH1 to PH4, the main and auxiliary paths, the diaphragm adapter, diagnostics and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/paraflex-horn
Two resonator paths couple the faces of the diaphragm and join again before one shared mouth. The four subtypes, PH1 to PH4, connect the driver and the auxiliary path at different points, so the same spans can give very different responses.
_Figure: The paraflex horn drawn by the simulator's schematic, with its chambers, paths and outputs._
The default Paraflex main and auxiliary paths, with a B&C 10PS26. Subtype: PH1. Drawn by the simulator when this page was built.
## How it connects
The main path has four spans, H1 to H4, and H4 radiates through the mouth. The auxiliary path has three, H5 to H7. H1 and H5 start at closed ends.
PH1 puts the driver between S2 and S7, and H7 rejoins the auxiliary path at S4. PH2 puts the driver between S4 and S7, and H7 rejoins at S2.
PH3 and PH4 couple one face through the adapter H7: to S2 in PH3 and to S7 in PH4. The auxiliary path then rejoins at S4 in PH3 and at S2 in PH4.
## When to use it
### Good for
- Deep bass designs where you want to try four connection layouts on the same spans.
- Comparing subtypes on the same spans in one workspace.
### Watch for
- The main path always has four spans and the auxiliary path three; they cannot be added or removed.
- There are no chamber controls in a Paraflex horn.
## What you set
Set the enclosure type to **Horn**, then choose **Paraflex** under **Horn type**, in the enclosure panel or in the **Horn Editor**’s path bar.
### In the horn card
The horn card in the enclosure panel lists each path as a row: click one to open that path in the **Horn Editor**. The card also sets:
| Control | What it sets |
| --- | --- |
| **Subtype** | PH1, PH2, PH3 or PH4. Also in the **Horn Editor**’s path bar. |
### In the Horn Editor
The path itself is set on the **Horn Editor** tile. Drag it in the drawing, or switch the tile to **Table** to type each value:
| Control | What it sets |
| --- | --- |
| **Main** | The main path: the area at its closed end, then its four spans, H1 to H4. |
| **H5–H7** | For PH1 and PH2: the auxiliary path’s three spans. |
| **H5–H6** and **Adapter H7** | For PH3 and PH4: the auxiliary resonator’s two spans, and the diaphragm adapter’s one span, from the driver end to its junction. |
The path bar has a subtype select and chips for the main path and the auxiliary path, or the resonator and adapter. There are no draggable markers. [How the Horn Editor works](https://simulator.00aud.io/docs/horns/editor).
## What the subtype does
The spans are the same for all four lines; only the subtype changes. PH1 and PH3 reach lowest here, PH2 gives up the most bass, and all four differ in where their peaks and notches fall above 100 Hz.
_Figure: Simulated SPL of the paraflex horn for 4 values of subtype: PH1, PH2, PH3, PH4._
The default Paraflex main and auxiliary paths. Only the subtype changes between the lines. Simulated when this page was built.
Subtype, SPL: B&C 10PS26, Half Space · 1.0 m · 50 W.
| Subtype | −3 dB |
| --- | --- |
| PH1 (the design drawn above) | 45 Hz |
| PH2 | 81 Hz |
| PH3 | 41 Hz |
| PH4 | 57 Hz |
## Diagnostics and stuffing
The one output is the Main mouth. Locations cover Main H1 to H4 and Auxiliary H5 to H7. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
The main spans, the auxiliary spans and the adapter can all be stuffed. The Hornresp export refuses stuffing on the auxiliary path. [How stuffing works](https://simulator.00aud.io/docs/horns/stuffing).
## Folding and Hornresp
- **Folding:** Not yet. Folding handles one horn path, so the **Fold into cabinet** button is disabled for Paraflex horns and the **Fold** tile says the type does not fold yet.
- **Hornresp export · PH1 to PH4:** Four main and three auxiliary spans. Hornresp derives S7 from one continuous H5/H6 flare, so the export asks you to match their flare and junction area first. Chambers and auxiliary stuffing are refused.
- **Checked against Hornresp:** 13 native Hornresp cases of this type are re-simulated in the regression tests. 13 of 13 agreement checks meet their tolerances.
[Folding a horn into a cabinet](https://simulator.00aud.io/docs/horns/folding) · [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp)
## Try it
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
There is no example for this type yet. Open the simulator, add an enclosure, set its type to **Horn** and choose **Paraflex** under **Horn type**. It starts from the default horn path.
- [Open the simulator](https://simulator.00aud.io/app)
## Ask your AI
**Ask your AI**
With 00 Simulator connected to Claude, ChatGPT or another MCP client, your assistant runs this same solver on your own workspaces.
> Using 00 Simulator, add a Paraflex horn to my open workspace for the driver I am using now. Simulate it as PH1, PH2, PH3 and PH4 without saving, at 50 W, show me SPL for all four, and tell me which subtype reaches lowest.
---
# Shape a horn in the Horn Editor
> How to shape a horn path in 00 Simulator: the Horn Editor tile, its path bar and markers, the drawing and its gestures, and the table of typed values.
Source: https://simulator.00aud.io/docs/horns/editor
The **Horn Editor** tile draws the horn path to scale and lets you change it by dragging. Every change goes straight into the simulation, so the graphs beside it follow as you work. Switch the tile to its table to type the same values as fields.
## Open it
- Choose the Horn Design layout. It is pinned as a tab beside the layout switcher above the graphs, and it is in the switcher’s **Layouts** menu. It puts the **Horn Editor** beside SPL, impedance, excursion and group delay.
- Or add the **Horn Editor** tile to any layout from **Add tile**.
- Or click a path’s row in the horn card, in the enclosure panel. That path opens in the **Horn Editor**, and the tile is added to the top of the layout if it isn’t there.
The **Schematic** tile, also in **Add tile**, draws the whole design, chambers and outputs included.
## The path bar
A small bar sits inside the top of the tile. From left to right:
- **Horn type**: the same choice as in the horn card. Each option says what the diaphragm faces connect to.
- **ⓘ**: how the current type is connected, the editing gestures, and a link to that type’s page in these docs.
- The Paraflex subtype, PH1 to PH4, for Paraflex horns.
- Path chips, when the horn has more than one path: **Front** and **Rear** for compound horns, **Main** and **Stub** for stubbed horns, **Main** and **H5–H7** for PH1 and PH2, and **Main**, **H5–H6** and **Adapter H7** for PH3 and PH4. Each chip shows its path’s length; click one to edit that path.
At the top right, **Drawing** and **Table** switch between the two views of the path. Both edit the same spans and markers, so they always agree. Phones start on the table, where every value is a touch-sized field; the tile remembers the view you last chose.
The tile’s own title bar has **Fold into cabinet**, which opens the **Fold** tile. It is disabled for horn types that don’t fold yet. [Folding a horn](https://simulator.00aud.io/docs/horns/folding).
## Gestures in the drawing
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
- Hover a span to see its flare, its stuffing toggle, and the buttons to add a span or remove it.
- Click a span’s H label to switch its flare to the next of conical, exponential and parabolic.
- The + at a station inserts a span there, and the one past the mouth adds a span at the end.
- Hover outside the horn to see its overall length and height.
- Click any value to type it.
- Drag an arrow or a divider between spans to reshape the path.
- Drag a driver or tap marker to move it along the path.
- Drag a stuffing flag or the stuffing itself to resize or slide it, and drag its resistivity chip up or down to change the material. [Stuffing](https://simulator.00aud.io/docs/horns/stuffing).
_Figure: The tapped horn example, drawn by the simulator’s own schematic._
The tapped horn example, with a B&C 21SW152. Front entry position: 14 % · 35 cm. Drawn by the simulator when this page was built. The **Schematic** tile draws the same path with its chambers and outputs.
## Markers by horn type
| Horn type | Markers |
| --- | --- |
| [Front-loaded](https://simulator.00aud.io/docs/horns/front-loaded-horn) | A driver marker, fixed at the throat. |
| [Back-loaded](https://simulator.00aud.io/docs/horns/back-loaded-horn) | A rear-of-driver marker, fixed at the throat. |
| [Tapped](https://simulator.00aud.io/docs/horns/tapped-horn) | Driver and rear-tap markers, both draggable. |
| [Offset-driver](https://simulator.00aud.io/docs/horns/offset-driver-horn) | A draggable driver marker. |
| [Stubbed](https://simulator.00aud.io/docs/horns/stubbed-horn) | A driver marker fixed at the throat, and a draggable stub junction. |
| [Compound](https://simulator.00aud.io/docs/horns/compound-horn) | A driver marker you can drag along either path. |
| [MEH](https://simulator.00aud.io/docs/horns/multiple-entry-horn) | D1 fixed at the throat; D2 and later draggable. Clicking a marker selects that driver. |
| [Paraflex](https://simulator.00aud.io/docs/horns/paraflex-horn) | No markers. The subtype sets where the driver connects. |
## The same values as a table
Switch the tile to **Table** when you already know the numbers. The first row is the station where the path starts, then one row per span, and every value is a field you can tab through.
- **Span:** H1 onward, 1 to 8 per path. Click a span’s name to select it; the **Schematic** lights the same span. Hover a row for + to insert a span after it and a bin to remove it; **Add segment** adds one past the mouth.
- **Flare, Length and Ends at:** The span’s flare, its length in cm, and how far along the path it ends.
- **Area:** The area at the end of each span, and at the start of the path on the first row: in cm², or click the column’s unit to type diameters in cm instead.
- **Stuffing:** **Stuff this span** fills the whole span. A stuffed span shows a chip with its resistivity and extent; click it for **Resistivity**, **Start** and **End**, or **Remove stuffing**.
- **Markers:** A dashed row between the spans each marker falls in, with its position in cm from the start of the path.
- **Readouts:** Under the table: the path’s **Length**, **Mouth Ø**, **Area ratio** and **Mode spacing**.
On a phone the table leaves out the **Flare** and **Ends at** columns and shows each span’s flare as an icon beside its name.
## The horn card
The horn card in the enclosure panel keeps what the tile doesn’t: the horn type, a row per path that opens it here, the chamber volumes with their cross-sections under **Advanced**, and a row for each extra driver of a multiple-entry horn. Volume divided by cross-section sets a coupling path’s length. Each type’s page lists its own controls.
## Flares
Each span has its own flare, which sets how its area changes between its two stations:
| Flare | How the area changes |
| --- | --- |
| Conical | The radius changes in a straight line, so the walls are straight. |
| Exponential | The area grows by the same ratio over each equal step along the span. This is the default flare. |
| Parabolic | The area grows in a straight line along the span. |
A span you add takes the flare of the span it continues. Spans run from 2 cm to 6 m long, with an area from 5 cm² to 2 m² at each station. Hornresp export maps the flares to its own Con, Exp and Par and never approximates one with another.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, look at the horn in my open workspace and describe its path span by span: length, areas and flare. Then suggest one change to the flare or the mouth area that should extend the bass, try it without saving, and show me SPL before and after.
---
# Damp a horn with stuffing
> How to stuff a horn in 00 Simulator: fibrous fill by airflow resistivity, set per span in the Horn Editor, the Miki material model and its limits, and Hornresp export.
Source: https://simulator.00aud.io/docs/horns/stuffing
Any span of any horn path can be partly or wholly filled with fibrous material. You set how resistive the material is and where the fill starts and ends, and the simulator models how it absorbs sound along that part of the path.
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The last step fills 50 % of H1 in the tapped horn example, from the closed end, at 10,000 Pa·s/m². Inside the working band, 25–120 Hz, the response changes by at most 1.0 dB. Above 200 Hz the fill does more: the highest peak moves from 119 dB at 243 Hz to 116 dB at 301 Hz. That is the usual reason to stuff a horn: to calm the path’s resonances above the band while keeping the band itself.
## Set it
### In the Horn Editor’s drawing
- Hover a span and click its stuffing toggle to fill the whole span. Click the lit toggle again to empty it.
- Drag a flag on the bottom edge to resize the fill. Drag it past a station to carry the fill into the next span.
- Drag the stipple to slide the fill along the path.
- Click the resistivity chip to type a value, or drag it up or down. Denser dots mean a higher resistivity.
- Hover the fill for its extent, its resistivity and the band the material model fits.
### In the Horn Editor’s table
Each span row has a **Stuffing** cell. **Stuff this span** fills the whole span at 10,000 Pa·s/m², or at the resistivity of a stuffed neighbour. A stuffed span shows a chip with its resistivity and extent: click it for **Resistivity** in Pa·s/m², **Start** and **End** in %, and **Remove stuffing**.
- **Airflow resistivity:** 100 to 100,000 Pa·s/m². Use the value measured for your material, or the supplier’s figure.
- **Start and End:** Percentages of the span, measured from where it starts. The fill occupies the whole cross-section between them.
- **Which spans:** Every path: main, rear, stub and the Paraflex auxiliary path and adapter.
- **Mode spacing:** Becomes **Unfilled mode spacing** once a path has fill. Filled air is dispersive, so read its resonances from the response instead.
## What the model assumes
Fill uses the equivalent-fluid model from Yasushi Miki’s 1990 paper, [Acoustical properties of porous materials: modifications of Delany-Bazley models](https://doi.org/10.1250/ast.11.19). Its absorption depends on frequency and on the material’s airflow resistivity.
- The material fills the whole cross-section over its length. A lining on the walls is a different thing and is not modelled.
- Compression of the fill and turbulent flow are not modelled.
- Density is not a substitute for airflow resistivity, and there are no material presets. Measure it, or ask the supplier.
- The model fits from 1/100 of the resistivity to the resistivity itself, in hertz: 10,000 Pa·s/m² fits from 100 to 10,000 Hz. Results outside that band are extrapolated.
- Start and End follow the span, so resizing a span changes the physical length of its fill.
## Check what it did
Compare SPL, impedance and the horn diagnostics before and after. Pressure and particle velocity along the path show where the fill is working. [Reading the horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
## Stuffing and folding
The **Fold** tile cannot carry stuffing onto the folded passage yet. A stuffed horn gets no folded line on the graphs, and its fold cannot be written back into the horn. [Folding](https://simulator.00aud.io/docs/horns/folding).
## Stuffing and Hornresp
The Hornresp export writes the fill’s resistivity and occupied length to Hornresp’s own fields, with a warning: Hornresp uses a different material model, so its response can differ. It refuses stuffing on a Paraflex auxiliary path and on a multiple-entry horn. The regression tests track stuffed cases against Hornresp without claiming agreement. [Exporting to Hornresp](https://simulator.00aud.io/docs/horns/hornresp).
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, open my horn and try stuffing the first span with 10,000 Pa·s/m² fibre, filling a quarter, a half and all of it, without saving. Simulate each and tell me which calms the peaks above the working band most while changing the band itself least.
---
# See what the air is doing inside the horn
> How to read horn particle velocity, pressure, acoustic impedance and radiating outputs in 00 Simulator, with figures from the tapped and back-loaded horn examples.
Source: https://simulator.00aud.io/docs/horns/diagnostics
A smooth SPL curve can hide a lot: air moving fast through a narrow section, a pressure peak at a closed end, or two outputs cancelling. The four horn diagnostic graphs read the path at any station you pick and split the sound into each thing that radiates.
## Open them
Add them from **Add tile**: **Horn Particle Velocity**, **Horn Pressure**, **Horn Acoustic Impedance** and **Horn Radiating Outputs**. They show horn enclosures only.
## The four graphs
| Graph | Unit | What it shows |
| --- | --- | --- |
| **Horn Particle Velocity** | m/s, peak | How fast the air moves at the chosen location: the volume flow divided by the area there. It is not the cone’s speed, and it is not a sum over outputs. |
| **Horn Pressure** | Pa, RMS, or phase in degrees | The sound pressure inside the path at the chosen location. Switch between **Magnitude** and **Phase**. |
| **Horn Acoustic Impedance** | Pa·s/m³ | Pressure divided by volume flow at the location, as **Magnitude**, **Phase**, **Resistance** or **Reactance**. It is acoustic, not the electrical impedance in ohms. Where no air flows, it is undefined and left out. |
| **Horn Radiating Outputs** | dB, or phase in degrees | Each mouth, port and exposed cone on its own, dashed, with their coherent total solid. The outputs add as pressures with their phase, so their dB values do not simply add. |
## Pick a location
Velocity, pressure and impedance read one location at a time. Locations are named by path, span and end, such as _Main H1 throat_, with their position and area. Where a driver enters or a branch joins partway along a span, the two sides are separate locations, marked toward the throat and toward the mouth. Pressure is continuous across the join, but the flow on each side can differ.
## An example: the tapped horn
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The tapped horn example at 100 W in half space. The air moves faster at the constriction, the narrowest station between the closed end and the mouth, than at the mouth itself; a narrow section like this is where to check for noise first. Pressure is highest at the closed end, because the air cannot move there. [The tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn).
## Outputs that add and cancel
Where a design radiates from more than one place, **Horn Radiating Outputs** shows each one. In a back-loaded horn the front of the cone and the horn mouth both radiate, and the total depends on how they line up in phase.
_Figure: Back-loaded horn, horn length 1.2 m: the coherent total, solid, and each radiating output on its own, dashed: main mouth and direct radiator._
The outputs are pressures, so they add with their phase: where the dashed lines are close in level and opposite in phase, the total drops below both.
Back-loaded horn, horn length 1.2 m. Solid: the total. Dashed: Main mouth and Direct radiator on their own.
[The back-loaded horn](https://simulator.00aud.io/docs/horns/back-loaded-horn) · [The compound horn](https://simulator.00aud.io/docs/horns/compound-horn), which has two mouths.
## What they are not
- They are linear. They do not predict turbulence, distortion or compression, and no air-speed warning is applied the way the port velocity check is for a box. Decide your own limit for the air speed in a narrow section.
- A location missing from a comparison enclosure is left out, not drawn at zero.
- Max SPL, excursion and impedance still apply to horns. Max SPL is the lower of two ceilings, the cone reaching Xmax and the driver’s thermal limit, with the thermal rule chosen in the tile’s settings. The default is real input power, the rule Hornresp uses. [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl).
- The dashed folded line from the **Fold** tile is not drawn on these four graphs.
Every graph, unit and display mode in detail: [Horn Particle Velocity](https://simulator.00aud.io/docs/reference/tiles/horn-particle-velocity), [Horn Pressure](https://simulator.00aud.io/docs/reference/tiles/horn-pressure), [Horn Acoustic Impedance](https://simulator.00aud.io/docs/reference/tiles/horn-acoustic-impedance), [Horn Radiating Outputs](https://simulator.00aud.io/docs/reference/tiles/horn-radiating-outputs).
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate my horn at the power it is set to and read its horn diagnostics. Where along the path is the particle velocity highest, how high does it get and at what frequency? Then tell me whether any outputs cancel inside the working band.
---
# Fold a horn into a cabinet
> How the Fold tile packs a front-loaded, back-loaded, tapped or offset-driver horn into a cabinet you can build: patterns, locks, checks, cut list and exports.
Source: https://simulator.00aud.io/docs/horns/folding
A horn that works on the graph still has to fit in a box. The **Fold** tile packs the horn path into a cabinet you can build and sits beside your graphs, where every frequency graph draws the folded horn as a dashed line. You see whether the fold can be built and what it does to the sound at the same time.
_Figure: Side section of the tapped horn example folded into a cabinet 1,130 mm high and 940 mm deep: the boards, the air passage, the dead space and the path from throat to mouth._
The [tapped horn example](https://simulator.00aud.io/app?template=tapped-horn), folded when this page was built: a serpentine fold with 5 runs in a cabinet 530 mm wide.
| | Folded | Your design |
| --- | --- | --- |
| Path length | 2,500 mm (+0.0 %) | 2,500 mm |
| Modelled air volume | 363 L | 409 L |
Cabinet outside: 530 mm wide, 1,130 mm high and 940 mm deep, with 18 mm walls.
## Which horns fold
Folding works on [front-loaded](https://simulator.00aud.io/docs/horns/front-loaded-horn), [back-loaded](https://simulator.00aud.io/docs/horns/back-loaded-horn), [tapped](https://simulator.00aud.io/docs/horns/tapped-horn) and [offset-driver](https://simulator.00aud.io/docs/horns/offset-driver-horn) horns, which each have one path. Stubbed, compound, multiple-entry and Paraflex horns need junction, branch or entry layouts the fold does not handle yet. For those, the **Fold into cabinet** button is disabled and the **Fold** tile says so.
## Open it
Choose **Fold into cabinet** in the **Horn Editor** tile’s title bar, where it reads **Fold** on narrow screens. The first time, it saves a suggested fold, a three-lane serpentine, fits a box to it and adds the **Fold** tile beside your graphs. You can also add the **Fold** tile from the graph picker and choose **Fold this horn**. From then on every change is saved with the enclosure, and undo takes it back.
## Choose the fold
**Auto** folds the path in a pattern you pick. Choose it from **Fold pattern** and set its count; the fit tries every variant of that pattern, with the throat on a wall or sliding and the mouth on the floor or the lid, and never switches pattern by itself.
- **Serpentine:** Lanes that double back on themselves, 2 to 6 lanes.
- **Spiral:** Turns the same way at every bend, 3 to 6 laps.
- **Wrapped serpentine:** A serpentine whose last turns carry on around the cabinet, 3 to 5 rows.
- **Columns:** A serpentine of upright columns, 2 to 5 columns.
- **Straight:** One run, no folds.
**Draw** lets you lay the path yourself. Tap cells from the closed end to the front column, or use the arrow keys and Backspace. Tapping one step past the edge grows the grid, tapping a path cell cuts the path back there, and dragging a bend flips it to the other corner. The fold solves as soon as the path reaches the front.
## Set the cabinet
The cabinet popover holds the outside **Height**, **Depth** and **Width** and the **Material**. Typing a dimension locks it: that is the one your room decides. The unlocked dimensions are solved for the smallest box that passes every check, and **Fit box** runs that fit again. When no box inside the locks passes, the fit returns the buildable fold closest to your horn.
In the drawing you can drag the driver along its board, and its taps follow. Drag a board across itself to hold it there. Shift keeps it level or plumb, and a double-click lets it follow the horn again.
## Read the checks
The tile shows one chip per check. A passing chip shows a tick, a warning keeps its number, and an error names what is wrong. Open a chip for its details and the fixes that apply, such as changing one dimension, re-centring the driver or moving your front tap to the smallest distance a board allows. Nothing blocks saving or simulating.
| Chip | What it checks |
| --- | --- |
| **Length** | The folded path against your design. It warns beyond 0.5 % and fails beyond 3 %. |
| **Front tap**, **Rear tap** or **Driver entry** | Where the driver actually sits on the folded path, against the positions you set. |
| **Driver** | Whether the driver fits where the fold puts it, clears the boards and the shell, leaves the cone room to move, and how much its motor blocks the passage. |
| **Chamber** | The throat or rear chamber the fold leaves, against the volume you set. |
| **Shape** | How far the runs give way from your areas, the narrowest passage, and boards pinned against a wall. |
| **Mouth** | The folded mouth area against your design. It warns beyond 15 %. |
| **Can't build** | Geometry that cannot be made: overlapping passages, boards ending in open space, the mouth off the front panel. The passage is drawn red. |
Boards you hold show a **Held** chip, which also releases them.
## The folded line on your graphs
Every frequency graph, apart from the horn diagnostic graphs, draws the horn this fold builds as a dashed line in the enclosure’s colour: the folded spans, with the taps where the driver really sits. Its pill in the legend and in the tile hides it. It is left out when the fold cannot be built, when the horn already matches the fold, and when the horn is stuffed or damped, because stuffing cannot be carried onto the folded passage yet.
**Use this fold** writes the folded spans and taps into your horn, so the simulation follows the fold. It locks the box and holds every board, and the pill then reads **Matches horn**. **Let the fold follow the horn** on the **Held** chip releases it, and one undo puts everything back.
## Full screen
**Full screen** opens the whole editor: the inputs on the left, the side section or a 3D cutaway in the middle, and **Profile**, **Cut list**, **Hornresp** and **Response** tabs on the right.
- **Profile** plots area against distance from the throat for your design, the folded passage and the simulator’s equivalent of it.
- **Cut list** lists the boards. **Hornresp** gives the folded passage in Hornresp’s terms, with **Copy Hornresp values**. [Hornresp export](https://simulator.00aud.io/docs/horns/hornresp).
- **Fork as enclosure** adds a copy of the enclosure that simulates the fold beside your design. It uses the taps the fold achieves when it places the driver, and your target taps otherwise, and says which in the copy’s name. It needs a fold without errors and a horn without damping.
- **Export** saves the whole geometry as JSON. It is not a fabrication drawing.
- **Boundary Lab** downloads a mesh and project for a coupled FEM and BEM solve in [Boundary Lab](https://github.com/JWSound/boundary-lab), once the fold has no geometry errors.
- **Path length:** Measured through the arc of each bend rather than into its corner, which matches measured horns more closely than the plain centreline.
- **The driver:** An editable estimate sized from the driver you chose. The B&C 18DS115, which has a measured model, uses its real frame, cutout, depth and magnet and is drawn as itself.
- **What it reports:** Tapped and offset-driver horns report the taps the fold achieves. Front-loaded horns report their throat and rear chambers, and back-loaded horns their throat chamber.
- **Dead space:** Every cell the path does not use, with its volume. Front- and back-loaded horns open the throat into it as a chamber.
## Limits
- Folds are side sections: boards span the full internal width, with no folding out of that plane.
- Bends are not modelled as losses or scattering, and driver obstruction is reported but not simulated.
- Chamber volumes and tap positions are geometric results. Check the folded line or a forked copy before you build.
## Ask your AI
**Ask your AI**
Your assistant folds your own horn the way the Fold tile does, through the 00 Simulator connector.
> Using 00 Simulator, fold my tapped horn into a cabinet no more than 600 mm deep and 900 mm high. Compare the alternative folds it finds, simulate the best one beside my design, and tell me what folding costs in response before I save anything.
---
# Hornresp export and validation
> How to export 00 Simulator horns as native Hornresp records, what each type becomes, what carries over, and how the horn model is checked against Hornresp.
Source: https://simulator.00aud.io/docs/horns/hornresp
00 Simulator works alongside Hornresp. Horns that fit Hornresp’s layouts export as native Hornresp records, so you can open the same design in both, and the horn model is regression-tested against native Hornresp results.
## Export a design
1. **Open the export.** Open the **Export** menu, the download icon in the header, and choose **Hornresp…**. It needs at least one horn in the workspace.
2. **Pick the horns.** In **Export Hornresp projects**, pick the horns to export. The dialog lists anything that will be simplified under **Export notes**, and a design that cannot be exported has to be deselected or changed first.
3. **Download the records.** Choose the **Export** button, which counts the records it will write, to download `hornresp-projects.zip`. Each enclosure has its own folder, with short record names and a README that repeats the notes.
4. **Import them into Hornresp.** Extract it, copy the records into Hornresp’s Import folder, then choose File, Import, Hornresp Record in Hornresp.
> **Multiple-entry horns** A multiple-entry horn exports as a throat record and one or two offset records. Import each record, then move to another record and back to reload it. Activate the offset records, then open Hornresp’s Multiple Entry Horn Wizard from the throat record.
## What each horn type becomes
| Horn type | Hornresp record | Limits |
| --- | --- | --- |
| [Front-loaded horn](https://simulator.00aud.io/docs/horns/front-loaded-horn) | Nd | Up to four spans export as a native record. A ported rear chamber is written as Hornresp’s Rear Vented chamber, a mapping that has not yet been checked against a native Hornresp capture. With no rear chamber, the export warns that Hornresp adds an exposed rear radiator. |
| [Back-loaded horn](https://simulator.00aud.io/docs/horns/back-loaded-horn) | Nd | Up to four spans export as a native record. Hornresp needs the two diaphragm faces at opposite polarities, and the export notes that absolute phase may be inverted and that you should use its combined acoustic output with Path = 0 cm. |
| [Tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn) | TH or TH1 | The front tap must be at S2 and the rear tap at S3 or S4; otherwise the export stops with that reason. Taps at either end of the path are refused. The two faces need opposite polarities. |
| [Offset-driver horn](https://simulator.00aud.io/docs/horns/offset-driver-horn) | OD, OD1 or OD2 | The driver must enter at S2, S3 or S4. A ported rear chamber is written as Rear Vented, a mapping that has not yet been checked against a native Hornresp capture. |
| [Stubbed horn](https://simulator.00aud.io/docs/horns/stubbed-horn) | SH | Up to three main spans and one stub span export as a native record. A ported rear chamber is written as Rear Vented. |
| [Compound horn](https://simulator.00aud.io/docs/horns/compound-horn) | CH, CH1, CH2 or CH3 | Entries must be at the throat or the first junction. A rear coupling chamber cannot currently be exported, and the export says so. The two faces need opposite polarities. |
| [Multiple-entry horn (MEH)](https://simulator.00aud.io/docs/horns/multiple-entry-horn) | Throat record plus ME1 and ME2 | Two or three drivers in total, with entries at S2 and, for a third, S3. Amplifier delay, an entry port without a front chamber and stuffing are refused with a reason. |
| [Paraflex horn](https://simulator.00aud.io/docs/horns/paraflex-horn) | PH1 to PH4 | Four main and three auxiliary spans. Hornresp derives S7 from one continuous H5/H6 flare, so the export asks you to match their flare and junction area first. Chambers and auxiliary stuffing are refused. |
## What carries over
- Geometry is converted to Hornresp’s units, and each flare keeps its law. Unsupported geometry is refused, never truncated or approximated.
- The driver’s moving mass is converted to Hornresp’s convention, power becomes a drive voltage using the nominal impedance, and series resistance becomes Rg.
- Arrays and dual voice coils become one equivalent driver, which keeps the same linear behaviour.
- One high-pass and one low-pass filter carry over when they share a Butterworth, Linkwitz-Riley or Bessel alignment.
- Stuffing carries over as its resistivity and occupied length, with a warning that Hornresp’s material model differs.
### What does not
- Other EQ, span attenuation and chamber loss values. The dialog and README name the designs they affect.
- A series capacitor. Hornresp models passive filters in its own Filter Wizard.
- Listening distance. Hornresp shows SPL at 1 m, so compare at 1 m.
- Multiple-entry amplifier delay, entry ports without a front chamber, and stuffing in a multiple-entry horn or a Paraflex auxiliary path.
## How the horn model is checked
The regression tests re-simulate 122 native Hornresp cases across 8 horn families: 114 complete curve sets and 8 sampled diagnostic checks. 109 of 109 agreement checks meet their stated tolerances. The other 13 cases track stuffing-model differences without claiming agreement.
| Family | Cases | Agreement checks passing | Stuffing cases tracked |
| --- | --- | --- | --- |
| [Front-loaded](https://simulator.00aud.io/docs/horns/front-loaded-horn) | 26 | 20 of 20 | 6 |
| [Tapped](https://simulator.00aud.io/docs/horns/tapped-horn) | 22 | 19 of 19 | 3 |
| [Offset-driver](https://simulator.00aud.io/docs/horns/offset-driver-horn) | 16 | 13 of 13 | 3 |
| [Back-loaded](https://simulator.00aud.io/docs/horns/back-loaded-horn) | 13 | 13 of 13 | 0 |
| [Stubbed](https://simulator.00aud.io/docs/horns/stubbed-horn) | 9 | 9 of 9 | 0 |
| [Compound](https://simulator.00aud.io/docs/horns/compound-horn) | 13 | 12 of 12 | 1 |
| [Paraflex](https://simulator.00aud.io/docs/horns/paraflex-horn) | 13 | 13 of 13 | 0 |
| [Multiple-entry](https://simulator.00aud.io/docs/horns/multiple-entry-horn) | 10 | 10 of 10 | 0 |
Full curves cover 20 Hz to 5 kHz, stuffing curves run to 2 kHz, and sampled diagnostics use three frequencies. These compare two simulators, not built cabinets. Directivity, thermal power compression and bend losses are outside this model.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own horn through the 00 Simulator connector.
> Using 00 Simulator, simulate my horn at 1 m in half space at the power it is set to, and give me its SPL and cone excursion at 20, 40, 80 and 160 Hz, so I can compare them with the same design in Hornresp.
---
# All guides
> Step-by-step guides for 00 Simulator: drivers, power and limits, EQ, comparing designs, layouts, measurements, sharing and more.
Source: https://simulator.00aud.io/docs/guides
Each guide starts from something you want to do and walks through the app’s own controls to get it done, with the graphs where they show the effect. New to 00 Simulator? Start with [Your first design](https://simulator.00aud.io/docs/start/first-design).
## Design
- [Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers): Find a driver in the 00 Simulator library, or add your own: enter or paste its T/S parameters, import WinISD or Unibox files, and fix values that disagree.
- [Power and limits](https://simulator.00aud.io/docs/guides/power-and-limits): Set the input power for each design, then use Max SPL and Headroom to see how loud it can play and which limit stops it first.
- [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port): Bring a vented box’s port under the air speed warning: more port area, less power or a high-pass, and what each fix costs.
- [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters): Add high-pass, low-pass, parametric, shelf and Linkwitz filters to an enclosure, edit them on the graph, and protect the cone.
- [Compare designs](https://simulator.00aud.io/docs/guides/compare): Compare enclosures: several designs on one graph, colours, eyes and solo, the Metrics and Compare tiles, and undo and saved versions.
## Work in the app
- [Layouts and pinned tabs](https://simulator.00aud.io/docs/guides/layouts): Arrange the 00 Simulator dashboard: add, move and resize tiles, switch between the built-in layouts, save your own and pin up to 5 as tabs.
- [Workspaces and accounts](https://simulator.00aud.io/docs/guides/workspaces): Work as a guest in your browser, or sign in to keep workspaces in the cloud: sign-in, the workspace library, drafts, Recently deleted, undo and saved versions.
- [Settings and themes](https://simulator.00aud.io/docs/guides/settings): Every setting: light or dark mode, themes and the theme builder, the frequency axis, units, the upper-response model and the warning lines.
- [Keyboard shortcuts](https://simulator.00aud.io/docs/guides/shortcuts): Every keyboard shortcut: undo and redo, the enclosure list, number fields, tiles, your workspaces, and search in the app, docs and gallery.
- [On a phone](https://simulator.00aud.io/docs/guides/phone): How 00 Simulator works on a phone: one tile at a time, the dock with its power, EQ and layout sheets, the drawers, and what needs a computer.
## Measure, share and build
- [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements): Import REW, .frd, .zma and CSV measurements into 00 Simulator, link and align them with a design, style them, and pin notes to your graphs.
- [Share and publish](https://simulator.00aud.io/docs/guides/sharing): Share a 00 Simulator design as a link: who can see it, guest links versus drafts, publishing to the Gallery, editing, deleting and your public profile.
- [Import and export](https://simulator.00aud.io/docs/guides/import-export): Move designs in and out of 00 Simulator: .00sim projects, WinISD projects and drivers, Hornresp records, measurements and other workspaces.
- [Calculators](https://simulator.00aud.io/docs/guides/calculators): The six free 00 Simulator calculators: what each one answers, what they share with the simulator, and when to open the simulator instead.
## Looking for something else?
- [Your first design](https://simulator.00aud.io/docs/start/first-design): Build a vented subwoofer from scratch and see what breaks when you turn it up.
- [All tiles](https://simulator.00aud.io/docs/reference/tiles): What each graph on the dashboard shows and how to read it.
- [Cookbook](https://simulator.00aud.io/docs/cookbook): Worked designs: vented 12-inch subwoofer, 15 L sealed subwoofer and tapped horn subwoofer.
- [What your assistant can do](https://simulator.00aud.io/docs/ai): What Claude, ChatGPT or another assistant can do in 00 Simulator through its connector.
---
# Drivers: find, create, import
> Find a driver in the 00 Simulator library, or add your own: enter or paste its T/S parameters, import WinISD or Unibox files, and fix values that disagree.
Source: https://simulator.00aud.io/docs/guides/drivers
Every enclosure needs a driver. Pick one from the 00 Bits library of 3,200+ drivers, or add your own by typing its T/S parameters, pasting them from a datasheet, or importing a WinISD, 00 Simulator or Unibox file. Before you simulate, the app checks that the values agree with each other.
- **Library:** 3,200+ drivers from 48 brands, online
- **Your own:** Up to 1,000 drivers in your account, or kept in this browser as a guest
- **Files:** WinISD `.wdr`, `.00dvr`, Unibox `.xlsx`
## Pick a driver
1. **Open the picker.** Select an enclosure and click the **Driver** box in the Driver panel. With no driver chosen it reads **Select a driver**. **Add enclosure** has the same picker.
2. **Search.** Type a brand or model, for example `12.00SW`. Results come in two groups: **Your drivers** (your own and your favourites) and **Catalogue**. Before you type, the picker shows **Recent**, **Your drivers** and a few catalogue drivers.
3. **Pick one.** Click a row to put it on the enclosure. Each row shows the model, brand, nominal impedance and size; the star makes it a favourite, listed under **Your drivers** from then on.
The line under the search box counts the catalogue, your favourites and your imports, and says _syncing_ while the catalogue refreshes. The catalogue is the online 00 Bits library. A driver you pick is saved with your workspace, so share links and your assistant see the same values.
## Search and filter
**Browse all**, beside the counts, opens **Advanced driver search**: a table of every driver with filters down the side. It lists the catalogue’s low-frequency drivers, your own drivers and your favourites.
Brand chips sit above the sliders. The box under them is a rule of thumb from EBP (Fs divided by Qes): under 50 suits sealed, 50 to 100 either, over 100 vented.
| Filter group | Sliders |
| --- | --- |
| **Dimensions** | Driver diameter, in inches |
| Basic | Fs, Qts, Qes, Qms, Vas |
| Electrical | Re, Le, BL |
| Mechanical | Mms, Sd, Xmax |
| Output | SPL, Pe |
| Derived | Vd, EBP |
- Each slider covers the range of the drivers in view; drag either end to narrow it. **Reset filters** puts them all back.
- **Include online drivers** switches the catalogue in or out. Off, the table shows only your drivers and favourites.
- **Show invalid T/S params** also lists catalogue drivers whose parameters do not check out. They are hidden by default.
- Results are grouped under **Favourites**, **My imports** and **Catalogue**, with columns for size, impedance, Fs, Qts, Vas, BL, Sd and Xmax. Click a row to pick it.
## Create a custom driver
When your driver is not in the library, click **Create custom driver** at the foot of the picker. The **Component library** opens on four ways to add one:
_Figure: The Component library’s create screen for a driver: Import driver file (Beta), Import UniBox, Paste T/S params and Enter manually._
| Option | What it does |
| --- | --- |
| Import driver file (Beta) | Load `.wdr` or `.00dvr` files |
| Import UniBox | Opens Import from Unibox for a Unibox spreadsheet |
| Paste T/S params | Extract from free text |
| Enter manually | Input T/S params directly |
1. **Enter manually.** Choose **Enter manually**. Fill in **Brand** and **Model**, then the parameters. Required ones are marked with an asterisk.
2. **Let the form fill the rest.** The required parameters are Re, Fs, Qts, Vas, Znom, BL, Qes, Xmax, plus Sd or Dd. Fields the form can work out from the others fill themselves in, marked with a calculator and _auto_; click one to type your own value. Hover a label for what it means and what it is worked out from.
3. **Choose a layout.** **Mode:** at the top switches between **Required first** and **Grouped** (electrical, mechanical, Q factors, physical).
4. **Create it.** Click **Create**. The driver joins your library and goes on the enclosure you started from.
## Paste T/S parameters from a datasheet
1. **Paste the text.** Choose **Paste T/S params** and paste the parameters as text, straight from a datasheet or a web page. The order does not matter.
2. **Extract.** Click **Extract params**. The app lists how many values it found. A number with no unit is read in the unit most datasheets use: litres for Vas, cm² for Sd, mm for Xmax, grams for Mms and mH for Le.
3. **Review any mismatch.** If some values disagree with each other, a warning offers **Review**: approve the corrections you want, then **Apply approved fixes**.
4. **Finish in the form.** Click **Populate editor**. The values land in the same form as **Enter manually**; add **Brand** and **Model**, check the rest, and click **Create**.
_Figure: Paste T/S params with Ciare 12.00SW datasheet values, Qts typed as 0.92. The app extracts 15 parameters and flags Qts; its review proposes 0.289 from Qms and Qes._
The Ciare 12.00SW’s parameters with Qts typed as 0.92 instead of 0.29, run through the app’s own parser and check when this page was built.
```
Ciare 12.00SW
Nominal impedance 4 ohm
Re 3.3 ohm
Fs 29 Hz
Qms 2.3
Qes 0.33
Qts 0.92
Vas 55 L
Sd 523 cm2
Xmax 13.5 mm
Mms 201 g
Bl 19.5 Tm
Le 1.6 mH
Pe 2000 W
```
Extract params: 15 parameters (Re, Le, Fs, Qms, Qes, Qts, Vas, Sd, Xmax, Bl, Mms, Pe, Znom, numVC, Xmech).
| Value | Why | Current | Proposed | Derived calculation |
| --- | --- | --- | --- | --- |
| Qts | Qts does not agree with Qms and Qes. | 0.92 | 0.289 | Qts = (Qms * Qes) / (Qms + Qes) = (2.3 * 0.33) / (2.3 + 0.33) = 0.288593 |
Here the check catches the slip: Qms and Qes give a Qts of 0.289, not 0.92. Hover the proposed value in the app to see the sum it comes from.
## Import driver files
- **Import driver file** (marked Beta) reads WinISD `.wdr` files and 00 Simulator’s own `.00dvr` files. Drop them on the box or click it to browse; you can bring in several at once. The app lists what it imported and anything that failed.
- **Import UniBox** opens **Import from Unibox** for a Unibox spreadsheet (`.xlsx` or `.xls`). Pick the sheet (the likely one is marked **Detected**), click **Continue**, then tick what to bring in under **Enclosures**, **Drivers** and **PRs**, and click **Import selected**. Enclosures go into your open workspace.
- The same imports are under **Import** on the My drivers tab of the library: **Driver file (.wdr, .00dvr)** and **Unibox (.xlsx)**.
To send your drivers the other way, as `.00dvr` or WinISD `.wdr` files, use **Export** in the library: [Import and export](https://simulator.00aud.io/docs/guides/import-export).
## Open a driver from 00 Bits
The _Open in 00 Simulator_ buttons on a [00 Bits](https://bits.00aud.io) driver page add the driver to My drivers straight away. A card then floats over the lower part of the editor and asks where to try it. The workspace behind it stays usable.
- **Start with** picks the first enclosure. When the page sent its maker’s box, for example _B&C’s box · 100 L · 40 Hz_, that comes first and is already chosen. If the maker gave no port, the app sizes one for the driver; hover the choice to see it. The other choices are the **Suggested** alignment for the driver, the **Default box**, and **Same box as…** an enclosure already in the workspace.
- **Add to** your workspace puts the enclosure beside what is there. **New workspace** opens a fresh one named after the driver.
- Close the card and the driver stays in My drivers for later.
## Edit a driver’s T/S parameters
1. **Open the editor.** With a driver on the enclosure, click **Edit T/S** beside **Driver** in the Driver panel. **Edit T/S parameters** opens with the same form.
2. **Change and save.** Change what you need and save. **Save modified driver** asks where the change goes, with a **Driver name** to confirm.
3. **Overwrite or save as new.** For a driver of your own, **Overwrite** updates it in every enclosure that uses it; **Save as new driver** makes a new one and leaves the old alone. A catalogue driver cannot be overwritten, so your changes become a new custom driver.
Whichever you choose, the saved driver goes on the enclosure. If the name you give would replace another of your drivers, or take this one away from other enclosures, the dialog warns you and offers a one-click fix.
## When the values disagree
T/S parameters depend on each other, so a typo or a rounded datasheet shows up as a mismatch. When the driver on an enclosure has one, a warning under the picker counts the values that do not match, with a **Review** button.
1. **Review.** Click **Review**. **Review loaded driver values** lists each suspect value with its **Current** and **Proposed** figures; hover the proposal for the sum behind it.
2. **Approve.** Every correction starts approved. Untick **Approve** on any value you want to keep as it is; **Clear all** and **Approve all** switch them all at once.
3. **Apply.** For your own driver, **Apply to custom driver** corrects it in place. For a catalogue driver, **Save corrected custom copy** saves a corrected copy to your library and puts it on the enclosure; the catalogue is left as it is.
Each check runs only when the values it needs are there. The same check runs on pasted values before they reach the form.
| Value | Checked against | Flagged when it differs by more than |
| --- | --- | --- |
| Rms | Fs, Mms and Qms | 8% |
| Qms | Fs, Mms and Rms | 8% |
| Qts | Qms and Qes | 5% |
| Cms | Vas and Sd | 20% |
| Mms | Fs and Cms | 8% |
| Bl | Re, Qes, Mms and Fs | 8% |
| Dd | Sd | 5% |
| Sd | Dd | 5% |
## Manage your library
**Manage library**, at the foot of the picker, and **Settings › Drivers…** in the header open the **Component library**. It has tabs for **Drivers** and **Passive radiators**. Under **Drivers** are the **00 Bits library** and your own drivers (My drivers), each with a count.
- Search either list. Your own list also filters and sorts, and has **Import**, **Export** and **Create**.
- **Use** on any driver offers **Create new enclosure**, or **Add to enclosure** with a list of the enclosures in your workspace.
- Your own drivers have edit and delete buttons. The star on a library driver makes it a favourite.
- Signed in, your drivers are saved to your account, up to 1,000 of them, and follow you to every workspace. As a guest they are kept in this browser.
## Ask your AI
**Ask your AI**
Your assistant’s `search_drivers` searches the same 00 Bits library as the app and gives each driver’s page on 00 Bits, with its shop prices. A driver it adds keeps its link to the library.
> Using 00 Simulator, find drivers with Fs below 30 Hz, Qts below 0.4 and a power rating of at least 500 W. Check each one’s T/S parameters for consistency, and suggest a starting enclosure for the two you would pick.
---
# Power and limits
> Set the input power for each design in 00 Simulator, then use Max SPL and Headroom to see how loud it can play and which limit stops it first.
Source: https://simulator.00aud.io/docs/guides/power-and-limits
Set how hard each design is driven, then find how loud it can go and what stops it: cone travel, voice coil heat or port air. Power is set per enclosure, so two designs on the same tiles can be at different levels.
## Set the power
1. **Select the enclosure.** Power belongs to each enclosure, not to the workspace. Click its row in the enclosure list.
2. **Open Power.** In the Driver panel, open **Power**. Its header shows the current watts, so you can read it with the section closed.
3. **Set the input power.** Type a value in **Input power**, drag the slider, or click one of the numbers under it. The slider is logarithmic, from 0.01 W to 100 kW, so each tenfold step in watts is the same distance.
- **Load voltage**, at the foot of the section, is the drive voltage that power works out to.
- **Series resistance** stands for the cable and the amplifier’s output, from 0 to 10 Ω; it starts at 0.1 Ω.
- **Series capacitor** puts a capacitor between the amplifier and the drivers, with its **Capacitance** (0.1 µF to 100,000 µF) and **ESR** (0 to 10 Ω). It starts at a stock value sized for the load: 1000 µF for the Ciare 12.00SW’s 3.3 Ω coil.
- With several drivers in one box, the input power is the total for all of them, shared equally. A multiple-entry horn has a power row for each driver, with a button that mutes it, and the header shows the total.
- On a phone, tap the watts in the dock to open the same control.
- Someone viewing your share link can change the power to hear your design at their level. The box itself stays as you made it.
## What power changes
More power raises the SPL curve without changing its shape. In the [vented example](https://simulator.00aud.io/app?template=vented), doubling the power from 100 W to 200 W adds 3.0 dB of level, and ten times the power adds 10.0 dB. The cone’s travel and the port’s air speed grow with the square root of power: both are 1.41 times as much for the same doubling.
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The app’s own SPL, Excursion and Port Velocity tiles running the vented example in your browser as the power goes from 1 W to 200 W. Nothing here is saved.
> **Compare designs at the same power** Each enclosure keeps its own power. Before you compare two designs on the same tiles, set both to the same **Input power**, or to the power each will really get.
## How loud can it go: Max SPL
1. **Add the tile.** Add **Max SPL (dB)** with **Add tile**. Its curve is the loudest each design can play at each frequency, one frequency at a time, before the cone passes Xmax or the voice coil passes its thermal limit.
2. **Turn on Limits.** Click **Limits** in the tile’s header to draw the two ceilings, heat dashed and Xmax dotted. The Max SPL line follows whichever is lower, so you can see which one stops the design at each frequency.
3. **Check the thermal rule.** Open the tile’s **Settings**. **Thermal limit** chooses how the driver’s power rating becomes a heat ceiling, and **Voice coil temperature** (20–300 °C) models a hot coil. Xmax applies in every rule.
How the rules differ, and why the coil heat budget is lower than the rating: [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits).
| Thermal rule | Matches | Its ceiling for the Ciare 12.00SW |
| --- | --- | --- |
| Real input power (default) | Hornresp | 2,000 W into the driver, its rating |
| Constant voltage | WinISD | 81.2 V at every frequency |
| Coil heating | Estimate | 1,029 W of heat in the coil |
_Figure: The vented example’s SPL at 10, 100, 1000 W against its Max SPL line. Each tenfold step in power lifts the SPL curve by 10 dB; the Max SPL line stays put._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, half space, 1 m. Simulated when this page was built.
| Frequency | Max SPL | SPL at 10 W | SPL at 100 W | SPL at 1000 W |
| --- | --- | --- | --- | --- |
| 20.0 Hz | 93.7 dB | 80.1 dB | 90.1 dB | 100.1 dB |
| 32.0 Hz | 120.7 dB | 96.1 dB | 106.1 dB | 116.1 dB |
| 50.0 Hz | 117.9 dB | 96.3 dB | 106.3 dB | 116.3 dB |
| 100 Hz | 122.4 dB | 96.9 dB | 106.9 dB | 116.9 dB |
Where an SPL curve rises above the Max SPL line, that power asks for more than the design can give. Here that first happens at 100 W, below 11.8 Hz; at 1000 W it is below 27.4 Hz. Low down the line is set by Xmax, so it is the cone that runs out first. The Max SPL line itself does not move with **Input power** or EQ: at 50 Hz it reads 117.9 dB at 10 W and at 1000 W.
> **Max SPL leaves out the port** Port air speed is not part of Max SPL. At 200 W the vented example is well under its Max SPL line from 32 Hz up, but its port is already past 17 m/s. Check **Port Velocity** too, or use Headroom, which counts it. [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port) brings it back under.
## Check a listening level: Headroom
Max SPL answers “how loud at most”. **Headroom** answers “can it play this level cleanly”, for music with peaks above its average, and it counts every limit, port air speed included.
1. **Add the tile.** Add **Headroom** with **Add tile**.
2. **Set the target.** Open its **Settings**. Under **Target level**, **Average** starts at the level the design already plays, at its loudest point. **Crest** is how far the peaks rise above the average, 12 dB unless you change it, and **Distance** is where you listen, 1 m to start with.
3. **Read the bands.** The coloured bands are what the design can play at each frequency: **Clean**, then **Threshold**, then **Over max**. Its average level is the solid line and its peaks the dashed one, drawn red where they are over the limit; **Tgt avg** and **Tgt peak** mark your target. Wherever the dashed line leaves the clean band, a limit is in the way.
> **The target and the power move together** Type a new **Average** and the enclosure’s **Input power** changes so its loudest point reaches it. Change the power and the target follows. Each enclosure keeps its own target.
The Headroom tile’s default limits, under **Limits** in its settings. Between the two columns is **Threshold**.
| Limit | Clean up to | Over max above |
| --- | --- | --- |
| Thermal power | 0.5 × Pe | 1 × Pe |
| Driver excursion | 1 × Xmax | 1.125 × Xmax |
| Port velocity | 17 m/s | 30 m/s |
| PR excursion | 1 × PR Xmax | 1.25 × PR Xmax |
## What limits what
| Limit | Where you see it | As power goes up | What helps |
| --- | --- | --- | --- |
| Cone travel past Xmax | **Excursion**; the Xmax line on **Max SPL (dB)**; **Headroom** | Grows with the square root of power | A high-pass below the tuning ([EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters)); less power |
| Voice coil heat | The thermal line on **Max SPL (dB)**; **Thermal power** in **Headroom** | Grows in step with power | Less power; more drivers to share it (**Number of drivers**); a driver with a higher rating |
| Port air speed | **Port Velocity**; **Headroom**. Not in Max SPL | Grows with the square root of power | More port area, less power ([Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port)) |
| Passive radiator travel | **PR Excursion**; **Max SPL (dB)**; **Headroom** | Grows with the square root of power | Less power; see [Passive radiator](https://simulator.00aud.io/docs/boxes/passive-radiator) |
Which limit comes first depends on the design and the frequency. The vented example runs out of cone travel below its 32 Hz tuning and of port air speed at it, long before its voice coil gets hot. Read the limits at the power you mean to use.
> **The limits are warnings, not ratings** The model is linear: a real driver softens as it nears Xmax, a hot coil compresses the output, and a port compresses before it chuffs. Design to stay clear of the lines rather than to sit on them.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver at other powers through the 00 Simulator connector, without changing your design.
> Using 00 Simulator, run each enclosure in my open workspace at 50 W, 100 W and 200 W without saving, and tell me for each power the peak cone excursion against Xmax, the peak port air speed against 17 m/s, and the Max SPL at 50 Hz.
---
# Fix a noisy port
> Bring a vented box’s port under the air speed warning in 00 Simulator: more port area, less power or a high-pass, and what each fix costs.
Source: https://simulator.00aud.io/docs/guides/noisy-port
A port chuffs when the air in it moves too fast. This guide takes the vented example from over the 17 m/s line to under it four ways, and shows what each fix costs: a longer port, less level or less bass.
## Check the port
1. **Open the example at 200 W.** [Open the vented example at 200 W](https://simulator.00aud.io/app?template=vented&power=200): the Ciare 12.00SW in 55 L, tuned to 32 Hz through one 100 mm port. It opens with the **Port Velocity** tile; in your own design, add it with **Add tile**.
2. **Read the peak against the line.** The curve is the air speed in the port at each frequency. The dashed line is the warning, 17 m/s unless you have changed it. Hover the curve to read the speed at a frequency.
3. **Read it at the power you will use.** Air speed follows the drive level. A port that is quiet at 10 W can chuff at 200 W, so set **Input power** first ([Power and limits](https://simulator.00aud.io/docs/guides/power-and-limits)).
_Figure: The Port Velocity tile for the vented example at 200 W: the air in its one 100 mm port peaks at 28.4 m/s near 30 Hz, over the 17 m/s line._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 100 mm port | 28.4 m/s | 30 Hz |
The air peaks at **28.4 m/s** near 30 Hz, a little below the 32 Hz tuning, where the port does most of the work. To bring it under 17 m/s you can give the air more room, send less power, or stop feeding the port the frequencies that drive it hardest.
> **Is the line right for your port?** Set it with **Port velocity** under **Settings › Simulation…**, from 10 to 30 m/s. The app’s hint says 15 to 20 m/s is typical, higher for flared ports. Change the line only for a port you will really build that way; it does not change the air speed.
## More port area
The same air through a bigger opening moves more slowly. The catch is length: to keep the same tuning, a port with more area has to be longer.
### Add a second port
1. **Open the port settings.** Select the enclosure. In the **Enclosure** panel, open **Port**.
2. **Set two ports.** Set **Number of ports** to 2. **Tuning** stays at 32 Hz, so the SPL curve does not move, and **Port length** grows to keep it. (If you last typed a **Port length**, the panel holds that instead and the tuning moves; type the tuning again to get it back.)
_Figure: Port Velocity with two 100 mm ports: the peak falls from 28.4 m/s to 14.2 m/s, under the 17 m/s line._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 100 mm port, 200 W | 28.4 m/s | 30 Hz |
| Two 100 mm ports | 14.2 m/s | 30 Hz |
Twice the area halves the speed: **14.2 m/s**. Each port is now 771 mm long instead of 356 mm, and the two take up 12.1 L of the box instead of 2.8 L. **Results**, under the port, shows it as **Port volume**, and **Gross volume** becomes 67.1 L: the box you build gets bigger, because the 55 L you set is the air around the ports.
### Use a wider port
1. **Widen the port.** In **Port**, raise **Diameter**. For this box, 130 mm is the smallest round port, in whole centimetres, that gets under the line.
2. **Check the length.** **Port length** follows: 624 mm.
_Figure: Port Velocity with one 130 mm port: the peak falls from 28.4 m/s to 16.8 m/s, just under the 17 m/s line._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 100 mm port, 200 W | 28.4 m/s | 30 Hz |
| One 130 mm port | 16.8 m/s | 30 Hz |
The peak falls to **16.8 m/s**, with less margin than two ports but a shorter port: 624 mm long, taking 8.3 L. For the model’s average air speed, total area is what counts: a slot port with the same area as the 100 mm round one peaks at the same 28.4 m/s. Shape, aspect ratio and the port ends still affect noise in a real port.
## Send less power
1. **Open Power.** In the Driver panel, open **Power**.
2. **Lower the input power.** Set **Input power** to 71 W. Air speed follows the square root of power, so the peak falls by the square root of the ratio.
_Figure: Port Velocity at 71 W instead of 200 W: the peak falls from 28.4 m/s to 16.9 m/s._
The same box at 71 W and 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 100 mm port, 200 W | 28.4 m/s | 30 Hz |
| One 100 mm port, 71 W | 16.9 m/s | 30 Hz |
71 W is the most this port takes and stays under the line: **16.9 m/s**. Nothing in the box changes, but everything is 4.5 dB quieter at every frequency. If the level matters more than the box size, a fix with more port area is the better trade.
## Add a high-pass
1. **Add the filter.** In the Driver panel, open **EQ / filters** and choose **Add** › **High-pass filter**. A new high-pass is Butterworth, 24 dB per octave.
2. **Set the cutoff.** Set **Cutoff** to 35 Hz, the lowest whole-hertz cutoff that brings this port under the line.
_Figure: Port Velocity with a 35 Hz high-pass: the peak falls from 28.4 m/s to 16.4 m/s._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 100 mm port, 200 W | 28.4 m/s | 30 Hz |
| 35 Hz high-pass | 16.4 m/s | 34 Hz |
The port peaks at **16.4 m/s**, but the filter has to sit above the 32 Hz tuning to do it, and that costs bass: F3 rises from 30.3 Hz to 36.8 Hz, and the level at the tuning drops 5.1 dB. A gentler 25 Hz high-pass moves F3 only to 31.1 Hz, and leaves the port at 26.0 m/s.
> **A high-pass is still worth having** Below the tuning the port stops holding the cone back, and a high-pass there keeps the cone inside Xmax. It just does not fix the port, which works hardest at the tuning itself. [Limits: travel, heat and air](https://simulator.00aud.io/docs/start/limits) shows a high-pass on the **Excursion** tile.
## Compare the fixes
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Fix | Peak air speed | What it costs |
| --- | --- | --- |
| None: one 100 mm port at 200 W | 28.4 m/s | Port 356 mm long, 2.8 L |
| [Two 100 mm ports](#add-a-second-port) | 14.2 m/s | Each 771 mm long, 12.1 L; gross volume 67.1 L |
| [One 130 mm port](#use-a-wider-port) | 16.8 m/s | 624 mm long, 8.3 L; gross volume 63.3 L |
| [71 W instead of 200 W](#less-power) | 16.9 m/s | 4.5 dB quieter everywhere |
| [35 Hz high-pass](#high-pass) | 16.4 m/s | F3 up to 36.8 Hz, 5.1 dB less at the tuning |
_Figure: Port length for each fix: one 100 mm port 356 mm, two ports 771 mm each, one 130 mm port 624 mm, against the 380 mm inside edge of a 55 L cube._
| Port | Length | Port volume | Gross volume |
| --- | --- | --- | --- |
| One 100 mm port | 356 mm | 2.8 L | 57.8 L |
| Two 100 mm ports | 771 mm each | 12.1 L | 67.1 L |
| One 130 mm port | 624 mm | 8.3 L | 63.3 L |
For scale, a 55 L cube is 380 mm along each inside edge.
Both port fixes need a port longer than the inside of a 55 L cube, so neither fits straight in a box that shape. Longer ports also resonate lower: the **1st port resonance** under **Results** falls from 482 Hz with one port to 222 Hz with two. Keep it well above the band the box plays.
- Fixes add up. A 120 mm port at 145 W peaks at 16.8 m/s, with a 526 mm port and 1.4 dB less level.
- Lowering the tuning is not a fix. At 28 Hz the peak only drops to 26.4 m/s and moves down with the tuning, while the port grows to 483 mm.
- Try each one without losing the original: duplicate the enclosure first and compare the two on the same tiles ([Compare designs](https://simulator.00aud.io/docs/guides/compare)).
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector, and can try each fix without changing your workspace.
> Using 00 Simulator, check the port air speed of every vented enclosure in my open workspace at its set power. Where it passes 17 m/s, try a second port, a wider port and a high-pass below the tuning without saving, and tell me each option's peak air speed, port length and what it costs in level or bass.
---
# EQ and filters
> Add high-pass, low-pass, parametric, shelf and Linkwitz filters to an enclosure in 00 Simulator, edit them on the graph, and protect the cone.
Source: https://simulator.00aud.io/docs/guides/eq-and-filters
Every enclosure has its own filters, in **EQ / filters** in the Driver panel. They shape the signal before it reaches the driver, so the output, the cone’s travel and the port’s air speed all follow them. The filter most boxes need is a high-pass just below the tuning.
## The six filters
**Add**, in **EQ / filters**, offers six kinds. Here is each one’s own gain:
_Figure: Six small plots of filter gain against frequency: a high-pass and a low-pass at 24 dB per octave, a parametric boost and a narrower cut, a low shelf up and a high shelf down, and a Linkwitz transform that boosts the lowest octaves._
Worked out with the app’s own filter maths. High-pass, low-pass and Linkwitz transform at the settings **Add** gives them; the others with example gains, since they start at 0 dB.
| Filter | Settings | Gain |
| --- | --- | --- |
| High-pass filter | 30 Hz · BW 24 dB/oct | −3.0 dB at 30 Hz, −24.1 dB an octave below |
| Low-pass filter | 120 Hz · BW 24 dB/oct | −3.0 dB at 120 Hz, −24.1 dB an octave above |
| Parametric EQ | 100 Hz, +6 dB at Q 1 | +2.8 dB an octave either side |
| Parametric EQ | 100 Hz, −6 dB at Q 4 | −0.1 dB an octave either side |
| Low shelf | 80 Hz · +6 dB | +4.0 dB at 80 Hz, +5.8 dB at 20 Hz |
| High shelf | 200 Hz · −6 dB | −3.0 dB at 200 Hz, −5.8 dB at 1 kHz |
| Linkwitz transform | 50 Hz, Q 0.707 to 25 Hz, Q 0.5 | +7.9 dB at 20 Hz, +1.1 dB at 50 Hz |
| Filter | Shown as | What it does | Settings |
| --- | --- | --- | --- |
| **High-pass filter** | `HP` | Rolls off everything below the cutoff, so the cone and port are spared bass the box cannot play. | **Cutoff**, **Type**, **Slope** |
| **Low-pass filter** | `LP` | Rolls off everything above the cutoff, as a subwoofer’s crossover to the mains does. | **Cutoff**, **Type**, **Slope** |
| **Parametric EQ** | `PEQ` | A boost or a cut around one frequency. | **Center frequency**, **Gain**, **Q (bandwidth)** |
| **Low shelf** | `LS` | Raises or lowers everything below its frequency. | **Shelf frequency**, **Gain** |
| **High shelf** | `HS` | Raises or lowers everything above its frequency. | **Shelf frequency**, **Gain** |
| **Linkwitz transform** | `LT` | Moves a sealed box’s roll-off from its own resonance and Q to a lower, gentler one, with boost. | **Source F₀ (Fc)**, **Source Q₀ (Qtc)**, **Target Fp**, **Target Qp** |
- **Cutoff**, **Center frequency** and **Shelf frequency** run from 10 Hz to 20 kHz, **Gain** from −15 to +15 dB, and **Q (bandwidth)** from 0.1 to 16: lower is wider.
- The Linkwitz transform takes a sealed box’s resonance and Q as its source (20–200 Hz, Q 0.3–2) and moves them to a target (10–100 Hz, Q 0.3–1.5). For a sealed box the enclosure panel shows both, as its system resonance (Fsc) and system Q (Qtc).
- A new filter starts at a sensible frequency (30 Hz for a high-pass, 120 Hz for a low-pass, 100 Hz for parametric EQ) and at 0 dB where it has a gain, so it changes nothing until you set it.
## High-pass and low-pass slopes
A high-pass or low-pass has a **Type**, the filter family, and a **Slope**, how fast it falls in dB per octave. A new one is **BW** at 24 dB/oct. Change the **Type** and it keeps the nearest slope the new family has.
| Type | Slopes | At the cutoff | Good for |
| --- | --- | --- | --- |
| **BW** | 6, 12, 18, 24, 36 and 48 dB/oct | −3 dB | The flattest passband. The usual choice for a subsonic high-pass. |
| **LR** | 12, 24 and 48 dB/oct | −6 dB | Sums flat with the matching filter at a crossover, so it is the one to cross a subwoofer to mains with. |
| **Bessel** | 12 and 24 dB/oct | −3 dB | The gentlest phase, and the softest knee. |
_Figure: A high-pass at 30 Hz drawn in five slopes: Butterworth 12, 24 and 48 dB per octave, Linkwitz-Riley 24 and Bessel 24._
The same 30 Hz high-pass in five slopes. Steeper slopes cut harder below the cutoff and leave more above it; they also turn the phase further near the corner.
| Slope | At 30 Hz | An octave below |
| --- | --- | --- |
| BW 12 dB/oct | −3.0 dB | −12.3 dB |
| BW 24 dB/oct | −3.0 dB | −24.1 dB |
| BW 48 dB/oct | −3.0 dB | −48.2 dB |
| LR 24 dB/oct | −6.0 dB | −24.6 dB |
| Bessel 24 dB/oct | −3.0 dB | −13.4 dB |
## Add, switch off and copy
1. **Select the enclosure.** Click its row in the enclosure list. Filters belong to one enclosure. A [multiple-entry horn](https://simulator.00aud.io/docs/horns/multiple-entry-horn) keeps a set per driver: pick the driver with the chips above its filters.
2. **Open EQ / filters.** It is in the Driver panel on the right. Its header counts the filters that are on.
3. **Add one.** **Add** › the kind you want. The new filter opens with its settings; click any filter’s row to fold or unfold it. If you have clicked a graph to lock its cursor, the new filter goes in at that frequency.
4. **Switch off or delete.** The tick box on a filter’s row turns it off and keeps its settings, the quick way to see what it does. The bin deletes it.
**Copy from...** appears once another enclosure, or another driver of a multiple-entry horn, has filters. It opens **Copy filters from**: choose a set and a copy of it replaces this enclosure’s filters.
> **Order does not matter** At each frequency the app adds up the gain of every filter that is on, so the order of the list changes nothing, and there is no way to reorder it. The total boost counts up to +30 dB at any one frequency.
## Edit filters on the graph
**EQ** in a tile’s header (**Edit EQ on graph**) draws the selected enclosure’s filters on that tile as handles, and **Exit** puts the tile back. It is on **SPL (dB)**, **Max SPL (dB)**, **Headroom**, **Excursion**, **Port Velocity** and **Transfer Function Magnitude**. The **EQ Editor** tile has its handles out all the time.
- A high-pass or low-pass is a triangle on a dashed line: drag it sideways to move the cutoff. Click it for its editor, where the `HP` or `LP` chip flips it between the two, with the frequency, **Type**, **Slope** and **Delete**.
- Parametric EQ and shelves are a dot: drag it sideways for frequency and up or down for gain. Selected, it shows a handle either side; drag those to make it wider or narrower. A shelf’s chip flips it between low and high.
- Right-click a graph for **Add filter**: each kind, placed at the frequency you clicked. The tile switches to EQ and the new filter opens.
- On a multiple-entry horn the other drivers’ filters show as dashed chips along the top; click one to edit that driver’s filters.
- On a phone, tap a graph to lock the cursor, then **EQ here** adds a filter at that frequency, and a selected filter’s editor opens as a sheet: [On a phone](https://simulator.00aud.io/docs/guides/phone).
**Undo** (⌘/Ctrl+Z) takes back filter changes like any other edit.
## Protect the cone with a high-pass
Below its tuning a vented box stops holding the cone back, and excursion climbs fast. In the 55 L vented example at 200 W, the Ciare 12.00SW passes its **13.5 mm** Xmax below 19 Hz. A 25 Hz high-pass at 24 dB/oct keeps it to **6.3 mm** and costs 0.6 dB at the 32 Hz tuning.
_Figure: Cone excursion of the vented example at 200 W with no filter, rising past Xmax below the tuning, and with a 25 Hz high-pass, staying well under it._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Excursion | Peak | At |
| --- | --- | --- |
| No filter | 21.2 mm | 10 Hz |
| High-pass 25 Hz, BW 24 dB/oct | 6.3 mm | 24 Hz |
_Figure: SPL of the same two runs: the high-pass takes the octave below the tuning away and leaves the tuning almost untouched._
The high-pass takes away the octave below the tuning, where the box makes little sound but the cone does most of its travelling.
| SPL (dB) | F3 | At 32 Hz | At 16 Hz |
| --- | --- | --- | --- |
| No filter | 30.3 Hz | 109.1 dB | 85.7 dB |
| High-pass 25 Hz, BW 24 dB/oct | 31.1 Hz | 108.5 dB | 70.4 dB |
The same box and power, 10 Hz to 200 Hz. 30 Hz is where **Add** puts a new high-pass.
| High-pass, BW 24 dB/oct | Peak excursion | Lost at 32 Hz | Peak port air speed |
| --- | --- | --- | --- |
| None | 21.2 mm and rising | 0 dB | 28.4 m/s |
| 20 Hz | 9.2 mm | 0.1 dB | 27.9 m/s |
| 25 Hz | 6.3 mm | 0.6 dB | 26.0 m/s |
| 30 Hz | 5.2 mm | 2.2 dB | 21.8 m/s |
- [Open the vented example](https://simulator.00aud.io/app?template=vented&power=200) at 200 W, add a **High-pass filter** and drag it on the **Excursion** tile until the curve sits under the Xmax line.
- Set it a little below the tuning. Higher protects more and costs more output at the tuning; the table shows the trade.
- A high-pass turns the phase, so group delay rises near the tuning: here from 26.7 ms to 41.7 ms at 32 Hz.
> **What the filters move, and what they do not** Filters change the drive, so **SPL (dB)**, **Excursion**, **Port Velocity**, **Cone Velocity**, **Phase** and **Group Delay** follow them, and **Headroom** counts them. **Impedance** and **Max SPL (dB)** do not change: Max SPL is the most each design can play before a limit, whatever the EQ.
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector, and can try filters without changing your workspace.
> Using 00 Simulator, try a 24 dB/oct Butterworth high-pass at a few frequencies below the tuning of each vented box in my open workspace, without saving. For each, tell me the peak excursion against the driver’s Xmax and how much output it costs at the tuning.
---
# Compare designs
> Compare enclosures in 00 Simulator: several designs on one graph, colours, eyes and solo, the Metrics and Compare tiles, and undo and saved versions.
Source: https://simulator.00aud.io/docs/guides/compare
Put the candidates in one workspace and every tile draws them together, one colour each. Duplicate, change one thing, then hide, solo and rank them until one wins.
## Several designs on one graph
Every visible enclosure in the workspace draws its own curve, in its own colour, on every tile. The quickest comparison is a copy with one thing changed. Here the vented example, and a copy made bigger and tuned lower:
_Figure: SPL of two vented boxes for the same driver at 200 W: the 55 L box tuned to 32 Hz, and a copy of 80 L tuned to 28 Hz that reaches lower._
Ciare 12.00SW at 200 W, half space, 1 m: Vented Example is 55 L tuned to 32 Hz, Vented Example 2 is 80 L tuned to 28 Hz. Simulated when this page was built.
| SPL (dB) | F3 | At 40 Hz |
| --- | --- | --- |
| Vented Example | 30.3 Hz | 110.1 dB |
| Vented Example 2 | 26.3 Hz | 108.5 dB |
1. **Duplicate.** Right-click the row › **Duplicate** (⌘D). The copy lands under the original as “Vented Example 2”, in a colour no other enclosure uses.
2. **Change one thing.** In the enclosure panel, set its **Volume** to 80 L and its **Tuning** to 28 Hz. The port length follows.
3. **Read the tiles.** The copy reaches lower (F3 26.3 Hz against 30.3 Hz) but its port runs faster: 33.4 m/s against 28.4 m/s on **Port Velocity**. That is the trade to judge.
- [Open the vented example](https://simulator.00aud.io/app?template=vented&power=200) at 200 W to try it.
- Hover a row in the list and its curve comes forward on every tile. Hover a hidden one and it shows dashed until you move on.
- For another type or driver, **Add new enclosure** at the foot of the list. Candidates for one question belong in one workspace, so they can share the graphs.
## Colours, eyes and solo
| To | Do this |
| --- | --- |
| Change a colour | Click the coloured dot on the row, or the swatch beside its name in a tile’s legend. |
| Take one off the graphs | Click its eye. It stays in the workspace and in the list. |
| Set several eyes at once | Press an eye and drag down the list: every row you pass takes the same state, as one undo step. |
| Show or hide them all | Click the count in the **Enclosures** header for **Show all**, **Hide all** and **Swap shown and hidden**. |
| Look at one alone | ⌥-click its eye (Alt-click on Windows and Linux), choose **Solo** from its menu, or press S with the list focused. ⌥⌘-click (Alt+Ctrl-click) adds another to the solo. |
| End a solo | Click the **SOLO** chip in the list header, or press Esc in the list. The eyes are as you left them. |
| Pick one to edit | Click its row, or its name in any tile’s legend. |
> **Name candidates in parts** Names split by ` | `, such as `Vented Example | 55 L` and `Vented Example | 80 L`, group into a family when the rows sit together: one label, with an eye and a fold for the lot. Copies with different drivers can be renamed that way in one go with **Name by driver** on the row menu.
Most of this has a key when the list has focus: [Keyboard shortcuts](https://simulator.00aud.io/docs/guides/shortcuts).
## Rank them with the Metrics tile
**Metrics**, under **Info** in **Add tile**, ranks every visible enclosure on one number and marks the best. Choose the number from its menu; some take a frequency or a band. A chip says which way wins, **Higher wins** or **Lower wins**, and each other row shows how far behind it is.
The Metrics tile’s own sums on the two runs above, at its default frequency and bands.
| Metric | Wins | Vented Example | Vented Example 2 |
| --- | --- | --- | --- |
| F3 (−3 dB) | Lower | 30.3 Hz · +4.0 Hz | 26.3 Hz · best |
| F10 (−10 dB) | Lower | 24.9 Hz · +2.8 Hz | 22.1 Hz · best |
| SPL at frequency, 40 Hz | Higher | 110.1 dB · best | 108.5 dB · −1.6 dB |
| Peak Xmax use over band, 20–80 Hz | Lower | 93% · +2% | 91% · best |
| Peak port velocity over band, 20–80 Hz | Lower | 28.4 m/s · best | 33.4 m/s · +5.0 m/s |
It offers F3 (−3 dB), F10 (−10 dB), SPL at frequency, Max SPL at frequency, Group delay at frequency, Average SPL over band, Peak Xmax use over band, Peak port velocity over band, Peak PR excursion over band, Minimum impedance over band and First port resonance. The tile’s own page explains each: [Metrics](https://simulator.00aud.io/docs/reference/tiles/metrics).
## Two quantities at once: the Compare tile
**Compare**, under **Graphs · advanced** in **Add tile**, draws two quantities for every visible enclosure on one frequency axis: the **Left axis** one solid and the **Right axis** one dashed, both in the enclosure’s colour. It starts on Excursion and Group Delay. Choose others in its settings, or one of its **Presets**:
- **Excursion + Group Delay**
- **SPL + Amplifier Load**
- **Impedance + Electrical Phase**
- **SPL + Excursion**
- **Max SPL + Limit Excursion**
- **Port Velocity + Excursion**
Use it to see why a design wins: where the excursion peaks against the group delay, or where the port speeds up against the cone. More on the tile: [Compare](https://simulator.00aud.io/docs/reference/tiles/compare).
## Try things and go back
- **Undo** and **Redo** (⌘/Ctrl+Z and ⌘/Ctrl+Shift+Z) step through your edits, tile moves included. The arrow between them lists the last six steps: choose one to undo back to before it.
- **History and saved versions…**, at the foot of that list, opens **Workspace history**. **This session** lists every step since you opened the workspace; signed in, **Saved versions** keeps a numbered version of each save to preview and restore.
- Signed in, a row’s menu has **Move to workspace** and **Copy to workspace**, to take a candidate to another workspace, or keep a finished one apart.
- A workspace your AI assistant starts for a new question is a draft. Drafts wait at the top of your library for **Keep**, and are archived after 7 days if nobody keeps them.
All of it, for guests and accounts: [Workspaces and accounts](https://simulator.00aud.io/docs/guides/workspaces).
## Ask your AI
**Ask your AI**
Your assistant adds the candidates to the same workspace, so they appear on your graphs next to the original.
> Using 00 Simulator, add two alternatives to the vented box in my open workspace, one bigger and tuned lower and one with twice the port area, then compare all three at their set power: F3, peak excursion against Xmax and peak port velocity.
---
# Layouts and pinned tabs
> Arrange the 00 Simulator dashboard: add, move and resize tiles, switch between the built-in layouts, save your own and pin up to 5 as tabs.
Source: https://simulator.00aud.io/docs/guides/layouts
The tiles on the dashboard, and where they sit, make a layout. Arrange them by hand, switch to one of the three built-in layouts, or save your own and pin it as a tab beside the switcher for one-click switching.
## Add, move and resize tiles
- **Add tile**, at the right of the layout bar, lists every tile in four groups, **Editor**, **Graphs · core**, **Graphs · advanced** and **Info**, with a search box. A tick marks the tiles already out, and choosing one of those scrolls to it. A new tile takes the first free space it fits.
- Drag a tile by its title (**Drag to move graph**). The tiles around it make room, a placeholder shows where it will land, and the rest close up behind it.
- Drag its right edge, bottom edge or corner (**Drag to resize**). The dashboard is four columns wide, and a tile can span one to four of them and be up to eight rows tall.
- **Expand to 2 columns** widens a tile to the full width and makes it taller; **Contract to 1 column** takes it back to half. **Remove graph** takes it off the dashboard.
- A new workspace starts with just **SPL (dB)**, and taking the last tile off brings it back.
The tiles and their places are part of the workspace: they save with it, and every add, move, resize and removal is a step for **Undo**. On a phone the same tiles page one at a time: [On a phone](https://simulator.00aud.io/docs/guides/phone).
## The built-in layouts
Three layouts come with the app, and all three start pinned as tabs:
_Figure: The three built-in layouts drawn as small dashboards: Basic with SPL (dB), Impedance and Excursion; Headroom with Headroom, Max SPL (dB) and Excursion; Horn Design with Horn Editor, SPL (dB), Impedance, Excursion and Group Delay._
Each layout as it lands on the four-column desktop grid.
| Layout | Rows, top to bottom |
| --- | --- |
| Basic | SPL (dB) across all four columns; Impedance two columns; Excursion two columns |
| Headroom | Headroom across all four columns; Max SPL (dB) two columns; Excursion two columns |
| Horn Design | Horn Editor across all four columns; SPL (dB) across all four columns; Impedance two columns; Excursion two columns; Group Delay two columns |
| Layout | Tiles | For |
| --- | --- | --- |
| **Basic** | SPL (dB), Impedance and Excursion | The response, the load the amplifier sees and the cone’s travel: where most designs start. |
| **Headroom** | Headroom, Max SPL (dB) and Excursion | How loud each design can go, and which limit stops it first. |
| **Horn Design** | Horn Editor, SPL (dB), Impedance, Excursion and Group Delay | Drawing a horn while its response, impedance, excursion and group delay follow. |
- Click a pinned tab, or open the switcher, the layout’s name at the left of the bar, and choose one under **Layouts** or **My layouts**.
- A layout brings only its tiles. Your enclosures, drivers and settings stay as they are.
- Leave tiles that were not saved as a layout and a note names the layout you switched to, with **Undo**. Leaving a saved layout you have not changed is quiet, since its tab brings it back.
## Save your own
When the tiles match no layout, the switcher reads **Custom layout** with a dot: these tiles are not saved. **Save as…**, in the switcher’s menu, keeps them as a layout of your own under a name, and **Pin to the header** in the same dialog is ticked unless the tabs are full.
- Change the tiles of a layout you are on and a dot appears beside its name, with **Revert** and **Save** in the bar. **Save** holds **Save as…** and **Discard changes**, and for a layout of your own an update that replaces its tiles with the ones on screen. The built-in layouts cannot be changed, only saved as a new one.
- You can keep 20 layouts of your own, each with a name of up to 60 characters.
- Your layouts and pins are kept in this browser, for your account. Another browser starts with the built-in three, while each workspace keeps its own tiles wherever you open it.
## Pinned tabs
A pinned layout is a tab beside the switcher, one click away. Basic, Headroom and Horn Design start pinned, and up to 5 can be.
- Pin or unpin with the pin on a layout’s row in the switcher’s menu (it shows when you point at the row), or in **Manage layouts…**. With 5 pinned the pin says **Unpin a layout first**.
- Right-click a tab for **Unpin**, **Move left**, **Move right** and **Manage layouts…**.
- Tabs that do not fit fold into a +N tab at the end; the tab you are on never folds. When the layout you are on is pinned, its tab names it and the switcher shrinks to its icon.
## Manage layouts and the layout menu
**Manage layouts…** is in the switcher’s menu, the layout menu and a tab’s right-click menu. It lists **Pinned to the header**, which you drag to reorder, then **Other layouts**. Every row has its pin and **Apply**; your own layouts add **Rename**, **Replace with current tiles** (for the one you are on) and **Delete**, while the built-in ones are marked **Built-in**. At the foot, **Save as new layout** saves the tiles on screen.
| Layout menu (⋯) | What it does |
| --- | --- |
| **Revert** | Puts the tiles back to the layout you are on, when you have changed them. |
| **Shrink charts** | Makes every tile half width and two rows tall. |
| **Reset tiles to default** | Back to what a new workspace starts with: **SPL (dB)**. |
| **Reset panels** | Puts the enclosure list back on the left and the Driver panel on the right, both open. |
| **Manage layouts…** | Opens the list above. |
## When your assistant arranges the tiles
Connected to your account, your AI assistant can put the tiles it is talking about on your screen. While it works, its activity takes the switcher’s place; the arrangement is only for the moment, and when it finishes you choose **Keep layout** or **Restore my layout**. More in [Watch it work live](https://simulator.00aud.io/docs/ai/live).
## Ask your AI
**Ask your AI**
Your assistant can arrange the tiles in your open tab while it explains them, and you decide afterwards whether to keep the arrangement.
> Using 00 Simulator, show the Headroom, Max SPL and Excursion tiles for my open workspace, then tell me for each enclosure which limit it reaches first and at what frequency.
---
# Workspaces and accounts
> Work as a guest in your browser, or sign in to keep workspaces in the cloud: sign-in, the workspace library, drafts, Recently deleted, undo and saved versions.
Source: https://simulator.00aud.io/docs/guides/workspaces
A workspace holds your enclosures, their drivers and the tiles you arranged. As a guest you have one, kept in this browser. Signed in, you can have many: they save to your account as you work, keep their earlier versions and open on any device.
## Guest or account
Your first visit starts you as a guest, with nothing to sign up for. An account is free.
| What | Guest | Signed in |
| --- | --- | --- |
| Where your work lives | In this browser only | In your account, on any device |
| Saving | Automatic, in this browser. **Save** offers **Download .00sim** for a copy | Automatic, to your account, as you work |
| Workspaces | One, the **Guest project** | Up to 250, in a library |
| Going back | **Undo** and this session’s history | **Undo**, this session’s history and every saved version |
| Your own drivers | In this browser | In your account, up to 1,000 drivers and 250 passive radiators |
> **Guest work lives in one browser** Clearing the browser’s data, or another browser or device, starts you afresh. **Save** in the header keeps it: **Download .00sim** for a file you can open again, or **Create free account** to move it to the cloud.
## Sign in
1. **Log in.** **Log in**, at the right of the header, or **Create free account** from **Save**.
2. **Choose a way in.** **Continue with Google**, or type your email and choose **Email me a sign-in code**. There is no password.
3. **Enter the code.** The email holds a 6-digit code: type it and choose **Verify code**. **Request another code** starts again if it expired. The same steps make an account if you have none.
- Your first sign-in turns this browser’s guest project, with your own drivers and passive radiators, into your first workspace. With nothing in the browser, you start with an empty one.
- Sign in later with guest work in the browser and **Import guest workspace?** asks: **Import** makes it a new workspace, **Skip** leaves it in the browser.
- Next time, a **Welcome back** screen offers the way you used last. **Continue as guest** is always there too.
**Account**, in the menu under your avatar, holds your **Sign-in methods** (**Change email** for an email account; a Google account’s address is managed at Google), which emails you get, your **Usage**, and **Delete account**: **Request deletion** hides your data at once and deletes it after 30 days.
## Switch and organise
Signed in, the header reads **Workspaces** › your workspace’s name.
- Click the name for **Recent** workspaces and **All workspaces**.
- The star beside the name pins it (**Pin workspace**), and the plus before **Workspaces** makes a **New workspace**.
- **Workspace actions** has **New workspace**, **Duplicate workspace**, **Rename workspace**, **Workspace history**, **Show info** and **Delete workspace…**.
- To move or copy enclosures between workspaces, right-click them in the list: **Move to workspace** or **Copy to workspace**.
## The workspace library
**All workspaces**, or **Workspaces** in the avatar menu, opens the library: every workspace you own, with a small plot of each one’s SPL.
- **New workspace** makes one; **Import** opens a project file as a new one: [Import and export](https://simulator.00aud.io/docs/guides/import-export).
- The search box (press /) looks through workspace names, enclosure names, drivers and enclosure types. Sort by **Last edited**, **Created**, **Last opened** or **Name (A–Z)**, as a **List view** or a **Grid view**.
- Workspaces are grouped by the date you sort on: Today, Yesterday, Previous 7 days, then by month; sorted by name they are one list. Pinned ones also sit on a **Pinned** shelf at the top.
- The arrow on a row shows the enclosures inside, with their type, drivers, volume, tuning and power, without opening it.
- **More actions** on a row: **Duplicate** (⌘D), **Rename**, **Export .00sim** and **Delete…**.
- The foot of the list counts your workspaces against the 250 you can keep.
## Drafts
A workspace is a draft until you claim it: one your AI assistant made, or a **New workspace** you left empty and unnamed. Drafts wait in a strip at the top of the library, apart from your workspaces, and stay out of **Recent**.
- Open the strip for **Keep** or the bin on each draft, or **Keep all** and **Discard all**. A discarded draft goes to **Recently deleted**.
- Editing, renaming, pinning, sharing or duplicating a draft keeps it too. Opening it does not: looking at a candidate is not keeping it.
- A draft nobody keeps is archived after 7 days, into **Recently deleted**.
- Drafts do not count towards your 250 workspaces; you can have up to 25 at once.
## Recently deleted
Deleting a workspace asks first, then moves it to **Recently deleted**, at the foot of the library, with drafts nobody kept. The app keeps them there for 30 days: choose **Restore** to bring one back.
## Undo, history and saved versions
- **Undo** and **Redo** in the header (⌘/Ctrl+Z and ⌘/Ctrl+Shift+Z; Ctrl+Y also redoes on Windows and Linux) step through your edits, tile moves and layout changes included. The arrow between them, or a right-click on **Undo**, lists the last six steps; choose one to undo back to before it.
- **History and saved versions…**, at the foot of that list, or **Workspace history** in **Workspace actions**, opens **Workspace history**.
- **This session** lists every step since you opened the workspace; choose one to go back to it.
- Signed in, **Saved versions** lists a numbered version for each save, with when it was made and by whom, you or your AI assistant. Choose one for a preview of what it held, then **Restore this version…** and **Restore version**: it becomes the newest version, and the ones before it stay.
- As a guest, **Saved versions** needs an account; **This session** still works.
## Limits
**Usage**, on your **Account** page, shows where you stand.
| What | Up to |
| --- | --- |
| Workspaces | 250 |
| Drafts, on top of those | 25 |
| One workspace | 2 MB |
| All your workspaces together | 100 MB |
| A file you import | 10 MB |
| Your own drivers | 1,000 |
| Your own passive radiators | 250 |
| Your drivers and passive radiators together | 25 MB |
## Ask your AI
**Ask your AI**
Signed in and connected, your assistant can read and tidy your workspaces. What it deletes goes to Recently deleted too.
> Using 00 Simulator, list my workspaces, say which are drafts and what enclosures each one holds, and ask me before deleting any of them.
---
# Settings and themes
> Every setting in 00 Simulator: light or dark mode, themes and the theme builder, the frequency axis, units, the upper-response model and the warning lines.
Source: https://simulator.00aud.io/docs/guides/settings
Where to change how 00 Simulator looks and what it warns you about. Everything here is under **Settings**, the cog at the right of the header, and none of it changes a design’s box or driver.
## The Settings menu
| Item | What it opens |
| --- | --- |
| **Display…** | Light or dark, the theme, the top of the frequency axis and the unit system. [Display](#display). |
| **Appearance…** | The theme builder, for a theme of your own. [Themes](#themes). |
| **Simulation…** | How the response is worked out above the bass, and the warning lines on the graphs. [Simulation](#simulation). |
| **Drivers…** | The driver library: the **00 Bits library** and the drivers you made or imported. [Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers). |
| **Passive radiators…** | The same library for passive radiators. |
> **On a shared design** A shared design’s page has only **Display…** and **Appearance…** in the menu, and its frequency axis stays as it was shared. The rest is for designs in your own workspace.
## Display
| Setting | Choices | What it does |
| --- | --- | --- |
| **Mode** | **Light**, **Dark**, **System** | **System** follows your computer or phone. Kept in this browser. |
| **Theme** | Default, Grosso, then any themes you have saved | Switches the app’s greys and lines. **Customise…** closes the dialog and opens the theme builder. [Themes](#themes). |
| **Upper frequency**, under **Axes** | **Auto**, 400 Hz, 1 kHz, 2 kHz, 5 kHz, **Custom** (20 to 20,000 Hz) | The right-hand end of every frequency axis, and the solver works up to it too. **Auto** is 400 Hz, or 2 kHz once the workspace holds a horn. Saved with the workspace. |
| **Unit system** | **Metric** or **Imperial** | Lengths and volumes in millimetres, centimetres and litres, or in inches and cubic feet. Saved with a signed-in workspace, and in this browser as a guest. |
> **Raise it to see the top end** A box speaker’s response above 400 Hz matters when you cross it over high, to a mid or a horn. Set **Upper frequency** to 1 kHz or 2 kHz and every tile, from **SPL (dB)** to **Impedance**, draws that far. Horns get 2 kHz on their own.
## Themes and the theme builder
A theme sets the app’s greys, lines and accent in both light and dark mode; it never changes an enclosure’s own colour. Default and Grosso are built in. As the Display dialog says, Grosso puts more contrast between the sections of the side panels: section headers stand out from the panel as bars, and fields sink to the background colour.
**Appearance…** opens the builder, **Appearance**, as a small palette over the dashboard. It has no backdrop, so the whole app is the preview, and you can drag it by its header to see either side panel. On a phone it is a sheet at the bottom of the screen.
| Part | What it changes |
| --- | --- |
| **Theme** and **Colour mode** | The theme you start from (**Built in** or **Yours**), and whether you are editing its **Dark** or **Light** version. |
| **Separation** | One slider for how strongly the panel sections stand apart: Default at 0, Grosso at 100, up to 160. |
| **Open section** | **Accent rail** draws a line in the section’s colour down an open section’s header; **Function tint** tints the header with it. |
| **Colours** | **Accent**, **Background** and **Text** for the mode you are editing. **Reset** puts one back to the app’s own. |
| **Advanced** | The 15 values behind **Separation** one by one: surfaces, hairlines, text, graph grids and more. Hover a name for what it touches. |
| **Contrast** | Checks for the mode you are editing. Text must reach 4.5:1, and field edges and the accent 3:1. A check that falls short says what to change, and **Fix** makes the change when one is enough; **Fix all** fixes several at once. Passing checks fold away. |
1. **Start from a theme.** Pick Default or Grosso under **Theme**. The built-in themes never change: the first edit starts an unsaved copy, and the header says so.
2. **Adjust it.** Move **Separation** first, then the rest. The app repaints as you drag, and **Contrast** warns you without stopping you.
3. **Save it.** **Save as…** names your copy. Once saved, **Save** writes later changes over it. You can keep 12 themes; signed in, they follow your account to other browsers.
The icons at the foot of the builder are **Import a theme** (paste one or choose a file), **Export this theme as a file**, **Copy the theme as JSON**, **Reset to the saved theme** and **Delete this theme**. A theme file is plain JSON, so you can pass one on.
> **Try Grosso first** If the side panels look flat to you, switch **Theme** to Grosso before you build your own. It sits at 100 on the **Separation** slider, so you can start from it and go further.
## Simulation
| Setting | Choices | What it does |
| --- | --- | --- |
| **Non-horn upper response** | **Estimated · BITS frequency limit** (the default) or **Physical model** | How SPL is worked out above the bass for every enclosure that is not a horn. Saved with the workspace. [How the two differ](#upper-response). |
| **Port velocity**, under **Warning thresholds** | 10 to 30 m/s in 1 m/s steps; 17 m/s to start | The dashed line on the **Port Velocity** tile. The dialog’s hint: 15 to 20 m/s is typical, higher for flared ports. [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity). |
| **Show Xmax reference lines** | On to start | The driver’s Xmax as a line on the **Excursion** tile. [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion). |
The two warning settings are kept in this browser, not in the workspace, so they apply to every design you open here. You can also change the port line from the **Port Velocity** tile: click the value in its header.
### Estimated or physical model
**Estimated · BITS frequency limit** treats the driver itself as flat and, when the driver’s data gives an upper frequency limit, rolls it off from there at 24 dB per octave. **Physical model** works the top end out from the driver’s parameters, voice coil inductance included. The box, the ports and your EQ apply either way, and **Impedance**, **Excursion** and **Phase** always use the physical model. Horns always use it too, which is why the setting says non-horn.
_Figure: SPL of the vented example with Non-horn upper response set to Estimated and to Physical model, from 20 to 400 Hz._
Ciare 12.00SW in the 55 L vented example at 1 W, half space, 1 m, up to the 400 Hz that Auto uses without a horn. Both curves come from one run of the solver when this page was built.
| SPL (dB) | Peak | At |
| --- | --- | --- |
| Estimated | 88.1 dB | 392 Hz |
| Physical model | 88.7 dB | 162 Hz |
| Frequency | Estimated | Physical model |
| --- | --- | --- |
| 50 Hz | 86.3 dB | 86.3 dB |
| 100 Hz | 86.9 dB | 87.9 dB |
| 200 Hz | 87.8 dB | 88.5 dB |
| 400 Hz | 88.1 dB | 85.7 dB |
Here the two stay within 1.1 dB of each other up to 100 Hz and part company above it: at 400 Hz the physical model reads 2.5 dB below the estimate. For a subwoofer that is crossed over low the choice hardly matters. For a box that plays higher, compare both before you trust the top octave, and [open this example](https://simulator.00aud.io/app?template=vented) to try it.
## Ask your AI
**Ask your AI**
The 00 Simulator connector can read, check and save themes on your account, so your assistant can make one to your description.
> Using 00 Simulator, save a theme based on Grosso with stronger section dividers, check its contrast in dark and light mode, and switch me to it once it passes.
---
# Keyboard shortcuts
> Every keyboard shortcut in 00 Simulator: undo and redo, the enclosure list, number fields, tiles, your workspaces, and search in the app, docs and gallery.
Source: https://simulator.00aud.io/docs/guides/shortcuts
Every keyboard shortcut 00 Simulator has, and the mouse moves that save a trip to a menu. On a Mac use ⌘ and ⌥; on Windows and Linux, Ctrl and Alt. The app writes them the same way, as ⌘/Ctrl+Z.
## Undo and redo
| Keys | What it does |
| --- | --- |
| `⌘/Ctrl+Z` | Undo the last change to the workspace. |
| `⌘/Ctrl+Shift+Z` | Redo it. |
| `Ctrl+Y` | Redo, on Windows and Linux. |
| Right-click **Undo** | The recent steps, to undo back to one, and **History and saved versions…**. |
| `Esc` | Closes the menu, dialog or popover that is open. In the **Appearance** palette it asks first if you have unsaved changes. |
Undo and redo work anywhere in the simulator, except while you are typing in a field (the field keeps its own undo) or another dialog is open. While your assistant is editing the workspace they point you to **Take control** instead.
## The enclosure list
Click in the list, or Tab to it, and these keys act on the selected enclosures, or on the one you have open when nothing is selected.
| Keys | What it does |
| --- | --- |
| `↑` `↓` | Open the enclosure above or below. |
| `Shift+↑` `Shift+↓` | Extend the selection up or down. |
| `Space` | Add the highlighted row to the selection, or drop it. |
| `⌘/Ctrl+A` | Select all. |
| `Esc` | Clear the selection; with nothing selected, end solo. |
| `Enter` | Rename the open enclosure. |
| `H` | Hide them, or show them if any are hidden. |
| `Shift+H` | Show all. |
| `S` | Solo them, so only they draw on the graphs. Press again to end solo. |
| `⌘/Ctrl+D` | Duplicate. |
| `⌘/Ctrl+Backspace` or `Delete` | Delete. One enclosure goes at once (undo brings it back); several ask first. |
| `⌥/Alt+↑` `⌥/Alt+↓` | Move up or down the list. |
| `⌥/Alt+Shift+↑` `⌥/Alt+Shift+↓` | Move to the top or the bottom. |
The right-click menu shows the same keys beside **Hide**, **Solo**, **Rename**, **Duplicate** and **Delete**, and the list menu beside **Select all** and **Show all**.
### With the mouse
| Move | What it does |
| --- | --- |
| ⌘-click (Ctrl-click on Windows and Linux) | Add a row to the selection, or drop it. |
| Shift-click | Select every row between the last one and this one. |
| Double-click a row | Rename it. |
| Drag a row | Move it up or down the list. |
| ⌥-click (Alt-click) an eye | Solo that enclosure. |
| ⌥⌘-click (Alt+Ctrl-click) an eye | Add it to the solo. |
| Press an eye and sweep over other rows | Show or hide them all the same way, as one undo step. |
## Number and name fields
| Keys | What it does |
| --- | --- |
| `↑` `↓` | Step the value up or down. |
| `Shift+↑` `Shift+↓` | A bigger step: ten steps, unless the field sets its own. |
| `Enter` | Keep what you typed. |
| `Esc` | Put the last good value back, or cancel a rename. |
A field’s step buttons show its step sizes the first time you hover them, under **Keyboard adjustment**. The fields in the [calculators](https://simulator.00aud.io/docs/guides/calculators) step the same way.
## In tiles
| Tile | Keys | What it does |
| --- | --- | --- |
| [Horn Editor](https://simulator.00aud.io/docs/reference/tiles/horn-editor) | Tab to a handle, then `←` `→` `↑` `↓` | Nudge it: a station’s area or position, a stuffing edge, the total length or the height. With `Shift`, ten times as far. |
| [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout) | Tab to the driver, then the arrows | Move it by 2% of the baffle’s shorter side, 8% with `Shift`. Needs baffle step on. |
| [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout) | Tab to an edge or corner handle, then the arrows | Change the width or height by 1 cm, 5 cm with `Shift`. |
| [Fold](https://simulator.00aud.io/docs/reference/tiles/fold), in **Draw** | Click the drawing, then the arrows | Extend the passage one cell up, down, back or to the front. |
| [Fold](https://simulator.00aud.io/docs/reference/tiles/fold), in **Draw** | `Backspace` or `Delete` | Remove the last cell. |
| [Fold](https://simulator.00aud.io/docs/reference/tiles/fold), in **Draw** | `Esc` | Cancel the drag in progress. |
| **Fold** › **Full screen** › **3D** | The arrows | Turn the cabinet 5° at a time, 15° with `Shift`. |
| **Fold** › **Full screen** › **3D** | `+` and `−`, `0` | Zoom in and out; `0` resets the zoom. |
## Your workspaces
On the page that lists [your workspaces](https://simulator.00aud.io/app/workspaces), signed in:
| Keys | What it does |
| --- | --- |
| `/` | Go to the search box, **Search names, enclosures and drivers**. |
| `↑` `↓` | Move from one workspace to the next. |
| `→` `←` | Open or close a workspace’s peek at its enclosures. |
| `⌘/Ctrl+D` | Duplicate the workspace under the pointer. |
More on the page itself in [Workspaces and accounts](https://simulator.00aud.io/docs/guides/workspaces).
## Help beside a tile
Choose the ⓘ in a tile’s header for a short explanation, what a healthy reading looks like and things to try. On a computer it stays open while you edit your design. **Full page** opens the complete reference in a new tab; **Ask AI** prepares a prompt for your own assistant. Use **Close help** or `Esc` to close the panel.
## Search and help
| Keys | Where | What it does |
| --- | --- | --- |
| `⌘/Ctrl+K` | Simulator, docs, [gallery](https://simulator.00aud.io/gallery) | Open search, except while another dialog is in use. |
| `/` | Simulator, docs, gallery | Open search, when you are not typing in a field or using another dialog. |
| `↑` `↓`, `Enter` | In search | Move through the results and open one. |
| `Tab` | The app or docs search field | Step through the scopes: All, Tiles, Pages, Terms, Sections, Calculators. |
| `⌘/Ctrl+Enter` | App or docs search | Hand what you typed to Ask your assistant, as a question. |
| `Esc` | In search | Close it. |
| `⌘/Ctrl+I` | Simulator or docs | Open or close Ask your assistant, unless you are typing in a field or using another dialog. |
| `⌘/Ctrl+Enter` | Ask your assistant | Copy the prompt with your question in it. |
In the simulator, **Info** › **Search workspace and docs** opens the same search. It can go to a tile already on your dashboard, explain a tile, or add an available tile when the layout is editable. Docs results open in a new tab. On the [docs home](https://simulator.00aud.io/docs), Tab to the search field and start typing: search opens with what you typed.
---
# On a phone
> How 00 Simulator works on a phone: one tile at a time, the dock with its power, EQ and layout sheets, the drawers, and what needs a computer.
Source: https://simulator.00aud.io/docs/guides/phone
00 Simulator runs on a phone with the same solver and the same tiles. The screen shows one tile at a time, the dock at the bottom holds what you change most, and the side panels become drawers.
_Figure: The vented example on a phone: the workspace menu at the top, the SPL tile, and the dock with a pill per tile, the add button, the power chip and the layout button._
The vented example at 200 W on a phone, as a guest. The tile is the solver’s curve for that design.
1. Workspace menu
2. The tile on screen
3. A pill per tile
4. Add or choose a graph
5. Input power
6. Layout
## The phone layout
Any window narrower than 768 pixels gets this layout: a phone, a small tablet held upright, or a narrow browser window on a computer. The header at the very top is the same as on a computer, with **Undo**, **Redo**, **Share**, **Export**, **Settings** and the rest as icons.
| Part | What it does |
| --- | --- |
| The cloud, top left | **Back to workspaces**, your saved designs. |
| The name in the middle | The workspace, or **Local workspace** as a guest. Tap it to rename a workspace of your own (**Rename workspace**). |
| The menu, top right | **Open workspace menu**: **Enclosures**, **Driver**, **Power**, **EQ** and **Environment**, each as a drawer. |
| The tile | One at a time, the full width of the screen. Swipe sideways for the next. |
| The dock | A pill per tile, **+** to add or choose one, the power chip and the layout button. |
## Enclosures and the Driver panel
- **Enclosures** slides in the enclosure list with the Enclosure panel below it, and **Measured traces** below that. Tap a row and it opens that enclosure and closes the drawer.
- **Driver**, **Power**, **EQ** and **Environment** open the Driver panel at that section, for the selected enclosure. [The workspace](https://simulator.00aud.io/docs/start/workspace#driver-panel) describes each one.
- Tap the dimmed page beside a drawer to close it.
## One tile at a time
- Swipe sideways to page through the tiles, or tap a pill in the dock. The pill of the tile on screen shows its name.
- **+** (**Add or choose a graph**) lists every tile by group. Choosing one already on the dashboard pages to it. The list has no search box on a phone, so the keyboard stays out of the way.
- Tap a graph to hold the readout at that frequency. The legend then offers **Note here**, and on tiles that take EQ, **EQ here** to add a filter right there.
- To edit EQ on a graph, tap **EQ** in its header. With no filters yet it says **Tap the response where you want a filter**.
## Help without leaving the tile
Tap the ⓘ in a tile’s header to open its help sheet. It explains what the tile shows, what a healthy reading looks like and what to try. Where the tile has a live reading, the sheet names the design and the computed frequency range, and updates as the design changes.
- **Full page** opens the tile’s complete reference in a new tab, keeping the simulator in place.
- **Ask AI** prepares a prompt about this tile for your own assistant. You can copy it, or open it in Claude or ChatGPT.
- **Search workspace and docs** searches the docs and offers ways to go to a tile, explain one, or add an available tile when the layout is editable. You can also reach it from **Info** in the app header.
- Tap **Close help**, or the dimmed page above the sheet, to return to the tile.
## The dock and its sheets
_Figure: The three dock sheets on a phone, each over the bottom of the tile: Input power with its slider, the EQ filter editor with a high-pass filter, and Layout with the layouts and the tiles in this one._
Values from the same example. A high-pass added from the EQ sheet starts at 30 Hz unless you are holding the readout at another frequency.
1. Input power
2. EQ filter
3. Layout
| Tap | Sheet | What is in it |
| --- | --- | --- |
| The power chip | **Input power** | The power as a number and on a slider whose marks you can tap. A multiple-entry horn shows a chip per driver first. |
| A filter on a graph | The EQ filter editor | A chip per filter, **+** (**Add another filter**), **Done**, and the chosen filter’s settings. A multiple-entry horn adds a row of driver chips. |
| The layout button | **Layout** | The current layout, or **Custom layout**, with **Revert**, **Save** or **Save as…** to keep what you changed; your layouts, pinned ones first, and **Manage…**; **Tiles in this layout**, each with a bin to remove it, and **Add tile**. |
- One sheet opens at a time: choosing a filter closes the power or layout sheet.
- A sheet sits over the dock and never changes the size of the graph above it, so EQ handles stay where your finger left them.
- Tap the grab handle at the top of a sheet, or swipe it down, to close it. The power sheet also closes when you tap outside it.
- The layout button shows a dot once you change the tiles of the layout you picked.
- While your assistant is editing the workspace, the dock shows what it is doing, with **Take control** in reach.
## What needs a computer
| On a computer | On a phone instead |
| --- | --- |
| Drag tiles to move and resize them, and **Expand to 2 columns** | Tiles fill the screen one at a time, in the layout’s order. Add and remove them from the **Layout** sheet. |
| Pinned layout tabs beside the layout switcher | Pinned layouts come first in the **Layout** sheet. |
| Side panels you drag to either side and resize | Drawers from **Open workspace menu**. |
| **Search tiles...** in the tile list | Scroll the list. |
| **Pin to side**, to keep a tile’s settings beside its chart | Settings open over the tile. |
| Right-click a graph for **Add filter** or **Add note** | Tap the graph, then **EQ here** or **Note here**. |
| Drop a measurement file on a tile | **Add measured trace** in the **Enclosures** drawer, or **Export** › **Measured trace…**. |
| The **Appearance** palette floats and drags | It opens as a sheet at the bottom. |
| [Keyboard shortcuts](https://simulator.00aud.io/docs/guides/shortcuts) | Taps and swipes. |
> **Arrange on a computer, read on a phone** A workspace keeps its tiles, so signed in you can set them up on a computer and page through the same ones on your phone. Layouts you save with **Save as…** stay in the browser you saved them in. [Open the vented example](https://simulator.00aud.io/app?template=vented&power=200) on your phone to try the dock.
## Ask your AI
**Ask your AI**
Your assistant can arrange the tiles in the tab you have open, on a phone too, and mark what to look at.
> Using 00 Simulator, put the Excursion and Port Velocity tiles of my open workspace on screen, and mark where each comes closest to its limit at the power I have set.
---
# Measured traces and notes
> Import REW, .frd, .zma and CSV measurements into 00 Simulator, link and align them with a design, style them, and pin notes to your graphs.
Source: https://simulator.00aud.io/docs/guides/measurements
Put a real measurement on the same graph as the simulation, line its level up with the design, and write notes on the graphs for whoever opens the design next. Traces and notes are saved with the workspace.
## Bring a measurement in
1. **Export it as text.** From your measurement software, export frequency and level per line, with phase if you have it: a REW text export, an .frd for SPL, a .zma for impedance, or a CSV.
2. **Drop it on the tile it belongs to.** Drag the file onto **SPL (dB)**, **Impedance**, **Phase** or **Max SPL (dB)**. The tile says **Drop to add a measured trace**, and the tile decides what the numbers are: ohms on **Impedance**, decibels on **SPL (dB)**. To paste a table instead, click the tile and paste.
3. **Check what was read.** The trace draws at once, linked to the enclosure you have selected. A card at the foot of the dashboard says what was **Added**: the file, its range, how many points and whether phase came with it. Change the link there, open **Details** or **Undo**. The card goes after 12 seconds, unless something failed or the file could be read two ways, when it waits with **Treat as**.
Two more ways in: **Add measured trace**, at the foot of **Measured traces** under the enclosure list, and **Export** › **Measured trace…** in its Import part. Both take several files at once. If the tile for a trace’s kind is not on the dashboard, it is added.
## What it reads
| Kind | Draws on | Comes from |
| --- | --- | --- |
| SPL | **SPL (dB)** | An .frd file; anything dropped on the tile; a table that looks like decibels |
| Impedance | **Impedance** | Every .zma file, wherever it lands; anything dropped on the tile; a table that looks like ohms |
| Phase | **Phase** | Anything dropped on the tile; a table that swings either side of zero |
| Max SPL | **Max SPL (dB)** and **Headroom** | Anything dropped on the tile; a short table of peak levels, such as a CEA-2010 result, when you choose it |
- Only lines that start with a number are read. Each is a frequency, a value and, optionally, phase in degrees, separated by spaces, tabs, commas or semicolons. Everything else is kept as the file’s header.
- A file added with **Add measured trace** or from the **Export** menu has no tile to go by, so unless it is a .zma or .frd its kind is guessed from the numbers. Whenever a file could be read two ways, the card asks with **Treat as**; a table of decibels with 64 rows or fewer is offered as **Max SPL** too.
- It needs at least 5 rows. A sweep with about 48 points per octave or more is stored on a 48-per-octave grid and drawn as a line; anything sparser, or 64 rows or fewer, is kept as it is and drawn as points.
- The header is read for the measuring software (REW, ARTA, CLIO, DATS, VituixCAD, Klippel, OmniMic), the date and any smoothing it already applied.
- A workspace holds up to 24 traces.
> **Not read yet** REW .mdat files, impulse responses (.wav), ARTA .pir files and Klippel exports. Export a frequency response as text from them first; the app says the same if you drop one.
## Link it and line it up
_Figure: The Measured traces section with one trace, linked to Vented Example, and its details open: Name, Kind, Linked to, the Display settings with Offset and Align…, and the measured conditions._
A sweep pasted onto **SPL (dB)** while Vented Example was selected, with its details open. Every setting shown is how a new trace starts.
1. Kind and the enclosure it measures
2. Level offset and Align…
3. How it is drawn
4. How it was measured
Click a trace in **Measured traces**, or its pill in a graph’s legend, to open its details.
| Setting | What it does |
| --- | --- |
| **Kind** | SPL, Impedance, Phase or Max SPL: which graphs the trace draws on. |
| **Linked to** | The enclosure this is a measurement of, or **Not linked**. A linked trace takes a shade of its enclosure’s colour, sits under it in the legend and hides with it; an unlinked one keeps its own colour. |
| **Offset** | Shifts the drawn level, from −60 to +60. The legend pill shows it whenever it is not zero. |
| **Align…** | Works the offset out for you: pick the enclosure to **Match** and a **Band** (60 to 120 Hz to start with), and it shows the new offset beside the old one and what is left over once it is applied (**Residual after aligning**, as an RMS). **Apply** stores it. |
> **Align takes out the constant, not the disagreement** A measurement at 2 m on a ground plane and a simulation at 1 m in half space differ by a fixed amount that says nothing about whether the model is right. Align removes that amount; the residual is how well the shapes agree over the band. Pick a band where the room and the microphone are not in charge.
> **Your numbers are never rewritten** Offset, smoothing and colour change only how a trace is drawn. **Export** in its details, or **Export** › **Measured trace…**, writes the stored values back as .frd (.zma for impedance, .csv for Max SPL), with any offset and smoothing noted in the header rather than applied.
## How a trace is drawn
| Setting | Choices |
| --- | --- |
| **Smoothing** | None, 1/48 octave, 1/24 octave, 1/12 octave, 1/6 octave, 1/3 octave. For sweeps; display only. |
| **Line** | Dotted for a sweep, dashed between points, or solid. A point trace can also have no line. |
| **Markers** | Dot, Ring, Square or Cross, for point traces. |
| **Colour** | From the enclosure, a shade of it when several traces share one, or a colour you pick. The arrow beside it goes back. |
- The eye on a trace’s row hides it everywhere. The eye on its legend pill hides it on that graph only.
- Each pill shows the trace’s badge (M1, M2…), its name, its offset when it has one, and its value at the cursor, so you can read it against the simulated curves.
- **Measured conditions**, all optional: **Distance**, **Space** (Half space, Full space, Quarter space, Eighth space or Ground plane), **Drive**, **Mic**, **Date** and **Notes**. Fill them in when you share a design, so others know how it was measured. The date comes from the file when it says.
## Graph notes
A graph note points something out on a graph, for you later or for whoever you share the design with. It is saved with the workspace, published with its shares and kept when someone makes a copy.
1. **Add one.** Right-click a graph and choose **Add note**: a point on an enclosure’s curve, a line at that frequency, a band around it or a level. Or click the graph to hold the readout and press **Note here**. On a phone, tap the graph, then **Note here**.
2. **Write it.** **Label on the graph** is the short label drawn on the chart, up to 48 characters. **Say more (optional)** takes up to 280. Switch between **Point**, **Line**, **Band** and **Level**, type exact frequencies, and pick the enclosure a point rides on or a mark takes its colour from.
3. **Keep it.** **Done** closes the note; a note closed with nothing written in it is removed, and Esc puts it back as it was. Click its label on the graph to edit it again, with **Delete**, **Delete all** and **Copy link** at the foot.
- Up to 6 notes on one graph and 30 in a workspace.
- Headroom, Compare, Metrics, Insights, Schematic, Horn Editor, Fold, Baffle Layout and T/S Parameters take no notes; the other graphs all do.
- Someone opening your shared design clicks a note’s label to read it and copy a link to it.
## Show or hide annotations
Beside **Undo** and **Redo**, a button (**Hide annotations**, then **Show annotations**) hides your notes and your assistant’s marks together, and brings them back. It only appears when there is something to hide, and adding a note turns annotations back on.
Your assistant’s marks are the numbered bands, lines, levels and points it draws while it explains a design through the 00 Simulator connector (`annotate_graphs`). They sit on the graphs in the tab you have open, never change the design, and clear themselves once the design changes. [Watch it work live](https://simulator.00aud.io/docs/ai/live) has more.
## Ask your AI
**Ask your AI**
The connector can import traces, compare them with a simulation and store the offset, so your assistant can check a build against its model.
> Using 00 Simulator, compare each measured trace in my open workspace with the enclosure it is linked to, between 40 and 200 Hz. Tell me the level offset, the RMS residual once that is removed, and where the largest remaining difference is. Do not apply the offsets yet.
---
# Share and publish
> Share a 00 Simulator design as a link: who can see it, guest links versus drafts, publishing to the Gallery, editing, deleting and your public profile.
Source: https://simulator.00aud.io/docs/guides/sharing
**Share** turns the enclosures you pick into a link anyone can open in 00 Simulator. Read who can see it before you press it: a link made as a guest is public straight away and listed in the **Gallery**, while signed in you get a private draft first.
_Figure: Two ways to share. As a guest: Share, then Create share link, and the link is public at once and listed in the Gallery. Signed in: Share, then Create draft, a draft only you can open, then Publish design, and the link is public, in the Gallery and on your profile._
Guest links go public in one step. Signed in, the link stays a private draft until you publish it.
- As a guest: **Share** → **Create share link** → public at once, and listed in the Gallery. You cannot edit, hide or delete it later.
- Signed in: **Share** → **Create draft** → a draft only you can open → **Publish design** → public, in the Gallery and on your profile. Manage it any time under **Shared links**.
## Share as a guest
> **Guest links are public and permanent** A link made without an account is published at once and listed in the **Gallery**, where anyone can find it. Nobody owns it, so it cannot be edited, taken out of the **Gallery** or deleted later. Sign in first if you might want to.
1. **Open the dialog.** Press **Share** in the header. **Share configuration** lists every enclosure in the project, all ticked.
2. **Choose what goes.** Untick the enclosures to leave out. **Name** suggests a title from the enclosures, and **Notes** takes a description, with Markdown.
3. **Make the link.** **Create share link** publishes it. **Share link created** shows the address, and **Copy link** puts it on your clipboard.
## Sign in, draft, then publish
Signed in, a share starts as a draft that only you can open: anyone else who tries the address is told it was not found. Publish it when it reads the way you want.
1. **Make a draft.** Press **Share**, untick what to leave out, check the **Name**, and press **Create draft**. The draft opens in a new tab, with the simulator still open in this one.
2. **Write it up.** The draft opens on its panel, marked **Draft · not yet published**. Give it a title, write **Design notes** (Markdown works) and, under **Links**, **Add link** for up to 12: discussion threads, GitHub, CAD files, cut lists, photos, videos or websites.
3. **Set the scene.** Collapse the panel to arrange the tiles, change the power or environment, and add notes to the graphs. The link keeps them as they are when you save.
4. **Save or publish.** **Save draft** keeps it private. **Publish design** makes it public and lists it in the **Gallery**; **Design published** gives you the link to copy.
Publishing gives the address the title’s words. The draft’s old address keeps working and leads to the same design.
## What a link carries
- The enclosures you ticked, with their drivers and passive radiators. Drivers you created go too, with every T/S value and their notes, so anyone who opens the link can use them.
- Every measured trace in the workspace. A trace linked to an enclosure you left out still goes, unlinked.
- Every note on the graphs, the tiles and their layout, and the environment: radiation space and listening distance.
- The **Name** and, for guests, the **Notes**; for drafts, the title, **Design notes** and **Links** you add later.
> **Check before you share** Measurements and graph notes go with every link, even ones about enclosures you left out. Delete any you would rather keep private before you share. [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements) shows where they are.
A link is a snapshot. Changes you make in your workspace afterwards do not reach it: share again for a link with the new design.
## Who can see it
| | Guest link | Draft | Published |
| --- | --- | --- | --- |
| Anyone with the address | Yes | No, only you | Yes |
| The **Gallery** | Yes, for good | No | Yes, until you hide it |
| Your public profile | No profile | No | Yes, until you hide it |
| Search engines | Can index it | No | Can index it |
| Edit, hide or delete later | No | Yes | Yes |
- The **Gallery** shows your account’s name and picture with each design you publish. Guest links show as a guest designer.
- The design’s own page names you by your username when your profile is public and has one, and by your account name otherwise. Your picture and a link to your profile appear only when your profile is public.
- The title you publish is what people see in the **Gallery**, in search results and in link previews.
- Views count other people opening a published link. Your own visits and drafts are not counted.
## Change a published design
- Open the link while signed in and press **Edit design** (**Edit** on the collapsed bar). Change the title, **Design notes**, **Links**, the tiles, the power, the environment or the graph notes, then **Save changes**.
- Everyone with the link sees the new version as soon as you save, at the same address.
- The enclosures themselves are fixed on the share page. To share a changed design, change it in your workspace and share it again.
- A draft you left shows **Resume** on its bar instead.
## Manage your links
**Shared links**, in the account menu under your avatar, lists your **Drafts** and **Published** designs with their views, and has a search. **Edit** opens a draft, **Open** a published design. **More actions** (⋯) on each:
| Action | What it does |
| --- | --- |
| **Copy link** | Copies a published design’s address. |
| **Hide from gallery** / **Show in gallery** | Takes it out of the **Gallery** or puts it back. The link still works. |
| **Hide from profile** / **Show on profile** | The same for your public profile. |
| **Delete…** | After you confirm, anyone who opens the link sees **Share link deleted**. Drafts can be deleted too. |
## Open a shared design
A shared link opens the design in the simulator with a bar at the top: who shared it, the title, **Notes** when there are any, **Files** and **Import**. Click the name on the bar for the full panel: notes, links, the enclosures, the notes on the graphs and any measurements.
- You can change the power, the environment and the tiles to explore it. The design itself is fixed, and nothing you do changes the original.
- **Files** (**Export files** in the panel) downloads it: **Project file** (`.00sim`), **WinISD project** (`.wpr`) or **Driver records** (`.wdr`). [Import and export](https://simulator.00aud.io/docs/guides/import-export) covers each.
- Signed in, **Import to my workspaces** opens **Import shared workspace**: name it under **Workspace name** and press **Import** for a new workspace of your own.
- As a guest, **Import to my simulator** loads it into this browser’s guest project. If that already holds a design, **Replace your browser draft?** asks first: **Replace browser draft** removes the current guest project, with the drivers and passive radiators you made in it, from this device.
## Your public profile
Your account comes with a profile page, and it is public unless you switch it off. After you sign in, **Set up your profile** asks for a picture, a **Name** and a **Username**; the page’s address is `/u/` followed by the username. **Skip for now** leaves it for later.
- It shows your name, picture and username, a bio and social profiles if you add them, when you joined, your published designs with their views, badges, and a graph of the days you used the simulator.
- Open it with **View public profile** in the account menu. On your own profile, a button leads to **Shared links**.
- Change it under **Account**: the **Public profile** switch (**Public** or **Private**), **Handle**, **Bio** and **Social profiles**, then **Save public profile**. **Public shares**, further down, has a switch per link: **On profile** or **Hidden**.
- A private profile has no page, but the **Gallery** still shows your account’s name and picture with each design you publish, and the design’s page shows your name.
## Ask your AI
**Ask your AI**
Your assistant can read and simulate your workspace through the 00 Simulator connector. Paste what it writes into **Design notes**; sharing and publishing stay with you.
> Using 00 Simulator, read my open workspace and simulate each enclosure at its saved power. Write a short design note for sharing it: the driver, box and tuning of each, its F3, and where excursion or port air speed runs out first.
---
# Import and export
> Move designs in and out of 00 Simulator: .00sim projects, WinISD projects and drivers, Hornresp records, measurements and other workspaces.
Source: https://simulator.00aud.io/docs/guides/import-export
Files go in and out through **Export**, the download icon in the header. It saves and opens `.00sim` project files, takes boxes to WinISD and horns to Hornresp, and brings in WinISD projects, measurements and enclosures from your other workspaces. Drivers have their own files, in the component library.
_Figure: The Export menu open under the download icon in the header. Export: Hornresp… (.txt), WinISD… (.wpr), 00sim project… (.00sim) and Measured trace…. Import: Open 00sim project… (replaces), WinISD…, From another workspace… and Measured trace… (.txt .frd .zma .csv)._
The **Export** menu in a signed-in workspace with a horn and a measured trace. An item that needs something the workspace lacks is greyed out or missing.
**Export**
- **Hornresp…** (`.txt`; reads “needs a horn” until the workspace has one)
- **WinISD…** (`.wpr`)
- **00sim project…** (`.00sim`)
- **Measured trace…** (when the workspace has measurements)
**Import**
- **Open 00sim project…** (replaces the open design)
- **WinISD…**
- **From another workspace…** (signed in)
- **Measured trace…** (`.txt`, `.frd`, `.zma`, `.csv`)
## Which file for what
In this table **Export** › is the header’s **Export** menu. Its top half writes files, and the items under its **Import** heading read them.
| File | Holds | Out | In |
| --- | --- | --- | --- |
| 00sim project, `.00sim` | A whole design: enclosures, drivers, measurements, graph notes and tiles | **Export** › **00sim project…** | **Export** › **Open 00sim project…**, or **Import** on **Workspaces** |
| WinISD project, `.wpr` | One box with its driver and filters | **Export** › **WinISD…** | **Export** › **WinISD…**, or **Import** on **Workspaces** |
| Hornresp record, `.txt` | A horn, as native Hornresp records | **Export** › **Hornresp…** | Not read |
| Driver, `.00dvr` or WinISD `.wdr` | One driver | **Settings** › **Drivers…** › **Export** | **Settings** › **Drivers…** › **Import** |
| Passive radiator, `.00prd` | One passive radiator | **Settings** › **Passive radiators…** › **Export** | **Settings** › **Passive radiators…** › **Import** |
| Unibox workbook, `.xlsx` | Enclosures, drivers and passive radiators | Not written | **Settings** › **Drivers…** › **Import** › **Unibox (.xlsx)** |
| Measurement, `.txt` `.frd` `.zma` `.csv` | One measured trace | **Export** › **Measured trace…** | **Export** › **Measured trace…** |
> **While your assistant is working** While an AI assistant is editing the workspace through the connector, design edits wait and the imports are greyed out. **Take control** hands the workspace back to you.
## 00sim project files
A `.00sim` file is 00 Simulator’s own format and keeps everything: the enclosures with their drivers and passive radiators, every measured trace and graph note, the radiation space and listening distance, the tiles and their layout, and your units. Use it for backups, to move a design between accounts, or to keep a guest project without signing in.
| To | Do this |
| --- | --- |
| Save some enclosures | **Export** › **00sim project…** opens **Export 00sim project**. Untick the enclosures to leave out and press **Export** for `project.00sim`. |
| Save a whole workspace | On **Workspaces**, open a workspace’s ⋯ menu and choose **Export .00sim**. The file takes the workspace’s name. |
| Keep a guest project | **Save** beside **Guest project** opens **Save this project**, and **Download .00sim** saves it. |
| Open one in a new workspace | On **Workspaces**, **Import** reads a `.00sim` or `.wpr` file into a new workspace and opens it. |
| Open one here | **Export** › **Open 00sim project…** (marked **replaces**) swaps the open design for the file’s: enclosures, measurements, notes, tiles, environment and units. |
> **Opening a file here replaces what is open** To keep the current design, open the file from **Workspaces** instead, where it becomes a workspace of its own.
Drivers in a file that match one you already have, by brand, model and T/S values, are used as they are. Others join your drivers, with “(Imported)” after the name when it is already taken by a different driver.
## WinISD
The WinISD items in the **Export** menu work with WinISD’s `.wpr` project files, one box each. The same item name appears twice: under **Export** it writes files, under **Import** it reads one.
### Export to WinISD
**Export** › **WinISD…** opens **Export WinISD project**, marked Beta. Tick the enclosures and press **Export**: you get a `.zip` with one `.wpr` file per enclosure. Anything simplified or left out is listed when the download starts.
| In 00 Simulator | In the .wpr |
| --- | --- |
| Sealed, Vented, Bandpass 4, Bandpass 6 | The same box type |
| Passive radiator loading, and horns | Skipped, with a warning |
| High-pass and low-pass filters | Kept, with the same order and cut-off. An alignment other than Butterworth is not kept, with a warning |
| Parametric EQ and Linkwitz transform | Kept |
| Shelf filters, and filters switched off | Left out |
| A series capacitor | Left out, with a warning: WinISD cannot model one |
### Import from WinISD
- **Export** › **WinISD…** under **Import** reads one `.wpr` file and adds its box beside your enclosures, selected. Nothing already there changes.
- The new enclosure takes the project’s description as its name, or the file name. Sealed, vented, fourth-order and sixth-order bandpass boxes come in as themselves; any other box type comes in as vented, with a warning.
- High-pass, low-pass, parametric EQ and Linkwitz transform filters come with it. Other filter types are skipped, with a warning.
- The project’s driver comes too, matched to one of yours or added as described above.
For single WinISD drivers, use the `.wdr` files under [Drivers and passive radiators](#drivers-and-radiators). [The WinISD comparison](https://simulator.00aud.io/validation/winisd) shows how closely the two programs agree on the same boxes.
## Hornresp
**Export** › **Hornresp…** opens **Export Hornresp projects** once the workspace has a horn. Pick the horns and download a `.zip` of native Hornresp records with import instructions. Hornresp files cannot be opened in 00 Simulator. [Hornresp export and validation](https://simulator.00aud.io/docs/horns/hornresp#export) covers what each horn type becomes and what carries over.
## Drivers and passive radiators
**Settings** › **Drivers…** opens the **Component library**. On your own list of drivers:
- **Export** opens **Export drivers**. Choose the format, **00 Audio driver** (`.00dvr`) or **WinISD driver** (`.wdr`, Beta), tick the drivers (your own start ticked) and press **Export** for one file per driver.
- **Import** › **Driver file (.wdr, .00dvr)** (Beta) reads both formats, several files at once.
- **Import** › **Unibox (.xlsx)** opens **Import from Unibox**, which brings in the enclosures, drivers and passive radiators in a Unibox workbook.
- **Settings** › **Passive radiators…** does the same for passive radiators, in 00 Simulator’s own `.00prd` format only.
Creating, pasting and editing drivers is in [Drivers: find, create, import](https://simulator.00aud.io/docs/guides/drivers).
## Measurements
**Export** › **Measured trace…** under **Import** reads REW text exports, `.frd`, `.zma` and `.csv` files, several at once. Under **Export**, **Measured trace…** lists the workspace’s traces and saves one: impedance as `.zma`, Max SPL as `.csv` and the rest as `.frd`. [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements) covers importing, aligning and comparing them.
## From another workspace
Signed in, **Export** › **From another workspace…** opens **Import from workspace**. It copies enclosures from one of your other workspaces into this one.
1. **Find the workspace.** Pick it from the list on the left, or type in **Search workspaces…**.
2. **Tick the enclosures.** Its enclosures load on the right, all ticked. **Select all** and **Clear** help with long lists.
3. **Import them.** The **Import** button counts the enclosures it will copy. Their boxes, drivers and EQ come across; this workspace keeps its own environment and tiles.
To send enclosures the other way, select them in the enclosure list, right-click, and choose **Copy to workspace** or **Move to workspace**.
## From a shared link
A shared design has **Files** on its bar: **Project file** (`.00sim`), **WinISD project** (`.wpr`) and **Driver records** (`.wdr`). **Import** puts the whole design in your account or your browser: [Open a shared design](https://simulator.00aud.io/docs/guides/sharing#open-a-shared-design).
## Ask your AI
**Ask your AI**
Your assistant can import measurements and compare them with the simulation through the 00 Simulator connector. Project files and WinISD exports stay in the app’s **Export** menu.
> Using 00 Simulator, import the REW measurement I paste below into my open workspace, link it to the enclosure it measures, and compare it with that enclosure’s simulation from 30 to 200 Hz: tell me the level offset and where the two differ most.
---
# Calculators
> The six free 00 Simulator calculators: what each one answers, what they share with the simulator, and when to open the simulator instead.
Source: https://simulator.00aud.io/docs/guides/calculators
Six free calculators each answer one box question in the browser, with no account: a port length, a box volume, sealed or ported. They run the simulator’s own model, so their numbers match the app’s closely. Open the simulator when the design needs more than one answer.
## The six calculators
| Calculator | What it answers | Needs a driver | Into the simulator |
| --- | --- | --- | --- |
| [Bass-reflex port calculator](https://simulator.00aud.io/calculators/bass-reflex-port) | How long to cut a port for a box and a tuning (**Port length**), or the tuning a port you have gives (**Tuning**). **Round** or **Slot**, one port or several, drawn to scale. | No | **Simulate it with a driver** |
| [Port velocity calculator](https://simulator.00aud.io/calculators/port-velocity) | How fast the air moves in a port across the bass range, with a real driver, power and an optional high-pass, and the cone excursion alongside. | Yes | **Open in the simulator** |
| [Speaker box volume and dimensions calculator](https://simulator.00aud.io/calculators/speaker-box-volume) | Net volume from a box’s **Outside** or **Inside** sizes (**Volume**), the depth for the volume you need (**Depth**), or a whole box in good proportions (**Box size**), allowing for the panels and what sits inside, with a cut list. | No | **Tune a port for this box** takes the volume to the port calculator |
| [Sealed box calculator](https://simulator.00aud.io/calculators/sealed-box) | The box volume for the Qtc you want (**Box volume**), or the Qtc of a box you have (**Qtc**), with the response, F3 and cone excursion. | Yes | **Open in the simulator** |
| [Ported box calculator](https://simulator.00aud.io/calculators/ported-box) | A box volume and tuning that suit the driver, with the port to build, the response against the same driver sealed, cone excursion and port air speed. | Yes | **Open in the simulator** |
| [Subwoofer box calculator](https://simulator.00aud.io/calculators/subwoofer-box) | Sealed or ported? Starting boxes for the driver side by side, by size, extension, level at your power and the most each can play, with a pick for **Compact**, **Balanced** or **Deep**. | Yes | **Open the pick in the simulator**, or **Simulator** on any box |
All six are listed together at [Calculators](https://simulator.00aud.io/calculators). Each links to the others that pick up where it stops: the box volume calculator’s **Sealed or ported?** leads to the subwoofer box calculator, for example.
## What they share
- _A driver._ The calculators that need one start on an illustrative 12-inch woofer marked **Example**. Search the driver library by brand or model, **Paste T/S values** from a spec sheet, or **Edit T/S** to type them in.
- _Units._ The switch at the top reads **mm · L** or **in · ft³**.
- _A link._ **Copy link** copies an address that reopens the calculator with your numbers. **Reset to the example** starts again.
- _The model._ The calculators with a driver run the simulator’s model in half space at 1 m, with one simplification: they leave out the driver’s voice coil inductance, which only rolls off the top of the range. The simulator includes it.
## The same model as the simulator
The [vented example](https://simulator.00aud.io/app?template=vented) is a 55 L box tuned to 32 Hz with one 100 mm port. The port calculator cuts that port to **355.6 mm**, and the simulator’s **Port length** reads the same.
_Figure: The Bass-reflex port calculator’s side section of a 100 mm port cut to 355.6 mm for a 55 L box tuned to 32 Hz, beside the simulator’s Enclosure panel for the same box, showing a Port length of 355.6 mm._
The same 55 L, 32 Hz box in the port calculator and in the simulator, with the same end corrections. Worked out when this page was built.
| | Port length |
| --- | --- |
| Bass-reflex port calculator | 355.6 mm |
| 00 Simulator, Enclosure panel | 355.6 mm |
The port calculator shows more about the port itself: the effective length the air behaves as, other port sizes for the same tuning, a guide to trimming a port to tune it, and a check that it fits a box of a given depth. [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports) explains the effective length.
## Take a design into the simulator
1. **Press the button.** At the foot of a calculator, **Open in the simulator** (or **Simulate it with a driver** on the port calculator) opens the simulator with the design in the address.
2. **Check it.** A dialog shows what will be added: **Inspect this vented design** or **Inspect this sealed design**, with the driver, box and power. The port calculator has no driver, so **Check this port with your driver** asks for one first.
3. **Add it.** **Create vented design** or **Create sealed design** adds it as a new enclosure beside the ones already there, and saves its driver to your own drivers if it is not there yet.
## When to open the simulator instead
The calculators cover sealed and vented boxes with one driver, in half space at 1 m. Open the simulator when you need:
- _Other box types._ Passive radiators, fourth- and sixth-order bandpass boxes and eight kinds of horn: [Choose an enclosure type](https://simulator.00aud.io/docs/start/enclosure-types).
- _Several boxes on one graph._ Every enclosure in a workspace draws its own curve: [Compare designs](https://simulator.00aud.io/docs/guides/compare).
- _More graphs._ Impedance, group delay, phase and the most each design can play before it reaches a limit: [All tiles](https://simulator.00aud.io/docs/reference/tiles).
- _The rest of the system._ Several drivers and their wiring, series resistance, full EQ, the radiation space and listening distance: [Power and limits](https://simulator.00aud.io/docs/guides/power-and-limits) and [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters).
- _To keep and share it._ Signed in, workspaces save as you go, and any design can be shared as a link: [Share and publish](https://simulator.00aud.io/docs/guides/sharing).
- _To check a build._ Import a measurement and compare it with the simulation: [Measured traces and notes](https://simulator.00aud.io/docs/guides/measurements).
## Ask your AI
**Ask your AI**
Your assistant can size, add and simulate boxes through the 00 Simulator connector, with the same model the calculators use.
> Using 00 Simulator, suggest a sealed and a vented box for the Ciare 12.00SW, add both to my open workspace, and compare their F3, peak cone excursion and peak port air speed at 200 W.
---
# What your assistant can do
> What Claude, ChatGPT or another assistant can do with 00 Simulator: find drivers, build and simulate designs, show you graphs and check a build.
Source: https://simulator.00aud.io/docs/ai
Connect 00 Simulator to Claude, ChatGPT or Claude Code and your assistant can do the legwork of a design: find a driver, build candidates in your workspace, run them through the same solver as the app and show you the graphs. You set the goal and the limits; every number it quotes comes from a simulation.
_Figure: An assistant session: the prompt, the 5 tools it calls, its reply and the simulated SPL of the vented example._
The wording is an example; the tools are the connector’s own, and the numbers and curve are the solver’s, run when this page was built.
Prompt: “Using 00 Simulator, design a vented box around a Ciare 12.00SW and show me the SPL and excursion at 100 W.”
Tools it calls: `search_drivers` (Ciare 12.00SW), `get_driver` (T/S parameters), `create_workspace` (Vented), `simulate_workspace` (100 W · half space · 1 m), `render_simulation_graphs` (SPL, excursion).
Reply: “Here is a vented box for the Ciare 12.00SW. Net volume 55 L, −3 dB 31 Hz, and 108 dB at 100 W in half space. From 20 to 300 Hz, peak excursion is 8.9 mm, comfortably inside the 13.5 mm Xmax.”
## How it works
- 00 Simulator is a connector (a remote MCP server at `https://simulator.00aud.io/mcp`) that gives your assistant 39 tools. It chooses which to call, and when, from what you ask.
- It works on your own workspaces, through your account, once you approve it. [Connect your assistant](https://simulator.00aud.io/docs/ai/connect) takes a couple of minutes.
- Its numbers come from the app’s own solver. The connector tells it never to invent a simulation value, and to try experiments without saving them.
- Keep the workspace open in 00 Simulator and you watch it work there: [Watch it work live](https://simulator.00aud.io/docs/ai/live).
> **No AI of our own** The thinking is your assistant’s; the physics is the solver’s. 00 Simulator has no chatbot. The Ask AI button on these pages writes a prompt for your own assistant to answer.
## What it can do
The jobs below follow a design from driver to build, then the ones outside that run. [Tools](https://simulator.00aud.io/docs/ai/tools) lists all 39 one by one.
### Pick a driver
Search simulation-ready drivers by name or Thiele/Small filters, read one in full, and check a set of parameters for missing fields and contradictions.
Tools: `search_drivers`, `get_driver`, `validate_driver`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#find-a-driver)
### Design
Suggest a starting alignment, read the fields each enclosure type takes, then build and edit candidates in a workspace of your own.
Tools: `suggest_enclosure`, `get_enclosure_schema`, `create_workspace`, `list_workspaces`, `get_workspace`, `add_enclosure`, `update_enclosure`, `update_workspace`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#design-and-compare)
### Simulate
Run the solver on a saved version, including horns, EQ and multiple-entry drivers, and read the numbers back.
Tools: `simulate_workspace`, `get_simulation_results`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#fix-a-problem)
### Show you
Draw graphs in the conversation, with power and EQ controls you can adjust, arrange the dashboard in your open tab around what is being explained, and mark the frequencies worth looking at.
Tools: `render_simulation_graphs`, `show_graphs`, `annotate_graphs`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#on-your-graphs)
### Check the build
Bring in a real measurement, such as a REW export, link it to the design it measures, and compare the two: the level difference and the shape difference are reported separately.
Tools: `import_trace`, `compare_trace`, `list_traces`, `get_trace`, `update_trace`, `delete_trace`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#check-a-build)
### Keep or undo
Finish with a summary you can undo in one go, restore any saved version, and clear away the candidates and workspaces that did not work out.
Tools: `end_workspace_session`, `list_workspace_revisions`, `get_workspace_revision`, `restore_workspace_revision`, `remove_enclosure`, `delete_workspace`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#tidy-up)
### Look it up
Search the 00 Simulator docs and read a page or one section of it, so answers about the app and what a result means quote the docs and link to them.
Tools: `search_docs`, `read_doc`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#explain-a-result)
### Appearance
Build an app theme for you, for instance more contrast between the side-panel sections, check it against the contrast floors, and switch to it when you ask.
Tools: `get_theme_schema`, `list_themes`, `get_theme`, `save_theme`, `activate_theme`, `delete_theme`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#appearance)
### Fold a horn
Fold a horn into a cabinet the way the Fold tile does, with other layouts, fixes and the folded horn to simulate beside the target, then export the saved fold as a Boundary Lab project to solve in 3-D.
Tools: `fold_horn`, `export_boundary_lab`. [Prompts for this](https://simulator.00aud.io/docs/ai/prompts#horns)
### Its own limits
List the workspace operations this connection allows and the permission each one needs.
Tools: `list_workspace_capabilities`.
## Where you see the results
| Where | What you get |
| --- | --- |
| In the conversation | Graph tiles from a simulation it ran, up to 6 at a time: SPL, Max SPL, Impedance, Phase, Group delay, Excursion, PR excursion, Port velocity, Rear port velocity, Apparent power, Current draw. Ask for power and EQ controls and you can change one enclosure’s power and filters in the chat and see its curves re-solved; nothing is saved until you apply it. See [Graph kinds](https://simulator.00aud.io/docs/ai/graph-kinds). |
| In your open tab | Its edits land in place, and it can bring up to 6 tiles to the front and mark them. See [Watch it work live](https://simulator.00aud.io/docs/ai/live). |
| Later | It works with the app closed too; its saved versions wait in your workspaces. A workspace it creates starts as a draft and is archived after 7 days unless you keep it: **Keep all** in your workspace list, or **Keep workspace** when it hands back. |
## What it won’t do
- Make up numbers. Every figure it quotes should come from a simulation it ran; if an answer has a number and no run behind it, ask it to simulate.
- Save your experiments unasked. It tries changes as temporary edits and saves only the ones you ask for, each as a new saved version you can go back to.
- Share or publish. It cannot create share links, so nothing becomes public without you.
- Delete without asking. It asks before deleting a workspace it did not make in the same conversation, and a deleted workspace can be restored for 30 days.
- Reach other designs. It sees only your own workspaces: not other people’s, and not designs you made as a guest, which stay in your browser.
> **A driver it can’t find** Paste the T/S parameters from the datasheet. It checks them for missing values and contradictions, then builds the enclosure with that driver inside it.
## Get started
1. **Connect it.** Add the server URL to Claude, ChatGPT, Claude Code or another MCP client, then sign in and approve it. [Connect your assistant](https://simulator.00aud.io/docs/ai/connect)
2. **Open a workspace.** Optional, but then you watch the work happen: open the workspace in 00 Simulator, signed in to the same account.
3. **Ask.** Start with “Using 00 Simulator,” and say what you want and the limits that matter. [Prompts that work](https://simulator.00aud.io/docs/ai/prompts)
**Ask your AI**
Your assistant reads the driver from your workspace, starts from the app’s own box suggestions and simulates both with the same solver.
> Using 00 Simulator, suggest a sealed and a vented box for the driver in my most recent workspace, add both to that workspace, and compare their F3, box volume and peak excursion at the saved power.
---
# Connect your assistant
> Add 00 Simulator to Claude, ChatGPT, Claude Code or another MCP client: the server URL, the steps for each app, and what you approve.
Source: https://simulator.00aud.io/docs/ai/connect
00 Simulator is a connector: a remote MCP server your assistant adds by its URL. Add it, sign in with your 00 Simulator account and approve it, and your assistant can open your workspaces, run the solver and show you the graphs. It takes a couple of minutes.
## What you need
- **Server URL:** `https://simulator.00aud.io/mcp`
- **Account:** A free 00 Simulator account with a verified email address.
- **Assistant:** Claude, ChatGPT, Claude Code, or another client that takes remote MCP servers with OAuth sign-in.
Your assistant’s own plan decides whether you can add a custom connector; the notes under each app below say which plans can.
## Set it up
Choose your app and follow its steps. The server URL has a Copy button wherever a step needs it. Signed in here, a line under the steps waits for the connection and turns green once you approve it.
_Figure: Set-up steps for Claude, ChatGPT, Claude Code and other MCP clients, one tab each, with the server URL to copy._
Claude (claude.ai):
1. Open Customize, then Connectors.
2. Choose Add custom connector and paste the server URL.
3. Choose Add. If Claude asks how to register the client, pick Register automatically.
4. Sign in to 00 Simulator and approve the connection.
5. In a chat, open the + menu, go to Connectors and switch 00 Simulator on.
Custom connectors work on Claude’s Free plan (one connector) and on paid plans. On Team and Enterprise plans, an owner adds the connector in Organization settings first.
ChatGPT (chatgpt.com):
1. In Settings, open Security and login and turn on Developer mode.
2. Go to chatgpt.com/plugins, choose +, name the app 00 Simulator and paste the server URL, including /mcp.
3. In a chat, open the + menu, choose Developer mode and select 00 Simulator.
4. Sign in to 00 Simulator when the first tool runs.
Developer mode is on the web for Plus, Pro, Business, Enterprise and Education plans. OpenAI marks developer mode as elevated risk, and ChatGPT asks before running tools that write, including saving edits and storing a simulation run.
Claude Code (terminal):
Add the server:
```
claude mcp add --transport http 00-simulator https://simulator.00aud.io/mcp
```
Then sign in from Claude Code:
```
/mcp
```
Add `--scope user` to use it in every project. Claude Code needs a Pro, Max, Team, Enterprise or Console account.
Other MCP clients:
- Transport: Streamable HTTP
- Server URL: `https://simulator.00aud.io/mcp`
- Sign-in: OAuth 2.1 with PKCE and dynamic client registration
- Account: A 00 Simulator account with a verified email address
A client that supports remote servers with OAuth sign-in should connect with these details. Client support varies, so check your client’s MCP documentation.
Menu names change as these apps update. If a step doesn’t match what you see, look for custom connectors or developer mode in the app’s settings.
## Check it works
1. **Switch it on in a new chat.** In Claude and ChatGPT, switch 00 Simulator on in the chat from its + menu, as your app’s steps say. Claude Code has nothing to switch: once the server is added and you have signed in with `/mcp`, its tools are there in every session.
2. **Ask something small.** Ask it to list your workspaces, as in the prompt below. It reads them from your account, so the names should be yours.
3. **Look in the app.** In 00 Simulator, open **AI** in the header (a robot icon on narrow screens). **Connections** shows how many assistants are connected to your account.
**A first question**
It reads your workspaces and opens the most recent one, without changing anything.
> Using 00 Simulator, list my workspaces and tell me which enclosures and drivers are in the one I opened last.
## What you are approving
Connecting needs a free account with a verified email address. When you sign in, a consent page lists the access your assistant is asking for, and you choose **Approve** or **Deny**. Once you approve it:
- **Your workspaces, no one else’s:** It reaches your own workspaces, the driver library, and your account name and email. Designs you made as a guest stay in your browser, out of reach.
- **Step in whenever:** Editing pauses only while it writes, and only for the design. Take control and it asks before editing again.
- **Undo the whole session:** The handback’s Undo reverts its changes. Every change is also a saved version, and an edit that started from an older version is refused rather than overwriting yours.
- **Deleted is not gone:** A workspace it deletes goes to Recently deleted, restorable for 30 days, and it asks first unless it made that workspace in the same conversation. It cannot create share links.
For what it can read, and how its changes reach you, see [What your assistant sees](https://simulator.00aud.io/docs/ai/what-it-sees) and [Watch it work live](https://simulator.00aud.io/docs/ai/live).
## Manage or disconnect
- Open **AI** in the simulator’s header and choose **Connections**, or choose **AI / MCP** from your account menu. Both open the list of assistants connected to your account and when you approved each.
- **Disconnect** ends an assistant’s access straight away.
- Signed out, **AI** in the header offers **Log in** instead: connections belong to an account.
## If it doesn’t connect
- ChatGPT: paste the whole server URL, including `/mcp` at the end.
- Claude: the Free plan takes one custom connector, and on Team and Enterprise plans an owner adds it in Organization settings first.
- It answers without your designs: switch the connector on in this chat, and check you approved it while signed in to the account that holds them. Designs you made as a guest stay in your browser, where no assistant can reach them.
- Menu names change as these apps update. If a step doesn’t match what you see, look for custom connectors or developer mode in the app’s settings.
## Ask AI on these pages
00 Simulator has no AI of its own, in the app or in these docs. The Ask AI button on every docs page writes a prompt about that page for your own assistant: copy it, or open it in Claude or ChatGPT, which copies it first in case the link does not fill it in.
Connected, your assistant can read the page and open your designs. Not connected, it can still read the page if it can open web links.
---
# Prompts that work
> Prompts for your assistant with 00 Simulator: find a driver, design and compare boxes, fix a noisy port, check a build against a measurement.
Source: https://simulator.00aud.io/docs/ai/prompts
Start with “Using 00 Simulator,” so your assistant reaches for the connector, say what you want and the limits that matter, and ask it to try changes without saving. Every prompt here asks only for what the connector can do; copy one, or open it in Claude or ChatGPT.
## How to ask
- Start with “Using 00 Simulator,”. It tells your assistant to use the connector rather than answer from memory.
- Say which design: “my most recent workspace”, “the workspace I have open” or a workspace by its name. It lists your workspaces with the one you opened last first, and can tell whether you are watching one.
- Give it the goal and the limits: the power you will use, the box size that fits, how low it should go, and the excursion or port air speed you will accept.
- Ask it to try changes without saving. It runs them as temporary edits, so your design changes only when you say so.
- Keep alternatives together. Ask it to add candidates to the workspace you are working in, where they share one graph, rather than making new workspaces.
- Ask for the numbers and the graphs. It can draw graph tiles in the chat and, with the workspace open, arrange your tiles and mark them.
## Find a driver
**Search by T/S values**
It searches the 00 Bits library by brand, impedance, size, Fs, Qts, Vas, Xmax, sensitivity and power handling with `search_drivers`, then sorts the matches itself.
> Using 00 Simulator, find 8 Ω drivers with an Fs under 30 Hz, a Qts between 0.3 and 0.45 and at least 500 W power handling. List the five with the most Xmax, with their Fs, Qts, Vas, Xmax and power handling.
**Check a datasheet**
For a driver the search does not have. `validate_driver` reports missing fields and values that disagree with each other.
> Using 00 Simulator, check the T/S parameters I paste below for missing values and contradictions, and tell me whether they are enough to simulate.
## Design and compare
**Two boxes for one driver**
It starts from the app’s own suggestions (`suggest_enclosure`), adds both boxes to one workspace (`add_enclosure`) and simulates them together.
> Using 00 Simulator, suggest a sealed and a vented box for the Ciare 12.00SW and add both to my most recent workspace. Simulate them at 100 W and compare their F3, box volume, peak excursion against Xmax and, for the vented box, peak port air speed.
## Fix a problem
**A port that chuffs**
Each option is a temporary change in a `simulate_workspace` run; 17 m/s is the app’s default warning line. See [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port).
> Using 00 Simulator, the vented box in my most recent workspace chuffs when I turn it up. Find the power at which its port passes 17 m/s, then try a bigger port, two ports and a lower tuning without saving, and tell me each option’s peak air speed and port length.
**Too much excursion**
EQ filters are part of the design, so it can try one as a temporary change and compare the runs.
> Using 00 Simulator, add a high-pass filter just below the tuning of the vented box in my most recent workspace, without saving. Tell me how much it lowers peak excursion below the tuning at the saved power, and how much level it costs at the F3.
## Show me on my graphs
**While I watch**
With the workspace open in 00 Simulator, `show_graphs` arranges your tiles and `annotate_graphs` numbers its marks. You keep the arrangement or go back to yours. See [Watch it work live](https://simulator.00aud.io/docs/ai/live).
> Using 00 Simulator, while I watch the workspace I have open, put the Excursion tile first with SPL (dB) and Port Velocity beside it, and mark where each cone passes Xmax.
## Check a build
**Measurement against simulation**
`import_trace` links the measurement to the box; `compare_trace` reports the level offset (distance or drive) apart from the difference in shape.
> Using 00 Simulator, import the REW export I paste below as an SPL measurement of the vented box in my most recent workspace, compare it with the simulation, and tell me the level offset and where the shape differs most.
## Horns
**Fold it and check it**
`fold_horn` folds it the way the Fold tile does and returns the passage as built, which it simulates beside your design.
> Using 00 Simulator, fold the horn in my most recent workspace into a cabinet, simulate the folded horn beside the straight one without saving, and tell me whether it fits, its path length and how much the fold changes the response.
**The smallest cabinet**
The same fold, asked for its smallest cabinet and its board cut list.
> Using 00 Simulator, find the smallest cabinet that holds the horn in my most recent workspace and give me its cut list, without saving anything.
## Explain a result
**Read the docs, then my design**
It finds the page with `search_docs`, reads it with `read_doc` and links it in the answer, then simulates your box.
> Using 00 Simulator, read the docs on the Port Velocity tile, then explain the port air speed of the vented box in my most recent workspace at its saved power and what I should change first.
## Tidy up and undo
**Clear the rejects**
It removes them with `remove_enclosure` and hands back with `end_workspace_session`: you read its summary in 00 Simulator, where you can keep or undo its changes.
> Using 00 Simulator, remove the candidates you added to my most recent workspace that we ruled out, and finish with a short summary of what is left.
**Go back a version**
Restoring adds the old version as a new one, so the versions after it are kept.
> Using 00 Simulator, list the saved versions of my most recent workspace and restore the one from before today’s changes.
## Change how the app looks
**A theme of your own**
It checks the theme with a dry run of `save_theme` before saving it; a theme under a contrast floor is refused.
> Using 00 Simulator, make me a theme based on Grosso with a bit more contrast between the side panel sections, check it against the contrast floors and switch to it.
## What won’t work
- Sharing or publishing a design. It cannot create share links; share it yourself from the app.
- Designs you made as a guest. They live in your browser, not your account.
- Reading your screen. It reads the workspaces saved in your account, not what is on your screen.
- Searching for a driver by size or Xmax. It searches by name and by brand, impedance, Fs, Qts, Vas and power handling, then reads Xmax and cone area from what it finds.
---
# Watch it work live
> What you see in 00 Simulator while your assistant works on an open workspace: its narration, the graphs it shows and marks, taking control and undoing it.
Source: https://simulator.00aud.io/docs/ai/live
Keep the workspace open in 00 Simulator while your assistant works on it and you watch it happen: it says what it is doing, its edits land in place, and it brings up the graphs behind its answer and marks them. You can take control at any time, and one Undo puts it all back.
## Open the workspace
Open the workspace in 00 Simulator, signed in to the account your assistant is connected to, and leave the tab on screen. Your assistant can tell that you are watching, and whether on a desktop or a phone, so it works in front of you. The tab updates by itself: there is nothing to refresh.
Not watching? It shows its results in the chat instead, and what it arranged is waiting when you open the workspace. A tab in the background stops counting as watching after about 40 seconds.
## While it works
_Figure: The graph header reads “Claude is editing” with its narration and Take control, over the Port Velocity tile with two numbered marks: the peak and the band over 17 m/s._
An example: the words are an assistant’s and the curves are the solver’s. Ciare 12.00SW in the 55 L vented example at 200 W, half space, 1 m. Simulated when this page was built.
Port Velocity, one 10 cm port at 200 W: mark 1 at the 28.4 m/s peak near 30 Hz; mark 2 over 17 m/s from 20 to 38 Hz.
- A line in the graph header says what it is doing: “Claude is looking” until it saves its first change, “Claude is editing” while it saves one, and “Claude paused” between changes.
- Beside it is its latest narration: a sentence or two on what it is doing and why. Click the line for every step so far and what each one changed.
- Its edits land in place as it saves them, each as one undo step. While it saves, your design controls wait; you can still look around and open sections and tabs.
- **AI** in the header says the same and offers **Take control**. On a phone, the bar under the graphs becomes the assistant’s while it edits, and its chip opens the steps.
## The graphs it shows you
- It can bring the graphs its answer rests on to the front: up to 6 tiles in the order to read them, the main one largest. On a phone they page in that order.
- It marks what it is talking about: a band over a range of frequencies, a line at a frequency, a level, or a point on a curve. The marks are numbered to match what it says, up to 8 at a time and 4 on one graph, and each new set replaces the last.
- Marks stay after it finishes, until the design changes under them. Click a mark’s label to keep them as your own graph notes, saved with the design (**Keep as notes**), or to clear them.
- **Hide annotations** in the header hides its marks and your notes together.
- Arranging and marking never change your design.
## Take control
Press **Take control** in the header line, or under **AI**, at any time. The design is yours again at once. If your assistant then tries to edit or rearrange anything, it is refused and told you took control, so it has to ask you before it carries on.
The handback then reads “You took control”, with the same Undo as below. With the keyboard: when a control refuses a key while it is editing, focus moves beside **Take control**; press Tab to reach it.
## When it finishes
_Figure: The Port Velocity tile after the change, with one numbered mark at the new peak, and the handback notification: “Claude finished · 1 change” with Undo, Details and a close button._
An example: the words are an assistant’s and the curves are the solver’s. Ciare 12.00SW in the 55 L vented example at 200 W, half space, 1 m. Simulated when this page was built.
Port Velocity, two 10 cm ports at 200 W: mark 1 at the 14.2 m/s peak near 30 Hz. Handback: Claude finished, 1 change.
- It ends with a summary of two or three sentences: what changed and what to try next. A notification at the foot of the editor says who stopped and how many changes it made, with **Undo** and **Details**. If it goes quiet for 2 minutes without finishing, the notification says it paused instead.
- The notification closes by itself after 15 seconds unless you point at it or use it. Closing it keeps everything, its arrangement and marks included.
- **Details** opens the summary and its steps, and the choices that apply: **Restore my layout** or **Keep layout** for the arrangement, **Keep as notes** or **Clear** for its marks, and **Revert to before** or **Keep** for its changes.
- A workspace it created is a draft: the notification waits for **Keep workspace** instead of closing, and a draft nobody keeps is archived after 7 days.
## Undo the whole session
- **Undo** in the notification reverts every change it saved, puts your layout back and clears its marks. If it only arranged and marked, Undo puts back just those.
- If you changed the design after it, Undo asks first, because reverting would discard your change too: **Revert anyway** or **Cancel**.
- Each of its edits is also one step of the app’s own undo, and every change it saved is a saved version, listed under **History and saved versions…** in the menu beside Undo in the header.
- If it deleted the workspace you have open, the tab says so and offers **Restore**.
**Ask your AI**
It arranges your tiles with `show_graphs`, marks them with `annotate_graphs` and hands back with `end_workspace_session`.
> Using 00 Simulator, while I watch the workspace I have open, check each enclosure’s excursion at its saved power. Put the Excursion tile first, mark where each cone passes Xmax, and finish with a short summary I can undo.
---
# What your assistant sees
> What a connected assistant can see and change in 00 Simulator, the permissions you approve, how to undo its changes and how to disconnect it.
Source: https://simulator.00aud.io/docs/ai/what-it-sees
A connected assistant works only with what you approve, only on your own workspaces, with changes you can undo and a connection you can end at any time. This page says exactly what it can reach.
- **You approve it:** Connecting needs a free account with a verified email. A consent screen lists what the assistant is asking for before you allow it.
- **Your workspaces, no one else’s:** It reaches your own workspaces, the driver library, and your account name and email. Designs you made as a guest stay in your browser, out of reach.
- **Step in whenever:** Editing pauses only while it writes, and only for the design. Take control and it asks before editing again.
- **Undo the whole session:** The handback’s Undo reverts its changes. Every change is also a saved version, and an edit that started from an older version is refused rather than overwriting yours.
- **Deleted is not gone:** A workspace it deletes goes to Recently deleted, restorable for 30 days, and it asks first unless it made that workspace in the same conversation. It cannot create share links.
- **Disconnect any time:** Choose AI in the simulator’s header and open Connections, or AI / MCP from your account menu. Access ends straight away.
## You approve it first
Connecting needs a 00 Simulator account with a verified email address; without one the connector refuses every call. The first time your assistant connects, you sign in to 00 Simulator and see a consent screen with the assistant app that is asking, the account you are signed in as, and the access it wants. Nothing is shared until you approve it.
Every connection asks for the same eight permissions, listed below. One of them lets it reconnect without asking you to sign in again. To set a connection up, see [Connect your assistant](https://simulator.00aud.io/docs/ai/connect).
## The permissions
Built from the connector’s own tool list. What each tool does is on [Tools your assistant can call](https://simulator.00aud.io/docs/ai/tools).
| Permission | On the consent screen | What uses it |
| --- | --- | --- |
| `openid` | Confirm your signed-in account | Signing in, not a tool |
| `profile` | Read your profile name and image | Signing in, not a tool |
| `email` | Read your account email address | Signing in, not a tool |
| `offline_access` | Reconnect without asking you to sign in again | Staying connected, not a tool |
| `simulation:run` | Run enclosure simulations | 4 tools: `simulate_workspace`, `get_simulation_results`, `compare_trace` and `render_simulation_graphs` |
| `workspace:read` | Read your simulator workspaces | 23 tools: `list_workspaces`, `get_workspace`, `list_workspace_revisions`, `get_workspace_revision`, `update_enclosure`, `add_enclosure`, `remove_enclosure`, `simulate_workspace`, `get_simulation_results`, `import_trace`, `list_traces`, `get_trace`, `update_trace`, `delete_trace`, `compare_trace`, `fold_horn`, `export_boundary_lab`, `render_simulation_graphs`, `show_graphs`, `annotate_graphs`, `list_themes`, `get_theme` and `end_workspace_session` |
| `workspace:write` | Create and update simulator workspaces | 13 tools: `create_workspace`, `delete_workspace`, `update_workspace`, `restore_workspace_revision`, `update_enclosure`, `add_enclosure`, `remove_enclosure`, `import_trace`, `update_trace`, `delete_trace`, `save_theme`, `activate_theme` and `delete_theme` |
| `share:create` | Create simulator share links | No tool uses it |
> **It cannot share your designs** No tool creates a share link, and the connector tells assistants never to make one to open a private workspace. Sharing stays something only you do, from **Share** in the app.
## What it can reach
- Your own workspaces: everything saved in them (each enclosure with its driver, power and EQ, the environment, measured traces and graph notes), their saved versions, and the simulation runs it makes. Every workspace tool checks that the workspace belongs to the account that approved the connection.
- The driver library the simulator searches, and these docs.
- Your themes, when you ask it to change how 00 Simulator looks.
- Your account name, profile image and email address, which the consent screen asks for.
It reads what is saved, not your screen: no tool looks at your tab. It can tell whether you have a workspace open, and while you do it can bring tiles to the front and mark the graphs there. See [Watch it work live](https://simulator.00aud.io/docs/ai/live).
## What it cannot reach
- Anyone else’s workspaces.
- Designs you make without signing in. A **Guest project** lives only in the browser you made it in, so your assistant cannot see or change it; it works on the workspaces in your account.
- Your sign-in. You sign in on 00 Simulator’s own page, and the assistant app gets only a token for this connection.
## Where your data goes
What your assistant reads through the connector (workspace contents, driver data and simulation results) goes to your assistant’s service, which handles it under its own privacy policy. Graphs drawn in the chat carry the curve data they show. Simulation runs it makes are kept for 24 hours, and only the newest 20 for each workspace. The [privacy policy](https://simulator.00aud.io/privacy) has the details.
## Changes you can undo
- Every edit it saves makes a new saved version of the workspace. **Workspace history** lists them, each marked with who made it, and any of them can be restored.
- It edits from the version it last read. If the workspace changed since, the edit is refused rather than written over yours.
- If you have the workspace open, the handback it leaves when it finishes has an **Undo** that reverts its changes in one go. See [Watch it work live](https://simulator.00aud.io/docs/ai/live).
- A workspace it deletes goes to **Recently deleted** under **All workspaces**, where **Restore** brings it back for 30 days. It is told to ask you first unless it made that workspace in the same conversation.
- Workspaces it creates start as drafts: they stay out of your workspace count and recents, and are archived after seven days unless you edit, rename, pin or keep them. An archived draft can still be restored from **Recently deleted**.
- A measured trace it removes stays in the workspace’s saved versions.
## Step in at any time
Choose **Take control** in your open workspace and its next change is refused: it has to stop and ask you before it edits again. Your own edits wait only while it is writing, and only for the design.
## Disconnect
1. **Open your connections.** In 00 Simulator, choose **AI** in the header, then **Connections**. Or open your account menu and choose **AI / MCP**.
2. **Disconnect the assistant.** Under **MCP connections**, choose **Disconnect** beside it and confirm.
Access ends straight away: the approval and its sign-in tokens are removed, so the assistant’s next call is refused. Disconnecting does not delete anything already in your assistant’s chats. To use it again, connect again and approve the consent screen.
## Ask your AI
**Ask your AI**
A quick way to tidy up after a few design sessions.
> Using 00 Simulator, list my workspaces and tell me which are drafts you created that I have not kept yet, so I can decide what to keep or delete.
---
# Tools your assistant can call
> Every tool the 00 Simulator connector gives Claude, ChatGPT and other assistants, grouped by job, with what each one can change.
Source: https://simulator.00aud.io/docs/ai/tools
Connect 00 Simulator to your assistant and it gets these 39 tools. It works on your own workspaces, and each description below is the text it reads to choose a tool. The list is built from the connector's own, so it matches what your assistant sees.
- **Tools:** 39
- **Change a workspace:** 11
- **Server URL:** `https://simulator.00aud.io/mcp`
## How to read this list
Your assistant picks which tool to call, and when, from what you ask: you never call one yourself. The tools are grouped by the job they do, and the tags say what a tool can change.
- _Changes a workspace_: 11 tools add, edit or remove something in a workspace you own. Edits to a design are saved as new versions you can go back to, and a deleted workspace can be restored: see [Changes you can undo](https://simulator.00aud.io/docs/ai/what-it-sees#changes-you-can-undo).
- _In your open tab_: `show_graphs`, `annotate_graphs` and `end_workspace_session` work on what you see in the workspace you have open in 00 Simulator, not on the design. See [Watch it work live](https://simulator.00aud.io/docs/ai/live).
- _Changes your theme_: `save_theme`, `activate_theme` and `delete_theme` change how 00 Simulator looks for you, never a workspace.
- Untagged tools leave your designs as they are. `simulate_workspace` is still marked as writing, because it keeps the run it makes, privately, so graphs can be drawn from it.
Your assistant app is also told which tools only read (23 of them) and which can overwrite or remove something (8), so it can ask you before one runs. Nine tools need nothing beyond signing in: `search_drivers`, `get_driver`, `validate_driver`, `suggest_enclosure`, `get_enclosure_schema`, `get_theme_schema`, `search_docs`, `read_doc` and `list_workspace_capabilities`. The rest need the permissions you approve when you connect, listed in [What your assistant sees](https://simulator.00aud.io/docs/ai/what-it-sees#permissions).
> **Narration, and taking control** 23 tools that work on a workspace also take a narration: one or two plain sentences your assistant writes about what it is doing and why, shown in 00 Simulator if you have that workspace open. Their descriptions end by asking for it, and most of those that change something add that once you take control, your assistant must stop and ask you before editing again. That closing sentence is left out below; the rest is word for word.
## A design job, step by step
Six steps, in the order someone would do them, from choosing a driver to keeping or undoing the work.
### 1. Pick a driver
Search simulation-ready drivers by name or Thiele/Small filters, read one in full, and check a set of parameters for missing fields and contradictions.
**search_drivers**: Search the 00 Bits catalogue of simulator-ready drivers, the same library as the app's driver picker, by brand, model or both, with optional T/S filters. It reads model codes typed with an impedance ("8fe200 4") and common brand spellings ("18sound"). Each result has a `driverRef` for `get_driver`, its `tsValidity`, and `bitsUrl`, the driver's page on 00 Bits with shop prices. `meta.total` is how many drivers matched before the limit, so narrow the filters when it is large.
**get_driver**: Fetch a full driver by driver ref: {kind:"bits",id} from `search_drivers`, {kind:"local",id}, or {kind:"raw",driver}. Returns its T/S values, any consistency warnings, and embed: pass embed unchanged as `add_enclosure`'s driver so the Workspace keeps the 00 Bits driver it came from.
**validate_driver**: Validate a raw driver payload and report missing fields, simulation readiness, and consistency warnings.
### 2. Design
Suggest a starting alignment, read the fields each enclosure type takes, then build and edit candidates in a workspace of your own.
**suggest_enclosure**: Suggest one or two starting enclosure alignments using the simulator suggestion logic.
**get_enclosure_schema**: Describe Workspace enclosure editing, SI units, horn types/profiles, Paraflex and MEH configuration. This schema is enforced by `update_enclosure` and temporary `simulate_workspace` overrides.
**create_workspace**: Create a cloud workspace for a new project or design question. Call `list_workspaces` first and prefer `add_enclosure` on an existing Workspace: alternatives for one question belong together, where they can be compared on one graph. Name it after the project, not the candidate, and keep the name under 40 characters. A Workspace created here starts as a draft: it stays out of the account's Workspace count and recents, and is archived automatically after a week unless the account edits, renames, pins or keeps it. _Changes a workspace._
**list_workspaces**: List cloud workspaces for the authenticated account. Read this before creating anything: when the account already has a Workspace for the design question at hand, add to it with `add_enclosure` instead of creating another. Each entry reports `isDraft` and `createdByClientId`, so a Workspace you created earlier in this conversation is easy to find and continue.
**get_workspace**: Fetch a cloud workspace document owned by the authenticated account.
**add_enclosure**: Add one enclosure to an owned Workspace, with its driver values embedded in the same call. Prefer this over creating another Workspace: candidates that belong to the same design question belong in one Workspace, where they can be compared on one graph. Requires the current `expectedRevision`. Uses the same SI-unit fields as `update_enclosure`; read `get_enclosure_schema` for horn fields and examples. _Changes a workspace._
**update_enclosure**: Update one enclosure in an owned Workspace with required revision control. Uses the same SI-unit fields as the app. Arrays replace; configuration and `hornParaflex` merge one level; null clears optional fields. Read `get_enclosure_schema` for horn fields and examples. _Changes a workspace._
**update_workspace**: Update workspace metadata or replace the portable workspace document using optimistic revision control. A document without a notes field keeps the graph notes the person wrote; pass notes: \[\] only when they asked for their notes to be removed. _Changes a workspace._
### 3. Simulate
Run the solver on a saved version, including horns, EQ and multiple-entry drivers, and read the numbers back.
**simulate_workspace**: Run selected enclosures from an exact owned Workspace revision on the server, including all horn topologies, EQ and MEH sources. Uses saved power, embedded drivers and `environment.simulation` settings (`maximumFrequency`: auto or 20–20000 Hz; `upperResponseMode`: estimated or physical; `maxSpl`: the Max SPL thermal rule, real input power by default, or constant voltage or estimated coil heat, with an optional voice coil temperature). Auto uses 2 kHz if the Workspace contains horns, otherwise 400 Hz. `frequencyRange` overrides sampling for this run. Temporary overrides do not edit the Workspace. Returns a private run ID; results expire after 24 hours and only the newest 20 runs per Workspace are retained.
**get_simulation_results**: Read a private Workspace simulation run by `runId` and `workspaceId`. Summary includes each enclosure, MEH source names, horn locations and radiating outlets. Full includes exact resolved configuration and `frequencyResponse` curves, including each MEH source’s SPL, impedance, excursion, voltage and current, and `hornDiagnostics` with complex RMS pressure/flow, peak particle velocity, local acoustic impedance and separate output pressures. Non-finite values are encoded as null.
### 4. Show you
Draw graphs in the conversation, with power and EQ controls you can adjust, arrange the dashboard in your open tab around what is being explained, and mark the frequencies worth looking at.
**render_simulation_graphs**: Render interactive graph tiles for a private simulation run. Call `simulate_workspace` first, then pass its `workspaceId` and `runId`. Choose up to 6 graphs per call, in display order (spl: SPL at the saved listening distance; `maxSpl`: highest SPL before the driver reaches Xmax or its thermal limit; impedance: impedance magnitude seen by the amplifier; phase: acoustic phase including EQ and filters; `groupDelay`: group delay; excursion: peak cone excursion per diaphragm with Xmax limits; `prExcursion`: peak passive radiator excursion with its Xmax limit; `portVelocity`: port air velocity with the 17 m/s warning level; `rearPortVelocity`: rear chamber port air velocity of a 6th-order bandpass; `apparentPower`: apparent amplifier load including reactive current; `currentDraw`: amplifier RMS current). Defaults to spl and excursion. Every selected enclosure is overlaid on each tile, and so are the Workspace's measured traces for that kind (drawn thin, marked source: measured, with any display offset applied); kinds an enclosure does not produce (for example port velocity for a sealed box) are left out, and the result lists the kinds available for the run. Add controls (power, eq) when the user wants to explore drive level or EQ interactively: the widget then shows a panel where they can change one enclosure's power and EQ filters and see its curves re-solved locally; those previews stay unsaved until the user applies them, which writes through `update_enclosure`. Leave controls out for a plain comparison. Reads stored results without editing or re-running the Workspace. Results expire after 24 hours; re-simulate if expired.
**show_graphs**: Arrange the dashboard of the person's open 00 Simulator tab around what you are explaining, without changing the design. List the tiles in reading order and mark one primary: on a desktop it takes the most room and the rest fill the first screen; on a phone the graphs page in that order. Show the graphs your numbers come from (for example horn-pressure when you quote throat pressure). The person keeps the arrangement or restores their own layout when you finish. Tile ids and what each shows are listed by `list_workspace_capabilities` under `liveActivity.graphs`. _In your open tab._
**annotate_graphs**: Mark what to look at on the graphs in the person's open 00 Simulator tab, without changing the design: a band over a frequency range, a vertical line at a frequency, a horizontal level, or a point on an enclosure's curve. Each call replaces your previous marks; an empty list clears them, and they hide by themselves once the design changes. Keep labels to a few words with units ("+2 dB", "71.7 Pa") and explain in narration. Put the graph on screen with `show_graphs` first. Tile ids and what each shows are listed by `list_workspace_capabilities` under `liveActivity.graphs`. _In your open tab._
### 5. Check the build
Bring in a real measurement, such as a REW export, link it to the design it measures, and compare the two: the level difference and the shape difference are reported separately.
**import_trace**: Import a measured trace (REW text export, .frd, .zma, CSV, or a table of numbers) into an owned Workspace, where it overlays the matching graph: SPL, impedance, phase or Max SPL. Pass the file contents as text (up to 512 KB) or rows as points. The same rules as dropping the file in the app apply: lines that start with a number are data, frequency ascending, at least 5 rows, decimated to 48 points per octave, phase kept when present. Link it to the enclosure it is a measurement of with `enclosureId`; omit or pass null for reference data that belongs to no design here. Stored values are never shifted: use offset or `compare_trace` to align levels. At most 24 traces per Workspace. Requires `expectedRevision`. _Changes a workspace._
**compare_trace**: Compare a measured trace with an enclosure simulated from the current Workspace revision. Reports the mean level offset over the band (simulated minus measured: a distance or drive difference, not a shape disagreement), the RMS residual once that offset is removed, the largest remaining deviation and its frequency, and the residual at 1/6-octave points. The simulated run is saved like `simulate_workspace`, so `render_simulation_graphs` can draw it with the trace overlaid; lower `pointsPerDecade` when a large horn's run would pass the 4 MB limit. Pass apply: true with `expectedRevision` to store the offset on the trace. _Changes a workspace._
**list_traces**: List the measured traces in an owned Workspace: kind, unit, linked enclosure, display offset, frequency range, point count and measurement conditions. No curve values; use `get_trace` for those.
**get_trace**: Read one measured trace's values. Values are the stored measurement unless `applyDisplay` is true, in which case the display offset and smoothing are applied as drawn. Long traces are resampled on a log grid to at most `maxPoints` (default 96, up to 1000).
**update_trace**: Edit a measured trace: name, kind, link to an enclosure (null unlinks), display offset, smoothing, line style, point marker, visibility, colour (null goes back to the automatic colour: a shade of the linked enclosure's, or the trace's own) or measurement conditions (merged; null clears a field). Stored values never change. Requires `expectedRevision`. _Changes a workspace._
**delete_trace**: Remove a measured trace from an owned Workspace. It stays in revision history. Requires `expectedRevision`. _Changes a workspace._
### 6. Keep or undo
Finish with a summary you can undo in one go, restore any saved version, and clear away the candidates and workspaces that did not work out.
**end_workspace_session**: Finish your work on a Workspace. The person watching it in 00 Simulator sees your summary with the steps you took, and can keep or revert your changes. Call it once when you are done, with a two or three sentence summary of what changed and what to try next. _In your open tab._
**list_workspace_revisions**: List immutable revision metadata for an owned cloud Workspace without returning revision documents.
**get_workspace_revision**: Fetch one exact immutable revision document for an owned cloud Workspace.
**restore_workspace_revision**: Restore one older immutable revision into an owned cloud Workspace as a new MCP-attributed revision. _Changes a workspace._
**remove_enclosure**: Remove one enclosure from an owned Workspace with required revision control. Use it to drop a candidate you added and ruled out, instead of leaving it behind. _Changes a workspace._
**delete_workspace**: Move an owned Workspace to Recently deleted, where the account can restore it for 30 days. Use it to clean up a Workspace you created and no longer need, so unwanted designs do not pile up. Ask the person before deleting a Workspace you did not create in this conversation. _Changes a workspace._
## Outside the design job
Tools that belong to no single step of a design.
### Look it up
Search the 00 Simulator docs and read a page or one section of it, so answers about the app and what a result means quote the docs and link to them.
**search_docs**: Search the 00 Simulator docs: how to do something in the app, and what a tile, result, setting or term means. Returns the best matching pages, sections, tiles and glossary terms, each with a url and a one-line summary. Then read the best match with `read_doc` and quote it with its url, rather than answering from memory.
**read_doc**: Read a 00 Simulator docs page as Markdown. Pass a url from `search_docs` or a docs path such as /docs/reference/tiles/port-velocity (/docs is an overview of every page). Pass section, a heading on the page, to read only that part; a url ending in #section reads just that section. Quote what you use and link its url.
### Appearance
Build an app theme for you, for instance more contrast between the side-panel sections, check it against the contrast floors, and switch to it when you ask.
**get_theme_schema**: Describe a 00 Simulator theme: every scalar with its range and what it changes, the per-mode settings, the contrast floors a theme must clear, and the built-in themes as examples. Read this before `save_theme`.
**list_themes**: List the themes this person can use in 00 Simulator, built in and saved, and which one is active.
**get_theme**: Read one theme in full, with its contrast report for dark and light mode. Use an id from `list_themes`; "default" and "grosso" are built in.
**save_theme**: Check and save a custom theme for this person. Pass `dryRun` true to get the normalised theme and its contrast report without saving. A theme under a contrast floor in either mode is refused, with the failing checks and what to change. Leave `themeId` out to add a new theme, and give it a name. Pass `themeId` to change one of their saved themes: only the scalars and mode settings you send move, and a colour sent as null goes back to the app's own. Pass activate true only when they asked to switch. The person sees a theme change in 00 Simulator when they next look at that tab; they never need to refresh. _Changes your theme._
**activate_theme**: Switch this person to a built-in or saved theme. Only when they asked for it. The person sees a theme change in 00 Simulator when they next look at that tab; they never need to refresh. _Changes your theme._
**delete_theme**: Delete one of this person's saved themes, for example one you made and they did not keep. Built-in themes cannot be deleted. If it was active, they go back to the built-in theme it came from. _Changes your theme._
### Fold a horn
Fold a horn into a cabinet the way the Fold tile does, with other layouts, fixes and the folded horn to simulate beside the target, then export the saved fold as a Boundary Lab project to solve in 3-D.
**fold_horn**: Fold a horn enclosure into a cabinet the way the 00 Simulator Fold tile solves it, on an exact Workspace revision, without saving anything. Uses the saved cabinet (`hornFoldLayout`) or, when none is saved, sizes and compacts one; a layout in Auto takes the ranking's best fold. Pass changes (the `update_enclosure` fields) to try horn edits or another cabinet first. A `hornFoldLayout` change replaces the whole saved layout, driver mock included (the result's `driver.mock` is the one in use): give outside dimensions and `wallThicknessMm` without a topology to let the ranking choose the fold for them. Returns whether it fits, every issue, path length, areas, volume, the driver's taps and chambers, alternative folds, grow/trim fixes, optionally the smallest cabinet, cut list, Hornresp readout and area profile, and `folded.changes`: the passage as built, to pass as a `simulate_workspace` override so you can simulate the folded horn next to the target. To keep a fold, save the returned layout with `update_enclosure` (`changes.hornFoldLayout`), pinned with `topologyMode` "pinned" once you have chosen it. A saved layout may also carry the Fold tile's editor, pattern, locks and pins (held passage faces); keep them when you echo a layout back, or leave pins out to let the fold follow the horn.
**export_boundary_lab**: Export a horn's saved fold as a Boundary Lab project (coupled FEM-BEM: the folded passage as tetrahedra, the cabinet as a boundary-element shell, the driver on its board for tapped horns) and return a download link that works without signing in for 24 hours. Save the fold with `update_enclosure` first; pass the revision that holds it. resolution "draft" meshes by wavelength alone and solves in seconds, close enough to iterate on; "final" meshes the passage to 20 mm for sign-off. The zip includes the project, both meshes, a README and `to_traces.py`, which turns a solved run into .frd and .zma files for `import_trace`. Solving needs Boundary Lab installed where you run it: download with curl, unzip, blab project validate, blab project solve, then run the script and import the files linked to this enclosure to compare them with `compare_trace`.
### Its own limits
List the workspace operations this connection allows and the permission each one needs.
**list_workspace_capabilities**: List authenticated workspace operations, required scopes, availability, and document mutation semantics.
## Ask your AI
**Ask your AI**
Your assistant answers from the connector itself, so it reflects the permissions you approved.
> Using 00 Simulator, tell me which workspace operations this connection allows, which permission each one needs, and which of them can change my designs.
---
# Graph kinds
> The graphs your assistant can draw in the chat from a 00 Simulator run, what each one shows, and the tile that matches it in the app.
Source: https://simulator.00aud.io/docs/ai/graph-kinds
Your assistant can draw eleven kinds of graph right in the conversation, from a run of your own design. Each is the same quantity as a tile in the app, drawn from the same solver.
- **Kinds:** 11
- **Per call:** Up to 6
- **When none is named:** Sound pressure level and cone excursion
## The kinds
The first column is the name your assistant passes. You can ask for a graph by its plain name.
| Kind | Graph | Shows | Tile in the app |
| --- | --- | --- | --- |
| `spl` | Sound pressure level (dB) | SPL at the saved listening distance. | [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl) |
| `maxSpl` | Maximum SPL (dB) | Highest SPL before the driver reaches Xmax or its thermal limit. | [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl) |
| `impedance` | Electrical impedance (Ω) | Impedance magnitude seen by the amplifier. | [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance) |
| `phase` | Acoustic phase (°) | Acoustic phase including EQ and filters. | [Phase](https://simulator.00aud.io/docs/reference/tiles/phase) |
| `groupDelay` | Group delay (ms) | Group delay. | [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay) |
| `excursion` | Cone excursion (mm) | Peak cone excursion per diaphragm with Xmax limits. | [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) |
| `prExcursion` | Passive radiator excursion (mm) | Peak passive radiator excursion with its Xmax limit. | [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion) |
| `portVelocity` | Port air velocity (m/s) | Port air velocity with the 17 m/s warning level. | [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) |
| `rearPortVelocity` | Rear port air velocity (m/s) | Rear chamber port air velocity of a 6th-order bandpass. | [Port Velocity (Rear Chamber)](https://simulator.00aud.io/docs/reference/tiles/rear-port-velocity) |
| `apparentPower` | Apparent power (VA) | Apparent amplifier load including reactive current. | [Amplifier Load (VA)](https://simulator.00aud.io/docs/reference/tiles/amplifier-load) |
| `currentDraw` | Current draw (A) | Amplifier RMS current. | [Amplifier Load (VA)](https://simulator.00aud.io/docs/reference/tiles/amplifier-load) |
## How a graph gets into the chat
1. **Your assistant runs the design.** `simulate_workspace` runs your saved design on the server, at its saved power and settings, or with changes it tries without saving them. The run is kept for 24 hours.
2. **It picks the graphs.** `render_simulation_graphs` draws up to six kinds from that run, in the order it chooses. When it names none, you get sound pressure level and cone excursion.
3. **Every enclosure on every graph.** Each enclosure in the run is drawn on each graph, so candidates compare side by side. A kind an enclosure does not produce is left out, such as port velocity for a sealed box.
4. **Your measurements too.** Measured traces saved in the workspace are drawn thin on the graph they match: sound pressure level, electrical impedance, acoustic phase and maximum SPL. Any display offset you set is applied, as in the app.
## Power and EQ in the chat
Ask for controls and the graphs come with an “Adjust” panel. Pick one enclosure, change its drive power and EQ filters, and its curves are solved again in the chat as you go. These are previews: nothing is saved until you apply them.
- “Apply to Workspace” saves the settings to that enclosure, as a new saved version. It appears only when the connection may change workspaces and the chat lets the graph call the connector.
- Where it does not appear, the panel spells out the settings to keep, so you can ask your assistant to apply them.
- “Reset” goes back to the saved settings.
## Where the graphs show
Assistant apps that show MCP Apps widgets, such as Claude and ChatGPT, draw the graphs as interactive tiles in the conversation. Everywhere else the same call returns a summary your assistant reads: each curve’s peak, where it peaks, and its limit line, so it can still answer with numbers.
> **One fixed warning line** Port velocity graphs in the chat always draw the warning at 17 m/s, the app’s default. The tiles in the app use your own **Port velocity** setting under **Settings › Simulation…**.
## In the app instead
The app has 27 tiles, more than the chat’s eleven kinds. If you have the workspace open, your assistant can bring the tiles its numbers come from to the front there and mark them, instead of drawing graphs in the chat. See [Watch it work live](https://simulator.00aud.io/docs/ai/live) and [every tile](https://simulator.00aud.io/docs/reference/tiles).
## Ask your AI
**Ask your AI**
In Claude and ChatGPT the graphs appear in the chat; elsewhere your assistant answers with the numbers.
> Using 00 Simulator, simulate my open workspace and show me SPL, Max SPL and port velocity in the chat, with power and EQ controls so I can try more drive without saving it.
---
# Docs for assistants
> How assistants read the 00 Simulator docs: a Markdown twin of every page, llms.txt, llms-full.txt, and the connector’s own docs search.
Source: https://simulator.00aud.io/docs/ai/docs-for-assistants
Every page of these docs can be read by an assistant as well as by you: as Markdown, as one index or one file, or through the connector’s own docs tools. It is the same text you read, so what your assistant quotes is what the page says.
- **Any page:** Add `.md` to its address
- **Index:** `https://simulator.00aud.io/llms.txt`
- **Everything:** `https://simulator.00aud.io/llms-full.txt`
## Every page as Markdown
Add `.md` to any docs address and you get the page as plain Markdown: `https://simulator.00aud.io/docs/reference/tiles/port-velocity.md`. The docs home as Markdown, `https://simulator.00aud.io/docs.md`, lists every page with a line on each.
- It starts with the title, a one-line summary and the page’s address, then the page itself.
- A figure becomes its description, followed by the numbers it shows as a table where it has them.
- An interactive walkthrough becomes a one-line note; prompts keep their full text.
- Links to other pages are full addresses, so they still work outside this site.
The Markdown is built from the same content as the page when the site is built, so the two cannot differ. Beside each page, Copy as Markdown copies it and View as Markdown opens it.
## llms.txt and llms-full.txt
`https://simulator.00aud.io/llms.txt` follows the [llms.txt convention](https://llmstxt.org): what 00 Simulator is, how to read the docs, then every page tab by tab with its Markdown address and a one-line description. `https://simulator.00aud.io/llms-full.txt` is every page in one file, in reading order, for pasting into a long chat or a project’s files.
```markdown
# 00 Simulator
> 00 Simulator is a loudspeaker enclosure simulator that runs in the browser. It models sealed, vented, passive-radiator, bandpass and horn enclosures from a driver’s T/S parameters, and assistants such as Claude and ChatGPT can use it through its connector.
Every docs page is also served as Markdown: add `.md` to its address, as in the links below. All of the docs in one file: https://simulator.00aud.io/llms-full.txt. Assistants connected to 00 Simulator (https://simulator.00aud.io/mcp) can search these docs and read a page or one section with the `search_docs` and `read_doc` tools.
…
## AI
- [Docs for assistants](https://simulator.00aud.io/docs/ai/docs-for-assistants.md): How assistants read the 00 Simulator docs: a Markdown twin of every page, llms.txt, llms-full.txt, and the connector’s own docs search.
…
```
## search_docs and read_doc
With 00 Simulator connected, your assistant has two docs tools, and the connector tells it to use them for how-to questions: search, read the best match, and quote the docs with a link instead of answering from memory. Both need nothing beyond signing in.
| Tool | What your assistant reads |
| --- | --- |
| `search_docs` | Search the 00 Simulator docs: how to do something in the app, and what a tile, result, setting or term means. Returns the best matching pages, sections, tiles and glossary terms, each with a url and a one-line summary. Then read the best match with `read_doc` and quote it with its url, rather than answering from memory. |
| `read_doc` | Read a 00 Simulator docs page as Markdown. Pass a url from `search_docs` or a docs path such as /docs/reference/tiles/port-velocity (/docs is an overview of every page). Pass section, a heading on the page, to read only that part; a url ending in #section reads just that section. Quote what you use and link its url. |
- Search uses the same index and ranking as the search box on this site (⌘K), so it finds the pages you would.
- `read_doc` returns the page’s Markdown twin, or just one section of it, with the address to link.
## An answer, step by step
Someone with the vented example open (the Ciare 12.00SW in 55 L, tuned to 32 Hz, one 10 cm port, at 200 W) asks their assistant: “Why does my sub chuff when I turn it up?”
1. **Search the docs.** `search_docs` for “port chuffing” finds the [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) tile page and [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port).
2. **Read the design.** `get_workspace` reads the saved design: the driver, the box, the port and the power.
3. **Try a change without saving it.** `simulate_workspace` runs it as it is and again with two ports. The port’s peak air speed goes from 28.4 m/s to 14.2 m/s, and each port grows from 35.6 cm to 77.1 cm long to keep the tuning.
4. **Read the part that explains it.** `read_doc` reads the [What moves it](https://simulator.00aud.io/docs/reference/tiles/port-velocity#what-moves-it) section of Port Velocity.
> **The answer it can give** Your port peaks at **28.4 m/s** at 200 W, over the 17 m/s line where ports start to be heard. Two 10 cm ports bring it to **14.2 m/s**, but each must be 77.1 cm long to keep 32 Hz, so check it fits the box. [Port Velocity › What moves it](https://simulator.00aud.io/docs/reference/tiles/port-velocity#what-moves-it)
## Point any assistant at the docs
- Connected to 00 Simulator: just ask. It searches and reads these docs itself. See [Connect your assistant](https://simulator.00aud.io/docs/ai/connect).
- Not connected, but it can open web pages: give it a page’s address, its `.md` twin, or `https://simulator.00aud.io/llms.txt`, and ask it to read what it needs.
- No web access: use Copy as Markdown on the page and paste it into the chat, or save llms-full.txt and attach it.
- On any page, Ask your assistant writes a prompt that names the page: copy it, or open it in Claude or ChatGPT with the prompt filled in.
```
Read https://simulator.00aud.io/llms.txt, then the 00 Simulator docs pages you need, and answer from them with links: what does the Headroom tile show, and when should I worry about it?
```
## Ask your AI
**Ask your AI**
With the connector, your assistant quotes the docs instead of answering from memory.
> Using 00 Simulator, search the docs for how the Headroom tile works, read me the part that explains it, and link the page.
---
# Reference overview
> Look up the controls, tiles, driver parameters and model limits in 00 Simulator.
Source: https://simulator.00aud.io/docs/reference
Find what a field changes, what a graph shows, or what a loudspeaker term means. Each tile has its own page with examples and things to try.
## Look something up
- [Tiles](https://simulator.00aud.io/docs/reference/tiles): Read the graphs, calculations and editors, including what a healthy result looks like.
- [Controls and fields](https://simulator.00aud.io/docs/reference/controls): Box size, port tuning, power, wiring, EQ and environment.
- [T/S parameters](https://simulator.00aud.io/docs/reference/ts-parameters): Driver symbols, units, derived values and excursion limits.
- [Glossary](https://simulator.00aud.io/docs/reference/glossary): Short definitions of the terms used throughout these docs.
- [Model and limits](https://simulator.00aud.io/docs/reference/model-and-limits): What the simulation calculates and what still needs a measurement.
## Follow the question
| Question | Look at |
| --- | --- |
| How much bass does the design produce? | [SPL](https://simulator.00aud.io/docs/reference/tiles/spl) and [Metrics](https://simulator.00aud.io/docs/reference/tiles/metrics) |
| How loud can it play? | [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl) and [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom) |
| Is the cone moving too far? | [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) and [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion) |
| Will the port be noisy? | [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) |
| What load does the amplifier see? | [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance) and [Amplifier Load](https://simulator.00aud.io/docs/reference/tiles/amplifier-load) |
| What is happening inside the horn? | [Horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics) |
---
# Tiles
> Find the right simulator tile for response, limits, horn diagnostics, editing and comparison, with a guide to every tile.
Source: https://simulator.00aud.io/docs/reference/tiles
Each tile answers a different question about your design. Add the ones you need with **Add tile**, or choose a layout that already groups them.
## Start with a question
| Question | Use |
| --- | --- |
| How deep and loud does it play? | [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl), then [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl). |
| Can it reach my listening target? | [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom), with the intended distance and crest factor. |
| Why is the port likely to be noisy? | [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity), including the rear port where present. |
| Why does my horn have a notch? | [Horn Radiating Outputs](https://simulator.00aud.io/docs/reference/tiles/horn-radiating-outputs) and the [Schematic](https://simulator.00aud.io/docs/reference/tiles/schematic). |
| Which of these designs suits my band? | [Metrics](https://simulator.00aud.io/docs/reference/tiles/metrics) and [Compare](https://simulator.00aud.io/docs/reference/tiles/compare). |
## Read the response
Start with the output, then inspect its shape, phase, delay and electrical load.
- [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl): Sound pressure level in dB at each frequency for every visible enclosure, at its power and EQ, the radiation space and the listening distance.
- [Transfer Function Magnitude](https://simulator.00aud.io/docs/reference/tiles/transfer-function): Each design’s response in dB against its own reference level, so power and listening distance drop out and only the shape is left.
- [Phase](https://simulator.00aud.io/docs/reference/tiles/phase): The phase of each design’s sound in degrees at each frequency, including EQ and filters, wrapped to the range −180° to +180°.
- [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay): How late each frequency arrives, in ms, worked out from how fast the phase turns. EQ and filters are included.
- [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance): The electrical load the amplifier sees, in ohms, at each frequency: its size only, not its phase.
## Check the limits
Use the power and filters you intend to run. Output alone cannot tell you whether a design has enough travel or port area.
- [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl): The loudest each design can play at each frequency, one sine at a time, before the cone reaches Xmax or the driver reaches its thermal limit.
- [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom): Your listening level and its peaks against what the design can play cleanly at each frequency, counting cone travel, heat, port air speed and passive radiators.
- [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion): How far the cone travels from rest, peak and one way, in mm at each frequency, against the driver’s Xmax.
- [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity): Peak air speed in the port, in m/s, at each frequency, against the warning line.
- [Port Velocity (Rear Chamber)](https://simulator.00aud.io/docs/reference/tiles/rear-port-velocity): Peak air speed in a bandpass box’s rear-chamber port, in m/s, at each frequency, against the warning line.
- [Port Volume Velocity](https://simulator.00aud.io/docs/reference/tiles/port-volume-velocity): How much air flows through a vented box’s port each second, at its peak, at each frequency.
- [Cone Velocity](https://simulator.00aud.io/docs/reference/tiles/cone-velocity): How fast the cone moves, at its peak, at each frequency: m/s, or mm/s below 1 m/s.
- [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion): How far each passive radiator travels, peak and one way, in mm at each frequency, against its own Xmax.
- [Amplifier Load (VA)](https://simulator.00aud.io/docs/reference/tiles/amplifier-load): Apparent amplifier demand in VA at each frequency, with optional RMS current.
## Shape and inspect a horn
Edit the acoustic path, try a cabinet fold and read the air inside the horn.
- [Horn Editor](https://simulator.00aud.io/docs/reference/tiles/horn-editor): The unfolded horn path as a drawing or a table, including spans, flares, stuffing and driver entries.
- [Fold](https://simulator.00aud.io/docs/reference/tiles/fold): A cabinet fold with boards, driver placement and checks against the intended horn.
- [Horn Pressure](https://simulator.00aud.io/docs/reference/tiles/horn-pressure): RMS acoustic pressure in Pa, or its phase, at a chosen station inside the horn.
- [Horn Particle Velocity](https://simulator.00aud.io/docs/reference/tiles/horn-particle-velocity): Peak air-particle speed in m/s at a chosen station inside the horn.
- [Horn Acoustic Impedance](https://simulator.00aud.io/docs/reference/tiles/horn-acoustic-impedance): Pressure divided by volume flow at a horn station, as magnitude, phase, resistance or reactance.
- [Horn Radiating Outputs](https://simulator.00aud.io/docs/reference/tiles/horn-radiating-outputs): Each radiating mouth, port or exposed cone separately, plus their coherent total.
## Edit and compare
Put the relevant controls and comparisons beside the response you are working on.
- [Metrics](https://simulator.00aud.io/docs/reference/tiles/metrics): Visible designs ranked by one selected measure, at a frequency or over a band when applicable.
- [Insights](https://simulator.00aud.io/docs/reference/tiles/insights): Rule-based notes about visible designs, including travel, port behaviour and response shape.
- [Compare](https://simulator.00aud.io/docs/reference/tiles/compare): Two different quantities against the same frequency axis, each with its own vertical scale.
- [Schematic](https://simulator.00aud.io/docs/reference/tiles/schematic): How drivers, chambers, ports and horn paths connect acoustically.
- [EQ Editor](https://simulator.00aud.io/docs/reference/tiles/eq-editor): SPL with editable filter handles for the selected enclosure or horn driver.
- [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout): The selected driver on a rectangular baffle, with the model’s baffle-step transition and correction.
- [T/S Parameters](https://simulator.00aud.io/docs/reference/tiles/ts-parameters): The selected driver’s electrical, mechanical and physical parameters, plus derived interpretation and sealed targets.
## Keep output and limits together
A useful starting set is **SPL (dB)**, **Excursion** and the outlet’s velocity or travel tile. Keep **Headroom** beside them when choosing a listening level. A blank port, radiator or horn tile may simply mean none of the visible enclosures has that part.
---
# SPL (dB)
> How to read the SPL tile in 00 Simulator: the level each design plays at your power and distance, its F3 and F10 markers, EQ on the curve and baffle step.
Source: https://simulator.00aud.io/docs/reference/tiles/spl
How loud each design plays at each frequency, at its set power and EQ and your listening distance. It is the tile to judge bass extension and response shape on, and to shape with EQ.
- **Shows:** Sound pressure level in dB at each frequency for every visible enclosure, at its power and EQ, the radiation space and the listening distance.
- **Healthy when:** The curve is smooth through the band you want, and F3 sits where you need the bass to reach.
- **If it is not:** Change the box or tuning for extension and EQ for shape, then check the limits at the power you will use.
## The tile
_Figure: The SPL (dB) tile for the vented example at 1 W, with F3 and F10 marked._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 1 W, half space, 1 m. Simulated when this page was built.
- Vented example, 1 W: loudest octave 88.1 dB
| Curve | Marker | Frequency | Level |
| --- | --- | --- | --- |
| Vented example, 1 W | F3 | 30.3 Hz | 85.1 dB |
| Vented example, 1 W | F10 | 24.9 Hz | 78.1 dB |
The vented example plays 88.1 dB averaged over its loudest octave at 1 W. The level is 3 dB below that at 30.3 Hz (F3) and 10 dB below at 24.9 Hz (F10).
- [Open this example](https://simulator.00aud.io/app?template=vented) in the simulator and switch on **F3** in the tile header for the markers. Hover the curve for the level at a frequency, or click the chart to hold the readout there.
- Each visible enclosure draws its own curve and its own markers, in its colour.
- A multiple-entry horn also draws a dashed line for each amplifier channel beside its solid total. The channels add with their phase, so the total is not the sum of their levels.
- The level is at the **Radiation space** and **Listening distance** set in the **Environment** section of the Driver panel: half space and 1 m unless you change them.
## How to read it
- Read the shape first: where the bass starts to fall, how steeply, and whether there is a hump or a dip on the way. Then read the level.
- F3 and F10 are measured down from each curve’s own loudest octave, not from a fixed level, so a quiet design and a loud one get comparable markers.
- The level follows the power: each doubling adds 3.0 dB. Compare designs at the same power, or on [Transfer Function Magnitude](https://simulator.00aud.io/docs/reference/tiles/transfer-function), which takes the level out.
- This tile does not say whether the driver survives that level. [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion), [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl) and [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom) do.
- It is the response without a room. **Radiation space** adds the gain of nearby walls and floor, but room modes and reflections are not in it.
## F-points
**F3** in the tile header shows or hides the markers. The cog beside it, **F-point settings**, chooses which ones and what they are measured from. On a desktop, **Pin to side** keeps those settings beside the chart.
| Setting | What it does | To start |
| --- | --- | --- |
| **F3**, **F6**, **F10** | Mark where each curve falls 3, 6 or 10 dB below its reference level. | F3 and F10 on, F6 off |
| **Custom** | A level of your own, from 0.1 to 80 dB down. | Off, at 4.7 dB |
| **Baffle step Fc** | Shows or hides the baffle step line, for enclosures that simulate it. | On |
| **Active enclosure only** | Markers for the selected enclosure only, instead of every visible one. | Off |
| **Advanced** › **Reference level** | What the markers are measured down from: **Auto · loudest octave average**, **Selected band average** over a band you type, or **Response peak**. It also lists each enclosure’s reference level and band. | Auto; a typed band starts at 50–100 Hz |
_Figure: The SPL (dB) tile for the bandpass example at 100 W, with F3 and F10 marked at both edges._
B&C 18SW115 in the fourth-order bandpass example, at 100 W, half space, 1 m. Simulated when this page was built.
- Bandpass example, 100 W
| Curve | Marker | Frequency | Level |
| --- | --- | --- | --- |
| Bandpass example, 100 W | F3L | 38.9 Hz | 108.9 dB |
| Bandpass example, 100 W | F3H | 92.2 Hz | 108.9 dB |
| Bandpass example, 100 W | F10L | 27.2 Hz | 101.9 dB |
| Bandpass example, 100 W | F10H | 134 Hz | 101.9 dB |
- Bandpass boxes and horns get two markers for each level, L at the low edge and H at the high edge. The bandpass example is 3 dB down at 38.9 Hz and 92.2 Hz, and 10 dB down at 27.2 Hz and 134 Hz.
- For a narrow bandpass box or a horn with separate humps, **Auto** can pick the wrong octave. Choose **Selected band average** and type the band you mean as the passband; humps outside it are ignored.
- A dip inside the band that falls below a marker’s level does not move the marker: markers show the outer edges, and **Advanced** notes the dip.
- The **Metrics** tile’s F3 and F10 always use **Auto**, whatever this tile is set to.
## Other lines on the tile
- **PR** marks a vented box’s port resonance: the frequency where the air in the port rings like an organ pipe. In the vented example it is at 482 Hz, past the default 400 Hz axis; set **Upper frequency** in **Settings › Display…** to 1 kHz to see it.
- A sixth-order bandpass box marks **Front PR** and **Rear PR**, and a horn with a ported rear chamber marks **Rear PR**. Here PR means port resonance, not passive radiator.
- A box with **Simulate baffle step** switched on, in the **Baffle step** section of the Enclosure panel, gets a line labelled Baffle at its transition frequency.
_Figure: The sealed example’s SPL with baffle step off and on, and the baffle transition line at 364 Hz._
Dayton Audio DCS205-4 in the 15 L sealed example, at 1 W, half space, 1 m. Simulated when this page was built.
- Baffle step off
- Baffle step on, 300 × 450 mm: −6.0 dB at 20 Hz
| Curve | Marker | Frequency | Level |
| --- | --- | --- | --- |
| Baffle step on | Baffle 364 Hz | 364 Hz | |
On the sealed example, **Simulate baffle step** with the default 300 × 450 mm baffle puts the transition at 364 Hz. Below it the bass wraps round the box instead of going forward: the curve is 3.0 dB lower at the transition and 6.0 dB lower at 20 Hz. The most it takes is **Step depth**, 6 dB to start. It is a smooth shelf; the ripple a real baffle edge adds is not modelled. The [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout) tile moves the driver on the baffle.
## EQ on the tile
- Every curve includes its enclosure’s EQ and filters that are switched on, whether or not you are editing them.
- Click **EQ** in the tile header to draw the selected enclosure’s filters over the chart and drag them into place. **Exit** puts the tile back.
- Right-click the chart and choose **Add filter** to put a high-pass, low-pass, parametric EQ, shelf or Linkwitz transform at the frequency you clicked.
- The [EQ Editor](https://simulator.00aud.io/docs/reference/tiles/eq-editor) tile is always in this mode. [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters#on-the-graph) covers each handle.
## What moves it
| Change | Effect | Why |
| --- | --- | --- |
| Double the power | +3.0 dB | The whole curve moves with the drive level. |
| Half space to quarter space | +6 dB | One more boundary next to the box. The same at every frequency for a box; a horn’s shape changes too. The app notes the offsets hold best at low frequencies. |
| Double the listening distance | −6.0 dB | Level falls with distance, and the tile reads it at the distance you set. |
| **Simulate baffle step** on | Up to −6 dB below the transition | A box on a stand loses the bass a wall would have sent forward. |
| Tune the vented example to 28 Hz instead of 36 Hz | F3 32.6 Hz → 29.6 Hz | Lower tuning reaches deeper; the port gets longer. |
| A high-pass filter | Less level below its corner | Every filter that is switched on is in the curve. |
## Settings and controls
| Control | Where | What it does |
| --- | --- | --- |
| **F3** | Tile header | Shows or hides the F-point markers. Off on a new tile. |
| **F-point settings** | The cog beside **F3** | Which markers show and what they are measured from ([above](#f-points)). |
| **EQ** | Tile header | Edits the selected enclosure’s filters on the chart. **Exit** leaves. |
| **Y-axis settings** | Tile header | **Auto** fits the curves; **Manual** takes a **Min** and **Max**. Either way the axis stops at 50 dB. |
| **Add filter**, **Add note** | Right-click the chart | A filter, or a note, at the frequency you clicked. |
| **Fix** | Over the chart | A design whose whole response is below 50 dB is left off the chart with a warning in its place. When the cause is a port with no room left (0 L), **Fix** takes you to the port settings. |
## What to try
| Try | What it changes |
| --- | --- |
| [Mark F3 and F10](https://simulator.00aud.io/docs/start/reading-a-response#f3-and-f10) | Switch on **F3** in the tile header to mark where each curve falls 3 dB and 10 dB below its loudest octave. |
| [Shape it with EQ](https://simulator.00aud.io/docs/guides/eq-and-filters) | Click **EQ** in the tile header, or right-click the chart and choose **Add filter**. The curve includes every filter that is switched on. |
| [Check it can play that loud](https://simulator.00aud.io/docs/reference/tiles/max-spl) | This tile is at the set power. **Max SPL (dB)** shows how loud each design can go before excursion or heat stops it. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate my open workspace and tell me each enclosure’s F3, F10 and the level of its loudest octave. Then put the SPL (dB) tile on screen and mark each F3 with a line.
---
# Transfer Function Magnitude
> How to read the Transfer Function Magnitude tile in 00 Simulator: each design’s response shape against its own reference, with power taken out.
Source: https://simulator.00aud.io/docs/reference/tiles/transfer-function
Each design’s response as dB above or below its own reference level. Power and listening distance drop out, so this is the tile to compare the shape of different boxes on, whatever their sensitivity.
- **Shows:** Each design’s response in dB against its own reference level, so power and listening distance drop out and only the shape is left.
- **Healthy when:** The curve holds near 0 dB through the band you want and rolls off smoothly below it, with no peak you did not plan.
- **If it is not:** Change the box, tuning or EQ for the shape, then read the level on the SPL tile.
## The tile
_Figure: The Transfer Function Magnitude tile for the vented example, with the dashed 0 dB reference line._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at any power, half space, 1 m. Simulated when this page was built.
| Curve | Reference | At 30 Hz |
| --- | --- | --- |
| Vented example | 88.1 dB SPL at 1 W | −3.2 dB |
Here the vented example’s 0 dB is 88.1 dB at 1 W, and at 30 Hz it is −3.2 dB. At 200 W the SPL is higher but this curve is the same: the largest difference is 0.0 dB.
- [Open this example](https://simulator.00aud.io/app?template=vented) in the simulator and add the tile, then hover the curve for the level at a frequency.
- Each visible enclosure draws its own curve in its colour, each against its own reference. The dashed line is 0 dB.
- For most enclosures, 0 dB is the average level over the top end of the simulated range: its highest 12 % of frequencies, on the chart’s log scale.
- For a bandpass box, which falls away at both ends, 0 dB is its peak.
## How to read it
- Below 0 dB is how far the bass has fallen compared with the top of the range. Above 0 dB is a hump.
- Boxes with different drivers or power line up near 0 dB, so the tile shows which one keeps its level deeper, not which is louder.
- It is the same curve as [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl) moved up or down, EQ and all. Read the level there, and the limits on [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) and [Max SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/max-spl).
- The F3 markers on the SPL tile measure from the loudest octave, not from this 0 dB, so the two can differ a little on a curve that is not flat at the top.
## Three shapes
The sealed, vented and bandpass examples: three drivers and three powers, on one scale.
_Figure: The sealed, vented and bandpass examples on the Transfer Function Magnitude tile._
The sealed example (Dayton Audio DCS205-4, 15 L), the vented example (Ciare 12.00SW, 55 L at 32 Hz) and the bandpass example (B&C 18SW115), half space, 1 m. Simulated when this page was built.
| Curve | At 30 Hz | At 60 Hz | 0 dB is |
| --- | --- | --- | --- |
| Sealed example | −11.8 dB | −3.2 dB | the top of the range |
| Vented example | −3.2 dB | −2.0 dB | the top of the range |
| Bandpass example | −8.8 dB | 0.0 dB | its peak |
- The sealed box rolls off early and gently: −11.8 dB at 30 Hz.
- The vented box holds its level down to its 32 Hz tuning and then falls fast: −3.2 dB at 30 Hz.
- The bandpass box peaks at 0 dB and falls away on both sides: −8.8 dB at 30 Hz.
> **Horns read high** A horn uses the same top-of-range reference as a sealed or vented box. Most horns are well down by the top of the range, so the passband sits above 0 dB, often above the top of the axis. In the tapped horn example, simulated to 500 Hz for this page, it reaches +15.2 dB. **Upper frequency** in **Settings › Display…** sets how far the solver runs, so it moves this reference too. Read a horn’s level on [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl).
## What moves it
| Change | Effect | Why |
| --- | --- | --- |
| Power, 1 W to 200 W | None (0.0 dB) | The SPL and its reference rise together. |
| Listening distance | None | It moves every frequency by the same amount. |
| Radiation space | None for a box | A box moves by the same amount at every frequency. A horn’s shape changes, because the walls and floor change how its mouth radiates. |
| A 25 Hz high-pass, 24 dB/oct | −10.1 dB → −13.2 dB at 25 Hz | EQ is in the curve, as on the SPL tile. |
| Box size, tuning or enclosure type | The shape | This is what the tile is for. |
| **Upper frequency** | Can shift the whole curve | The reference is the top of the simulated range. |
## Settings and controls
| Control | Where | What it does |
| --- | --- | --- |
| **EQ** | Tile header | Edits the selected enclosure’s filters on the chart. **Exit** leaves. |
| **Y-axis settings** | Tile header | Shows −30 to +5 dB in 5 dB steps, in **Auto** and **Manual** alike. For more room, type a **Min** (down to −80 dB) and **Max** in **Manual**. |
| **Add filter**, **Add note** | Right-click the chart | A filter, or a note, at the frequency you clicked. |
## What to try
| Try | What it changes |
| --- | --- |
| [Compare shapes, not levels](https://simulator.00aud.io/docs/guides/compare) | A quiet design and a loud one both sit near 0 dB here, so you see only how each box rolls off. |
| [Try a high-pass](https://simulator.00aud.io/docs/guides/eq-and-filters) | Filters show here as they do on **SPL (dB)**: click **EQ** in the tile header, or right-click the chart and choose **Add filter**. |
| [Read horns on SPL](https://simulator.00aud.io/docs/reference/tiles/spl) | A horn’s passband can sit well above 0 dB on this tile. **SPL (dB)** shows its real level. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate my open workspace and compare the response shape of each enclosure regardless of its level: how many dB each is below its own passband at 25, 35 and 50 Hz. Then put the Transfer Function Magnitude tile on screen.
---
# Phase
> How to read the Phase tile in 00 Simulator: the acoustic phase of each design in degrees, including EQ and filters, and why the line jumps at ±180°.
Source: https://simulator.00aud.io/docs/reference/tiles/phase
Where each frequency’s sound sits in its cycle, in degrees, with EQ and filters included. It shows how much a box and its filters turn the sound, which matters where two sources play the same notes.
- **Shows:** The phase of each design’s sound in degrees at each frequency, including EQ and filters, wrapped to the range −180° to +180°.
- **Healthy when:** It turns smoothly. A jump from −180° to +180° is the wrap, not a fault.
- **If it is not:** A fast twist comes from a resonance or a steep filter. Check the same frequency on the SPL tile, and try a gentler filter slope.
## The tile
_Figure: The Phase tile for the vented example, with the phase wrapping from −180° to +180° near the box tuning._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at any power, half space, 1 m. Simulated when this page was built.
| Frequency | Phase |
| --- | --- |
| 20 Hz | −100° |
| 30 Hz | −167° |
| 40 Hz | 120° |
| 60 Hz | 79° |
| 100 Hz | 45° |
| 200 Hz | −2° |
| 400 Hz | −40° |
Reading left to right, the vented example’s phase falls steadily. Near 31.2 Hz, close to its 32 Hz tuning, it passes −180° and carries on from +180°. That jump is the wrap, not a change in the sound.
- [Open this example](https://simulator.00aud.io/app?template=vented) in the simulator and add the tile, then hover the curve for the phase at a frequency.
- Each visible enclosure draws its own line in its colour.
- It is the phase of the sound each design makes, not of its impedance. The [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance) tile shows magnitude only.
## How to read it
- A whole cycle is 360°. The tile folds every angle into −180° to +180°, so a vertical jump from one edge to the other is the same angle, one turn on.
- The phase turns fastest where the level changes fastest: around a tuning, a resonance and a filter’s corner. How fast it turns is the delay on [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay).
- The steeper the roll-off, the further it turns. Below its tuning a vented box turns about twice as far as a sealed box does below its resonance.
- Phase counts where two sources play the same frequencies, such as a subwoofer and the main speakers around the crossover. The tile shows each design on its own; it does not add two together.
- The time sound takes to reach you is left out: **Listening distance** does not change this tile.
## Filters turn it too
A high-pass filter turns the phase well above its corner. The same vented box with a 25 Hz high-pass:
_Figure: The vented example’s phase with and without a 25 Hz Butterworth 24 dB/oct high-pass._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at any power, half space, 1 m. Simulated when this page was built.
| Frequency | No filter | 25 Hz high-pass |
| --- | --- | --- |
| 40 Hz | 120° | −140° |
| 60 Hz | 79° | 142° |
| 100 Hz | 45° | 82° |
| 200 Hz | −2° | 16° |
Added to the vented example’s phase, simulated when this page was built. The steeper filters turn it further, and the turn is still 38° at 100 Hz, 4 times the corner frequency, for the 24 dB/oct Butterworth.
| 25 Hz high-pass | Turn at 40 Hz | Turn at 100 Hz |
| --- | --- | --- |
| Bessel, 12 dB/oct | 48° | 19° |
| Butterworth, 12 dB/oct | 55° | 21° |
| Butterworth, 24 dB/oct | 100° | 38° |
| Linkwitz-Riley, 24 dB/oct | 110° | 41° |
A gentler slope turns it less: the 12 dB/oct Butterworth adds 21° at 100 Hz. The Phase tile has no **EQ** button; edit filters on [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl#eq-on-the-tile), on the [EQ Editor](https://simulator.00aud.io/docs/reference/tiles/eq-editor) tile or in **EQ / filters** in the Driver panel, and this tile follows.
## What moves it
| Change | Effect | Why |
| --- | --- | --- |
| Power, 1 W to 200 W | None (0°) | Turning the level up does not change the timing. |
| **Listening distance** | None | The time the sound takes to travel is left out. |
| **Radiation space** | None for a box | A box only gets louder. A horn’s phase changes, because the walls and floor change how its mouth radiates. |
| A high-pass or low-pass filter | Turns it, most near the corner | Every filter that is switched on is in the phase. |
| Box type and tuning | Where and how far it turns | A higher-order box turns further below its tuning. |
| **Non-horn upper response** | None | It only changes the level; phase always uses the physical model. |
## Settings and controls
| Control | Where | What it does |
| --- | --- | --- |
| **Y-axis settings** | Tile header | Shows −180° to 180° with a line every 45°, in **Auto** and **Manual** alike. **Manual** takes other limits as a **Min** and **Max**. |
| **Add note** | Right-click the chart | A note at the frequency you clicked. |
## What to try
| Try | What it changes |
| --- | --- |
| [Read the delay](https://simulator.00aud.io/docs/reference/tiles/group-delay) | The faster the phase turns, the later that frequency arrives. **Group Delay** shows it in milliseconds. |
| [Try a gentler slope](https://simulator.00aud.io/docs/guides/eq-and-filters#slopes) | A 12 dB/oct high-pass turns the phase less than a 24 dB/oct one at the same frequency. |
| [Compare two designs](https://simulator.00aud.io/docs/guides/compare) | Each visible enclosure draws its own line in its colour, so you can see where their phase parts company. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, try a 25 Hz Butterworth 24 dB/oct high-pass on each enclosure in my open workspace without saving, and tell me how much it turns the phase at 40, 80 and 120 Hz. Then put the Phase tile on screen.
---
# Group Delay
> How to read the Group Delay tile in 00 Simulator: how late each frequency arrives, in milliseconds, and what box, tuning and filters do to it.
Source: https://simulator.00aud.io/docs/reference/tiles/group-delay
How late each frequency arrives, in milliseconds, worked out from how fast the phase turns. It peaks near a box’s tuning and a filter’s corner, so it is the tile for comparing how tight different bass designs are in time.
- **Shows:** How late each frequency arrives, in ms, worked out from how fast the phase turns. EQ and filters are included.
- **Healthy when:** Delay stays low through the band you care about, with no tall, narrow peak.
- **If it is not:** A sealed box or a higher tuning lowers the peak; a high-pass adds to it, more the steeper it is. Compare the options here.
## The tile
_Figure: The Group Delay tile for the vented example, peaking near its 32 Hz tuning._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at any power, half space, 1 m. Simulated when this page was built.
| Group Delay | Peak | At |
| --- | --- | --- |
| Vented example | 26.9 ms | 31 Hz |
The vented example peaks at 26.9 ms near 30.9 Hz, just below its 32 Hz tuning, and falls to 1.9 ms by 100 Hz. At the peak, sound at that frequency arrives as late as if it came from 9.2 m further away.
- [Open this example](https://simulator.00aud.io/app?template=vented) in the simulator and add the tile, then hover the curve for the delay at a frequency.
- Each visible enclosure draws its own line in its colour.
- The delay includes EQ and filters. The time sound takes to reach you does not count: **Listening distance** does not change this tile.
## How to read it
- It is the slope of the [Phase](https://simulator.00aud.io/docs/reference/tiles/phase) tile: where the phase turns fast, that frequency arrives late.
- The peak sits near the tuning of a vented or passive-radiator box and near the corner of a high-pass. A few octaves above them, the delay is small.
- There is no single number that is too much for every system. Compare designs on the same tile, at the frequencies your music uses.
- A box’s line stays between 0 and 100 ms. A horn’s line can dip below 0 ms, and it breaks where the horn’s outputs cancel, because the delay is undefined there.
## Box, tuning and filters
The vented example’s driver in the same 55 L, sealed and vented, and vented with a 25 Hz high-pass.
_Figure: Group delay of the Ciare 12.00SW in 55 L: sealed, vented at 32 Hz, and vented with a 25 Hz high-pass._
Ciare 12.00SW in 55 L, sealed and vented at 32 Hz, the high-pass a Butterworth 24 dB/oct. Half space, 1 m, simulated when this page was built.
| Design | Peak | At | At 30.9 Hz |
| --- | --- | --- | --- |
| Sealed, 55 L | 10.3 ms | 10.0 Hz | 4.5 ms |
| Vented, 32 Hz | 26.9 ms | 30.9 Hz | 26.9 ms |
| Vented with a 25 Hz high-pass | 43.8 ms | 29.4 Hz | 42.9 ms |
- Sealed, the same driver has 4.5 ms of delay at 30.9 Hz against 26.9 ms vented. It pays in bass: F3 is 81.2 Hz sealed against 30.3 Hz vented.
- A high-pass below the tuning protects the cone, and adds its own delay on top: the peak rises from 26.9 ms to 43.8 ms.
## What moves it
A lower tuning reaches deeper, and the bass there arrives later.
| Vented example tuned to | Peak delay | F3 |
| --- | --- | --- |
| 28 Hz | 28.8 ms at 26.1 Hz | 29.6 Hz |
| 32 Hz | 26.9 ms at 30.9 Hz | 30.3 Hz |
| 36 Hz | 25.5 ms at 35.7 Hz | 32.6 Hz |
The steeper the filter, the more delay it adds.
| Vented example with a 25 Hz high-pass | Peak delay |
| --- | --- |
| No filter | 26.9 ms at 30.9 Hz |
| Bessel, 12 dB/oct | 32.0 ms at 30.9 Hz |
| Butterworth, 12 dB/oct | 33.8 ms at 30.9 Hz |
| Linkwitz-Riley, 24 dB/oct | 40.9 ms at 30.1 Hz |
| Butterworth, 24 dB/oct | 43.8 ms at 29.4 Hz |
Power and **Listening distance** leave the tile alone: at 200 W the curve is the same as at 1 W (the largest difference is 0.0 ms).
## Settings and controls
| Control | Where | What it does |
| --- | --- | --- |
| **Y-axis settings** | Tile header | Starts on **Auto**, which fits the lines in 5 ms steps and keeps room below 0 ms. **Manual** takes a **Min** and **Max**. |
| **Add note** | Right-click the chart | A note at the frequency you clicked. |
The tile has no **EQ** button. Edit filters on [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl#eq-on-the-tile), the [EQ Editor](https://simulator.00aud.io/docs/reference/tiles/eq-editor) tile or **EQ / filters** in the Driver panel, and this tile follows.
## What to try
| Try | What it changes |
| --- | --- |
| [Compare a sealed box](https://simulator.00aud.io/docs/boxes/sealed) | The same driver sealed has far less delay near the tuning, and less deep bass. |
| [Try a gentler high-pass](https://simulator.00aud.io/docs/guides/eq-and-filters#slopes) | A 12 dB/oct high-pass adds less delay than a 24 dB/oct one at the same frequency. |
| [Read the phase](https://simulator.00aud.io/docs/reference/tiles/phase) | **Phase** shows the turn this tile is worked out from. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate my open workspace and tell me each enclosure’s peak group delay and the frequency it is at. Then try a 25 Hz high-pass at 12 and at 24 dB/oct on each vented box without saving, and tell me how much each adds to the peak and to F3.
---
# Impedance
> How to read the Impedance tile in 00 Simulator: the load your amplifier sees, where the box and port tuning show, and why the lowest point matters.
Source: https://simulator.00aud.io/docs/reference/tiles/impedance
The electrical load each design puts on the amplifier, in ohms, at each frequency. Its peaks show where the box and port are tuned, and its lowest point is the load the amplifier has to drive.
- **Shows:** The electrical load the amplifier sees, in ohms, at each frequency: its size only, not its phase.
- **Healthy when:** The peaks sit where the box and port are tuned, and the lowest point is a load your amplifier can drive.
- **If it is not:** Check the box volume and tuning, and plan the amplifier for the lowest point rather than the nominal rating.
## The tile
_Figure: The Impedance tile for the sealed and vented examples: one peak for the sealed box, two peaks with a dip at 32 Hz for the vented box, and the 4 Ω nominal rating as a line._
The sealed example (Dayton Audio DCS205-4 in 15 L) and the vented example (Ciare 12.00SW in 55 L tuned to 32 Hz), half space, 1 m. Simulated when this page was built.
| Impedance | Peak | At |
| --- | --- | --- |
| Sealed, 15 L | 40.4 Ω | 54 Hz |
| Vented, 55 L at 32 Hz | 22.8 Ω | 19 Hz |
The sealed example peaks at 40.4 Ω at 53.6 Hz. The vented example has two peaks, at 19.1 Hz and 49.9 Hz, and between them a dip to 4.63 Ω at 31.6 Hz, at its 32 Hz tuning. Higher up the vented example falls to 3.53 Ω at 191 Hz, below its driver’s 4 Ω rating; the sealed example bottoms out at 4.06 Ω at 182 Hz.
- Open the [sealed example](https://simulator.00aud.io/app?template=sealed) or the [vented example](https://simulator.00aud.io/app?template=vented) in the simulator, then hover the curve for the ohms at a frequency.
- Each visible enclosure draws one line in its colour. The value is what the amplifier sees: the drivers as they are wired, plus the **Series resistance** and any **Series capacitor**.
- A multiple-entry horn draws its throat driver as the main line and each other driver as a dashed line, named D2, D3 and so on in the legend, because each driver has its own amplifier channel.
- The curve is the size of the impedance only. The **Phase** tile shows the phase of the sound, not of the impedance; **Compare** can plot **Electrical Phase** beside impedance.
- The **Headroom** tile’s **Amp** pane lists the same curve’s **Min impedance** and **Max impedance** beside the **Nominal load**, with the voltage and current your target level needs.
## How to read it
- A peak is a resonance. On its own in free air a driver peaks at its Fs; in a sealed box the air behind the cone stiffens it, so the peak moves up. The Dayton Audio DCS205-4 has an Fs of 32.3 Hz and peaks at 53.6 Hz in 15 L.
- A vented box splits that peak in two. The dip between them sits at the port tuning, where the port does the work and the cone barely moves: 31.6 Hz for a box tuned to 32 Hz. Neither peak is at the driver’s Fs (29 Hz for the Ciare 12.00SW).
- Above the peaks the curve settles close to the coil’s resistance, Re, plus the series resistance, then rises slowly as the coil’s inductance takes over. The vented example bottoms out at 3.53 Ω at 191 Hz (Re 3.30 Ω).
- The lowest point is an important amplifier-load check: the nominal rating is a label, not a floor. A tall peak is not a problem in itself; the amplifier delivers little current there.
- Power and EQ do not move the curve. They change how hard the design is driven, not the load: the vented example’s curve is the same at 1 W and at 100 W.
> **Use it to check a build** Impedance is easy to measure on a real box. If the dip of a vented box lands away from where the simulation puts it, the port is not the length or area you think, or the box volume differs.
## What each enclosure looks like
The app’s examples from 10 to 400 Hz, simulated when this page was built.
| Example | Peaks | Dips between them | Lowest point |
| --- | --- | --- | --- |
| Sealed, 15 L | 53.6 Hz | None | 4.06 Ω at 182 Hz |
| Vented, 55 L at 32 Hz | 19.1 Hz, 49.9 Hz | 31.6 Hz | 3.53 Ω at 191 Hz |
| Passive radiator, 10 L | 30.1 Hz, 54.9 Hz | 37.4 Hz | 3.55 Ω at 205 Hz |
| Bandpass 4, front tuned to 59 Hz | 36.5 Hz, 95.3 Hz | 57.6 Hz | 3.47 Ω at 226 Hz |
| Tapped horn | 22.6 Hz, 47.5 Hz, 105 Hz | 39.2 Hz, 80.6 Hz | 6.18 Ω at 221 Hz |
- A sealed box has one peak, at the resonance of the driver on the air in the box.
- A vented box, a passive radiator box and a fourth-order bandpass box have two peaks. The dip between them is the tuning of the port or passive radiator.
- A horn has a peak for each of its own resonances, so its curve is busier.
## What moves it
| Change | Effect | Why |
| --- | --- | --- |
| A smaller sealed box | Peak from 53.6 Hz (15 L) to 68.1 Hz (8 L); 44.2 Hz in 30 L | Less air is a stiffer spring behind the cone. |
| A lower port tuning | Dip from 31.6 Hz (32 Hz tuning) to 28.0 Hz (28 Hz) | The dip follows the tuning. |
| More drivers | Parallel lowers the load, series raises it | Set by **Number of drivers** and **Wiring**. The peaks move too, because the drivers share the box. |
| **Series resistance** | Adds to the whole curve | Cable and amplifier resistance sit in series with the drivers. |
| A **Series capacitor** | Rises steeply at the bottom | The capacitor’s own impedance grows as the frequency falls. |
| Power or EQ | No change | They set the drive, not the load. |
## What to try
| Try | What it changes |
| --- | --- |
| [Find the tuning](https://simulator.00aud.io/docs/boxes/vented) | A vented box draws two peaks with a dip between them. The dip sits at the port tuning, so it checks the box does what you meant. |
| Read the lowest point | Above the peaks the curve falls close to the voice coil’s resistance, often below the nominal rating. That is the load the amplifier has to drive. |
| [Change the wiring](https://simulator.00aud.io/docs/boxes/multiple-drivers) | With several drivers, **Number of drivers** and **Wiring** set the load: parallel lowers it, series raises it. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate every enclosure in my open workspace and read its impedance from 10 to 400 Hz. For each one, tell me the frequency and ohms of every peak, the dip between them, and the lowest impedance, and compare the lowest point with the driver’s nominal rating.
---
# Max SPL (dB)
> How to read the Max SPL tile in 00 Simulator: the loudest a design can play at each frequency before Xmax or its thermal limit, and the three thermal rules.
Source: https://simulator.00aud.io/docs/reference/tiles/max-spl
The loudest each design can play at each frequency before a limit stops it: the cone reaching Xmax, or the driver reaching its thermal limit. It describes what the driver and box can take, so your power setting and EQ do not move it.
- **Shows:** The loudest each design can play at each frequency, one sine at a time, before the cone reaches Xmax or the driver reaches its thermal limit.
- **Healthy when:** The line sits above the level you want, with room to spare, across the band you will play.
- **If it is not:** More cone area where Xmax sets the line, more drivers to share the power where heat sets it, or a lower level.
## The tile
_Figure: The Max SPL tile for the vented example with Limits on: the Max SPL line and the two ceilings it follows, the power limit dashed and Xmax dotted._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, half space, 1 m, with the default thermal rule. Max SPL does not depend on the input power you set. Simulated when this page was built.
| Frequency | Max SPL | Power limit ceiling | Xmax ceiling | Set by |
| --- | --- | --- | --- | --- |
| 20 Hz | 93.7 dB | 111.3 dB | 93.7 dB | Xmax |
| 32 Hz | 120.7 dB | 120.7 dB | 123.6 dB | Heat |
| 50 Hz | 117.9 dB | 127.4 dB | 117.9 dB | Xmax |
| 100 Hz | 122.4 dB | 122.4 dB | 125.4 dB | Heat |
| 200 Hz | 121.3 dB | 121.3 dB | 137.1 dB | Heat |
In the vented example the line reads 120.7 dB at the 32 Hz tuning, where heat sets it: the port does the work there and the cone barely moves, so the Xmax ceiling shoots up to 123.6 dB. Either side of the tuning the cone moves more and Xmax takes over.
- [Open this example](https://simulator.00aud.io/app?template=vented) in the simulator and add **Max SPL (dB)** with **Add tile**. Hover the line for the level at a frequency.
- Click **Limits** in the tile header to draw both ceilings: the thermal ceiling dashed and the Xmax ceiling dotted. Hover with Limits on and the legend lists both ceilings, the excursion against Xmax, and the rule’s own quantity (power, voltage or coil heat) against its limit.
- The tile’s **Settings** choose the thermal rule and the voice coil temperature, for every enclosure in the workspace. **Pin settings to side** keeps them open beside the tile.
- When a setting differs from the default, a small chip beside the tile title names it, so a shared chart says how it was drawn. The settings are saved with the workspace and used by share links and your assistant.
Which ceiling sets the vented example’s line, from 10 to 400 Hz.
| Frequencies | Set by |
| --- | --- |
| Below 30.9 Hz | Xmax: the cone runs out of travel |
| 30.9 Hz to 34.8 Hz | Heat: the power limit |
| 34.8 Hz to 86.6 Hz | Xmax: the cone runs out of travel |
| Above 86.6 Hz | Heat: the power limit |
## How to read it
- The line is the lower of two ceilings at each frequency. Where they cross it turns a corner, because the limit that sets it has changed.
- Each frequency is a steady sine at its own limit. Music spreads its energy across frequencies and shares one thermal budget, so no programme reaches every point at once, and the highest point on the line is not a broadband maximum.
- Compare it with what you ask for. Put the **SPL (dB)** tile beside it at the power you plan to use: where the SPL rises above this line, the design is asked for more than it can give.
- Your **Input power** and EQ do not move the line: they change what you send, not what the speaker can take. Listening distance, radiation space and the baffle step do move it, because they change the level at the listener.
- Port air speed is not part of Max SPL. Check the [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) tile too, or use [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom), which counts it.
## Xmax
Excursion grows with the drive, so the Xmax ceiling is the level at which the cone reaches its rated one-way excursion. Passive radiators have their own Xmax and cap the line too, and a multiple-entry horn checks every driver. Xmax applies under every thermal rule.
In a vented box or a tapped horn the cone barely moves at the tuning, because the port or horn does the work. The Xmax ceiling shoots up there and heat takes over. Either side, excursion rises quickly and Xmax usually sets the line, which is why horn curves are angular.
> **Xmax is a distortion reference** Makers define Xmax in different ways, and passing it is not a damage point. [Klippel’s assessment of Xmax](https://www.klippel.de/fileadmin/klippel/Files/Know_How/Literature/Papers/Assessment_of_Voice_coil_peak_displacement_XMAX_02.pdf) explains why the definition matters.
## Three ways to read the thermal limit
A power rating is one number of watts, but a loudspeaker is not a resistor. Its impedance rises and falls with frequency, so the same watts mean a different voltage, current and coil heat at every frequency. Each rule holds a different quantity at the limit; choose one under **Thermal limit** in the tile’s **Settings**.
| Rule | Matches | Holds at the limit | Vented example | Lonely.TH21-30 horn |
| --- | --- | --- | --- | --- |
| Real input power (the default) | Hornresp | The real power going into the driver, at its rating. The voltage climbs at every impedance peak. | 2,000 W | 1,700 W |
| Constant voltage | WinISD | One amplifier voltage at every frequency, by default √(rating × Re) per driver. | 81.2 V | 93.1 V |
| Coil heating | An estimate | The heat in the voice coil, at a budget re-created from the driver’s own rating test. | 1,029 W of heat | 739 W of heat |
The rules part most where the impedance swings most. On the vented example real input power and constant voltage differ by up to 3.6 dB; on the tapped horn below, by up to 10.4 dB.
### Real input power, the default
This rule holds the electrical power going into the driver at its rating, the rule Hornresp’s maximum SPL tool uses. Where the impedance is high the driver draws little current, so reaching the rated power takes a high voltage: the thermal ceiling rises at every impedance peak, and Xmax usually caps it there.
**Power limit** sets the limit as a percentage of each driver’s rating, from 5 to 1,000%, so one setting suits every enclosure in a workspace. To match a chart drawn at another power, set it to that power over the rating: the Lonely.TH21-30’s designer used 2,160 W, 127% of the 1,700 W rating. In a multiple-entry horn, a driver moved by the others is charged at least its own coil heat.
### Constant voltage
This rule holds one amplifier voltage at every frequency, WinISD’s convention. Left blank, **Voltage ceiling** is √(rating × Re) for each enclosure, the rated power into the coil’s resistance.
Type your amplifier’s voltage, from 0.1 to 2,000 V, to see what that amplifier can do with every enclosure. The result is an amplifier envelope rather than a driver limit: at the impedance peaks the driver could take much more.
### Coil heating, an estimate
What damages a voice coil is heat, the current squared times the coil’s resistance. Power that moves the cone and the air is not coil heat, so this rule credits a design, a horn above all, that turns more of its input into sound.
A power rating is not the heat a coil can shed. A rating counts watts as the test voltage squared over the lowest impedance in the test band, while the pink noise spreads across frequencies where the impedance is well above that minimum, so the coil takes much less than the rating says. The tile re-creates the test in the model, driver in free air and coil cold, to estimate the heat the driver survived. That is the **Coil heat budget**, 100% by default.
B&C 21DS115-8, rated 1,700 W: coil heat in its re-created rating test, by **Rating test band**.
| Assumed test band | Coil heat | Share of the rating |
| --- | --- | --- |
| 20–200 Hz | 592 W | 35% |
| 30–300 Hz (default) | 739 W | 43% |
| 50–500 Hz | 812 W | 48% |
Drivers do not store their test band, so the band is an assumption. If you have better data, scale the budget as a percentage. The rule stays an estimate because the real limit is temperature, not heat, and cooling depends on how the cone moves and air flows past the coil. Use it to compare designs, not as a rating.
### The rules as formulas
```
Real input power: I² × Re{Z} = rating × power limit
Constant voltage: V = voltage ceiling
Coil heating: I² × Re(T) = heat budget
Xmax: |x| = Xmax, for every diaphragm
Max SPL = SPL at the solve + 10 log10(min(thermal ratio, Xmax ratio))
```
I is the coil current, Z the driver’s impedance and Re{Z} its real part. The model is linear, so one solve per frequency scales to every limit: a drive ratio s multiplies power and heat by s, and voltage and excursion by √s.
## Try the rules on a tapped horn
Horns show the rules at their most different, because their impedance swings widely. This is the Lonely.TH21-30, a tapped horn for the B&C 21DS115-8 ([the designer’s thread and charts](https://www.diyaudio.com/community/threads/lonely-th21-30-21-30hz_tapped-horn-b-c-21ds115-8.439970/) on diyAudio), drawn under each rule in your browser. Tick the designer’s Hornresp chart to compare, or match the designer’s settings: real input power at 2,160 W with a cold coil.
_Figure: An interactive Max SPL chart of the Lonely.TH21-30 tapped horn: choose a thermal rule, a power limit and a voice coil temperature, and compare with the designer’s Hornresp chart._
| Frequency | Real input power | Constant voltage | Coil heating |
| --- | --- | --- | --- |
| 30 Hz | 128.8 dB | 128.7 dB | 125.3 dB |
| 35 Hz | 133.3 dB | 129.9 dB | 130.2 dB |
| 43 Hz | 132.3 dB (Xmax) | 129.2 dB | 132.3 dB (Xmax) |
| 55 Hz | 135.2 dB | 130.8 dB | 132.5 dB |
| 91 Hz | 140.1 dB | 130.3 dB | 139.9 dB |
| 121 Hz | 138.5 dB | 136.0 dB | 136.4 dB |
| 178 Hz | 142.3 dB | 137.7 dB | 143.1 dB |
Lonely.TH21-30 tapped horn with a B&C 21DS115-8 (rated 1,700 W, Xmax 16.5 mm), half space, 1 m, at the default settings. “(Xmax)” marks where Xmax, not the thermal limit, sets the level.
Under real input power at 2,160 W, the model lands within 0.4 dB of every point read off the designer’s published chart from 20 Hz to 178 Hz.
## Voice coil temperature
A hot coil has a higher resistance: for copper, Re(T) = Re × (1 + 0.00393 × (T − 20 °C)), so at 150 °C it is 51% higher. The same voltage then drives less current, and output falls most where the impedance is close to Re. This is power compression.
Set **Voice coil temperature** from 20 to 300 °C in the tile’s **Settings**. It applies under every rule and only to Max SPL; the **SPL (dB)** tile stays cold. At 150 °C the vented example’s line drops 1.6 dB at 100 Hz and 1.4 dB at its 32 Hz tuning. Like Hornresp’s power compression tool, it sets a temperature; it does not predict one.
## With a series capacitor
A capacitor between the amplifier and the driver uses no power, so under real input power and coil heating the line does not move: the capacitor changes the voltage the amplifier needs, not what the driver and box can take. Under constant voltage the line follows the capacitor. It falls below the capacitor’s resonance with the driver, and rises slightly around it, where the driver sees more voltage than the amplifier gives.
A multiple-entry horn scales all its amplifiers together, so a capacitor on one driver changes the balance between them, and Max SPL moves with it under every rule.
## Matching Hornresp and WinISD
| To match | Thermal limit | Then |
| --- | --- | --- |
| A Hornresp maximum SPL chart | Real input power | Set **Power limit** to the chart’s power as a percentage of the rating. |
| A WinISD maximum SPL chart | Constant voltage | Leave **Voltage ceiling** at √(rating × Re). |
If the curves still differ, compare the SPL and impedance at one fixed power first: a difference there comes from the model, not the rule. The [WinISD validation](https://simulator.00aud.io/validation/winisd) compares the solver with WinISD on a public set of designs.
## Limits of the model
> **Read it as a ceiling to stay under** The model is linear. Motor force, suspension and ports change at high levels, Xmax is a distortion reference, and a hot coil compresses the output. Amplifier voltage and current limits belong to the [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom) tile.
## What to try
| Try | What it changes |
| --- | --- |
| [Turn on Limits](https://simulator.00aud.io/docs/reference/tiles/max-spl#how-to-read-it) | Click **Limits** in the tile header to draw the thermal ceiling dashed and the Xmax ceiling dotted. The line follows whichever is lower. |
| [Check the thermal rule](https://simulator.00aud.io/docs/reference/tiles/max-spl#thermal-rules) | The tile’s **Settings** choose how the power rating becomes a ceiling: real input power as in Hornresp (the default), constant voltage as in WinISD, or coil heating. |
| [Compare with what you ask for](https://simulator.00aud.io/docs/guides/power-and-limits) | Max SPL does not move with **Input power** or EQ. Put the **SPL (dB)** tile beside it: where your SPL crosses the line, the design is asked for more than it can give. |
## Ask your AI
**Ask your AI**
Your assistant reads the same Max SPL, with your workspace’s thermal rule, through the 00 Simulator connector.
> Using 00 Simulator, simulate every enclosure in my open workspace and tell me its Max SPL at 30, 50 and 100 Hz, whether Xmax or the thermal limit sets it at each, and how far its SPL at the set power sits below it.
---
# Headroom
> How to read the Headroom tile in 00 Simulator: your listening level and its peaks against cone travel, heat and port limits, and what the amplifier must supply.
Source: https://simulator.00aud.io/docs/reference/tiles/headroom
Whether a design can play the level you want, with music’s peaks on top, and which limit gets in the way first. It checks cone travel, heat, port air speed and passive radiators at every frequency, and tells you what the amplifier must supply.
- **Shows:** Your listening level and its peaks against what the design can play cleanly at each frequency, counting cone travel, heat, port air speed and passive radiators.
- **Healthy when:** The dashed peak line stays in the **Clean** band and the number above the graph is positive.
- **If it is not:** Hover where the peaks leave the band to see which limit is over, then lower the target, filter below the tuning or give the port more area.
## The tile
The app’s own Headroom tile on a Dayton Audio DCS205-4 in 25 L tuned to 35 Hz. Change the power, crest factor and distance, add a high-pass, or relax a limit, and watch the bands and lines move.
_Figure: The Headroom tile for a Dayton Audio DCS205-4 in 25 L tuned to 35 Hz, with controls for input power, crest factor and listening distance, a 30 Hz high-pass and the limits._
The app’s tile and solver, running in your browser. Nothing here is saved.
| In the explorer | Band | Margin | At | Limit |
| --- | --- | --- | --- | --- |
| 10 W, 12 dB crest, 1 m | Over max | −7.7 dB | 10.2 Hz | Driver excursion |
| The same, with the 30 Hz high-pass | Clean | +0.5 dB | 34.7 Hz | Port velocity |
| The same, with 6 dB crest | Over max | −1.7 dB | 10.2 Hz | Driver excursion |
| The same, at 2 m | Over max | −7.7 dB | 10.2 Hz | Driver excursion |
Dayton Audio DCS205-4 in 25 L tuned to 35 Hz, one 80 mm port, half space. At 10 W and 12 dB crest the amplifier needs 24.9 V peak and 6.12 A peak (at 181 Hz).
At 10 W with 12 dB of crest, the peaks go 7.7 dB over the maximum at 10.2 Hz, on driver excursion: below its tuning the box stops holding the cone. With the 30 Hz high-pass the whole band is **Clean**, 0.5 dB inside the clean limits, and the tightest point moves to 34.7 Hz, where port velocity is now the limit.
- The solid line is the average level, **Average SPL**: the enclosure’s SPL at its set power, EQ included. The dashed line is **Peak SPL**, the average plus the crest factor. It turns red where it is over the maximum.
- The coloured bands are what the design can play at each frequency: **Clean** up to the clean thresholds, **Threshold** between clean and maximum, **Over max** above. At each frequency the tightest limit sets them, so the edge can be cone travel at one frequency and port air speed at the next.
- **Tgt avg** and **Tgt peak** mark your target level and its peaks.
- The number above the graph is the smallest clean margin anywhere in the band. Once anything is over the maximum, it shows how far over instead, as a negative number.
- Hover for the average and peak readouts at a frequency: power, excursion and port air speed, each against its target and maximum. Click to hold the cursor.
- The tile draws the selected enclosure. Expanded and wide, it lists up to six enclosures under the graph with their margins; click one to show it.
- The **EQ** button edits the enclosure’s filters on the tile, and a right-click offers **Add filter**. The lines move with every change.
## How to read it
- Follow the dashed peak line. The gap between it and the top of the **Clean** band is the clean headroom at that frequency.
- Headroom is in decibels. A 6 dB gap allows about twice the signal amplitude, or four times the power, before the limit.
- **Clean** means below the clean thresholds, not a promise of clean sound: the thresholds are limits you chose, and a linear model misses distortion and noise near them.
- The limit that runs out first tells you what to change. Cone travel wants a high-pass or more cone area; port air speed wants more port area; heat wants more drivers or less power.
## Settings
Open **Settings** in the tile header. **Pin settings to side** keeps them beside the tile when it is wide enough.
| Setting | What it sets |
| --- | --- |
| **Target level** › **Average** | The average level you want to listen at, 40 to 140 dB. It starts at the level the design already plays at its loudest point. |
| **Target level** › **Crest** | How far music’s peaks rise above the average, 0 to 40 dB; 12 dB unless you change it. **Peak target** is the two added together. |
| **Target level** › **Distance** | Where you listen, in m or ft, 1 m to start with. |
| **Limits** | The clean and maximum thresholds for each limit, as sliders with two handles. |
| **Copy from...** | Copies another visible enclosure’s average and crest targets. |
> **The target and the power move together** Type a new **Average** and the enclosure’s **Input power** changes so its loudest point reaches it. Change the power and the target follows. Each enclosure keeps its own target, so lowering **Average** by a dB gives a dB more headroom everywhere.
The default thresholds under **Limits**. Between the two columns is **Threshold**.
| Limit | Clean up to | Over max above | Shown for |
| --- | --- | --- | --- |
| **Thermal power** | 0.5 × Pe | 1 × Pe | Every enclosure |
| **Driver excursion** | 1 × Xmax | 1.125 × Xmax | Every enclosure |
| **Port velocity** | 17 m/s | 30 m/s | Enclosures with a port |
| **PR excursion** | 1 × PR Xmax | 1.25 × PR Xmax | Enclosures with a passive radiator |
- In a new workspace the clean port limit starts at **Port velocity** under **Settings › Simulation…**, the warning line the Port Velocity tile draws.
- In a multiple-entry horn the ratios apply to each driver’s own rating and Xmax, and every driver is checked.
- These are the app’s defaults, not the maker’s damage ratings. Your saved workspace may differ.
## Music and crest factor
A sustained bass note and a short kick can reach the same peak with very different average levels. Crest factor is the largest peak over the average (RMS) level, in dB. A sine wave has 3.0 dB; 12 dB means peaks about 4 times the RMS amplitude.
Keep the power fixed and raise the crest factor from 6 to 12 dB: the average line stays put and the peak line rises 6 dB, so the peaks ask for twice the voltage and about twice the cone travel and port air speed. In the explorer that takes the peaks from −1.7 dB to −7.7 dB against the maximum, and the peak voltage from 12.5 V to 24.9 V.
Treat crest factor as an assumption about the signal reaching this speaker. A whole track’s crest factor can differ from the bass after a crossover or high-pass, and the recording, processing and measurement window all change it; a genre name is not enough to choose a value.
## What the amplifier must supply
An amplifier makes a larger copy of its input voltage. The speaker’s impedance sets the current it must supply, and that changes with frequency. When the voltage asked for exceeds what the amplifier can swing, it clips; current limits or protection can also stop it.
The tile’s **Amp** button opens **Amplifier Insights**: what one amplifier channel must supply at your target level, EQ and crest factor included, with the frequency of each maximum.
| Row | What it is |
| --- | --- |
| **Peak voltage**, **Peak current** | The largest signal peaks the target asks for. They can fall at different frequencies, so multiplying them does not give an amplifier rating. |
| **Min impedance**, **Max impedance**, **Nominal load** | The lowest and highest impedance across the band, beside the drivers’ nominal rating as wired. |
| **RMS required** | The average voltage and the power setting at the target. The watts are the model’s drive reference, not heat in the voice coil. |
| **Thermal target** | The voltage and power at the clean thermal threshold. |
| **Peak limiter** | The signal peak voltage the target’s peaks need, subject to the excursion and thermal limits. |
When the target asks for more than the maximum thresholds allow, a **Danger** note appears; **Apply** lowers the target until it fits. A multiple-entry horn lists each amplifier channel on its own.
In the explorer at 10 W, the peak current, 6.12 A, comes at 181 Hz, where the impedance is lowest. A rating such as 200 W describes what an amplifier can deliver under test, not what it sends all the time; the signal and the volume set the demand, and brief peaks can need a lot of voltage while the average power stays low.
### Worked example: 25 W average into 8 Ω
```
V rms = √(25 × 8) = 14.1 V
V peak = V rms × 10^(12 / 20) = 56.3 V
I peak = V peak / 8 = 7.0 A
Crest factor = 20 log10(V peak / V rms)
```
A steady sine reaching 56.3 V peak would deliver about 198 W into 8 Ω (V peak² / 2R), and the instantaneous power at that peak is about 396 W (V peak² / R). The signal itself still averages 25 W. A loudspeaker is not a resistor, so for a real design read the tile’s own voltage, current and impedance.
## Listening distance
Twice the distance is about 6.0 dB less direct sound. In the explorer, Distance moves the listener at a fixed power: the level falls from 96.6 dB to 90.6 dB at its loudest point, and the headroom stays at −7.7 dB, because the driver and port do the same work.
In the app, **Distance** keeps your **Average** target at the new distance, so the enclosure’s power changes to reach it: listening at 2 m instead of 1 m takes four times the power and uses about 6 dB of headroom. The correction is for direct sound only; your room’s reflections and modes change the real level.
## Choosing an action
- A high-pass: in a vented box the port does much of the work near its tuning; below it, the cone travel climbs. A high-pass there, like the explorer’s 30 Hz one, cuts that demand, and the low bass with it: check what you gave up as well as what you gained.
- Less drive: a lower target lowers the demand at every frequency.
- More port area: port air speed is a check for noise and compression; flares, area and placement change what you hear. More area usually means a longer port for the same tuning, so check it fits.
- Passive radiators: they have their own Xmax and can run out while the driver is still inside its own.
> **Relaxing a limit changes the rule, not the speaker** Raising the excursion or port thresholds moves the boundary; the cone and the air move exactly as before. Use it only for a limit you can justify from measurements or the maker’s data. Red turning green after a relaxed limit is a change of criteria, not a better design.
The thermal check compares the power you set, after EQ, with fractions of the driver’s power rating, Pe. It is not a voice coil temperature or the heat the coil sheds: a rating is a test figure, and sustained level, spectrum and cooling set the real heat. The [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl#coil-heating) tile’s coil heating rule is the closer estimate.
## Limits of the model
- The tile checks each frequency separately, from 10 Hz to the top of the frequency axis (**Upper frequency** under **Settings › Display…**). It does not analyse a recording or add frequencies into a music waveform, and it does not mean every frequency gets the full power at once.
- The target’s reference is the loudest point of the average line in that band. A narrow response peak can set it; it is not an integrated loudness.
- Heating, motor force and suspension changes, and port losses at high level can take a real speaker away from the prediction. The maximum boundary comes from your thresholds, not a measured damage limit.
## What to try
| Try | What it changes |
| --- | --- |
| Lower the target | Each dB off **Average** is a dB more headroom at every frequency; the enclosure’s power follows the target. |
| [A high-pass below the tuning](https://simulator.00aud.io/docs/guides/eq-and-filters) | Cuts the cone travel a vented box needs below its tuning, where it usually runs out first. |
| [More port area](https://simulator.00aud.io/docs/guides/noisy-port) | Where the port sets the limit, a second or wider port lowers the air speed. It gets longer to keep the tuning. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, simulate every enclosure in my open workspace at its set power and, assuming music peaks 12 dB above that level, tell me for each one where it runs out first: the frequency where peak cone excursion, peak port air speed or power against the driver’s rating comes closest to its limit, and by how many dB.
---
# Excursion
> Read peak cone travel against Xmax, identify unloading below a vented box’s tuning, and check what power and filters change.
Source: https://simulator.00aud.io/docs/reference/tiles/excursion
Use this tile to check whether the cone has enough travel for the bass you ask it to play. The curve is peak, one-way displacement from rest, not peak-to-peak travel.
- **Shows:** How far the cone travels from rest, peak and one way, in mm at each frequency, against the driver’s Xmax.
- **Healthy when:** The curve stays under the Xmax line through the band you will play, at the power you will use.
- **If it is not:** A high-pass just below the tuning, less power, or more cone area.
## The tile
_Figure: Cone travel against the driver’s Xmax, with the dip at the box tuning._
Ciare 12.00SW, vented example at 200 W, half space, 1 m. Simulated when this page was built.
| Excursion | Peak | At |
| --- | --- | --- |
| 200 W | 21.2 mm | 10 Hz |
The vented example peaks at 21.2 mm near 10 Hz across this plotted range. The driver’s Xmax is 13.5 mm. [Open this example](https://simulator.00aud.io/app?template=vented&power=200) and hover for the travel at a particular frequency.
Each visible design has its own curve. Dashed Xmax lines use the drivers’ own limits; Xmech and Xdamage appear when the driver data includes them and excursion warnings are enabled. Multiple-entry horns also show the additional drivers.
## Read the dip, then look below it
Near the 32 Hz tuning, the port supplies much of the sound and cone travel falls. Below tuning the cone unloads, so falling SPL can accompany rising excursion. Judge the band you intend to reproduce, including anything left below the crossover.
> **Xmax is a linear travel limit** Going past Xmax means the small-signal model is no longer a reliable description of clean travel. Staying below it does not check coil heating, port noise or every mechanical failure mode. Use **Headroom** for the other limits.
## The same box at different powers
_Figure: Three powers on the same box, each against the same Xmax._
| Case | Peak | At | Note |
| --- | --- | --- | --- |
| 50 W | 10.6 mm | 10 Hz | 10.6 mm at 10 Hz; Xmax 13.5 mm |
| 100 W | 15 mm | 10 Hz | 15.0 mm at 10 Hz; Xmax 13.5 mm |
| 200 W | 21.2 mm | 10 Hz | 21.2 mm at 10 Hz; Xmax 13.5 mm |
Ciare 12.00SW, vented example at 200 W, half space, 1 m. Simulated when this page was built.
Reducing power to a quarter reduces peak travel to 0.50 times the original. A high-pass can instead reduce demand mainly below the useful band; inspect the filtered SPL as well.
## What moves it
| Change | What to watch |
| --- | --- |
| More power or bass boost | More travel wherever the voltage rises. Filters are included in the curve. |
| Change box volume or tuning | The dip and peaks move; recheck the complete working band. |
| Add a high-pass | Less travel below its corner, with less SPL there too. |
| Add another driver | Compare at the output you need, with wiring and power set correctly. |
## What to try
| Try | What it changes |
| --- | --- |
| [A high-pass below the tuning](https://simulator.00aud.io/docs/guides/eq-and-filters#protect-the-cone) | Below the tuning a port or passive radiator stops holding the cone back. Right-click the chart, choose **Add filter** and put a high-pass just under the tuning. |
| [Less power](https://simulator.00aud.io/docs/guides/power-and-limits) | Travel follows the square root of power: half the power is about 0.7 times the excursion, and 3 dB quieter. |
| [More cone area](https://simulator.00aud.io/docs/boxes/multiple-drivers) | A second driver, or a bigger one, moves the same air with less travel each. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, check cone excursion against each driver’s Xmax at my workspace’s current powers. Identify the frequencies over the limit, then preview a high-pass that protects the useful band and compare its SPL before saving.
---
# Port Velocity
> How to read the Port Velocity tile in 00 Simulator: peak air speed in a vented box’s port against the warning line, and what to change when it chuffs.
Source: https://simulator.00aud.io/docs/reference/tiles/port-velocity
How fast air moves through the port, at its peak, at each frequency. High air speed increases the risk of chuffing and whistles, so this is the tile to size a port with.
- **Shows:** Peak air speed in the port, in m/s, at each frequency, against the warning line.
- **Healthy when:** The curve stays under the line at the power you will actually use.
- **If it is not:** More port area, less power, or a high-pass below the tuning.
## The tile
_Figure: The Port Velocity tile for the vented example at 200 W, with the 17 m/s warning line._
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One 10 cm port | 28.4 m/s | 30 Hz |
In this example the port peaks at 28.4 m/s near 30 Hz, over the 17 m/s line. Each visible enclosure with a port draws its own curve in its colour; the dashed line is the port velocity warning, and the same value shows in the tile's header.
- [Open this example](https://simulator.00aud.io/app?template=vented&power=200) in the simulator at 200 W, then hover the curve for the speed at a frequency.
- Click the warning value in the tile header to change the line. It is the same setting as **Port velocity** under **Settings › Simulation…**, from 10 to 30 m/s.
- Bandpass boxes show their front port here. A sixth-order bandpass has a second, rear-chamber port on its own tile, [Port Velocity (Rear Chamber)](https://simulator.00aud.io/docs/reference/tiles/rear-port-velocity).
## How to read it
- Read it at the power you plan to use. Air speed follows the drive, so a port that is fine at 10 W can chuff at 200 W.
- The peak sits near the box tuning, where the port does most of the work and the cone the least.
- Inspect speeds throughout the band your signal reaches. The line is a warning threshold, not a promise that a real port is quiet below it.
- 17 m/s is the default warning, not a universal noise threshold. A well-flared port can run faster before you hear it; the settings hint says 15 to 20 m/s is typical and higher for flared ports.
## Three port-area choices
The same 55 L box and driver at 200 W, with three ports that all keep the 32 Hz tuning.
_Figure: Three ports on the same box at 200 W: two 10 cm ports, one 10 cm port and one 7.5 cm port._
| Case | Peak | At | Note |
| --- | --- | --- | --- |
| Two 10 cm ports | 14.2 m/s | 30 Hz | 14.2 m/s · each 77.1 cm long |
| One 10 cm port | 28.4 m/s | 30 Hz | 28.4 m/s · 35.6 cm long |
| One 7.5 cm port | 50.5 m/s | 30 Hz | 50.5 m/s · 18.9 cm long |
Ciare 12.00SW in the 55 L vented example tuned to 32 Hz, at 200 W, half space, 1 m. Simulated when this page was built.
> **Quieter ports are longer ports** Halving the air speed took twice the port area, and to keep the same tuning each port grew from 35.6 cm to 77.1 cm. Check it fits the box before you build: the port length shows in the enclosure panel.
## What moves it
| Change | Effect | Why |
| --- | --- | --- |
| Halve the power | × 0.71 | Air speed grows with the square root of power. |
| Double the port area | × 0.50 | Same air, twice the opening. The port gets longer to keep the tuning. |
| Lower the tuning | Peak moves down | And the port gets longer for the same area. |
| High-pass below the tuning | Lower peak | The cone moves less air near the tuning. |
## What to try
| Try | What it changes |
| --- | --- |
| [More port area](https://simulator.00aud.io/docs/guides/noisy-port) | A second port, or a wider one, halves the speed for twice the area. Each port gets longer to keep the tuning. |
| Less power | Air speed follows the square root of power: half the power is about 0.7 times the speed, and 3 dB quieter. |
| [A high-pass below the tuning](https://simulator.00aud.io/docs/guides/eq-and-filters) | The cone moves less air near the tuning, so the port does too. |
## Ask your AI
**Ask your AI**
Your assistant runs the same solver on your own designs through the 00 Simulator connector.
> Using 00 Simulator, check every vented box in my open workspace at its set power. For any port above 17 m/s, try two ports and a larger diameter without saving, and tell me each option’s peak air speed and port length.
---
# Port Velocity (Rear Chamber)
> Check the rear port of a sixth-order bandpass separately from its front port, using the same air-speed warning and power setting.
Source: https://simulator.00aud.io/docs/reference/tiles/rear-port-velocity
A sixth-order bandpass can have a quiet front port and a noisy rear one. This tile reads the rear chamber’s port independently.
- **Shows:** Peak air speed in a bandpass box’s rear-chamber port, in m/s, at each frequency, against the warning line.
- **Healthy when:** The curve stays under the line at the power you will actually use.
- **If it is not:** More rear port area, less power, or a high-pass below the band you play.
## The tile
_Figure: Rear port air speed with one and two rear ports at the same tuning._
Sixth-order bandpass bench design at 100 W, half space, 1 m. Simulated when this page was built.
| Port Velocity (Rear Chamber) | Peak | At |
| --- | --- | --- |
| One rear port | 19.8 m/s | 20 Hz |
| Two rear ports | 9.9 m/s | 20 Hz |
The rear port peaks at 19.8 m/s near 19.6 Hz. With two rear ports it peaks at 9.9 m/s. Both use the same rear-chamber volume and target tuning.
Use **Port Velocity** for the front chamber and this tile for the rear. A sealed rear chamber has no rear-port curve. A rear chamber loaded by a passive radiator belongs on **PR Excursion** instead.
## Read the warning at your working power
The dashed line is the same adjustable port-speed warning used by the front-port tile, 17 m/s in this example. It is a warning threshold, not a prediction of exactly when a particular port will become audible.
| Change on the rear chamber | Trade-off |
| --- | --- |
| More port area | Lower air speed at the same tuning, with longer ports. |
| Lower tuning | Moves the low-frequency behaviour and increases required port length. |
| Less input power | Reduces both front and rear port speeds, along with output. |
| A high-pass below the band | Removes demand where little useful sound remains; recheck the lower passband edge. |
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The live bench shows how both chambers affect the result.
## What to try
| Try | What it changes |
| --- | --- |
| [More rear port area](https://simulator.00aud.io/docs/boxes/bandpass-6) | On the **Rear** tab, a second port or a wider one slows the air for the same tuning. Each port gets longer. |
| [A high-pass below the band](https://simulator.00aud.io/docs/guides/eq-and-filters) | If the peak sits below the band you play, a high-pass there slows the air for little output. |
| Less power | Air speed follows the square root of power: half the power is about 0.7 times the speed, and 3 dB quieter. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, check both port velocities in my sixth-order bandpass at its current power. Preview more area on whichever port exceeds the warning, keeping the chamber tunings fixed, and report the new speeds and port lengths.
---
# Port Volume Velocity
> Distinguish the volume of air flowing through a port from its speed, and see why larger ports can keep the same flow while reducing noise risk.
Source: https://simulator.00aud.io/docs/reference/tiles/port-volume-velocity
This tile shows how much air the port moves each second. It helps explain the port’s contribution to the sound; Port Velocity is the tile to use for air speed and noise risk.
- **Shows:** How much air flows through a vented box’s port each second, at its peak, at each frequency.
- **Healthy when:** It has no limit of its own. The peak sits near the tuning, where the port takes over from the cone.
- **If it is not:** Check the tuning and filters if the curve differs from the alignment you intended. For port noise, read **Port Velocity**.
## The tile
_Figure: Total port volume flow with one and two ports, at the same tuning and power._
Vented example at 100 W, half space, 1 m. Only port count changes. Simulated when this page was built.
| Port Volume Velocity | Peak | At |
| --- | --- | --- |
| One port | 157.6 L/s | 30 Hz |
| Two ports, same tuning | 157.6 L/s | 30 Hz |
The vented example’s total port flow peaks at 157.6 L/s near 30.1 Hz. [Open this example](https://simulator.00aud.io/app?template=vented&power=100). The app uses mL/s, L/s or m³/s to suit the value and shows vented enclosures only.
Volume flow is air speed multiplied by the total open port area. A large opening can carry a large flow at modest speed. There is no warning line for volume flow itself.
## The same flow can need less speed
_Figure: The corresponding air speeds: more opening area lowers speed._
Vented example at 100 W, half space, 1 m. Only port count changes. Simulated when this page was built.
| Port Velocity | Peak | At |
| --- | --- | --- |
| One port | 20.1 m/s | 30 Hz |
| Two ports | 10.0 m/s | 30 Hz |
In these runs the one-port and two-port flow peaks are 157.6 and 157.6 L/s. Their air-speed peaks are 20.1 and 10.0 m/s. More port area must be paired with more length to preserve tuning.
| Change | What moves |
| --- | --- |
| Increase area, keep tuning | Air speed falls; total flow is largely unchanged. |
| Change tuning | The flow peak moves with the new alignment. |
| Change power or EQ | Flow follows the applied signal at each frequency. |
| Read **Cone Velocity** beside it | Multiply cone speed by Sd before comparing it with a volume flow. |
## What to try
| Try | What it changes |
| --- | --- |
| [Compare port sizes](https://simulator.00aud.io/docs/reference/tiles/port-velocity) | At the same tuning a wider port, or a second one, moves the same air more slowly: this curve stays put while **Port Velocity** falls. |
| [Compare with the cone](https://simulator.00aud.io/docs/reference/tiles/cone-velocity) | **Cone Velocity** times the driver’s Sd is the air the cone moves. Near the tuning the port moves far more than the cone. |
| [Change the tuning](https://simulator.00aud.io/docs/boxes/vented) | The peak follows the tuning up or down. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, preview one and two ports on my vented design at the same tuning and power. Compare total port volume velocity, port air speed and required port length, without saving the change.
---
# Cone Velocity
> Read peak cone speed, distinguish it from excursion and air speed, and recognise the slowing cone around a vented box’s tuning.
Source: https://simulator.00aud.io/docs/reference/tiles/cone-velocity
This is the cone’s motion shown as speed. Use it to see where the cone is doing the work, then use Excursion to decide whether its travel is acceptable.
- **Shows:** How fast the cone moves, at its peak, at each frequency: m/s, or mm/s below 1 m/s.
- **Healthy when:** It has no limit line. It is the same motion as **Excursion**, shown as speed; the limit to watch is on that tile.
- **If it is not:** Bring it down the way you bring excursion down: less power, a filter, or a different box.
## The tile
_Figure: The cone’s peak speed at two powers, with a dip around tuning._
Vented example at 100 W, half space, 1 m. Simulated when this page was built.
| Cone Velocity | Peak | At |
| --- | --- | --- |
| 100 W | 1.1 m/s | 59 Hz |
| 50 W | 0.8 m/s | 59 Hz |
[Open this example](https://simulator.00aud.io/app?template=vented&power=100). The tile labels small speeds in mm/s and larger ones in m/s. There is no maximum-speed line: it is a diagnostic view of motion, not a separate driver rating.
## Speed is not travel
For a sinusoid, peak cone speed is peak excursion multiplied by 2π and frequency. The same travel therefore means more speed at a higher frequency. A low-speed reading at a very low frequency can still exceed Xmax.
| Frequency in this run | Peak travel | Peak speed |
| --- | --- | --- |
| 20.0 Hz | 8.86 mm | 1.12 m/s |
| 31.6 Hz | 1.80 mm | 0.36 m/s |
| 80.6 Hz | 2.15 mm | 1.09 m/s |
The dip around tuning is where a vented box’s port takes over from its cone. Compare **Port Volume Velocity** to see the volume flow through the port. Multiplying cone speed by the driver’s Sd gives the cone’s own volume flow.
## What moves it
| Change | Result |
| --- | --- |
| Halve the power | 0.71 times the cone speed at the same frequency in this run. |
| Move the tuning | Moves the loading dip and changes the speed on either side. |
| Add a filter | Changes speed in the frequencies where the filter changes voltage. |
| Change listening distance | Changes the SPL at the listener, not the motion at fixed drive. |
## What to try
| Try | What it changes |
| --- | --- |
| [Find the tuning](https://simulator.00aud.io/docs/boxes/vented) | In a vented box the cone slows to a dip at the tuning, where the port takes over. |
| [Read travel from speed](https://simulator.00aud.io/docs/reference/tiles/excursion) | Speed is travel times 2π times frequency, so a slow cone at a low frequency can still be travelling a long way. |
| [Compare with the port](https://simulator.00aud.io/docs/reference/tiles/port-volume-velocity) | Times the driver’s Sd, it is the air the cone moves. Put it beside **Port Volume Velocity**. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, simulate my vented enclosure at its current power and compare cone velocity, excursion and port velocity around tuning. Explain where the port takes over and whether cone travel exceeds Xmax below it.
---
# PR Excursion
> Check each passive radiator’s travel against its own Xmax, and understand why count and added mass change both travel and tuning.
Source: https://simulator.00aud.io/docs/reference/tiles/pr-excursion
A passive radiator can run out of travel while the powered cone is barely moving. This tile checks the radiator separately, against its own Xmax.
- **Shows:** How far each passive radiator travels, peak and one way, in mm at each frequency, against its own Xmax.
- **Healthy when:** The curve stays under the PR Xmax line at the power you will use, and the driver stays under its own Xmax on **Excursion**.
- **If it is not:** More radiators, a radiator with more travel, or less power.
## The tile
_Figure: Passive radiator travel at two powers and with two radiators, against the radiator’s own Xmax._
Passive radiator example at 50 W, half space, 1 m. Simulated when this page was built.
| PR Excursion | Peak | At |
| --- | --- | --- |
| One radiator | 9.5 mm | 33 Hz |
| Two radiators, same mass each | 6.1 mm | 37 Hz |
| One radiator, 25 W | 6.7 mm | 33 Hz |
The single radiator peaks at 9.5 mm near 33.2 Hz at 50 W. The curve is peak, one-way travel per radiator. [Open this example](https://simulator.00aud.io/app?template=passive-radiator&power=50).
The dashed PR Xmax line belongs to the passive radiator, not the powered driver. Check **Excursion** alongside it. With passive radiators in both chambers of a bandpass box, the main curve is the larger front or rear travel at each frequency, and the limit lines identify their chamber roles.
## Count and mass must be considered together
In this comparison, two identical radiators with unchanged mass each peak at 6.1 mm near 37.4 Hz. Adding a radiator changes the tuning as well as the available area, so it is not a comparison at the same alignment.
| Change | What to check next |
| --- | --- |
| Increase **Number of PRs** | Recheck the new tuning, the response shape and each radiator’s travel. |
| Increase **Added mass (tuning)** | Tuning falls; recheck peak travel and the powered cone below tuning. |
| Choose a radiator with more Xmax or area | Confirm its mass, compliance and mounting space as well as travel. |
| Reduce power | Both radiator and driver motion fall; compare the remaining SPL. |
> **Check the weakest moving part** Passing the powered driver’s Xmax check does not make the radiator safe. **Headroom** checks both when their limits are available.
## What to try
| Try | What it changes |
| --- | --- |
| [Use two radiators](https://simulator.00aud.io/docs/boxes/passive-radiator) | Set **Number of PRs** to 2. They share the work, so each travels less, and the tuning rises. |
| [Mind the added mass](https://simulator.00aud.io/docs/boxes/passive-radiator#added-mass) | More **Added mass (tuning)** tunes the box lower and can increase peak travel; recheck both the radiator and powered cone. |
| Less power | Travel follows the square root of power: half the power is about 0.7 times the excursion. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, check the driver and passive radiator excursion in my design at its current power. Preview a second identical radiator, report how tuning and peak travel change, and do not save the change yet.
---
# Amplifier Load (VA)
> Read apparent power and RMS current demand, understand why VA differs from the input-power setting, and check amplifier peaks in Headroom.
Source: https://simulator.00aud.io/docs/reference/tiles/amplifier-load
This tile shows the electrical demand on the amplifier as impedance changes with frequency. It reports apparent power in VA, with an optional RMS current curve.
- **Shows:** Apparent amplifier demand in VA at each frequency, with optional RMS current.
- **Healthy when:** Voltage, current and load suit your amplifier at the level and crest factor you intend to use.
- **If it is not:** Reduce power or boost, review wiring, and inspect the amplifier requirements in **Headroom**.
## The tile
_Figure: Apparent power changes with impedance across frequency, despite a fixed input-power setting._
Vented example at 100 W reference input, half space, 1 m. Simulated when this page was built.
| Amplifier Load (VA) | Peak | At |
| --- | --- | --- |
| 100 W input setting | 113.4 VA | 191 Hz |
| 50 W input setting | 56.7 VA | 191 Hz |
At the 100 W input setting, the example reaches 113.4 VA. Its largest RMS current is 5.67 A near 191.1 Hz. [Open this example](https://simulator.00aud.io/app?template=vented&power=100) and switch on **Current** to see the current demand.
The faint Pin line is the input-power setting. It is a reference, not an amplifier limit. Multiple-entry horns can show additional amplifier-channel loads. Hover readouts retain their units; do not read the current line as VA.
## Why VA and watts differ
The power control establishes a drive voltage using the nominal load. The actual impedance varies with frequency, so the current varies too. Apparent power is RMS voltage multiplied by RMS current; real power also depends on the phase between them.
> **This is demand, not an amplifier model** The tile does not simulate clipping or protection in a particular amplifier. For the voltage and current peaks needed by music, open **Headroom** and its **Amp** panel, set the listening target and crest factor, then compare with your amplifier’s specifications.
## What moves it
| Change | Effect |
| --- | --- |
| Lower the power setting | Reduces apparent power and RMS current. |
| Change wiring or the number of drivers | Changes the nominal load and impedance seen by the amplifier. |
| Add EQ boost | Raises demand at the boosted frequencies. |
| Change the enclosure | Changes the impedance peaks and dips, and therefore current demand. |
## What to try
| Try | What it changes |
| --- | --- |
| [Show current](https://simulator.00aud.io/docs/reference/tiles/impedance) | Turn on **Current** to find where RMS current demand is highest. |
| [Check music peaks](https://simulator.00aud.io/docs/reference/tiles/headroom) | Open **Headroom** and **Amp** for voltage and current requirements at your target and crest factor. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, simulate my workspace at its current powers and EQ. Report the maximum apparent power and RMS current for each design, where they occur, and the minimum impedance. Then explain which design asks the most of the amplifier.
---
# 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.
---
# 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.
---
# Horn Pressure
> Inspect RMS pressure and phase at stations inside a horn, distinguish internal pressure from listening SPL, and interpret pressure peaks with flow.
Source: https://simulator.00aud.io/docs/reference/tiles/horn-pressure
Horn Pressure reads the acoustic pressure inside the horn at the station you choose. Use it to locate pressure build-up and understand how the path loads the driver.
- **Shows:** RMS acoustic pressure in Pa, or its phase, at a chosen station inside the horn.
- **Healthy when:** The station and mode are the ones you mean; a pressure peak is interpreted alongside flow and SPL.
- **If it is not:** Compare another station and inspect particle velocity before changing geometry.
## The tile
_Figure: Horn Pressure at Main H1 throat, Main H2 mouth, Main H4 mouth in the tapped-horn example._
Tapped-horn example at 100 W, half space, 1 m. Stations are measured from the closed end. Simulated when this page was built.
| Station | Position | Area | Peak | At |
| --- | --- | --- | --- | --- |
| Main H1 throat | 0.00 m | 400 cm² | 1,485.42 Pa RMS | 40.2 Hz |
| Main H2 mouth | 0.95 m | 600 cm² | 1,130.97 Pa RMS | 41.2 Hz |
| Main H4 mouth | 2.50 m | 2,400 cm² | 178.68 Pa RMS | 93.1 Hz |
In the tapped-horn example the closed-end station peaks at 1,485.4 Pa RMS, while the mouth peaks at 178.7 Pa RMS. Those maxima occur at different frequencies. [Open the example](https://simulator.00aud.io/app?template=tapped-horn&power=100) and compare stations at the same frequency with the hover readout.
Choose a location above the plot. The initial location is the first span’s throat. **Magnitude** shows Pa RMS; **Phase** shows pressure phase relative to the electrical drive. This is local pressure, not the SPL at the listening position.
## High pressure need not mean fast air
A closed end can support a large pressure variation while its volume flow is essentially zero. At other stations a narrow passage can have much more air motion. Read **Horn Particle Velocity** at the same location before drawing conclusions about air speed.
| Change or observation | Interpretation |
| --- | --- |
| More input power | Pressure rises with drive amplitude in the linear model. |
| Choose another station | The reading changes location; the horn itself is unchanged. |
| Change length, flare or stuffing | Changes resonances and acoustic loading; check SPL and excursion as well. |
| A comparison enclosure has no matching station | Its curve is left out; it is not a zero-pressure result. |
> **No pressure pass or fail line** The tile has no structural pressure rating and does not predict panel vibration, turbulence or nonlinear distortion. It describes the linear acoustic field inside the model.
## What to try
| Try | What it changes |
| --- | --- |
| [Choose a station](https://simulator.00aud.io/docs/horns/diagnostics#locations) | Compare the throat, a constriction and the mouth; the default is the first span’s throat. |
| [Compare pressure with flow](https://simulator.00aud.io/docs/reference/tiles/horn-particle-velocity) | High pressure can occur where flow is small. Read **Horn Particle Velocity** at the same station. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, simulate my horn at its current power and compare pressure and particle velocity at the throat, a narrow station and the mouth. Explain the largest pressure peak and identify its frequency without treating it as listening SPL.
---
# Horn Particle Velocity
> Inspect peak air speed at a horn station, find narrow passages, and compare both sides of driver entries without confusing it with cone speed.
Source: https://simulator.00aud.io/docs/reference/tiles/horn-particle-velocity
This tile shows peak air speed at a chosen point inside the horn. Inspect the narrow passages and the stations around driver entries, not only the mouth.
- **Shows:** Peak air-particle speed in m/s at a chosen station inside the horn.
- **Healthy when:** Speed is acceptable for the passage and output you intend to use; the tile has no automatic speed limit.
- **If it is not:** Inspect narrow stations, then compare a larger area or lower drive and recheck SPL.
## The tile
_Figure: Horn Particle Velocity at Main H1 throat, Main H2 mouth, Main H4 mouth in the tapped-horn example._
Tapped-horn example at 100 W, half space, 1 m. Stations are measured from the closed end. Simulated when this page was built.
| Station | Position | Area | Peak | At |
| --- | --- | --- | --- | --- |
| Main H1 throat | 0.00 m | 400 cm² | 0.00 m/s peak | 10.7 Hz |
| Main H2 mouth | 0.95 m | 600 cm² | 5.78 m/s peak | 38.3 Hz |
| Main H4 mouth | 2.50 m | 2,400 cm² | 3.33 m/s peak | 42.2 Hz |
At Main H2 mouth, the 600 cm² passage peaks at 5.8 m/s near 38.3 Hz. The mouth peaks at 3.3 m/s. The closed-end throat is almost stationary, so leaving the selection at its default would miss the faster air farther along this horn.
The value is local volume flow divided by local area, expressed as sine-peak speed. It is neither the cone’s speed nor a sum over the horn’s radiating outputs. The tile has one magnitude view and no port-style warning line.
## Read both sides of a connection
Station names identify path, span and end. Where a driver enters or a branch joins, locations may distinguish the side toward the throat from the side toward the mouth. Pressure can be continuous while flow differs because a source or branch adds or removes flow there.
| Try | Check afterwards |
| --- | --- |
| A larger area at the constriction | The new speed and the changed SPL. Geometry changes the loading as well as the opening area. |
| Less drive | Lower speed and lower output at the same geometry. |
| A filter outside the useful band | Whether the speed peak falls without losing wanted output. |
| A different station | That it exists in every comparison enclosure. Missing stations are left out. |
> **The model stays linear** There is no simulated turbulence or air-speed compression and no universal horn speed limit applied here. Judge the passage shape and intended use, and validate a real build with measurements.
## What to try
| Try | What it changes |
| --- | --- |
| [Inspect the constriction](https://simulator.00aud.io/docs/horns/diagnostics) | Choose a station at a narrow part of the path, not just the mouth. |
| Compare both sides of an entry | Flow changes where a driver or branch enters, so check the stations either side. |
| [Test more area](https://simulator.00aud.io/docs/reference/tiles/horn-editor) | Preview a larger passage and compare its response as well as its speed. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, find the highest particle velocity across every station of my horn at its current power. Report its station, local area and frequency, then preview a larger passage there and compare the new velocity and SPL before saving.
---
# Horn Acoustic Impedance
> Read local acoustic loading as pressure divided by volume flow, distinguish magnitude and complex components, and recognise zero-flow singularities.
Source: https://simulator.00aud.io/docs/reference/tiles/horn-acoustic-impedance
Horn Acoustic Impedance describes the acoustic load at a station: local pressure divided by local volume flow. It is useful for understanding the horn’s loading, rather than choosing an amplifier.
- **Shows:** Pressure divided by volume flow at a horn station, as magnitude, phase, resistance or reactance.
- **Healthy when:** You are reading the intended station and distinguishing acoustic loading from the amplifier’s electrical load.
- **If it is not:** Compare pressure and velocity there, or choose another station if volume flow vanishes.
## The tile
_Figure: Horn Acoustic Impedance at Main H2 mouth, Main H4 mouth in the tapped-horn example._
Tapped-horn example at 100 W, half space, 1 m. Stations are measured from the closed end. Simulated when this page was built.
| Station | Position | Area | Peak | At |
| --- | --- | --- | --- | --- |
| Main H2 mouth | 0.95 m | 600 cm² | 35.53 kPa·s/m³ | 49.9 Hz |
| Main H4 mouth | 2.50 m | 2,400 cm² | 1.99 kPa·s/m³ | 392.4 Hz |
The example compares a narrow station with the mouth; its axis uses kPa·s/m³ to keep the values readable. In the app choose the station and then the display mode. Electrical **Impedance**, in ohms, is a different tile.
| Mode | Meaning |
| --- | --- |
| **Magnitude** | The size of the pressure-to-flow ratio, in Pa·s/m³. |
| **Phase** | The phase angle of pressure relative to volume flow, in degrees. |
| **Resistance** | The real part of the acoustic impedance. |
| **Reactance** | The imaginary part, which can change sign around resonances. |
## A closed end needs care
At exactly zero volume flow the ratio is undefined and the solver can leave it absent. Very small numerical flow can instead give an extremely large ratio. A closed-end throat is therefore a poor starting station for a readable impedance comparison; choose a station farther along the path.
The sign convention treats flow towards the stored segment end as positive. Keep the same location and orientation when comparing resistance, reactance or phase. A missing matching station in another enclosure is omitted, not represented by zero.
> **Read the numerator and denominator** A large ratio can come from high pressure, small flow, or both. Check **Horn Pressure** and **Horn Particle Velocity** at the same station before deciding what to change.
## What moves it
| Change | Effect |
| --- | --- |
| Input power alone | Pressure and flow scale together, so the linear ratio is unchanged. |
| Path length, area or flare | Changes resonances and the load seen at a station. |
| Stuffing or chamber losses | Changes the dissipative and reactive behaviour. |
| Selected station | Reads a different local load within the same horn. |
## What to try
| Try | What it changes |
| --- | --- |
| Separate the components | Switch between **Magnitude**, **Phase**, **Resistance** and **Reactance**. |
| Explain a gap | A station with no flow has no defined acoustic impedance; a missing value is not zero. |
| [Check amplifier load elsewhere](https://simulator.00aud.io/docs/reference/tiles/impedance) | Use **Impedance** for electrical impedance in ohms. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, inspect the acoustic impedance of my horn at a non-zero-flow station and at the mouth. Explain the magnitude, resistance and reactance in the working band, using the pressure and volume flow to explain any extreme values.
---
# Horn Radiating Outputs
> Separate a horn’s radiating mouths, ports and exposed cones, and see where their phases make the coherent total add or cancel.
Source: https://simulator.00aud.io/docs/reference/tiles/horn-radiating-outputs
A horn can radiate from more than one place. This tile splits those contributions so you can see whether they support or cancel one another.
- **Shows:** Each radiating mouth, port or exposed cone separately, plus their coherent total.
- **Healthy when:** The outputs combine usefully over the intended band, without an unwanted cancellation notch.
- **If it is not:** Compare their levels and phases, then test the path lengths or driver positions that set their relationship.
## The tile
_Figure: The back-loaded horn’s direct cone and mouth shown separately, with their coherent total._
The outputs are pressures, so they add with their phase: where the dashed lines are close in level and opposite in phase, the total drops below both.
Back-loaded horn: direct cone and mouth. Solid: the total. Dashed: Main mouth and Direct radiator on their own.
This is the back-loaded-horn guide’s design: B&C 10PS26, Half Space · 1.0 m · 50 W. Dashed curves show Main mouth and Direct radiator. The solid curve is their coherent total.
**Magnitude** shows SPL from each radiating output. **Phase** shows their far-field pressure phases and the phase of the summed pressure. There is no station selector because these are the outlets to the room, rather than internal locations.
## Read a cancellation
1. **Find the notch.** Look for a total below strong individual outputs at the same frequency.
2. **Compare phase.** Switch to **Phase**. Outputs with similar levels and opposing phases can nearly cancel. Their decibel readings must not be added as ordinary numbers.
3. **Change the cause.** Preview the path length, driver entry or other geometry that sets their relationship, then recheck the complete useful band. Moving one notch may create another.
| Horn connection | What to look for |
| --- | --- |
| Back-loaded horn | The exposed front cone combining with the rear-loaded horn mouth. |
| Compound horn | The front and rear horn mouths combining. |
| A ported rear chamber | The port contribution combining with the other radiating output. |
| A single-mouth horn | A single outlet can leave little to separate; use internal diagnostics for path behaviour. |
## Keep the model’s limits in view
These outputs are the model’s coherent far-field pressures at its configured distance and radiation conditions. The tile is not a room-interference or directivity prediction. It also omits the dashed folded-horn comparison shown on ordinary frequency graphs.
## What to try
| Try | What it changes |
| --- | --- |
| Find cancellation | Look for the solid total falling below strong individual dashed outputs. |
| Check phase | Switch to **Phase** at a suspected notch; the outputs combine as pressures, not as dB values. |
| [Trace each output](https://simulator.00aud.io/docs/reference/tiles/schematic) | Use **Schematic** to see where each radiating contribution comes from. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, inspect the radiating outputs of my horn and find any cancellation inside its intended working band. Compare each output’s level and phase at the notch, then preview a geometry change and report whether the total response improves.
---
# Metrics
> Rank visible designs by one measure, choose a frequency or band, and understand what a winning number does and does not establish.
Source: https://simulator.00aud.io/docs/reference/tiles/metrics
Metrics answers one comparison question at a time. Choose the quantity that matters, then see the visible designs ranked by it.
- **Shows:** Visible designs ranked by one selected measure, at a frequency or over a band when applicable.
- **Healthy when:** The measure and band match your goal, and you compare designs at appropriate drive and environment settings.
- **If it is not:** Choose another measure or band, then inspect the curves behind the ranking.
## The tile
Choose a measure in the tile’s menu. Point measures add a frequency field; band measures add start and end frequencies. **Higher wins** or **Lower wins** tells you the ranking direction. Rows show the result and difference from the best value; click a row to select its design.
Only visible enclosures participate. Missing or unavailable quantities are left unranked. F3 and F10 come from the simulation summary, so custom reference settings in the SPL tile do not alter these rows.
## Choose a measure
| Measure | Where it is read | Ranking |
| --- | --- | --- |
| **F3 (-3 dB)** | From the whole-response summary | Lower wins |
| **F10 (-10 dB)** | From the whole-response summary | Lower wins |
| **SPL at frequency** | At your chosen frequency | Higher wins |
| **Max SPL at frequency** | At your chosen frequency | Higher wins |
| **Group delay at frequency** | At your chosen frequency | Lower wins |
| **Average SPL over band** | Across your chosen band | Higher wins |
| **Peak Xmax use over band** | Across your chosen band | Lower wins |
| **Peak port velocity over band** | Across your chosen band | Lower wins |
| **Peak PR excursion over band** | Across your chosen band | Lower wins |
| **Minimum impedance over band** | Across your chosen band | Higher wins |
| **First port resonance** | From the whole-response summary | Higher wins |
## A ranking answers only its chosen question
The same sealed-example driver at 1 W, half space, 1 m. Values are simulated when the page is built.
| Sealed example volume | F3 | F10 |
| --- | --- | --- |
| 7.5 L | 65.9 Hz | 40.9 Hz |
| 15.0 L | 62.2 Hz | 33.8 Hz |
| 30.0 L | 63.9 Hz | 30.1 Hz |
A larger box may rank better for extension while costing cabinet space and cone travel. Change the measure to Xmax use or maximum output in your band before deciding. Ordinary SPL also depends on each design’s power and EQ, so check those before treating a higher row as a more efficient design.
## What to try
| Try | What it changes |
| --- | --- |
| Choose the useful band | Use a band measure to compare only the frequencies the speaker will play. |
| [Check the trade-off](https://simulator.00aud.io/docs/guides/compare) | Compare extension, maximum output and Xmax use; winning one row does not mean winning all three. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, compare the visible designs in my workspace for F3, average SPL and maximum Xmax use over my intended passband. State the power and EQ used for each and explain the trade-offs before recommending one.
---
# Insights
> Use the simulator’s rule-based design notes to find issues, inspect the relevant curves and test suggested changes.
Source: https://simulator.00aud.io/docs/reference/tiles/insights
Insights turns selected simulation checks into short notes. Start here to find a likely problem, then inspect the graph that explains it.
- **Shows:** Rule-based notes about visible designs, including travel, port behaviour and response shape.
- **Healthy when:** The flagged items are understood at your current power and thresholds, with the important graphs checked.
- **If it is not:** Select a flagged design, inspect its curve, and test the suggested change.
## The tile
The tile analyses visible designs and sorts flagged items by severity: **Watch**, **High** and **Critical**. Each note names the enclosure, gives its reading and explains a possible change. **Select** selects that design. Expand the tile to read more of the notes.
These are rules applied to simulation results. They do not come from an AI conversation. Changes to power, EQ, enclosure settings or the port-warning threshold can change the notes.
## What it checks
| Check | Inspect beside it |
| --- | --- |
| Cone travel compared with Xmax | [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) and the frequency band over the line. |
| Passive-radiator travel | [PR Excursion](https://simulator.00aud.io/docs/reference/tiles/pr-excursion), using the radiator’s own Xmax. |
| Front and rear port air speed | The relevant [port-velocity tile](https://simulator.00aud.io/docs/reference/tiles/port-velocity). |
| Port resonance and impractical port geometry | The port dimensions, tuning and intended low-pass band. |
| Response shape and sealed-box Qtc | [SPL (dB)](https://simulator.00aud.io/docs/reference/tiles/spl), then the box alignment. |
## Act on a note
1. **Select the design.** Use **Select** and confirm the power and filters are the ones you intend to use.
2. **Inspect the curve.** Find the flagged frequency and decide whether it lies in, or below, the band you will reproduce.
3. **Test the change.** Where a high-pass action is offered, it adds a real enabled filter. Check the filtered SPL and travel afterwards; it is not just a dismiss button.
> **A candidate is not a verdict** **Best current candidate** reflects this set of rule scores. It does not choose your desired bandwidth, cabinet size or listening level. **No flagged issues** means no issue crossed these thresholds, not that the design has been physically validated.
## What to try
| Try | What it changes |
| --- | --- |
| Inspect the cause | Use **Select** on a note to select the design it describes. |
| [Try a protective filter](https://simulator.00aud.io/docs/guides/eq-and-filters) | Where a note offers a high-pass action, it adds a real filter; recheck the response afterwards. |
| [Check beyond the notes](https://simulator.00aud.io/docs/reference/tiles/headroom) | Read **Headroom** and the relevant limit tiles even when there are no flagged issues. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, review my visible designs at their current settings. Check cone and radiator travel, front and rear port speed, and response shape. Explain the most important issue and preview one change that addresses it before saving.
---
# Compare
> Plot two quantities against frequency with separate vertical axes, and choose useful pairs for acoustic, mechanical and electrical comparisons.
Source: https://simulator.00aud.io/docs/reference/tiles/compare
Compare puts two different measurements on the same frequency chart. Use it to connect output with the effort behind it, or to inspect electrical magnitude and phase together.
- **Shows:** Two different quantities against the same frequency axis, each with its own vertical scale.
- **Healthy when:** The pair answers a question, and you read each curve against its own units.
- **If it is not:** Choose a useful pair under **Left axis** and **Right axis**, or start with **Presets**.
## The tile
Choose **Left axis** and **Right axis** in the tile’s settings. The left quantity is solid; the right is dashed. Each visible enclosure keeps its own colour. The horizontal axis remains frequency: this is not a scatter plot of one quantity against another.
> **Read the correct scale** A crossing between a solid and a dashed curve does not mean their values are equal. The two vertical axes have different units and scale independently. Use the hover readout for values at the same frequency.
## Useful pairs
| Preset | Question it answers |
| --- | --- |
| **Excursion + Group Delay** | Where do travel and delay rise together? |
| **SPL + Amplifier Load** | What electrical demand accompanies this output? |
| **Impedance + Electrical Phase** | Where is impedance low, and what is its electrical phase? |
| **SPL + Excursion** | Where does cone travel buy useful output? |
| **Max SPL + Limit Excursion** | How much travel is used at the maximum-output ceiling? |
| **Port Velocity + Excursion** | Where does the port take over from the cone? |
For a vented box, **Port Velocity + Excursion** makes the handover near tuning easy to see: the cone’s travel dips while the port speed rises. For amplifier questions, **Impedance + Electrical Phase** keeps the two electrical quantities together.
## Available quantities
| Quantity | Unit |
| --- | --- |
| **SPL** | dB |
| **Max SPL** | dB |
| **Excursion** | mm |
| **PR Excursion** | mm |
| **Port Velocity** | m/s |
| **Rear Port Velocity** | m/s |
| **Cone Velocity** | m/s |
| **Port Volume Velocity** | L/s |
| **Group Delay** | ms |
| **Acoustic Phase** | ° |
| **Impedance** | Ω |
| **Electrical Phase** | ° |
| **Amplifier Load** | VA |
| **Current Draw** | A |
| **Power at Limit** | W |
| **Excursion at Limit** | mm |
Choose different quantities for the two axes. A quantity that does not exist for an enclosure, such as passive-radiator travel on a sealed box, has no meaningful curve. Do not interpret an absent line as a passing limit check.
## What to try
| Try | What it changes |
| --- | --- |
| [Output and effort](https://simulator.00aud.io/docs/reference/tiles/excursion) | Compare SPL and excursion to find frequencies that cost travel for little sound. |
| [Electrical load](https://simulator.00aud.io/docs/reference/tiles/impedance) | Compare impedance and electrical phase to understand the changing load. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, compare SPL and excursion in my visible designs over their intended working band. Identify frequencies where extra travel gives little output, and put the relevant response and limit tiles on screen.
---
# Schematic
> Read how the driver, chambers, ports and horn paths connect, and edit the active design’s values directly in its acoustic schematic.
Source: https://simulator.00aud.io/docs/reference/tiles/schematic
The schematic is a map of the acoustic connections. Use it to verify what each face of the cone drives and where sound leaves the enclosure.
- **Shows:** How drivers, chambers, ports and horn paths connect acoustically.
- **Healthy when:** The connections, volumes and outlets match the design you intend to simulate.
- **If it is not:** Select the intended enclosure and check its type and editable values before tuning the response.
## The tile
_Figure: A driver between a sealed rear chamber and a front chamber radiating through a port._
The driver sits between a sealed rear chamber and a front chamber that radiates through a port. Only the chamber outlets reach the room.
In this bandpass example, one diaphragm face sees a sealed chamber while the other drives a chamber with a port to the room. The room hears that port. The diagram shows acoustic roles and connections, not a proposed cabinet’s panel positions.
## Read and edit in place
1. **Select the enclosure.** Choose an enclosure in the legend below the drawing. The tile shows one schematic at a time; the active drawing accepts edits when you have editing permission.
2. **Inspect a part.** Select a driver, chamber or path to follow its connection. In a multiple-entry horn, selecting a driver also selects that driver for editing.
3. **Change a value.** Click an editable dimension or value and enter the new one. The edit updates the same enclosure or input setting used by the side panel and response graphs.
4. **Check the environment.** The drawing’s environment control exposes **Radiation space** and **Listening distance**. These are workspace settings, so they affect the other designs too.
## Choose the right detail view
| Need | Use |
| --- | --- |
| Understand the whole acoustic connection | **Schematic**, including chambers and outlets. |
| Change a horn’s spans, flares or entries | [Horn Editor](https://simulator.00aud.io/docs/reference/tiles/horn-editor). |
| Fit a horn path into boards and a cabinet | [Fold](https://simulator.00aud.io/docs/reference/tiles/fold). |
| Set the rectangular baffle and driver position | [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout). |
## What to try
| Try | What it changes |
| --- | --- |
| [Trace the sound path](https://simulator.00aud.io/docs/start/enclosure-types) | Follow each diaphragm face to a chamber, horn or radiating outlet. |
| Edit a value in place | Click an editable value on the active drawing; it updates the same design as the enclosure panel. |
| [Inspect a horn path](https://simulator.00aud.io/docs/reference/tiles/horn-editor) | Use **Horn Editor** for segment detail and **Fold** for cabinet geometry. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, inspect my selected enclosure and explain the acoustic path from each face of the driver to the radiating outputs. Put the Schematic tile on screen and identify which chamber or path each editable value belongs to.
---
# EQ Editor
> Edit filters directly on the SPL chart, select the correct enclosure or horn driver, and check the result on excursion and headroom.
Source: https://simulator.00aud.io/docs/reference/tiles/eq-editor
EQ Editor keeps the selected enclosure’s filters open on its SPL graph. Every edit changes the simulated signal, so the other response and limit tiles follow it.
- **Shows:** SPL with editable filter handles for the selected enclosure or horn driver.
- **Healthy when:** The response has the shape you need and the filtered design still passes its travel and power checks.
- **If it is not:** Select the correct enclosure, adjust one filter, and recheck **Excursion** and **Headroom**.
## The tile
The tile is always in filter-editing mode. On other supported charts, the **EQ** button enters that mode and **Exit** leaves it. Select the intended enclosure first; for a multiple-entry horn, also select the driver whose filters you mean to edit.
| Control | Action |
| --- | --- |
| **Add filter** | Right-click the chart to add a filter at that frequency. |
| High-pass or low-pass triangle | Drag sideways to change cutoff; open its control for type and slope. |
| Parametric or shelf dot | Drag sideways for frequency and vertically for gain. Selected handles expose bandwidth where applicable. |
| **EQ / filters** | Use the side panel for exact values, enabled state and deletion. |
| **Copy from...** | Copy another enclosure’s filters; the copy dialog replaces the current filter set. |
## Check the cost, not just the shape
_Figure: A high-pass reduces the low-frequency travel demanded by the vented example._
Vented example at 200 W, with and without a 25 Hz Butterworth high-pass. Half space, 1 m; simulated when the page was built.
| Excursion after EQ | Peak | At |
| --- | --- | --- |
| No filter | 21.2 mm | 10 Hz |
| High-pass enabled | 6.3 mm | 24 Hz |
Here the plotted peak excursion falls from 21.2 mm to 6.3 mm. The high-pass also removes low-frequency SPL. Keep **SPL (dB)** and **Excursion** together to see whether that trade suits the band you need.
> **Boost asks the driver to do more** Bass boost raises travel and electrical demand where it raises voltage. It cannot increase the driver’s intrinsic maximum-output ceiling. Check **Headroom**, port velocity and passive-radiator travel after the response looks right.
## What to try
| Try | What it changes |
| --- | --- |
| [Protect the bottom octave](https://simulator.00aud.io/docs/guides/eq-and-filters#protect-the-cone) | Add a high-pass below the useful band, then compare its cost in SPL. |
| [Compare without deleting](https://simulator.00aud.io/docs/guides/eq-and-filters) | Disable a filter in **EQ / filters** to compare the result, then enable it again. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, preview a protective high-pass for my selected enclosure. Compare the original and filtered SPL, cone excursion and port velocity at the current power, and explain the lost bandwidth before saving any filters.
---
# Baffle Layout
> Set a rectangular baffle and driver position for the baffle-step approximation, and inspect the resulting low-frequency shelf in SPL.
Source: https://simulator.00aud.io/docs/reference/tiles/baffle-layout
Use Baffle Layout to place the selected driver on a rectangular front panel. The dimensions and position feed the simulator’s smooth baffle-step correction.
- **Shows:** The selected driver on a rectangular baffle, with the model’s baffle-step transition and correction.
- **Healthy when:** Baffle dimensions and driver position match the intended cabinet, and the approximation fits your purpose.
- **If it is not:** Enable baffle step, enter the dimensions and place the driver; then inspect SPL.
## The tile
1. **Enable the model.** Switch on **Enable baffle step**. The layout and enclosure’s **Simulate baffle step** control refer to the same setting.
2. **Set the panel.** Type **Width** and **Height**, or drag the edge and corner handles. Dimensions are shown in millimetres.
3. **Place the driver.** Drag the driver or focus it and use the arrow keys. Shift makes larger moves. **Center driver** restores the centre position.
The readouts show the baffle dimensions, driver position, transition frequency and correction at the displayed reference frequency. Changing them changes the selected enclosure; it does not lay out several physical drivers or check cabinet bracing.
## What changes in the response
_Figure: The low-frequency shelf introduced by enabling the baffle-step model._
Sealed example at 1 W, half space, 1 m, with its default baffle-step geometry. Simulated when this page was built.
| SPL with baffle step | Peak | At |
| --- | --- | --- |
| Baffle step off | 85.4 dB | 392 Hz |
| Baffle step on | 82.6 dB | 392 Hz |
The default baffle for this driver is 300 × 450 mm. Its calculated transition is 364 Hz, with a 6 dB shelf depth. Wider effective baffles move the transition lower; offsetting the driver changes the effective edge distances.
> **A smooth approximation** The model produces a low-frequency shelf. It does not calculate individual edge-diffraction ripples, a measured polar response or room reflections. Treat the result as a broad response adjustment and verify the finished speaker with measurements.
## What to try
| Try | What it changes |
| --- | --- |
| Set the dimensions | Type **Width** and **Height**, or drag the baffle’s resize handles. |
| Place the driver | Drag the driver or use its arrow-key controls. **Center driver** puts it back in the middle. |
| [Check the response](https://simulator.00aud.io/docs/reference/tiles/spl) | Compare the low-frequency shelf in **SPL (dB)**. The model does not predict edge-diffraction ripple. |
---
# T/S Parameters
> Inspect the selected driver, explore temporary parameter changes, and distinguish graph-only adjustments from editing saved driver data.
Source: https://simulator.00aud.io/docs/reference/tiles/ts-parameters
This tile puts the selected driver’s source values and derived interpretation beside the graphs. Use it to check the input data or explore how a parameter change affects the design.
- **Shows:** The selected driver’s electrical, mechanical and physical parameters, plus derived interpretation and sealed targets.
- **Healthy when:** The driver, units and wiring are correct, and any temporary adjustments are intentional.
- **If it is not:** Check the source data. Use **Reset all** to remove temporary tweaks or **Edit params** to create corrected driver data.
## The tile
| Section | What it contains |
| --- | --- |
| **Electrical** | Resistance, inductance, motor strength and power rating, with wiring-related values where applicable. |
| **Mechanical** | Resonance, moving mass, compliance, losses and Q values. |
| **Physical** | Equivalent compliance volume, radiating area and linear travel. |
| **Interpretation** | Derived efficiency, sensitivity and broad enclosure guidance. |
| **Sealed targets** | Ideal sealed alignments calculated from Fs, Qts and Vas. An unavailable target is not a suggested zero-litre box. |
## Explore a variation
Enable **T/S adjust sliders** to make temporary, per-enclosure graph adjustments. Each slider also accepts a typed value. Related quantities are recalculated by the adjustment model, so changing a fundamental parameter can change derived ones too.
1. **Choose a baseline.** Confirm the selected driver and turn off existing adjustments before comparing with source data.
2. **Change one thing.** Vary a parameter and observe the response and limit tiles. Treat this as sensitivity analysis, not a measurement of how a real driver will change.
3. **Restore the original.** Reset that parameter, use **Reset all**, or switch the sliders off. The driver-library record has not been rewritten by the sliders.
## Correct the source data
**Edit params** opens the driver editor. Saving a new driver or overwriting an editable custom driver changes saved driver data, unlike the temporary graph adjustments. Check units and internal consistency before saving.
> **Interpretation is a starting point** An efficiency-bandwidth-product suggestion or ideal sealed target cannot choose your preferred cabinet size, output or filters. Simulate the actual enclosure and inspect the working band.
## What to try
| Try | What it changes |
| --- | --- |
| [Check the inputs](https://simulator.00aud.io/docs/reference/ts-parameters) | Compare Fs, Qts, Vas, Sd and Xmax with the manufacturer’s data, including units. |
| Explore a variation | Enable **T/S adjust sliders** to see how a parameter change affects this enclosure’s graphs. |
| Return to the baseline | Use **Reset all** or switch off the adjustments before judging the original driver. |
## Ask your AI
**Ask your AI**
> Using 00 Simulator, inspect the driver used by my selected enclosure. Explain its Fs, Qts, Vas, Sd and Xmax, check the units and consistency of the data, and describe which values most affect this design.
---
# Controls and fields
> A field guide to enclosure size, port tuning, power, wiring, filters and environment in 00 Simulator.
Source: https://simulator.00aud.io/docs/reference/controls
Select an enclosure to edit its driver, box, power, filters and environment. These settings belong to that design, so check them before comparing curves from different enclosures.
## Enclosure configuration
| Field | What it changes | Watch for |
| --- | --- | --- |
| **Type** | The acoustic arrangement: sealed, vented, passive radiator, bandpass or horn. | Changing the type changes which chamber and port fields are available. [Compare the types](https://simulator.00aud.io/docs/start/enclosure-types). |
| **Volume** | The chamber volume, 0.01–100,000 L. | Net air space, not the outside dimensions of the cabinet. Port volume is handled separately. |
| **Tuning** | The target resonance of a ported chamber, 15–1,200 Hz. | Typing a tuning holds that frequency and recalculates the port length as geometry changes. |
| **Port length** | The physical length of the duct. | Typing a length holds that length and recalculates tuning as geometry changes. |
| **Shape** | Round, slot or a custom cross-sectional area. | Use the actual opening area, especially for a slot. |
| **Number of ports** | How many identical ports share the air flow. | More total area usually needs longer ports to keep the tuning. |
| **End correction** | The allowance for moving air beyond the physical ends. | Choose the termination that matches the build. See [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports). |
| **Port model** | A lumped resonance or a distributed duct model. | The distributed model includes the duct’s changing response along its length. See [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports). |
**Box volume adjustments** contains **Driver displacement** and **Bracing / other**. Enter the space occupied inside the cabinet, then check **Results** for the resulting volumes. A bandpass box has separate chambers; check which chamber a field belongs to.
A sealed box also lets you work from the target system resonance or Q. A passive radiator uses **Added mass (tuning)**, **Passive radiator** and **Number of PRs**. Horn geometry lives in the [Horn Editor](https://simulator.00aud.io/docs/reference/tiles/horn-editor).
## Input power
| Field | Meaning |
| --- | --- |
| **Power › Input power** | Sets the drive for this enclosure. For an array in one box it is the total power shared by the drivers. Multiple-entry horns have a power setting per driver entry. |
| **Load voltage** | The voltage corresponding to the power setting and the effective DC resistance of the wired driver load: V = √(P × R). |
| **Series resistance** | Resistance between amplifier and driver, such as cable and amplifier output resistance. It changes level and electrical damping. |
| **Series capacitor** | A physical capacitor in series with the driver load. Its **Capacitance** and **ESR** interact with the driver’s impedance. |
| **Wiring** | The series/parallel arrangement of multiple drivers. Dual voice-coil drivers also have a coil-wiring choice. Check the load before choosing an amplifier. |
> **Watts are a drive setting** The model converts the setting to voltage. Actual current and real input power then vary with impedance across frequency. Use [Amplifier Load](https://simulator.00aud.io/docs/reference/tiles/amplifier-load) to inspect that load. Raising the drive raises SPL and excursion; it does not raise the speaker’s [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl) limit.
## Radiation space and distance
Open **Environment** to set **Radiation space** and **Listening distance**. The space is an idealised boundary condition, not a room simulation.
| Setting | Geometry | Displayed offset from full space |
| --- | --- | --- |
| **Full space** | No nearby large boundary | 0 dB |
| **Half space** | One boundary, such as the floor | +6 dB |
| **Quarter space** | Two boundaries, such as floor and one wall | +12 dB |
| **Eighth space** | Three boundaries, such as floor and two walls | +18 dB |
**Listening distance** applies free-field distance attenuation to the sound level. It does not reduce how far the cone moves or how fast the port air moves. A real room adds reflections, cancellations and modes that these controls do not predict.
> **Horn loading also changes** For horns, radiation space is part of the mouth load. Changing it can alter the response shape as well as the level. Recheck the horn’s curves instead of assuming a fixed gain everywhere.
## Filters and baffle
- [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters): Set the operating band and protect the driver with the filters you intend to use.
- [EQ Editor](https://simulator.00aud.io/docs/reference/tiles/eq-editor): Edit filter settings on their response curve.
- [Baffle Layout and baffle step](https://simulator.00aud.io/docs/reference/tiles/baffle-layout): Place the driver on the baffle and model the broad response change caused by the cabinet’s front face.
---
# T/S parameters
> Driver parameter symbols, units, derivation relationships and limits used by 00 Simulator.
Source: https://simulator.00aud.io/docs/reference/ts-parameters
The driver’s small-signal parameters define its electrical and mechanical behaviour. Xmax and the power rating add limits; they do not make the underlying model nonlinear.
## Box and motor parameters
| Symbol | Default input unit | Meaning | Can be derived from |
| --- | --- | --- | --- |
| Fs | Hz | Free-air resonance frequency | Mms, Cms |
| Qts | Unitless | Total quality factor | Qms, Qes |
| Qes | Unitless | Electrical quality factor | Qts, Qms |
| Qms | Unitless | Mechanical quality factor | Qts, Qes |
| Vas | L | Equivalent acoustic compliance volume | Cms, Sd |
| Re | Ω | Voice coil DC resistance | Enter from the data sheet or measurement |
| Le | mH | Voice coil inductance | Enter from the data sheet or measurement |
| Bl | T·m | Motor force factor (BL product) | Re, Qes, Mms, Fs |
| Znom | Ω | Nominal impedance | Enter from the data sheet or measurement |
Re is DC resistance. Znom is the nominal impedance class, not the resistance at every frequency. **Impedance** shows the changing load of the driver in the enclosure. Le describes coil inductance; the non-horn upper-response setting changes how it affects the acoustic estimate, as described in [Model and limits](https://simulator.00aud.io/docs/reference/model-and-limits#upper-response).
## Mechanics and radiating area
| Symbol | Default input unit | Meaning | Can be derived from |
| --- | --- | --- | --- |
| Mms | g | Moving mass including air load | Fs, Cms |
| Cms | mm/N | Mechanical compliance of suspension | Fs, Mms, Vas, Sd |
| Rms | kg/s | Mechanical resistance (damping) | Qms, Mms, Fs |
| Sd | cm² | Effective piston radiating area | Dd |
| Dd | mm | Effective piston diameter | Sd |
Sd is the effective radiating area and Dd is the diameter of that area. They describe the moving piston, not the outside basket diameter. Enter one and let the form derive the other.
Related parameters must agree: Qts = Qms × Qes / (Qms + Qes), and Fs depends on Mms and Cms. The form derives missing values where it has enough information. Do not mix measurements from different samples or coil configurations merely to fill every field.
## Travel and power limits
| Symbol | Default input unit | Meaning |
| --- | --- | --- |
| Xmax | mm | Maximum linear excursion (one-way) |
| Xmech | mm | Mechanical excursion limit (surround/spider bottoming) |
| Xdamage | mm | Excursion threshold for physical damage |
| Pe | W | Rated power handling (RMS) |
Xmax is one-way linear travel, not peak-to-peak travel. Xmech and Xdamage are optional further limits. The [Excursion tile](https://simulator.00aud.io/docs/reference/tiles/excursion) can show these reference lines, while [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl) uses Xmax and the selected thermal rule.
> **Read the manufacturer’s definitions** A mechanical clearance is not interchangeable with a linear excursion rating. Power ratings also depend on the test signal and conditions. Check the original data sheet before using either as a design limit.
## Check the inputs
1. **Match the exact driver.** Check the model suffix, impedance version and coil wiring against the data sheet.
2. **Check the units.** The form offers unit choices. Check whether a source gives litres or cubic feet, grams or kilograms, millihenries or henries, and one-way or peak-to-peak travel.
3. **Inspect derived values.** Open **T/S Parameters** and use **Edit params** to inspect the values. Missing information may be derived; derived information is not a separate measurement.
4. **Compare the resulting alignment.** Use the same driver in a known enclosure, or compare the predicted impedance with a measurement. Fix input mistakes before optimising the box.
**Ask your AI**
> Using 00 Simulator, read the driver data for my selected enclosure. Explain which parameters set its box alignment and which set its output limits. Flag missing or inconsistent values, and do not change the design.
---
# Glossary
> Plain definitions of loudspeaker, enclosure, horn and measurement terms used in 00 Simulator.
Source: https://simulator.00aud.io/docs/reference/glossary
Short definitions of the terms you meet when designing an enclosure. Follow the links for the controls, graphs and worked examples behind them.
## Response and level
**SPL** (sound pressure level): Sound pressure expressed in decibels at the chosen listening distance and radiation space. The [SPL tile](https://simulator.00aud.io/docs/reference/tiles/spl) shows the response at the input power you set.
**F3** (−3 dB point): A frequency where the response is below its reference level by 3 dB. Read it with the response shape: a peak can make a single cutoff figure misleading. [Reading a response](https://simulator.00aud.io/docs/start/reading-a-response).
**F6 and F10**: Cutoff markers like F3, but at drops of 6 dB and 10 dB. They show how the low-frequency roll-off continues beyond F3.
**Phase**: The angle of an oscillating response relative to the drive. Outputs add with their phase, so similar levels can reinforce or cancel. [Phase](https://simulator.00aud.io/docs/reference/tiles/phase).
**Group delay**: How quickly phase changes with frequency, expressed as a time. It describes the modelled response and filters, not a separate echo from the room. [Group Delay](https://simulator.00aud.io/docs/reference/tiles/group-delay).
**Impedance**: The frequency-dependent electrical load, with both magnitude and phase. It includes resistance, coil inductance and the driver’s movement against its acoustic load. [Impedance](https://simulator.00aud.io/docs/reference/tiles/impedance).
**Baffle step**: The broad level change as wavelengths become large compared with the baffle. The app’s optional model is a smooth correction, not a full diffraction simulation. [Baffle Layout](https://simulator.00aud.io/docs/reference/tiles/baffle-layout).
## Driver and limits
**T/S parameters** (Thiele/Small parameters): Small-signal measurements that describe a driver’s motor, moving mass, suspension and damping. See the [parameter reference](https://simulator.00aud.io/docs/reference/ts-parameters) for the symbols and units.
**Fs**: The driver’s free-air resonance frequency, before the enclosure adds its acoustic load.
**Qts**: The total quality factor of the driver’s free-air resonance, combining electrical and mechanical damping. It is not the Q of the finished box.
**Vas**: The volume of air with the same compliance as the driver’s suspension. It is a property of the driver, not a recommended box size.
**Sd**: The effective area of the moving piston. Cone velocity multiplied by Sd gives volume velocity.
**Excursion**: The cone’s displacement from its resting position. The [Excursion tile](https://simulator.00aud.io/docs/reference/tiles/excursion) reports peak, one-way movement.
**Xmax**: The manufacturer’s maximum linear one-way excursion. Passing it warns that the small-signal model no longer describes the driver reliably; it is not itself a prediction of damage.
**Pe**: The driver’s rated power handling. [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl) interprets it through the selected thermal rule.
**Max SPL**: The modelled sound level at which excursion or the chosen thermal ceiling is reached, one frequency at a time. Port air speed is checked separately. [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl).
**Headroom**: The margin between the demanded level and a limit. The [Headroom tile](https://simulator.00aud.io/docs/reference/tiles/headroom) compares average and peak demand with clean and maximum thresholds.
**Crest factor**: The difference between average and peak level. It lets the headroom calculation separate sustained thermal demand from brief peaks.
## Boxes and ports
**Alignment**: The response produced by a particular driver, box volume, tuning and losses together. A box size alone is not an alignment.
**Net volume**: The air volume available to the acoustic chamber, excluding the space occupied by the port, driver and other objects. [From simulation to a build](https://simulator.00aud.io/docs/start/simulation-to-build).
**Gross volume**: The internal cabinet volume needed to contain the net air volume plus the port and entered displacements. It does not include wall thickness.
**Qtc**: The total Q of a driver in a sealed box. It describes the damping and shape around the system resonance. [Sealed](https://simulator.00aud.io/docs/boxes/sealed).
**Fb** (tuning frequency): The resonance of the air in a port against the chamber air, or the corresponding tuning of a passive radiator system.
**End correction**: The allowance for air moving just beyond the ends of a duct. It makes the acoustic length greater than the physical length. [Ports and end correction](https://simulator.00aud.io/docs/boxes/ports).
**Port velocity**: Peak air speed through the port opening. It is a useful warning for noise and compression, which the linear model does not calculate directly. [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity).
**Volume velocity**: Volume flow per unit time, equal to particle velocity multiplied by cross-sectional area. The same flow moves faster in a narrower passage.
**Passive radiator**: An undriven diaphragm that replaces the moving air mass of a port. Its mass tunes the system and its travel needs checking. [Passive radiator](https://simulator.00aud.io/docs/boxes/passive-radiator).
## Horns
**Throat**: The start of a horn path, normally its smallest cross-section.
**Mouth**: An opening where the path radiates into the surrounding space. Mouth area and radiation space affect the load seen by the path.
**Flare**: The change of cross-sectional area along a segment. The horn editor can join segments with different profiles. [Horn Editor](https://simulator.00aud.io/docs/reference/tiles/horn-editor).
**Tapped horn**: A horn with both faces of the driver coupled into one path at different positions. Their outputs combine with a frequency-dependent phase relationship. [Tapped horn](https://simulator.00aud.io/docs/horns/tapped-horn).
**Particle velocity**: The local speed of air in a horn section. It differs from volume velocity because it also depends on the section area. [Horn diagnostics](https://simulator.00aud.io/docs/horns/diagnostics).
**Fold**: A cabinet arrangement that fits the acoustic path into a smaller footprint. The acoustic simulation follows the path geometry rather than calculating three-dimensional flow around each bend. [Folding](https://simulator.00aud.io/docs/horns/folding).
---
# Model and limits
> What 00 Simulator calculates, how the linear model treats boxes and horns, and which results still need measurements.
Source: https://simulator.00aud.io/docs/reference/model-and-limits
00 Simulator predicts the response of the driver and acoustic system you describe. Use it to compare designs and find likely limits, then measure the finished cabinet and system.
## What is modelled
| Part | Model | Practical limit |
| --- | --- | --- |
| Driver | An electrical and mechanical network built from the T/S parameters, coupled to the enclosure. | It depends on the quality and consistency of the driver data. |
| Box chambers | Lumped air compliance, with the configured losses and connected ports or passive radiators. | A chamber is not a three-dimensional cabinet with panel vibration and internal standing waves. |
| Ports | A lumped port model, or a distributed duct when selected. | Neither predicts audible turbulence, chuffing or large-signal flow compression. |
| Horns | A one-dimensional plane-wave solution along each path and its changing cross-section. | Bends, higher-order modes and three-dimensional mouth directivity are outside this model. |
| Electrical drive | Driver count and wiring, series resistance and capacitor, and the configured filters. | The amplifier is not a full clipping, current-protection or power-supply simulation. |
| Listening conditions | Radiation space, distance, and optional baffle-step correction. | Room modes, reflections and listening-seat cancellations need measurement. |
Horns carry an **Alpha** label in the enclosure selector. Check the relevant topology and diagnostic pages before using a design for a build.
## What linear means here
At fixed settings, increasing drive raises SPL and motion without changing the shape of the response. The model does not suddenly compress or distort when the cone crosses Xmax. That is why the output curves and limit checks must be read together.
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The same vented design at changing drive: SPL rises, while excursion and port air speed reveal the cost. This demonstration does not save changes to your workspace.
> **A warning line is not a nonlinear simulation** Xmax and port-speed thresholds mark conditions to investigate. They do not predict a distortion percentage, the sound of a port, or the exact point of mechanical damage.
## The upper response
For box designs, **Settings › Simulation… › Non-horn upper response** offers two readings of the upper acoustic response.
| Setting | What it means |
| --- | --- |
| **Estimated · BITS frequency limit** | Estimates an ideal driver response without the acoustic roll-off from coil inductance, then applies the published upper-frequency limit when the driver data provides one. The chamber response and EQ still apply. |
| **Physical model** | Uses the driver’s physical electrical and mechanical model, including its coil inductance. Horns always use this mode. |
The estimate changes acoustic magnitude and SPL limits; electrical impedance, cone motion and phase remain physical results. Neither mode replaces a measured midrange or treble response. Changing **Upper frequency** under **Settings › Display…** extends the calculation range, not its accuracy.
## Output limits
| Check | What it tells you | What it does not tell you |
| --- | --- | --- |
| [Excursion](https://simulator.00aud.io/docs/reference/tiles/excursion) | Travel compared with the entered Xmax, and optional further mechanical limits. | How distortion changes with displacement in the actual driver. |
| [Max SPL](https://simulator.00aud.io/docs/reference/tiles/max-spl) | The lower of excursion and the selected thermal ceiling, one frequency at a time. | A broadband music rating or a port-noise limit. |
| [Headroom](https://simulator.00aud.io/docs/reference/tiles/headroom) | Average and peak demand compared with its configured clean and maximum thresholds. | A guarantee that the system sounds clean under every signal. |
| [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) | Peak air speed compared with a warning threshold. | The effect of the exact flare, surface finish or obstructions on audible noise. |
**Voice coil temperature** in the Max SPL settings changes the resistance used for the capacity calculation. It is a specified thermal condition, not a time simulation of a coil warming during a track. The normal SPL response stays at its regular model condition.
## Validation and measurement
Not modelled: transmission lines, isobaric and dipole loading, crossovers or summing separate enclosures as one system, directivity, room or cabin gain, and nonlinear or large-signal behaviour.
The [WinISD validation](https://simulator.00aud.io/validation/winisd) and the [Hornresp comparison](https://simulator.00aud.io/docs/horns/hornresp#validation) show comparison cases and their scope. Agreement with another simulator checks a particular model, driver and configuration; it does not prove every enclosure or a finished physical build.
1. **Match the inputs.** Use the same driver data, net volume, port ends, losses, electrical drive, radiation space and distance before comparing tools or measurements.
2. **Check the physical build.** Measure impedance to check resonance and tuning. Verify internal volume and port dimensions, and investigate leaks or unexpected peaks.
3. **Compare acoustic response.** Import a measured trace with its distance and space recorded. Compare shape as well as level, and account for the room and microphone position.
4. **Increase level gradually.** Check amplifier clipping, driver noise and port noise as level rises. The small-signal curve alone cannot approve the final operating limit.
---
# Cookbook
> Worked sealed, vented and tapped-horn subwoofer examples with real simulation results and practical checks before a build.
Source: https://simulator.00aud.io/docs/cookbook
Start with a real example, change one thing and read what happens. These recipes show how to make a design decision from the response and its limits.
## Pick a recipe
- [15 L sealed subwoofer](https://simulator.00aud.io/docs/cookbook/sealed-subwoofer): Swap the driver and power in a fixed-size box. Read bass output and cone travel together.
- [Vented 12-inch subwoofer](https://simulator.00aud.io/docs/cookbook/vented-subwoofer): Balance extension, port air speed and the space a longer duct needs.
- [Tapped horn subwoofer](https://simulator.00aud.io/docs/cookbook/tapped-horn): Increase drive and compare a high-pass filter before the driver runs out of travel below the horn’s working band.
## Use the results
- Each recipe states its driver, enclosure and listening conditions. Figures and quoted results come from the app’s solver.
- Change one variable at a time and keep the original design for comparison.
- Inspect the limits at the power you intend to use, including the frequencies below the useful band.
- Treat the example as a starting point. Check the driver data, physical dimensions and finished measurements before approving a build.
---
# Vented 12-inch subwoofer
> Tune the vented subwoofer example, size its ports, check the duct length and protect the driver below tuning.
Source: https://simulator.00aud.io/docs/cookbook/vented-subwoofer
Use the Ciare 12.00SW in the 55 L vented example to explore three linked decisions: tuning, port area and low-frequency protection. A deeper response is only useful if the port fits and the cone stays within its limits.
- **Starting box:** 55 L net, tuned to 32 Hz
- **Starting port:** One 10 cm round port, 35.6 cm long
- **Comparison conditions:** 100 W, half space at 1 m
## Start with the example
1. **Open the starting design.** [Open the vented example](https://simulator.00aud.io/app?template=vented&power=100), at 100 W. Keep its driver and volume fixed for this comparison.
2. **Read the response and its costs.** Compare **SPL (dB)**, **Excursion** and **Port Velocity**. The cone moves least near tuning, while the port moves much of the air. Below tuning, output falls and cone travel rises.
3. **Keep a reference.** Use **Duplicate** to keep the original before changing the copy. Match input power and environment when comparing.
## Tune and size the port together
_Interactive walkthrough in the page: the simulator's own tiles running a short demo._
The app’s controls lower **Tuning** to 28 Hz, then change **Number of ports** to two. The original response stays visible for comparison.
All at 100 W over 10–400 Hz. The port warning is 17 m/s; the driver’s Xmax is 13.5 mm.
| Design | F3 | Each port’s length | Peak port speed | Peak cone travel |
| --- | --- | --- | --- | --- |
| 32 Hz, one port | 30.3 Hz | 35.6 cm | 20.1 m/s at 30.1 Hz | 15.0 mm |
| 28 Hz, one port | 29.6 Hz | 48.3 cm | 18.6 m/s at 26.1 Hz | 15.2 mm |
| 28 Hz, two ports | 29.6 Hz | 102.6 cm | 9.3 m/s at 26.1 Hz | 15.2 mm |
A lower tuning changes the response shape and needs a longer port. Increasing the total port area reduces air speed, but adds still more length at the same tuning. Check **Port length** and **Gross volume** before deciding the change is practical.
> **F3 is not the whole result** A lower tuning can trade level higher in the bass for more output lower down. Compare the full SPL curve over your intended band, not only a single cutoff number.
## Protect the cone below tuning
Now double the drive to 200 W on the 28 Hz design with two ports. Compare it with a 28 Hz fourth-order Butterworth high-pass. The filter reduces low-frequency output as well as travel.
_Figure: Cone excursion of the lower-tuned, two-port design, with and without a high-pass filter, against the driver’s Xmax._
Ciare 12.00SW, 55 L tuned to 28 Hz, two 10 cm ports, 200 W, half space at 1 m. Simulated when this page was built.
| Excursion with and without a high-pass filter | Peak | At |
| --- | --- | --- |
| No filter | 21.5 mm | 10 Hz |
| 28 Hz high-pass | 5.6 mm | 40 Hz |
Across 10–400 Hz, peak travel changes from 21.5 mm at 10.0 Hz to 5.6 mm at 40.2 Hz. Compare that with 13.5 mm Xmax, then inspect the filtered SPL and port speed too. This is a filter comparison, not a certified operating limit.
Add the intended **High-pass** in the enclosure’s filter controls and check **Max SPL (dB)** and **Headroom**. A filter does not remove the need to check the thermal limit and amplifier load. [EQ and filters](https://simulator.00aud.io/docs/guides/eq-and-filters) explains the controls.
## Before you cut wood
- Allow for the air volume, ducts, driver displacement and bracing inside the walls.
- Use end corrections that match the physical port ends. Keep enough clearance around the openings and check the duct’s first resonance against the operating band.
- Save the final driver, port, filters and power together, then measure the finished tuning and response.
- If the required ports cannot fit, compare a larger box or a passive radiator design instead of accepting a noisy port.
**Ask your AI**
> Using 00 Simulator, compare my selected vented enclosure with two ports and a lower tuning without saving. At its current power, report the SPL changes, port lengths, peak port air speed and peak cone excursion. Then compare a high-pass filter and explain the output it gives up.
---
# 15 L sealed subwoofer
> Change the driver and power in a live 15 L sealed box, then compare bass output, system Q and cone excursion.
Source: https://simulator.00aud.io/docs/cookbook/sealed-subwoofer
Start with the Dayton Audio DCS205-4 in a 15 L sealed box. Compare its output at 40 Hz with the travel it needs, then try another driver in the same space.
- **Box:** 15 L sealed, net air volume
- **Starting drive:** 50 W, equivalent to 14.0 V RMS
- **Conditions:** Half space at 1 m, 0.1 Ω series resistance
## Keep the first experiment simple
A sealed box removes port tuning and duct geometry from the experiment. The question becomes whether the driver and available air volume give useful extension and enough output before travel becomes the limit.
At the starting power, this driver has Qtc 0.62, system resonance 54.0 Hz and F3 65.8 Hz. It produces 94.5 dB at 40 Hz under these modelled conditions.
## Try the model
_Figure: Interactive sealed-box example with driver and power controls, SPL and cone-excursion graphs._
The box stays at 15 L. Changing the driver is a comparison, not a recommendation that every driver belongs in this volume.
Driver comparison at 50 W in 15 L, half space at 1 m.
| Driver | Qtc | F3 | SPL at 40 Hz | Peak travel, displayed band | Xmax |
| --- | --- | --- | --- | --- | --- |
| Dayton Audio DCS165-4 | 0.46 | 76.6 Hz | 91.6 dB | 12.8 mm | 6.0 mm |
| Dayton Audio DCS205-4 | 0.62 | 65.8 Hz | 94.5 dB | 7.9 mm | 8.8 mm |
| Dayton Audio DCS255-4 | 0.82 | 69.4 Hz | 94.5 dB | 4.3 mm | 8.3 mm |
## Read both graphs
1. **Increase the power.** Compare 1 W with 100 W. The level at 40 Hz changes from 77.5 to 97.5 dB. F3 stays at 65.8 Hz: more drive changes level, not the alignment.
2. **Watch the travel.** At 50 W the displayed band peaks at 7.9 mm near 10.1 Hz, against this driver’s 8.8 mm Xmax. At 100 W the peak becomes 11.2 mm. Check the whole operating band.
3. **Swap the driver.** The box stays the same, but its system Q, resonance and travel change. Compare the bass level and travel together instead of choosing by nominal cone size alone.
> **Look below the visible graph** The graph starts at 10 Hz; the solver continues to 5 Hz. At the starting power the full simulation peaks at 9.9 mm near 5.0 Hz. Include a suitable high-pass filter in the final design if the source contains unwanted energy that low.
## Before you cut wood
- Build enough internal space for 15 L of air plus the driver, bracing and anything else inside the cabinet.
- Verify the exact driver data and Xmax. A linear-travel rating is not a guarantee about distortion or mechanical noise.
- Use the final filter settings and intended drive in the main simulator. Check **Max SPL (dB)** and **Headroom** as well as the two graphs here.
- Measure impedance and acoustic response on the finished box. Room gain, cabinet vibration and sample variation are outside this example.
- [Open the starting design](https://simulator.00aud.io/app?template=sealed&driver=Dayton%20Audio%20DCS205-4&power=50): Continue with the same driver, volume and power in the simulator.
**Ask your AI**
> Using 00 Simulator, inspect my selected sealed enclosure at its current power. Report system Q, F3, cone excursion and the limiting frequencies. Compare a lower power and a high-pass filter without saving either change.
---
# Tapped horn subwoofer
> Drive the tapped-horn example harder, compare a high-pass filter and check cone excursion inside and below the useful band.
Source: https://simulator.00aud.io/docs/cookbook/tapped-horn
How hard can you drive the 2.5 m tapped-horn example? Use its B&C 21SW152, increase power and compare a high-pass filter while reading SPL and excursion together.
- **Path:** 2.5 m tapped horn
- **Starting drive:** 100 W, half space at 1 m
- **Driver travel limit:** 15 mm Xmax
## The path loads both sides of the cone
A tapped horn couples both faces of the driver into one path at different positions. Their outputs combine at the mouth, with the path length and entry positions shaping the useful band. [How the tapped horn is connected](https://simulator.00aud.io/docs/horns/tapped-horn).
At 100 W the lower and upper −3 dB points within this example’s working band are 39 Hz and 113 Hz. Those are response markers, not recommended crossover settings.
## Try the model
_Figure: Tapped-horn SPL and cone excursion at three powers, with and without a high-pass filter._
Every combination was simulated when this page was built, in half space at 1 m. The 25–120 Hz working band is solid on SPL; the response outside it is dashed.
B&C 21SW152, 2.5 m tapped horn, half space at 1 m. Working band: 25–120 Hz. Xmax: 15 mm.
| Power | High-pass | Lower / upper −3 dB | In-band peak SPL | In-band peak travel | Peak travel below band |
| --- | --- | --- | --- | --- | --- |
| 100 W | Off | 39 Hz / 113 Hz | 123 dB | 6.0 mm | 10.9 mm |
| 100 W | 28 Hz, 4th-order Butterworth | 39 Hz / 113 Hz | 123 dB | 3.8 mm | 3.3 mm |
| 400 W | Off | 39 Hz / 113 Hz | 129 dB | 12.0 mm | 21.9 mm |
| 400 W | 28 Hz, 4th-order Butterworth | 39 Hz / 113 Hz | 129 dB | 7.7 mm | 6.5 mm |
| 800 W | Off | 39 Hz / 113 Hz | 132 dB | 17.0 mm | 30.9 mm |
| 800 W | 28 Hz, 4th-order Butterworth | 39 Hz / 113 Hz | 132 dB | 10.9 mm | 9.3 mm |
## Three things to notice
1. **Power changes level.** From 100 W to 400 W to 800 W, the in-band peak rises from 123 to 129 to 132 dB. The linear model scales the response instead of compressing it.
2. **Check below the working band.** At 100 W, peak cone travel is 6.0 mm inside the band and 10.9 mm below it. The unfiltered model reaches Xmax at about 190 W below the band, compared with 620 W inside it. These are excursion-only comparisons over the simulated ranges.
3. **Compare the high-pass.** With the 28 Hz, 4th-order Butterworth high-pass, peak travel below the band at 400 W changes from 21.9 to 6.5 mm. At 800 W, peak travel across the explorer’s graph is 10.9 mm. Read that against 15 mm Xmax and check the filtered SPL too.
> **Travel is only one limit** The filter reduces low-frequency demand and output. It does not establish thermal capacity or predict passage noise. Compare **Max SPL (dB)** with the intended SPL, inspect **Headroom**, and check the horn diagnostics at the final drive.
## Then try
- [Change an entry position](https://simulator.00aud.io/docs/horns/tapped-horn): Compare the upper response and the useful band before accepting the change.
- [Try stuffing](https://simulator.00aud.io/docs/horns/stuffing): Damp a selected part of the path and compare what changes inside and outside the band.
- [Inspect the path](https://simulator.00aud.io/docs/horns/diagnostics): Check pressure, impedance and particle velocity through the horn.
- [Fold the design](https://simulator.00aud.io/docs/horns/folding): Fit the path into a cabinet and simulate the folded version beside the original.
## Before you cut wood
- Check the exact driver data and excursion definition against the manufacturer’s sheet or your own measurements.
- Select the working band, filters and amplifier drive together. Useful in-band output does not prevent over-excursion below the band.
- The one-dimensional model follows the acoustic path. It does not calculate bend turbulence, cabinet vibration or large-signal compression.
- Cross-check an export in Hornresp, then measure the finished cabinet before setting an operating limit.
- [Open the tapped-horn example](https://simulator.00aud.io/app?template=tapped-horn&power=100): Start with the unfiltered design at 100 W.
## Ask your assistant the same question
_Figure: Illustrative assistant session comparing tapped-horn excursion and a high-pass filter with solver-derived results._
The conversation above is illustrative. The tool names are the server’s own, and the curve and numbers are solver output from when this page was built.
You: Using 00 Simulator, how much power can my tapped horn take before the driver passes Xmax? Show me the excursion.
The assistant calls `get_workspace` (Tapped Horn · B&C 21SW152), `get_driver` (Xmax 15 mm), `simulate_workspace` (100 W · Half Space · 1.0 m), `render_simulation_graphs` (Excursion).
Assistant: At 100 W the cone peaks at 6.0 mm between 25 and 120 Hz, well inside its 15 mm Xmax, but reaches 10.9 mm below 25 Hz, where the horn stops loading it. Excursion grows with the square root of power, so the driver reaches Xmax in the band at about 620 W and below it at about 190 W. A 28 Hz, 4th-order Butterworth high-pass protects the low end: at 400 W the peak below the band falls from 21.9 mm to 6.5 mm.
| Result | Value |
| --- | --- |
| Peak, 25–120 Hz, 100 W | 6.0 mm |
| Peak below 25 Hz, 100 W | 10.9 mm |
| Reaches Xmax in the band at | 620 W |
| Reaches Xmax below it at | 190 W |
**Ask your AI**
> Using 00 Simulator, inspect my selected tapped horn and compare the power it can take before the driver passes Xmax, with and without a 28 Hz, 4th-order Butterworth high-pass. Do not save changes. Show the excursion inside and below the working band, and state the frequency range used.