• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Mechano23: Klippel, VituixCAD, and LoudspeakerLab comparison and real measurements v. spec sheets

wigginjs

Member
Joined
Mar 26, 2026
Messages
10
Likes
35
Mechano23 is an unusually good DIY validation case. XMechanik published an excellent open-source speaker design and shared the driver measurements and VituixCAD project files in the original Mechano23 AudioScienceReview thread. Amir later measured the finished speaker on the Klippel NFS and shared images and measurement data in the Mechano23 AudioScienceReview review thread. That gives us a rare chance to compare the full chain: raw driver measurements, design software predictions (VituixCAD, LoudspeakerLab), and real-world loudspeaker performance. Design meausrement data from LoudspeakerLab is attached.

The goal of this post is to explor how close modeled designs get to real-world results and how does the completness of the meausrement dataset affect the accuracy. Also, how does LoudspeakerLab compare to the current DIY reference workflow in VituixCAD? Finally, how much do we give up if we design from manufacturer spec-sheet data instead of in-cabinet measurements?
on_axis_overlay.png

cta_overlay.png

polar_directivity_slices.png



h-contour-compare.jpg


v-contour-compare.jpg

impedance_overlay.png

crossover_transfer_overlay.png

klippel_error_heatmap.png

Compared Sources

  1. Klippel NFS measurement from Amir's Mechano23 AudioScienceReview review, treated here as ground truth.
  2. VituixCAD from XMechanik's original Mechano23 AudioScienceReview post, using exported frequency response, impedance, crossover-transfer, CTA, and directivity data from the shared VituixCAD project.
  3. Mechano23 LoudspeakerLab, using the in-cabinet driver measurements.
  4. Mechano23 LoudspeakerLab spec sheet, using manufacturer spec-sheet FR/ZMA data.

Reference Notes And Caveats

  • Klippel is treated as ground truth for acoustic response.
  • Klippel On-Axis, Listening Window, Early Reflections, and polar comparisons use Amir's provided horizontal and vertical SPL data.
  • Klippel Sound Power and Directivity Index use the best available extraction from the CEA2034 image, so those conclusions are lower confidence than the On-Axis, Listening Window, Early Reflections, and polar-shape conclusions.
  • Klippel impedance/phase are digitized from the supplied impedance image. This is good enough to compare the main impedance shape and minima, but lower precision than source text data.
  • Crossover-transfer errors are referenced to VituixCAD exported crossover-transfer data because Klippel does not provide electrical transfer-function data.
  • LoudspeakerLab data comes from the two public designs linked above, using their generated frequency response, impedance, CTA, crossover-transfer, and polar outputs.
  • The VituixCAD preference score shown in the shared VituixCAD materials is 8.139, using the VituixCAD default of omitting the low-frequency extension score; LoudspeakerLab's Preference Score is based more closely on Olive standard and includes the low-frequency extension penalty by default, but a "w/ Sub" Preference Score is also calculated which omits the low-frequency extension and produces a result more comparible to the defaul VituixCAD score.
Error cells are median / p95 / max dB over 100 Hz-16 kHz. SPL curves are level-aligned over 300 Hz-1 kHz before acoustic shape comparisons; DI is not level-aligned.

Input Data


Source

Input data

Angular coverage used by LL

VituixCAD

Shared Mechano23 VituixCAD project exports from in-cabinet driver measurements

As exported by VituixCAD

LoudspeakerLab

Same in-cabinet driver measurement family, public LL design

H 10..180 plus signed V -170..180 for both drivers

LoudspeakerLab (spec sheet)

Manufacturer FR/ZMA and sparse manufacturer horizontal polars

H30/H60 only; LL estimates the missing vertical and rear surface

Core Metrics Vs Klippel

This shows the delta (p95 error) between the Klippel data from Amir and the values from VituixCAD, LoudspeakerLab, and LoudspeakerLab using spec sheet. Lower is better on all scored except Preference Rating. p95 error is in dB over 100 Hz-16 kHz after level-aligning SPL curves over 300 Hz-1 kHz. Directivity Index is not level-aligned.


Source

