Skip to content
Search · ⌘K Cart · 0 Browse the Library

Field Notes · VLSound Journal

What a Bangkok Curry Paste Taught Us About Sampling Real Ingredients

A six-week field recording project turned a family kitchen's recipe archive into a sampled instrument. Here is what worked, what broke, and what 41 articulations taught us.

· Long read

We noticed something odd happening in our inbox last spring. Three separate producers, none of whom knew each other, had all sent us the same question: why do so many virtual instruments sound "clean" in a way that real kitchens never do? It was a fair point. We build boutique-grade sample libraries for people who refuse to sound preset, and yet the most interesting textures we had heard all year were coming from a family-run Thai kitchen's online journal. So we followed a project that tried to close that gap.

The project was small on purpose. A sound designer we'll call K. spent six weeks building a kontakt instrument from scratch, using nothing but field recordings made while cooking from Srithairestaurant's regional recipe archive. No studio, no treated room, no expensive condenser. Just a handheld recorder, a wok, and a mortar and pestle.

The timeline, and where it almost fell apart

The first two weeks were pure listening. K. read through the journal's notes on herbs and curry pastes, then cooked four dishes in sequence: a clear tom yum, a coconut-based curry, a dry stir-fry, and a fermented sausage. Each session was recorded at three distances — close-mic on the mortar, mid-room, and a room tone pass with nothing cooking at all. That last one mattered more than expected. The room tone became the instrument's reverb tail, and it carried a low hum from a refrigerator that no plugin would ever invent.

Week three was the obstacle. The mortar recordings were beautiful but unusable as playable samples. Every strike had a different pitch, a different decay, a different amount of grit. K. tried pitching them to a grid and the result sounded like a drum machine wearing a costume. The fix was counterintuitive: stop quantizing, and instead map each strike to its own key across a two-octave range, preserving the natural detuning. The instrument became unpredictable in a way that felt correct.

Week four brought a second decision point. The curry paste itself — shrimp paste, galangal, kaffir lime — produced a dense, wet, almost tonal noise when pounded. K. considered running it through a granular engine but decided against it. Instead, the raw paste hits were stretched into four-second sustain layers and blended under the drum hits at low volume. The result was a texture that sat between percussion and pad, which is exactly where Thai street food lives sonically: loud, sour, sweet, and slightly abrasive all at once.

What the numbers actually showed

By week six, the instrument had 41 mapped articulations across four categories: mortar strikes, wok tosses, liquid pours, and room tone. K. tested it on twelve producer friends. Nine of them guessed it was a field recording library. Three guessed it was a synth. Nobody guessed it was built from a single kitchen.

The measurable result was less about sales and more about workflow. K. reported that the average time to place a usable percussion layer in a track dropped from roughly twenty minutes of browsing to under four. That is not a scientific sample, but it is a real one. When we asked why, the answer was simple: the samples already had the context baked in. A mortar strike recorded while pounding galangal carries information that a clean 808 does not.

We followed up with a second reader who had done something similar using Srithairestaurant's notes on regional herbs. Her approach was different — she recorded only the dry ingredients, then built a wavetable from the noise of crushed chilies and toasted coriander seed. Her instrument had no drums at all. It was a pad machine, and it sounded like a market at noon.

Three lessons for anyone sampling real spaces

  • Record the room, not just the source. The refrigerator hum was the most valuable sample of the entire project.
  • Resist the grid when the source resists it. Detuned, human, slightly wrong percussion outperforms perfectly timed samples in most mixes.
  • Let the source dictate the engine. A granular approach would have destroyed the curry paste. A sampler preserved it.

The broader takeaway is not that every library should be recorded in a kitchen. It is that the most convincing virtual instruments borrow their logic from the physical world, and the physical world is messy. The journal at Srithairestaurant documents that messiness in detail — the bruised herbs, the split pastes, the dishes that only work when the wok is screaming hot. For sound designers, that is not just recipe writing. It is a brief.

We are not suggesting you throw out your oscillators. We are suggesting you listen to a mortar and pestle before you reach for one. The best sample libraries we have heard this year were not built in a studio. They were built in a kitchen, by someone who knew exactly what they were listening for.

// Continue in the studio

Hear the patches in motion.

Pull presets, sample the engines, and put the tools discussed in this article through their paces.