Skip to content
Idle Foundry markIdle Foundry
Menu

Listening comparison

CA-72 vs. MODEL D

Recorded Behringer MODEL D hardware next to the released CA-72 0.2.8 and CA-72 0.3.0. Same patch, same notes, 37 examples. Pick any two, switch between them at the same moment and compare the measurements.

These recordings use the 0.2.8 and 0.3.0 releases. Download links lead to the latest release.

Triangle

Oscillator 1 alone, triangle wave, one held A. · 2.0 s

Either side can also be the 0.3.0 build at another QUALITY: the same settings and notes with only QUALITY changed. HI is the 0.3.0 clip itself. Not level-matched: every QUALITY plays at the 0.3.0 clip’s gain. Every QUALITY is measured and graphed on its own.

0:00.0 / 0:02.0

1 or A, 2 or B switch between them at the same moment · Space play or pause

Graphs

Loading graphs…
  • A · MODEL D hardware
  • B · CA-72 0.3.0, QUALITY HI

Hover or touch a graph for values. Drag across it with a mouse, or use + and −, to zoom; double-click to reset.

MODEL D settings
The Behringer MODEL D panel as set for “Triangle”

The panel as recorded for this example.

CA-72 settings
The CA-72 panel with the saved settings for “Triangle”

Download these settings (.toml) · saved with 0.3.0’s development build; 0.2.8 was rendered with the same control values.

Levels, measurements and provenance for this example
Playback gain relative to the hardware
0.2.8 +5.90 dB · 0.3.0 +5.91 dB
Level and timing
Fixed active-note RMS matching; 2 s playback, about 50 ms lead. PCM24; fixed gain and timing only.

Provenance for this example (gains, crops, checksums and build identities) · Hardware audio (FLAC) · 0.2.8 audio (FLAC) · 0.3.0 audio (FLAC)

Method

How these were made

The three sources

MODEL D hardware
A Behringer MODEL D, recorded at 48 kHz and 24 bits through an audio interface. Each patch was set by hand, photographed, and played from MIDI with timed notes. Its own background noise is left as recorded.
CA-72 0.2.8
The public 0.2.8 release, the unmodified plug-in binary, rendered offline with the same saved control values as 0.3.0. It was not fitted to the recordings separately, so it shows where the release stands with these settings, not its best possible match.
CA-72 0.3.0
The public 0.3.0 release, whose oscillator waveforms were calibrated against this hardware. For each example its front-panel controls were adjusted to match the recording, then the settings were saved; the audio is an offline render of exactly those settings, and the screenshot is the plug-in showing them. ENTROPY, CA-72’s per-note variation, is off in every example. The clips were rendered from 0.3.0’s development commits before its release; the released plug-in, rendering the same saved settings, reproduces every one of them, at every QUALITY, sample for sample.

What was done to the audio

Each source has one fixed playback gain, chosen so the notes play at the same loudness, and one fixed start point, so the notes line up. That is all: no EQ, filtering, compression, pitch correction or time stretching. Every clip is mono and plays centred. The CA-72 renders its two output channels, which are averaged. The files here are lossless FLAC and decode to exactly the published samples. Each example’s gains, start points and checksums are listed under its “Levels, measurements and provenance”. In the four feedback examples, the gain is set from the two lower notes only.

Every example can also be heard at each of CA-72’s QUALITY settings, LO, HI and ULTRA, from the same saved settings with only QUALITY changed. The 0.3.0 clip is the one the example was matched at: HI, or ULTRA for feedback. The other two keep its crop and gain, so any change in level is heard as rendered.

The two-oscillator bass and the detuned lead have one addition. Like the hardware’s, their two oscillators run freely and drift in and out of phase, so the sound swells and changes colour from note to note. Their starting phase can’t be set, so each CA-72 render starts a moment early (4.25 s for the bass, 0.23 s for the lead), which lines its beating up with the recording’s. That lead-in is cut off and never heard. The glide example uses a similar silent lead-in, so that CA-72 starts from the same remembered pitch as the hardware. Both examples are their six-note phrases; the separate held notes recorded for measurement aren’t published.