On-Axis
Listening Window
Early Reflections
Sound Power
Predicted In-Room
Directivity Index
Preference Rating (no LF)
VituixCAD
2.04
2.07
2.14
2.22
2.12
1.38
8.148
LoudspeakerLab
1.39
1.34
1.15
1.13
1.05
1.74
8.081
LoudspeakerLab (spec sheet)
3.18
2.34
1.56
2.64
1.62
4.00
7.122

Klippel's VXC-style score from the extracted reference curves is 7.920. The shared VituixCAD materials report 8.139, which is close to the recomputed value from these curves.

Supporting Electrical Checks

Source
Minimum impedance
Impedance p95 vs Klippel
Crossover transfer p95 vs VituixCAD
VituixCAD
4.13 ohm @ 219 Hz
1.56 ohm
reference
LoudspeakerLab
4.13 ohm @ 217 Hz
1.48 ohm
W 0.07 dB / T 0.01 dB
LoudspeakerLab (spec sheet)
1.42 ohm @ 40 Hz
3.08 ohm
W 1.48 dB / T 0.35 dB

Conclusions

1. Modeled speakers can match the real speaker surprisingly well when the input data is good

The in-cabinet models are close enough to the Klippel curves to be useful design tools rather than rough sketches. VituixCAD lands at 2.04 dB p95 on-axis error and 2.07 dB Listening Window p95 error after level alignment. LoudspeakerLab gives lower error at 1.39 dB and 1.34 dB on the same metrics.

The practical takeaway is that robust in-cabinet measurements remain the high-confidence path. They already contain the real baffle, mounting, diffraction, grille-less driver integration, sample variation, and low-frequency loading behavior. The software still has to sum drivers, apply offsets, apply crossover transfer functions, and calculate CTA curves, but it is no longer being asked to invent the loudspeaker from generic driver curves.

One key difference between LoudspeakerLab and similar speaker modeling tools is it's ability to "unload" and "re-load" the box and baffle from measurements if those measurements were taken in a cabinet versus on a large measurement baffle. This cabinet/baffle unload-reload path exists for the core purpose of measurement re-use. An in-cabinet driver measurement is not just the driver; it also contains the measurement box, baffle, mounting, and low-frequency loading. VituixCAD's classic workflow works when those measurements are already from the final cabinet. LL's unload/re-load process makes the same driver profile reusable in other designs by estimating measured in cabinet A -> remove cabinet A/baffle A -> apply cabinet B/baffle B. The higher agreement here is best read as a useful by-product of that architecture, incorporating accurate box and baffle models based on T/S parameters to help estimate anechoic speaker behavior.


2. Why LoudspeakerLab and VituixCAD differ with the same input data

On the directly measured response curves, LoudspeakerLab is lower-error on On-Axis, Listening Window, and Early Reflections, at least for Mechano23. VituixCAD is lower-error on Directivity Index (1.38 dB p95 for VituixCAD versus 1.74 dB for LoudspeakerLab). That is the main place where LL trails in the headline graphic.

I studied this to try to better understand why, since they use the same source measures and crossover, and the strongest clue is the cabinet/baffle ablation. When I used the same LL in-cabinet FRDs directly and by-passed LL's measurement-cabinet/baffle unload and target-cabinet/baffle reload step, the main errors become VituixCAD-like: On-Axis 2.05 dB, Listening Window 2.06 dB, and Early Reflections 2.10 dB. With the normal LL process, those are ~30-40% lower: 1.39, 1.34, and 1.15 dB. That suggests the unload/reload process is likely a real contributor to LL's stronger front-curve agreement in this Mechano23 case.

The electrical transfer overlay is the strongest sanity check: LoudspeakerLab's in-cabinet crossover transfer differs from VituixCAD by only about 0.07 dB p95 on the woofer and 0.01 dB p95 on the tweeter, essentially the same. So it's acoustic modeling, not electrical, that produces this lower error.


3. Spec-sheet modeling is useful, but it is not equivalent to in-cabinet measurement

The spec-sheet model gives a view into the widely accessible speaker design use case. Making in-cabinet spherical measurements requires a lot of expertise, expense, and effort. You have to buy the drivers, build the cabinet, and then actually take the 72 measurements correctly. Alternatively, you could use manufacturer FR/ZMA files or scraped spec sheet data to get sparse manufacturer horizontal polars, then asks LL to predict the cabinet/baffle transformation, vertical behavior, rear radiation, acoustic offsets, and system integration. This is not as accurate as the in-cabinet spherical mesuring process, but the quantification of the gap is interesting. On-Axis p95 error is 3.18 dB, Listening Window is 2.34 dB, and Directivity Index is 4.00 dB, higher, but not unusable to create a high-quality speaker design.

