Setting up a remote studio session that actually feels live

For a long time, recording with someone in another city meant booking flights, hauling amps, and praying the airport didn't lose a snare drum. Today the same work happens over a fibre line, a couple of audio interfaces, and a coffee on each end of the call. Still, the gap between "we'll just Zoom it" and "that sounded like we were in the same room" is wider than most people expect. The gear matters, the routing matters, and — especially for musicians working out of Australia — the time zones matter more than anything else.

The past few years have turned what used to be a novelty into a daily workflow at studios like LnL Recording, where vocalists in Footscray dial in from a home booth while a drummer plays in a control room an ocean away. Producers in Brisbane co-write with songwriters in Stockholm, and a folk artist in Hobart lays harmonies over a track tracked in Nashville. None of this is science fiction anymore, but it does reward preparation. A remote session that starts loose usually ends loose, and the artist on the other side of the link can feel every second of hesitation.

This guide walks through the practical steps for setting up a remote studio session that runs on time, sounds right, and leaves both parties with files they can actually use. We will look at platform choice, room prep, time zone planning, talkback and cue mix design, overdub-friendly routing, and the quiet work of wrapping and delivering a session. None of it is glamorous, but every minute spent here saves an hour of frustration later.

Picking the right platform and timing the call

The first decision is whether the session needs real-time monitoring or whether it can run asynchronously. For tracking a lead vocal or guitar solo where the artist plays along with the existing track, you want a low-latency solution: Source-Connect, SessionLinkPRO, Audiomovers, or a hardware unit like TieLink. These tools route audio over a peer-to-peer or studio-grade connection and keep round-trip latency playable. For overdubs where the artist just lays a part without playing in time with anything live, even a stable FaceTime or Zoom call can work, especially with a rough guide mix printed locally for them to track to.

The choice changes a lot of downstream decisions. A real-time link needs dedicated bandwidth, a hard-wired ethernet connection at both ends, and a session operator whose only job is to babysit the connection. A simpler video call lets you record locally at the artist's end, then send WAV files for the producer to drop into the session later. Both are valid; what matters is being honest about what the song needs before the call begins. A soul ballad with stacked harmonies across continents usually wants the real-time option. A podcast interview almost never does.

For Australian collaborators, bandwidth is rarely the bottleneck in capital cities — NBN fibre in Sydney or Melbourne comfortably handles multichannel audio — but regional studios between Cairns and Broome can find upload speeds that bottleneck a full-duplex link. If the artist is recording from a farm in the Yarra Valley or a shed in the Wheatbelt, build in a fallback. Test the link the day before, record a local safety track in parallel, and decide together whether the real-time path is reliable enough for the take.

Australia is the world's largest time-zone anomaly for a musician's calendar. Sydney and Melbourne sit around UTC+10 or +11 with daylight saving, Perth is fixed at UTC+8, and Adelaide drifts in between. A producer in Perth calling a mixer in London chooses between a 6 a.m. local start or a midnight one. A vocalist in Brisbane co-writing with a songwriter in Los Angeles faces a 17-to-19-hour gap, leaving only an hour or two of useful overlap on weekdays. The trick is to anchor every session in writing with explicit local times in both zones and confirm the day before, including any daylight saving shift, because Australia and the United States move their clocks in opposite directions.

Prepping the room, mic, and signal chain

A remote session magnifies every weakness in your room and gain staging. If a room has a 60-cycle hum when nobody is moving, that hum travels through the link and lands in the other artist's ears. If your preamp is clipping two dB hot, the artist will hear it as grit and assume it's the song. Spend a quiet hour before the call walking the room: kill lights on the same circuit as your monitors, swap dodgy XLR cables, and check that your talkback mic is positioned somewhere it won't pick up the click track bleeding from the performer's headphones.

Gain staging matters more remotely because the engineer on the far end has no way to reach over and turn a knob. Set levels so a strong performance sits around -18 dBFS, leave at least 6 dB of headroom, and confirm the headphone feed is loud and clear before tracking. If printing to a DAW like Pro Tools or Logic, set the buffer to 128 samples for tracking and bump to 1024 only for mixing. Extra round-trip latency at higher buffers is enough to throw off a singer's pitch on sustained notes.

It also pays to think about redundancy. Run two simultaneous record paths where you can: the main session at full quality, plus a safety capture on a portable recorder or spare interface. Power supplies fail, ethernet cards drop sync, and the one time you skip the backup will be the time the magic take gets corrupted. A remote session has no "we'll just do another one" the way a local session does, because the other artist may not be available for another eight-hour slot.

