Nine hours over the Atlantic, no signal

Listen instead · voiced on a MacBook Air, offline

In the 1980s, newspaper correspondents carried a small grey slab called the Tandy Model 100. It had a tiny screen, eight lines of text, and roughly nothing else. Reporters loved it with an intensity that later, better laptops never quite earned, and the reason was simple. It worked in a field, in a hotel with no power, in the back of a car. It did not need anything from anybody. When the story was written you found a telephone, clipped the handset into a coupler, and sent it. Until that moment, the machine and the work were entirely yours, and the world could not reach either one.

I thought about that machine a lot somewhere over Greenland, with a script due the following morning and an inflight wifi portal that had been cheerfully failing to load for two hours.

How I got there

The episode was a twenty-two minute narrated piece, roughly nine thousand words of final script, and it was supposed to have been recorded the week before. It was not, for the usual reasons. The plan on the day I flew was the plan every freelancer has made at least once, which is that I would do it on the plane, because nine uninterrupted hours is more focused time than I get in any normal week.

The part of the plan I had not examined was that my usual tool needed a network. Not for anything dramatic. It just sent the text up, generated the audio somewhere else, and sent it back. I had never once thought of that as a dependency, in the same way you do not think of the floor as a dependency.

“You never notice which of your tools are borrowed until you take them somewhere quiet.”Somewhere over Greenland

What the nine hours actually looked like

I had installed Usovo a few weeks earlier and had, honestly, barely used it. The models were already sitting on the disk from that first download, which turned out to be the only piece of foresight in this entire story.

The first pass was structural. I ran the whole script through the small fast model, start to finish, not to keep any of it but to listen to the shape of the thing. That is a habit I had lost without noticing, because on a metered service rendering nine thousand words to check pacing feels like setting money on fire. Here it cost nothing, so I did it four times over the first two hours, rewriting between each pass. Two paragraphs I had been quietly proud of turned out to be unreadable out loud, which is the kind of thing you only ever learn by hearing them.

The second pass was casting. There are three quoted characters in this episode and I had always given them to the same narrator voice with different phrasing, which works in the way that a compromise works. With seventeen voices sitting locally and no per-take cost, I spent a slow hour somewhere past Iceland auditioning them properly. Sebastian for the older of the two quoted engineers, Noor for the researcher, the house narrator for everything else. It took an hour because I could be indecisive, and being indecisive was free.

The final pass was the real render, chapter by chapter into a folder, while I ate a fairly grim tray of pasta and watched the map. The laptop got warm. The battery went down about as fast as it does on a long video call. Nothing else happened, which was the entire point.

We landed at seven in the morning. I filed from the airport on hotel wifi, uploading a finished audio file rather than sending a script off to be processed, which is a distinction I had never had cause to think about before and have thought about a fair amount since.

I am not going to pretend this changed my life. It is a text-to-speech app, and I still do plenty of work with a perfectly good internet connection. But something about that flight rearranged how I think about the tools on my machine. There are the ones that are actually mine, and there are the ones that are a login and a working connection away from being nobody’s. The correspondents with their grey slabs knew which kind theirs was. It took me an ocean to find out.

· · ·