The electrical side points in the same direction. The spec-sheet model's impedance mismatch is much larger than the in-cabinet models, especially in the low-frequency region where box alignment and driver parameters dominate. That is a reminder that manufacturer ZMA/T/S data can be perfectly legitimate for its fixture and still be a poor stand-in for the exact driver/box/crossover combination being built.

That does not make the spec-sheet workflow worthless. It can get a plausible design into the right neighborhood, especially for early crossover exploration and enclosure sizing when no measurements exist. This can be helpful in making driver purchase decision and later making spherical measurements, or accepting the lower accuracy design from spec sheet as final. But this comparison argues against treating it as interchangeable with in-cabinet data. Manufacturer curves are measured on standardized baffles and fixtures, often on different driver samples, with different boundary conditions than the finished speaker. LL can model the transformation, but it cannot recover information that was never present in the input data.


4. The Preference Rating differences are real, but they are not a single-number verdict

The Klippel-derived VXC-equation score is 7.920. VituixCAD computes to 8.148, LL in-cabinet to 8.081, and the spec-sheet LL model to 7.122. Those numbers move because the score is sensitive to smoothness, directivity, and bass extension. A model can be close on on-axis response and still diverge in score if Sound Power, DI, or low-frequency extension shifts.

For DIY design work, the score is best treated as a useful summary statistic, not a substitute for looking at the curves. The score is especially vulnerable when Sound Power and DI are based on reconstructed or sparse angular data. That is exactly the region where this study finds the largest remaining LL/VXC/Klippel disagreement.


5. Where the agreement is strongest in modeled speakers

  • The in-cabinet LL and VXC models both broadly reproduce the real-speaker on-axis and listening-window shape.
  • Electrical impedance for the in-cabinet designs tracks the digitized Klippel impedance shape much better than the spec-sheet design.
  • Crossover transfer functions between LL and VXC are close enough that transfer math is unlikely to be the dominant explanation for acoustic differences.
  • Horizontal polar behavior is much more constrained for the in-cabinet LL design because measured H data extends to 180 degrees.

Bottom Line

If you have good in-cabinet driver measurements, both VituixCAD and LoudspeakerLab can produce a model that is meaningfully close to a real Klippel-measured speaker. If you only have manufacturer data, both tools can also still be useful, but will be limited by the input data. This study says to keep expectations realistic: the spec-sheet path is good for narrowing design space, not for proving final performance. The healthiest conclusion is boring in the best way: better input measurements beat cleverer modeling. The encouraging part is that when the input data is comparable, the output is broadly comparable too.

And here are my Mechano23's. I use them nearfield on my desk everyday. They really are excellent.

unnamed.jpg
 

Attachments

  • h-contour-compare.jpg
    h-contour-compare.jpg
    129.8 KB · Views: 408
  • v-contour-compare.jpg
    v-contour-compare.jpg
    144.4 KB · Views: 410
  • mechano23_ll_share_dataset.zip
    mechano23_ll_share_dataset.zip
    984.2 KB · Views: 29
Last edited:
The VituixCAD preference score shown in the shared VituixCAD materials is 8.139, using the VituixCAD default of omitting the low-frequency extension score; LoudspeakerLab's Preference Score is based more closely on Olive standard and includes the low-frequency extension penalty by default, but a "w/ Sub" Preference Score is also calculated which omits the low-frequency extension and produces a result more comparible to the defaul VituixCAD score.
In VituixCAD you can use the Olive equation by pressing Ctrl plus clicking on "Full space". Doing so with the Mechano23 data from Amirm's review provides a score of 6.079 and using Xmechanik's data 6.398 (likely due to the lower bass extension in Xmechanik's measurements). Kimmo has pointed out that VituixCAD provides a score about 0.3 higher (I have found about 0.5 higher when comparing ASR/Spinorama scores to VituixCAD's) due to different averaging methods and resolution (points per octave (PPO)). ASR/Spinorama Tonality for Mechano23 is 5.5.

