Skip to the main text

Section

In the Room

Six pieces about the part of the work that happens before anything is transmitted: capturing a voice, wiring a room so it can hold a conversation, deciding how loud the result should be, and organising the hours and the rights around it.

A studio is a strange kind of room. It is built to be acoustically boring, wired so that no signal ever arrives back where it started, and run against a clock that was drawn months in advance. None of that is arbitrary. Each convention exists because a specific failure kept happening: a caller hearing their own delayed voice, a jingle that vanished under a song, a station that missed a legal identification, an hour that sounded identical to the previous one.

The order below runs from the physical to the contractual. Microphones and wiring are about electricity and air. Loudness is about measurement and about a ceiling that nobody can raise. The broadcast day and the format are about attention. Licensing is about who owns the two separate copyrights inside every recording, which is the question that stops most podcasts from playing the song they want.

Overhead view of a radio studio desk with a broadcast console, a boom arm holding a large dynamic microphone, closed-back headphones and two screens showing a playout log.
The layout of a self-operated studio: the console within reach of the microphone, the log on screen, and the monitors muted the moment the fader opens.

Pieces in this section

  • How a Remote Viewing Session Is Recorded and Read

    A session record is not a transcript of a voice but a stack of paper: raw notes, sketches, monitor comments, and the later judgments that turned them into data. The piece traces that chain from the first handwritten page to the 1995 evaluation, and it asks what blinding and replication can and cannot settle about a claim. It also argues for keeping the vocabulary and testimony of the earlier communities intact, since the record, not the anecdote, is the unit of study. Readers who want the full account can follow the remote viewing archives for the details.

  • Testing a backup before you need it

    A backup is only as good as its last restore, and a piece on documented digital workflows treats that claim as a procedure rather than a slogan. It separates synchronization from versioning, sets out how to catalogue files on a Mac, and lists the criteria to weigh before any product name enters the conversation. It also covers browser hygiene, a second factor, and the habit of writing the restore test down, since the test itself becomes the documentation when the next failure arrives.

  • The First Hour After a Digital Failure

    A hacked account, a phishing click, a lost phone and a ransomware warning all follow the same clock, and the order of the first hour decides how much is recoverable. The piece lays out first-hour steps after a digital failure for small teams, covering account recovery, what a one-page response plan should hold, and why sequence matters more than speed. It is written for readers who handle this themselves, without a security department on call.

  • What a Memory Test Proves, and What It Does Not

    A memory test, SMART attributes, voltage sensors, and a burn-in run each answer a narrow question, and the piece at the burn-in desk sets out what PC stability diagnosis can and cannot establish. It walks through what a memory test actually proves, how SMART attributes and voltage sensors are read, what a burn-in run establishes and where its limits lie, and how a live diagnostic USB stick is built, closing on where the method ends.

  • PCI Express lanes, LTSSM and the PIPE interface

    A reader who wants to know how a graphics card, a network adapter or a solid state drive actually reaches the processor can start with a plain description of the serial lanes that carry the traffic, the ordered states a link steps through before it is usable, and the logic block that sits between the controller and the electrical signaling. The piece walks through lane counts, link training, the PIPE interface, and the roles of root complex, switches and endpoints, then explains why generation and encoding numbers change the rate at which the PCI Express link moves data.

  • Who gets paid when a record plays

    Composition against sound recording, performing rights organisations against SoundExchange, and the statutory licence that covers streaming but not podcasts.

    14 minute read4 notes

  • The wiring of a room that talks back

    Console buses, the telephone hybrid, mix-minus, the profanity delay, and what happened when the wiring became a network.

    13 minute read3 notes

  • Loudness, and the ceiling nobody can raise

    K-weighting, gating, integrated loudness, true peak, and the ten unit gap between what broadcast asks for and what streaming platforms normalise to.

    14 minute read4 notes

  • Microphones, and the six inches that decide everything

    Dynamic against condenser, polar patterns, proximity effect, the inverse square law, and why the room usually matters more than the microphone.

    12 minute read3 notes

  • A format is a promise about the next song

    Rotation categories, separation rules, imaging, burn, and the research methods that decide when a song leaves the list.

    12 minute read3 notes

  • The shape of a broadcast day

    Dayparts, the hour clock, the stopset, the legal identification, and the ratings vocabulary that explains why the clock looks the way it does.

    13 minute read4 notes

The other section

The other section : In the Room: microphones, wiring, loudness and the working day
  • On Air

    Four pieces on the transmitted side: FM baseband, the AM band after sunset, coverage limits and emergency alerting.

  • Glossary

    Every term used in these six pieces, defined briefly, with a link back to the piece that explains it in full.