-
Notifications
You must be signed in to change notification settings - Fork 2
DEADBEEF Presets
0xDEADBEEF is a magic number. Programmers use it to poison uninitialized memory — when your process allocates a chunk of RAM and fills it with 0xDEADBEEF before use, any code that accidentally reads it before writing gets back something obviously wrong. Not zero. Not garbage. A recognizable corpse. Dead beef.
I built iQualize — a native macOS system-wide parametric EQ — and I had a free afternoon. So I asked myself: what does 0xDEADBEEF sound like?
The hex value splits cleanly into two halves: 0xDEAD and 0xBEEF. That suggested two distinct presets with two distinct personalities.
DEADBEEF takes the split literally. 0xDEAD (57,005 decimal) owns the low end — I bit-shifted it down into the audible range and used those frequencies as the bass foundation. 0xBEEF (48,879 decimal) takes the top — its shifted values land in the presence and air zone, narrow and aggressive. The mid range between them is scooped hard. The result is exactly what the name implies: dead weight at the bottom, beef at the top, a void in between.
0xDEADBEEF is where it gets deranged.
Every single band frequency is a mathematically derived bit-shift of either 0xDEAD or 0xBEEF. No frequency was chosen by ear. The logic is simple: right-shift each half-word down through the audible spectrum in octave steps. 0xDEAD >> 10 lands at 55 Hz. 0xDEAD >> 9 lands at 111 Hz. 0xDEAD >> 8 at 222 Hz. All the way up to 0xDEAD >> 2 at 14,251 Hz. Same for 0xBEEF. That gives you 20 frequencies across the full spectrum, two per octave, one from each half-word — and they sit just a few dozen Hz apart at every step.
So I made the 0xDEAD shifts boosts (the surviving signal) and the 0xBEEF shifts narrow notch cuts sitting just below each boost (the poisoned addresses, the corrupt memory). They fight each other at every octave across the entire frequency range.
The curve in iQualize looks like a seismograph reading from a building collapse.
0xDEAD = 57005
0xDEAD >> 11 = 27 Hz 0xBEEF >> 11 = 23 Hz
0xDEAD >> 10 = 55 Hz 0xBEEF >> 10 = 47 Hz
0xDEAD >> 9 = 111 Hz 0xBEEF >> 9 = 95 Hz
0xDEAD >> 8 = 222 Hz 0xBEEF >> 8 = 190 Hz
0xDEAD >> 7 = 445 Hz 0xBEEF >> 7 = 381 Hz
0xDEAD >> 6 = 890 Hz 0xBEEF >> 6 = 763 Hz
0xDEAD >> 5 = 1781 Hz 0xBEEF >> 5 = 1527 Hz
0xDEAD >> 4 = 3562 Hz 0xBEEF >> 4 = 3054 Hz
0xDEAD >> 3 = 7125 Hz 0xBEEF >> 3 = 6109 Hz
0xDEAD >> 2 = 14251 Hz 0xBEEF >> 2 = 12219 Hz
Twenty bands. Fully deterministic. Zero taste involved.
Honestly — both go in the same direction. Same dark techno character, same general shape. The experiment worked, just not in the dramatic way I expected.
0xDEADBEEF sounds flatter. The alternating boost/notch pairs across every octave cancel out some of the depth and warmth. It's not corrupted memory chaos — it's more like a less resolved version of its sibling. The high end doesn't round off the same way. Less dimensional.
DEADBEEF is the better preset. Fuller low bass range, deeper sub, more width in the bottom end. Where 0xDEADBEEF feels flat and clinical, DEADBEEF feels like a room. The two-personality structure — dead weight in the sub, beef in the presence — actually translates to something that sounds intentional rather than derived.
So the conclusion is a bit anticlimactic: the pure math experiment produced a working preset, but the one where I applied actual judgment to the hex concept sounds better. DEADBEEF is just the optimized, fine-tuned version of the same idea. The gimmick is real but the ear still wins.
Both presets ship as built-in presets in iQualize and as downloadable .iqpreset files.
iQualize is a native macOS system-wide parametric EQ — no virtual audio driver, no kernel extensions. Built in Swift using Core Audio Taps. Download on GitHub →
"I build tools that shouldn't need to exist."
iQualize Wiki