Most accurate bass measurement is ground plane if you have the space to do it correctly, but careful farfield + nearfield can be very accurate (especially for a small 2-way) but getting it right takes a good amount of work.
 
Also, for your directivity plots to be comparable, you should change VituixCAD's polar plot to be +/- 180 degrees and set the color profile to Klippel palette.
 
In VituixCAD you can use the Olive equation by pressing Ctrl plus clicking on "Full space". Doing so with the Mechano23 data from Amirm's review provides a score of 6.079 and using Xmechanik's data 6.398 (likely due to the lower bass extension in Xmechanik's measurements). Kimmo has pointed out that VituixCAD provides a score about 0.3 higher (I have found about 0.5 higher when comparing ASR/Spinorama scores to VituixCAD's) due to different averaging methods and resolution (points per octave (PPO)). ASR/Spinorama Tonality for Mechano23 is 5.5.

Most accurate bass measurement is ground plane if you have the space to do it correctly, but careful farfield + nearfield can be very accurate (especially for a small 2-way) but getting it right takes a good amount of work.
Thanks, I did not know you could do that in VituixCAD. The comparable default LoudspeakerLab Preference Rating is 5.8 using Xmechanik's measurements. So, I suppose the LF extension included Preference Rating comparison is:
ASR/Spinorama w/ Klippel data = 5.5
LoudspeakerLab (Xmechanik data) = 5.8
VituixCAD (Xmechanik data) = 6.4
 
Also, for your directivity plots to be comparable, you should change VituixCAD's polar plot to be +/- 180 degrees and set the color profile to Klippel palette.
Yes, I struggled with this a bit. Today, LoudspeakerLab only allows you to view H and V contours +/- 90 degrees, so that's what I set VituixCAD to. But, Amir's original Klippel plots are +/- 180. So you are correct that they all contain +/- 90, but the Klippel image is broader.
 
Yes, I struggled with this a bit. Today, LoudspeakerLab only allows you to view H and V contours +/- 90 degrees, so that's what I set VituixCAD to. But, Amir's original Klippel plots are +/- 180. So you are correct that they all contain +/- 90, but the Klippel image is broader.
I brought it up because a lot of people get confused with the polar settings in VituixCAD. When you right click the mouse on the directivity pane, it gives you choices for +/- 90 degrees and +/- 45 degrees so many people ask how to display the +/- 180. But you just unselect both of those and the default is +/- 180.
 
Yes, I struggled with this a bit. Today, LoudspeakerLab only allows you to view H and V contours +/- 90 degrees, so that's what I set VituixCAD to. But, Amir's original Klippel plots are +/- 180. So you are correct that they all contain +/- 90, but the Klippel image is broader.
This causes a lot of confusion when comparing power and DI charts when the measurement space is not the same. +/- 90 is a half space measurement and should be computed with a 3dB higher overall DI as the DI cannot go below 3dB for a half space condition.

Vituix has an option setting to choose half or quarter space when the measurement set is restricted. Just restricting the polar display to +/-90 does not change anything in the background other than cropping the graph. So it is important to know if the measurement space is the same as if it is not there can not be a valid comparison of Soundpower and DI. If there is only +/-90 data for one available, all the others would need to have their data truncated at source.
 
@fluid, @a4eaudio Great suggestions. I updated the H and V contour comparison to scale Amir's data to just +/- 90 and changed the VituixCAD palette to Klippel so that the three images are more directly visually comparable.
 
This is an expansion of the study I posted in a previous post, but I can't figure out how to edit that post to update it. If this thread can be combined with that one, that's great. Apologies if separating these adds clutter.

This study asks a practical design question: how close should a LoudspeakerLab simulation be to a real, completed speaker when the input data comes from in-cabinet measurements versus ordinary manufacturer spec sheets? The reference target is the completed-speaker Klippel-style measurement for each design.

Mechano23 is the most complete case because it includes Klippel NFS data, VituixCAD exports from the original design thread, and LoudspeakerLab models from both in-cabinet and spec-sheet profiles. Copperhead, Overnight Sensations MT, and Samba MT add Erin's mounted-driver NFS export workflow. C-Note is included as a harder spec-sheet-only reconstruction using the ASR/Spinorama Klippel reference. Together, these examples define realistic accuracy expectations by measurement provenance.

