Treat the ten hour gap as two shifts on one record. The artist tracks during the Kyiv day, I produce and mix during the Burbank day, and the session changes hands twice every twenty-four hours at fixed times. I composed and produced Stefania for Kalush Orchestra, and a large share of my current production work still happens with artists and writers who record in Ukraine while I sit in my Burbank room. The records that move fastest are the ones where nobody waits for anybody, and that takes rules, not enthusiasm.
What does the ten hour gap actually do to a schedule?
Kyiv runs on Eastern European Time, UTC+2 in winter and UTC+3 in summer. Burbank runs on Pacific Time, UTC-8 and UTC-7. The result is a ten hour offset almost all year, with a short nine or eleven hour wobble in the weeks when the two countries change their clocks on different dates.
The only live window that works for both sides without anyone suffering is my 8:00 to 10:00 in the morning, which is 18:00 to 20:00 in Kyiv. Every call, every attended playback and every argument about a chorus happens inside those two hours. Everything else is asynchronous by design. The handoff rhythm looks like this: the artist finishes a vocal session by Kyiv midnight and uploads, the files are waiting when I sit down at 9:00, I work the Burbank day and bounce by my evening, and the new version is waiting when Kyiv wakes up. Two handoffs a day, every day. A song in production this way gets roughly sixteen working hours per calendar day, which is the one real advantage a split-continent record has over a local one, and the entire job is not losing that advantage to sloppy handoffs.
What file rules stop a remote session from falling apart?
Every delivery is consolidated audio: each track exported as a WAV from bar 1 to the end, at the session rate, 48 kHz and 24 bit on my current productions, so the files line up by dropping them at zero. The tempo map rides along as a MIDI file, and the delivery note names the key and the sample rate in plain text. Project files travel too, but only as a backup, because the other room never has the same plugin list and a session that opens with twelve missing inserts is a support ticket, not a handoff.
Each package carries a manifest with an MD5 checksum per file. That sounds bureaucratic until the first time a 400 MB upload silently truncates over hotel wifi and a verse prints with a click in it three days later. Checking hashes takes a minute and has caught real corruption on my sessions more than once.
Version names are boring on purpose: song title, v number, date. Nothing is ever called final. The versioning and recall discipline is the same one I use locally, written up in session versioning that survives a recall, and the folder that travels is prepared exactly like the one in how I prepare a mix folder.
How does a review loop work when nobody shares a room?
One bounce per day in each direction, leveled. Review versions go out loudness-matched to the previous version, because a bounce that arrives 2 dB hotter wins the comparison for reasons that have nothing to do with the arrangement, and at a distance nobody can lean over and say so. The chat gets a 320 kbps MP3 for instant listening on a phone; the folder gets the full WAV, and approvals only ever point at the WAV by its version name.
Notes come back as one numbered list per version: timecode, element, problem. "2:14, backing vocals, the word is unreadable" is a note I can act on at 9:00 without a call. "Make the chorus bigger" at a ten hour offset costs a day, because the clarifying question and its answer each wait overnight. For the moments that genuinely need ears in both rooms at once, a verse comp, a tuning call on a borderline take, I run an attended pass inside the overlap window with the session streaming and decisions logged in the same numbered format, the remote version of the attended sessions I described in what an attended mix session is for.
What changes when the song is Ukrainian and the team is split?
The language work has to be front-loaded, because the person tracking the vocal and the person judging it are no longer in the same room. Before a Kyiv vocal session I send back a marked lyric sheet: stress marks on every line, the consonant clusters flagged, and reference syllables for the spots where the melody fights the word stress. Catching a stressed syllable on the wrong note costs one overnight round trip to fix remotely, so it gets caught on paper instead. The mix side of the same problem, the sibilants and the six vowels that keep their color, is its own subject, covered in how I mix a Ukrainian vocal for a global audience.
Release logistics also read differently across the gap. A release that goes live Friday morning Kyiv time is still Thursday evening in Burbank, which has caught more than one team off guard on delivery deadlines. I put every deadline in both time zones in the project note, written out in full, because "Friday" is not a date when a record lives in two of them.
What goes wrong most often?
Unanswered questions, not bad audio. A single question asked outside the overlap window waits ten hours for an answer, so every message carries all of its questions at once, numbered, ordered so the answer to the first one does not change the rest. Second, the clock-change weeks, when a 18:00 Kyiv call quietly becomes 17:00 or 19:00 for me; the calendar invite in UTC fixes that. Third, trust in the upload bar: a transfer that says 100 percent is not verified until the hashes match. None of these are audio problems. The audio has been the easy part since the files started lining up at bar 1.
Frequently asked
What is the time difference between Kyiv and Los Angeles? Ten hours for most of the year. Kyiv sits at UTC+2 with summer time at UTC+3, Los Angeles at UTC-8 with daylight time at UTC-7. For a few weeks each spring and autumn the two countries switch their clocks on different dates and the gap briefly becomes nine or eleven hours, which is worth checking before booking a call.
What audio files should a remote session exchange? Consolidated WAV files, every track exported from bar 1 at the session's sample rate and bit depth, plus the tempo map and a note naming the key. Project files travel as a backup, never as the only source, because plugin mismatches break them on the other end.
How do you give mix notes remotely? In one numbered list per version, each note carrying a timecode, the element, and the problem rather than a prescription. One list per version keeps the record moving; notes that arrive one message at a time cost a full day each at a ten hour offset.
If your team is split between Europe and Los Angeles
Send me the current session and the way you are exchanging files today. I will send back an audit of the handoff: the file spec, the version scheme, the overlap window for your two cities, and the first three things that will fail if nothing changes. Credits are at /credits, background at /about.