Sound that matters,
written by someone
who builds it.

Written by Darren Smith

Worldray is written by Darren Smith — a working sound engineer with many years across studio mixing, live sound, and broadcast post-production, and a lifelong home cinema enthusiast.

Every product featured is chosen, heard, or evaluated through that lens. The aim is simple: real opinions on real gear, in plain English, from someone who's actually spent time with it. No paid placements. No softened verdicts. If a £15k speaker disappoints, we'll tell you. If a £249 pair surprises us, we'll tell you that too.

The ethos

Three rules sit behind everything published here.

• Independent. No brand sends us gear in exchange for a positive review. No PR pitches drive the editorial calendar. The gear we cover is the gear we’d spec for our own rooms.
• Curated. A short list, not a catalogue. Every review earns its place against real alternatives at the price it actually costs. When we don’t cover a category — centre channels, in-ceiling speakers, two-channel integrated amps — we say so plainly.
• Calibrated. The rooms we test in are treated, the speakers are placed correctly, the AVRs are run through Audyssey or Dirac. Reviews that ignore the room’s contribution are reviewing the wrong system.

How affiliate links work here

Worldray is a participant in the Amazon EU Associates Programme. When you click a Buy on Amazon button on the site and complete a purchase, Amazon may pay us a small commission at no extra cost to you.

That commission funds the writing. It does not influence which products are recommended. The Marantz Cinema 30 is recommended on the Cinema page because it’s the right AVR for that build at that price — not because the affiliate margin on a £4,499 receiver is better than a £499 one. We say so when a cheaper alternative is genuinely the right call.

Get in touch

Questions, corrections, suggestions for products to review, or just a thread to share — write to signal@worldray.com. The inbox is read by Darren personally.

For privacy and data-handling questions, see the privacy policy.