Zero difference is not the right expectation for a DIY loudspeaker. A builder starts with ordinary physical variance from driver samples, break-in, crossover part values, cabinet volume, port effective length, damping, leakage, and measurement setup. The simulation and measurement-provenance errors below should be read on top of that normal build-variance floor.

What Was Compared


DesignCompleted-speaker referenceLoudspeakerLab inputs tested
Mechano23: in-cabinet / spec-sheetASR Klippel NFS reviewGated in-cabinet profiles and manufacturer spec-sheet profiles
Copperhead: mounted / spec-sheetErin review / Spinorama referenceMounted-driver NFS exports and manufacturer PS95-8 data
Overnight Sensations MT: mounted / spec-sheetErin review / Spinorama referenceMounted-driver NFS exports and manufacturer FRD/ZMA profiles
Samba MT: mounted / spec-sheetErin review / Spinorama referenceMounted-driver NFS exports and manufacturer FRD/ZMA profiles
C-Note: spec-sheetASR review / Spinorama referenceManufacturer FRD/ZMA profiles only
CTA error cells below are RMS dB error over 100 Hz-16 kHz after SPL level alignment over 300 Hz-1 kHz. Directivity curves are not level-aligned. Mechano23 is the only study here with structured VituixCAD exports, so VituixCAD is discussed in that section rather than used as a cross-study column.

Accuracy Expectations By Input Data
The most useful result is not a single all-purpose error number. Accuracy tracks input provenance. When the driver data already represents the mounted driver, LoudspeakerLab is generally in the 0.5-1.0 dB RMS range on the main CTA response curves: on-axis, listening window, early reflections, and sound power. With manufacturer/spec-sheet inputs, the model can still be directionally useful, but the expected tolerance is wider. Directivity-index RMS is typically higher than the response-curve RMS because it compares curve shape without SPL level alignment. The heatmap keeps the per-curve RMS view; the provenance chart uses the same on-axis RMS metric so the cross-study comparisons stay consistent.


Reference caseExpected difference vs published referenceHow to use it
Same exact speaker, same measurement path0 dB theoretical limitUseful only as the mathematical ideal. A user-built copy should not be expected to land here.
Careful DIY rebuild from a published design~0.4-0.8 dB RMS through the passbandNormal build variance from driver samples, parts, cabinet execution, mounting, and measurement setup.
Conservative competent DIY rebuild~0.8-1.2 dB RMS through the passbandA result in this range can still be a good real-world match, especially around crossover features.
Bass alignment regionSeveral percent tuning or parameter uncertainty; 1-3 dB local LF differences are plausibleLF agreement should be interpreted with impedance, tuning, damping, leakage, and break-in in mind.
Measured-driver LoudspeakerLab models in this studyObserved ~0.5-1.0 dB RMS on the main CTA response curvesGenerally near the normal DIY variance floor when the source data represents the mounted driver.
Spec-sheet LoudspeakerLab models in this studyObserved ~1-4 dB RMS in the weaker casesAdds a measurement-provenance penalty on top of ordinary build variance.
Gradient heatmap of LoudspeakerLab CTA RMS errors across studies and input provenance

Green means closer to the Klippel reference. Red marks the wider-error region that appears mostly in spec-sheet models.
Observed on-axis RMS error by input measurement provenance

Each dot is one LoudspeakerLab model. The shaded bands show normal DIY build-variance context using the same RMS scale as the tables.
In practical terms, about 0.5-1.0 dB RMS is excellent for a simulated physical loudspeaker because it is in the same scale as ordinary careful-build variation. A 1-2 dB RMS result is still a useful engineering match. A 2-4 dB RMS result is a realistic risk band for spec-sheet models, sparse polars, uncertain cabinet data, or driver curves that do not represent the final mounting.

Normal DIY build-variance floor

The study examples are not interpreted against a zero-error baseline. A competent DIY build with good parts and careful woodworking still has a normal passband variance floor around 0.4-0.8 dB RMS, with 0.8-1.2 dB RMS a reasonable conservative expectation. Local crossover-region differences can be another 0.5-1.5 dB depending on topology, and bass alignment is often better thought of as several percent of tuning or parameter uncertainty, sometimes producing 1-3 dB local LF differences.

