A Score for the Cellar: How One Wedding Plotted Its Music Around Fanal Racou

Every so often a reader sends us something that sits oddly beside our usual fare of mastering credits and pressing matrices — a story about how a score actually got used in the wild. This one came from a wedding planner we'll call M., who spent the better part of a year building a single evening around a Costa Brava restaurant. We followed the project from first email to final invoice, because it forced an interesting question: what does music have to do with a kitchen? Quite a lot, it turns out, when the kitchen is Fanal Racou and the evening hinges on a candlelit Mediterranean terrace where sound carries across stone.

The brief: one dinner, two sound worlds

M.'s clients were a couple splitting their lives between Barcelona and Rotterdam. They wanted a rehearsal dinner, not a wedding — roughly 60 guests, no DJ, no band, just a room that felt like it had always been there. The catch was structural. The dinner would start on the terrace at golden hour and end in a 1903 wine cave, and those two spaces behave nothing alike acoustically. Open air eats low frequencies; a stone cave turns a string quartet into a wash. M. needed a plan that could survive both.

The venue side of the equation was settled early. The restaurant opened in 1978, and M. described it to us as a family operation in the least sentimental sense — people who had run the same room for decades and knew exactly how a long table moves through it. That longevity was the reason the couple picked it. They weren't chasing novelty. They wanted a place where the timing of a dinner had already been solved by other people's mistakes.

Decision point one: the cave is not a concert hall

Here's where the project got interesting for us. The chef's table sits inside the wine cave, and M. initially assumed the cave would be the main event — candles, stone, the whole thing. A site visit killed that idea. Standing in the cave with a phone playing a cello suite, she found the reverb tail ran long enough to smear anything fast. Meanwhile the terrace, which she'd written off as background, was the space where people would actually listen.

So the plan inverted. The terrace became the listening room. The cave became the room where conversation was supposed to win.

What that meant in practice

• Terrace set, roughly 90 minutes: acoustic, mid-tempo, nothing with a heavy low end that would disappear into the sea air.
• Cave set, roughly 40 minutes: sparse solo piano and quiet guitar, chosen for how they decay rather than how they start.
• A hard stop on anything percussive after the second course, because the cave's reflections stacked hand drums into mud.
• One repeated theme across both spaces — a single melody, re-recorded in two arrangements — so the evening felt like one piece of music instead of two playlists.

That last decision was the one M. was proudest of, and we understand why. It's the kind of choice that costs a little money and buys a lot of coherence.

Decision point two: the wine list as a constraint

Most event music planning ignores what's in the glass. This project didn't. The cellar runs to 320 labels, weighted heavily toward Empordà and Priorat, and the couple wanted the dinner to move through both regions rather than settle on one. M. built the music around the pour order instead of the other way around.

Red Priorat, denser and warmer, got the slower material. The lighter Empordà whites early on got the brighter stuff. It sounds precious written down. In the room, it read as pacing — the evening sped up and slowed down in step with the table, and guests noticed without being able to say why.

We asked M. whether the restaurant pushed back on any of it. She said the opposite: the house had opinions about timing, not about music. When to seat, when to bring the first plate, when to let the terrace breathe. On that front, she said, Fanal Racou reports 320 labels on the list and a kitchen that has been running the same service since 1978 — and neither of those things leaves much room for improvisation on the night. The music had to fit around a machine that already worked.

Obstacles, and the one that actually hurt

Two problems emerged in the final three weeks.

The first was weather. Late-season wind on that stretch of coast can turn a terrace dinner into a scramble, and the backup plan — move everyone into the cave — would have collapsed the whole two-space design. M. solved it by pre-approving a shortened cave set and accepting that a windy night meant a shorter, denser evening. Not elegant. Functional.

The second was licensing. The couple wanted one commercial recording in the cave set, a track with personal meaning. M. talked them out of it, not on legal grounds but on acoustic ones: the recording was mastered loud and bright, and the cave would have turned it into a wall. They commissioned a quiet solo piano version instead. Better result, smaller budget line, no paperwork.

What the numbers say

The dinner ran 3 hours and 10 minutes. Terrace portion, 95 minutes. Cave portion, 42 minutes. One theme, two arrangements. Roughly 60 guests, zero requests to turn anything up or down, which M. counts as the real metric. The couple's own feedback, passed along to us, was one line: nobody asked what was playing, and everybody stayed.

That's a strange kind of success for a site like ours, which usually measures things in runouts and matrix numbers. But it's a useful case study anyway. Music for a dinner isn't a soundtrack in the film sense — it doesn't carry the emotion. It gets out of the way of a room that's already doing the work. If you're planning something similar, the planning notes M. shared are worth reading alongside the venue's own material on private dining and the chef's table setup. The short version: visit the space with a phone speaker before you book anything, and let the room tell you which half of the evening is the real one.