Building a talkback and cue mix the remote artist trusts

The single biggest reason remote sessions feel awkward is that the performer cannot hear the engineer the way they would in a real room. Talkback through the DAW gets buried under the click, the engineer's reactions arrive a beat late, and the artist ends up performing into a void. A solid talkback setup fixes this: a dedicated talkback mic routed to the artist's headphones, a footswitch to engage it so the engineer's hands stay on the mouse, and a separate channel for general conversation that bypasses the click track entirely.

The cue mix is the other half of the trust. Give the artist control over their headphone balance rather than dictating it from the control room. A tablet running a custom mix scene lets them pull the vocal up, push the reverb back, or remove the click for an acapella overdub. Send the cue mix in stereo so panning decisions actually mean something; a mono cue mix flattens the spatial cues the brain uses to lock into a groove, and the take will sound stiff even if the player swears they were loose.

Latency compensation between the talkback, the click, and the playback track is fiddly but worth chasing. The artist should hear their own voice in their headphones at the same moment they feel it in their body, and any audible delay throws pitch and timing. Most low-latency platforms offer a "perform" mode that bypasses some processing to keep the round-trip tight; use it. If the platform exposes an offset setting, dial it in by ear with the artist clapping or speaking a rhythm — the alignment point is when the click and the artist's own voice feel like one event rather than two.

Routing for clean overdubs and creative processing

Routing decisions made at the start of a remote session shape everything that comes after. Decide in advance which channels will print flat and which can carry processing, because a vocal track recorded with baked-in reverb is much harder to mix later than a clean dry take with the reverb on a separate bus. Print the dry version by default. Send the artist a rough mix of the existing track with their cue level matched to what they hear in their headphones so there are no surprises about how the song "feels" once the take is in the multitrack.

Creative processing has a place, but usually after the artist has signed off on the performance. If the song calls for pumping drums or a ducking vocal, those moves tend to land better when the artist hears a clean playback of themselves. When demonstrating a processing idea live, even something as textural as sidechain compression for creative effects, build a parallel bus, print the dry take, and let the artist toggle the processed version on and off.

This is also where you decide on session frame rates and timecode references if you are working with picture. Australian commercials and audiobooks often come in at 25 fps for PAL compatibility, while US collaborators will hand you 23.976 or 29.97. Lock the choice early, confirm it in writing, and double-check that the artist's local recording rig is set to match. A mismatch of three seconds per minute will not show up in a waveform preview, but it will absolutely show up when the dialogue editor tries to align to picture.

Wrapping the session and delivering files worth keeping

The end of a remote session is where most projects leak time. The "we'll figure it out later" approach leaves a producer combing through files at midnight trying to figure out which take is the final one and whether the tempo map got nudged. Build a wrap-up routine and stick to it: rename every printed file with song, take number, and a short note from the engineer. Drop the multitrack and a rough bounce into a clearly named folder. Send a follow-up email within an hour confirming what was captured, what is owed, and when the next call is.

Cloud delivery has its own quirks. WeTransfer is fine for a rough bounce under 2 GB, but anything bigger wants a proper studio delivery service: SessionLinkPRO's file transfer, Dropbox with a shared folder, or a hard drive shipped by courier if the project is enormous. Australian collaborators often default to Google Drive because it integrates with their email and works across NBN connections, but be aware of upload caps in regional locations with a quota. Compress the multitrack as a single ZIP or session bundle before sending, not loose files, so nothing gets reordered at the other end.

Finally, document the session in a text file inside the project folder: sample rate, bit depth, tempo, tuning reference, any tempo maps, the artist's preferred cue mix levels, and notes for the mix engineer about which takes to favour. A tidy, well-documented project is one an engineer can pick up cold three weeks later and finish. A scatter of unlabelled files is one that gets re-tracked.

Habits that keep remote sessions healthy

• Lock the platform choice to the song's needs: real-time low-latency tools for live tracking, video or local-record options for overdubs.
• Hard-wire every endpoint and run a parallel local backup recording on every take, including the safety tracks.
• Write every schedule in both time zones, including daylight saving shifts, and confirm the day before each call.
• Give the remote artist real control over their headphone mix and talkback, with latency trimmed as close to zero as the platform allows.
• Print dry takes by default, route processing on parallel busses, and document everything for whoever picks the project up next.