Sources: audioXpress two-sample SPL comparison, SB Acoustics T/S and break-in note, Dayton capacitor tolerance example, Dayton inductor tolerance example, Dayton resistor tolerance example, Helmholtz tuning relationship.


Variance sourceWorking expectationHow it affects this study
Driver sample responseExcellent pairs can be within about 0.2-0.5 dB; 0.5-1 dB is a practical good-driver assumption.Mostly controlled when the driver input is a mounted-driver measurement from the same physical speaker; confounded when using generic spec-sheet data.
T/S, break-in, and conditionsFs and compliance-related parameters can move several percent; break-in can shift Fs by roughly 10-15%.Most visible in bass alignment, impedance peaks, and box tuning. This is why LF agreement is judged less rigidly than midband shape.
Crossover partsCommon film capacitors and air-core inductors are often +/-5%; good resistors are often +/-1-2%.Usually a small local acoustic effect, but notches, compensation networks, and high-order crossovers can amplify it.
Cabinet, port, damping, and leakageCareful builds may hold dimensions closely, but effective volume, stuffing, leaks, and port end correction remain real variables.A published design and a user build should not be expected to have identical LF output or impedance unless tuning is verified.
Measurement provenanceMeasured mounted-driver inputs avoid much of the above mismatch; spec sheets add an input-data penalty.The observed study pattern is roughly 0.5-1.0 dB RMS with strong mounted-driver data, versus roughly 1-4 dB RMS in the weaker spec-sheet cases.

The practical error budget should therefore be combined conceptually, not treated as a single number: normal build variance plus simulation mismatch plus any input-data provenance penalty. In this framing, a measured-driver LoudspeakerLab model landing near 0.5-1.0 dB RMS is already close to the expected variance floor of a careful DIY build, while a spec-sheet model landing near 1-4 dB RMS is showing an additional source-data penalty on top of ordinary physical build variation.

Mechano23

Mechano23 remains the best controlled study because it has a completed-speaker Klippel reference, original gated in-cabinet driver measurements, a VituixCAD project/export set, and matching LoudspeakerLab designs. XMechanik's original design materials are in the AudioScienceReview design thread, and Amir's completed-speaker Klippel review is the Mechano23 ASR review.

Sources: ASR design thread and VituixCAD files, ASR Klippel review.

LoudspeakerLab study designs: LL gated in-cabinet design, LL spec-sheet design.

In this case, LoudspeakerLab and VituixCAD both track the Klippel result closely. That is the main point of including VituixCAD: when the input measurements are strong, LoudspeakerLab lands in the same practical accuracy class as the established DIY reference workflow. After tagging the Mechano measured inputs as gated farfield, the current LL run is especially close on the main CTA response curves. Relative to normal DIY build variance, the in-cabinet model is near the expected floor; the spec-sheet model shows a larger input-data penalty. The remaining differences are mostly in acoustic/directivity modeling rather than gross crossover math.

Mechano23 on-axis comparison for Klippel, VituixCAD, LoudspeakerLab, and LoudspeakerLab spec-sheet models


Mechano23 CTA-2034A curve comparison


Mechano23 horizontal and vertical polar directivity slice comparison


Mechano23 impedance comparison


Mechano23 crossover transfer comparison



SourceOn Axis RMSLW RMSER RMSSound Power RMSDI RMSScoreBuild-variance context
VituixCAD0.860.850.941.090.908.148Near the conservative DIY rebuild range; included as the established reference workflow.
LoudspeakerLab gated in-cabinet0.520.490.530.591.148.397Near the careful-build variance floor; same-cabinet measured input controls much of the physical variance.
LoudspeakerLab spec sheet1.421.021.041.672.286.798Above normal build variance on several curves; provenance penalty is visible.
Copperhead
Copperhead is the single-driver anchor case. It uses a Dayton PS95-8 full-range driver with a simple passive network, so the comparison is mostly about whether the input driver data represents the real mounted driver. Erin's review says the completed speaker was measured on the Klippel NFS, then the crossover was disconnected and the mounted driver was exported for simulation.

Sources: Erin's Copperhead review, mounted-driver raw archive, Spinorama Klippel JSON, Parts Express kit page, Parts Express manual, Dayton PS95-8 product data, Loudspeaker Database PS95-8.