The comparison clips here have nothing added. The blind test uses separate copies in which recorded hardware noise is added to the CA-72 side, so that the quiet background at the start and end of a clip can’t identify it. To hear the instruments as they are, listen here.

What the graphs show

The graphs are measured from these same playback files. Depending on the example they show the spectrum, the level over time, individual harmonics, pitch, a short stretch of waveform, or the spectral peak through a filter sweep. They show the two sources being compared. Hollow points mark values too close to the noise to trust.

Where they still differ

  • The filter and envelopes are close but not identical, and the difference grows with emphasis. It is clearest in the 30-second sweep at emphasis 10.
  • The oscillators run freely on both instruments, so beating between them and the waveform phases are not the same from one recording to another.
  • At high resonance, some pitch estimates late in a held note are unresolved, because the filter’s own ringing competes with the oscillator.
  • With one glide setting, the shape of the glide and the octave tracking differ slightly from the hardware.
  • In the detuned lead, the hardware’s second oscillator tracks the keyboard slightly less steeply than its first, so their beat slows a little on higher notes. CA-72 has one detune for both, set to suit the phrase as a whole.
  • The feedback examples play A, where both loops lock to a tone near 55 Hz. On some other notes, such as C and D, the hardware’s loop pulls to a fraction of the played note while CA-72’s stays near 55 Hz, so they sound further apart.
  • Released 0.2.8 shares 0.3.0’s control values rather than being fitted on its own, so some of its differences come from settings, not only from the engine.

We don’t reduce these comparisons to a similarity score. Listen, and look at the measurements.

Build and measurement details
Released 0.2.8
CLAP plug-in, SHA-256 ade13d59bf3b7395868f79d77e27c6d5f3ba25571509bbc96c813c6389bfcaae, rendered by an offline host; every supported control was read back after loading. Controls added after 0.2.8 were left inactive.
Released 0.3.0
Tag v0.3.0, commit edcefbb. The macOS installer (SHA-256 743aea94305bb55d89336dd475b444ad5ceb493e97ca163c9ccee3d54a268ffb) is signed by Idle Foundry Ltd. and notarised; its CLAP plug-in (SHA-256 64c7e59c11f6940717d97ac79d5d72302ef3d5cb91eefc550bfa7bd23209a41d) was rendered by the same offline host as 0.2.8, at each example’s saved settings and seed and at QUALITY ULTRA, HI and LO. All 111 renders equal the published clips at 24 bits. Controls added after these settings were saved were left at their defaults.
0.3.0 development renders
All but the feedback examples: commit c49624d, engine source SHA-256 da7fecdfeb020a33cda010359386aa3cb0f84b44d67a6ce87b70aede333b10e8, rendered offline by its renderer (SHA-256 320b0942625c0cac9744951da034c8d3ee1def75eaad47ee2642aba7d0a1dc56). Waveform selections are the fixed hardware positions and ENTROPY is 0. Each saved preset was reloaded and re-rendered to identical audio before publication. The screenshots come from a macOS build of the same commit, taken only after its live settings matched the render’s.
0.3.0 development renders, feedback
A later commit on the same branch, 762f83f, which models the feedback loop’s preamplifier as the hardware runs it. Engine source SHA-256 7992575dc6878885990060d8831ee400c3bcb59eb1573c02ea41a7605cd071a6. These four render with QUALITY at ULTRA, CA-72’s most exact setting, and ENTROPY 0, on A1, A2 and A3. They come from a macOS build of the commit (renderer SHA-256 b42e3765043b8e78d70a3e9dba5ba766fc5e8568f4c5fc75dad7b677f15018ba), which reproduced the fitted renders bit for bit and took the screenshots.
Recording
48 kHz, 24-bit, from the MODEL D’s output into one interface input. The notes were timed against the interface clock. Levels are compared relative to the hardware recording, so absolute volume settings don’t affect the comparison.
Photos
Each MODEL D photo is the camera original taken for that recording, levelled (by up to 3°) and cropped to the panel. Nothing else is retouched.
Verification
Every clip’s checksum was matched against the session’s audits before encoding, and every FLAC was decoded and compared sample for sample. Verification summary.

MODEL D is a Behringer product. Idle Foundry is not affiliated with Behringer.