@@ -214,6 +214,66 @@ the *parametric* model behind each research target, so you can:
214214 vs Toole at +6 dB bass)
215215- Treat target curves as code : version-controlled, diffable, reproducible
216216
217+ # # FAQ
218+
219+ # ## What is a Dirac Live target curve?
220+
221+ A target curve tells Dirac Live what frequency response you want from your
222+ speakers in your room. Dirac measures your actual in-room response, then
223+ computes correction filters that shape it toward the target. A flat target
224+ rarely sounds good — bass loses its weight and the highs feel sharp. The
225+ standard recommendations (Harman, Olive-Welti, Brüel & Kjær, Toole) all
226+ build in a deliberate bass shelf and a gentle treble tilt because listeners
227+ consistently prefer that shape over flat in blind preference tests.
228+
229+ # ## Harman, Olive-Welti, B&K, Toole — which curve should I use?
230+
231+ Quick orientation, by listening goal :
232+
233+ - **Harman** — community-standard, gentle bass shelf around 100 Hz, treble
234+ close to flat. Safe default for music; nothing surprising.
235+ - **Olive-Welti in-room** — slightly more aggressive bass and a steeper
236+ treble tilt than Harman. The current Harman research target; often
237+ preferred in blind preference studies.
238+ - **Brüel & Kjær 1974** — flatter mid/high, more "studio monitor"
239+ character. Use when you want a reference, not a flavored sound.
240+ - **Toole in-room** — gentle downward slope across the whole band, no
241+ shelf. Good when your room already loads up the bass on its own.
242+ - **Welti subwoofer** — sub-only curve; pair with one of the above for the
243+ rest of the band.
244+
245+ Try a couple — curveforge makes overlay comparison cheap
246+ (`curveforge plot a.yml b.yml -o overlay.svg`).
247+
248+ # ## How is this different from REW or the Dirac Live app itself?
249+
250+ REW (Room EQ Wizard) and the Dirac Live app let you edit target curves
251+ visually, breakpoint by breakpoint. That works once. If you want to try
252+ +0.5 dB on the bass shelf, you redraw the curve.
253+
254+ curveforge inverts the workflow : your target is a *recipe* — a few
255+ parameters or a YAML file. Editing means changing a number. Result :
256+ reproducible (lives in git), parametric (sweep and overlay), composable
257+ (stack transforms — peaking EQ, shelves, tilts — on any base). REW and the
258+ Dirac Live app are still the right tools for measuring and applying
259+ correction; curveforge is for designing the target that goes into them.
260+
261+ # ## Do I need to take room measurements to use curveforge?
262+
263+ No. curveforge produces *target* curves — what you want your room to sound
264+ like. Dirac Live (the desktop app) takes the measurements and computes the
265+ correction filters to hit that target. You hand Dirac the `.targetcurve`
266+ file curveforge generates. The two tools sit on either side of the
267+ measurement step.
268+
269+ # ## Does curveforge work with Dirac Live 2 and 3?
270+
271+ Yes. The `.targetcurve` format is shared between Dirac Live 2 and Dirac
272+ Live 3, and curveforge writes the format both versions consume. Tested
273+ against Dirac Live 3 on macOS and Windows; should work identically on the
274+ embedded Dirac builds shipped with miniDSP, NAD, Storm Audio, and similar
275+ hardware.
276+
217277# # References
218278
219279Each curve module ships with full citations accessible via
0 commit comments