LoudspeakerLab study designs: mounted-driver model, spec-sheet model.

Copperhead on-axis comparison for Klippel reference, LoudspeakerLab in-cabinet model, and LoudspeakerLab spec-sheet model



ModelOn Axis RMSLW RMSER RMSSound Power RMSSPDI RMSPPR w/subNotesBuild-variance context
LL mounted-driver NFS export0.590.590.650.751.514.998Excellent agreement outside the lowest box/tuning regionInside or near the normal careful-build range on the main response curves.
LL manufacturer spec sheet2.902.572.182.442.564.760Manufacturer curve does not reproduce the mounted-driver responseFar above normal build variance; this is source-data mismatch, not ordinary builder spread.
The useful lesson is provenance-driven. The mounted-driver NFS export is around 0.6-0.8 dB RMS on the main CTA response curves, while the generic PS95-8 manufacturer data is around 2-3 dB RMS. The same cabinet and passive network do not make those two input datasets equivalent. The mounted-driver result is in the normal careful-build variance range; the spec-sheet result is not.

Overnight Sensations MT
Overnight Sensations adds the first normal two-way crossover problem in this group. It has published cabinet and crossover documentation, plus Erin's mounted-driver NFS export workflow. The mounted-driver model is clearly better than the spec-sheet version and sets a reasonable expectation for a well-matched two-way design: roughly 1 dB RMS on the main CTA response curves.

Sources: Erin's Overnight Sensations review, mounted-driver raw archive, Spinorama Klippel JSON, Paul Carmody design writeup, Parts Express kit page, Parts Express manual, HiVi B4N product data, Dayton ND20FA-6 product data.

LoudspeakerLab study designs: mounted-driver model, spec-sheet model.

Overnight Sensations MT on-axis comparison for Klippel reference, LoudspeakerLab in-cabinet model, and LoudspeakerLab spec-sheet model



ModelOn Axis RMSLW RMSER RMSSound Power RMSSPDI RMSPPR w/subNotesBuild-variance context
LL mounted-driver NFS export0.940.920.960.751.695.773Best available model; about 1 dB RMS on the main CTA response curvesAround the conservative competent-build range, with crossover/directivity uncertainty still visible.
LL manufacturer FRD/ZMA1.711.701.702.312.775.428Low-end and high-frequency behavior remain limited by input provenanceAbove normal build variance; spec-sheet provenance expands the expected tolerance.

The spec-sheet version is not useless; it keeps the broad design in the neighborhood. But it should be read as a lower-confidence prediction. Missing or sparse driver data, version differences, and the lack of real mounted response all show up as extra error versus Klippel. The mounted-driver model is close to a conservative DIY variance budget, while the spec-sheet model adds another visible error source.

Samba MT

Samba is the strongest new positive case. The mounted-driver NFS export model lands very close to the completed-speaker Klippel reference. The spec-sheet version is still useful for qualitative work, but its on-axis error is much higher than the mounted-driver model.

Sources: Erin's Samba MT review, mounted-driver raw archive, Spinorama Klippel JSON, Parts Express kit page, Parts Express manual, Dayton RS180P-4 product data, Dayton RST28F-4 product data.

LoudspeakerLab study designs: mounted-driver model, spec-sheet model.

Samba MT on-axis comparison for Klippel reference, LoudspeakerLab in-cabinet model, and LoudspeakerLab spec-sheet model



ModelOn Axis RMSLW RMSER RMSSound Power RMSSPDI RMSPPR w/subNotesBuild-variance context
LL mounted-driver NFS export0.610.810.630.781.516.633Best scanner-derived two-way result so farNear the careful-build variance floor on several curves.
LL manufacturer FRD/ZMA4.063.382.453.102.346.875Score looks strong, but on-axis shape shows large source-data mismatchOn-axis error is far above normal build variance despite a strong preference score.

This is a good warning about single-number scores. The spec-sheet version has a strong preference score with subwoofer, but its on-axis RMS error is above 4 dB. For accuracy evaluation, the curve agreement and provenance matter more than the score alone. Compared with normal DIY build variance, the mounted-driver result is a realistic engineering match; the spec-sheet on-axis mismatch is much larger than ordinary build spread.

C-Note

C-Note is deliberately included as the harder, more ordinary case: public completed-speaker Klippel data exists, but this study does not have Erin-style mounted-driver NFS exports. The LoudspeakerLab model therefore uses manufacturer driver data, the kit enclosure, and the published crossover topology. That makes it a useful test of what happens when the input data does not already contain the real mounted-driver response.

Sources: ASR C-Note Klippel review, Spinorama Klippel JSON, Parts Express kit page, Parts Express manual, Parts Express PCB manual, Dayton DSA135-8 product data, Dayton ND25FW-4 product data.

LoudspeakerLab study designs: spec-sheet model.

C-Note on-axis comparison for Klippel reference and LoudspeakerLab spec-sheet model



ModelOn Axis RMSLW RMSER RMSSound Power RMSSPDI RMSPPR w/subNotesBuild-variance context
LL manufacturer FRD/ZMA1.791.521.411.762.406.149Spec-only result; useful, but much lower confidence than mounted-driver studiesAbove normal build variance; combines spec-sheet provenance, version/sample uncertainty, and simulation limits.

C-Note shows why spec-sheet simulation should be treated as design guidance rather than proof of final performance. The software can model the enclosure, crossover, baffle, and offset, but it cannot recover sample-specific mounted response that was never present in the input measurements. Its error should be read as a combination of normal physical build variance, unknown sample/version differences, ordinary simulation limits, and the spec-sheet provenance penalty.

Cross-Study Conclusions

1. Accuracy is mostly bounded by measurement provenance
The strongest pattern across all five examples is simple: better input measurements produce tighter agreement with the completed-speaker Klippel reference. Mounted-driver NFS exports and strong in-cabinet measurements consistently support about 0.5-1.0 dB RMS agreement on the main CTA response curves, which is close to the normal variance floor expected from competent DIY construction. Manufacturer/spec-sheet data can be useful, but the expected tolerance is wider because it adds a provenance penalty on top of ordinary build variation.

2. Spec-sheet models are design tools, not final-performance evidence

The spec-sheet studies are not failures; they define the realistic expectation for the common case where only manufacturer curves exist. A spec-sheet simulation can choose drivers, set enclosure size, evaluate crossover direction, and identify obvious problems. But this data set does not support treating it as a substitute for measuring the drivers in the target cabinet. A builder should expect normal DIY variance even from a measured design; spec-sheet input expands that expectation further.

3. VituixCAD comparison is available for Mechano23 only, but it is still useful

Mechano23 shows LoudspeakerLab and VituixCAD in the same broad accuracy class when both start from strong measured input data. VituixCAD is slightly better on directivity index in that comparison, while LoudspeakerLab is slightly better on several CTA response curves. The important conclusion is not that one number settles the tool comparison; it is that both tools are close enough to be useful engineering references when the input data is high quality.

4. Preference scores need curve-level context

The preference rating is useful, especially for comparing finished designs, but it can hide important provenance-driven errors. Samba's spec-sheet model is the clearest example: the score is strong, but the on-axis RMS error is much worse than the mounted-driver model. Accuracy claims should be based on the curves first, with the score used as a summary rather than a verdict.

5. Remaining uncertainty is mostly acoustic, not electrical

Mechano23 is the useful control here: the LoudspeakerLab and VituixCAD crossover-transfer outputs are very close, so the remaining differences are not primarily electrical. At a high level, the uncertainty comes from how completely the input data captures the real acoustic system: mounted response, directivity, low-frequency behavior, sample variation, and exact cabinet/version match.

Bottom Line

LoudspeakerLab can closely track Klippel-measured completed speakers when the source data is strong, especially when mounted-driver NFS or high-quality in-cabinet measurements are available. Based on these examples, a measured-input model landing around 0.5-1.0 dB RMS on the main CTA curves is a realistic good result. A spec-sheet model landing around 1-4 dB RMS can still be useful, but should be treated as a planning estimate until measured.

For current users, the practical recommendation is straightforward: use measured mounted-driver data when possible, treat spec-sheet simulations as directional until verified, and inspect the curves rather than relying on any single score.

And here are my Mechano23s. I use them nearfield on my desk every day. They really are excellent.

Completed Mechano23 speaker build on a desk
 
Last edited:
Most of the text in the newest post doesn't show up on the forums dark theme for whatever reason.
 
Back
Top Bottom