The first thing I usually hear from a host in Anchorage is not about cameras or intros or thumbnails at all, it is about a guest, somebody calling in from a village, a fishing camp, a remote job site or a lodge a long way off the road system, and the audio from that guest arrived sounding like it was recorded inside a tin can, with a dropout every few minutes and a generator humming underneath it, and the host wants to know, very simply, can any of this be saved.
Most of the time the honest answer is that a lot more can be saved than people expect, and some of it cannot, and the real skill is knowing the difference before you promise anything, right, because the worst thing an editor can do with a remote guest is polish the bad audio until it sounds strange and robotic, which is somehow worse than the original.
Who in Anchorage is hosting podcasts, and what are they about?
Mostly people who work in aviation, air cargo, logistics and the outdoors, because Anchorage sits at the centre of how goods and people move through the North, and those people have real operational knowledge worth recording.
Ted Stevens Anchorage International Airport is one of the busiest air cargo airports in the world, and that means the city is full of people who understand freight, pilots, dispatchers, ground operations people, freight forwarders, maintenance crews and the business owners who supply all of them, and when people like that start a show it tends to be practical, technical and full of stories you will not hear anywhere else. Then there is the outdoor world, guides, outfitters, mushers and the people who build businesses around the Chugach Mountains rising right behind the city, and every March the Iditarod sled dog race starts ceremonially in Anchorage, so dog mushing and the culture around it is a genuine local subject and not just a postcard.
What ties these shows together, basically, right, is the guest list. A logistics host wants a dispatcher who is out on a route, an aviation host wants a bush pilot who lives somewhere remote, an outdoor host wants a guide who is calling from the end of a long valley, and so the remote guest is not an occasional problem for an Anchorage show, it is the format.
Why does audio from remote Alaska guests sound so rough?
It sounds rough because many Alaska communities rely on slower internet connections, and live call audio is compressed hard and drops packets whenever the connection struggles.
When a guest joins over a normal video call, the software is constantly making trade-offs to keep the conversation going in real time, so it squeezes the voice, smears the high end, and when the connection hiccups it simply loses a fragment of speech and carries on. That is fine for a meeting, right, but for a podcast it means the recording you have is only as good as the worst moment of the connection. On top of that, remote guests are often in loud rooms, and the thing is, right, they are usually on a laptop microphone a metre away from their mouth.
The single biggest improvement you can make before it ever reaches us is to have each person record on their own device and upload afterwards, which is what tools built for remote recording, like Riverside, are designed around, because then the slow connection only affects the live conversation and not the file. Even then, pushing a big file up from a slow line can take hours, and that is genuinely fine, our shared folder accepts files of any size, so a guest at a lodge can start the upload before bed and the full-quality recording is there in the morning.
How much of a rough recording can actually be rescued?
A surprising amount, background hum, uneven levels, room echo and harsh compression can usually be reduced a lot, but words that were never recorded because the connection dropped cannot be invented back.
This is where I want to be really really clear, because it is where hosts get burned. Our podcast audio cleanup work is about making a voice clear and even and pleasant to listen to, levelling the host and the guest so nobody is reaching for the volume button, reducing noise, taming the echo, and making the remote guest sit comfortably next to a host who recorded on a good microphone in a quiet room. What it cannot do is recover a sentence that the internet ate, and I would rather tell you that on the first call than send you a cut that pretends.
I would rather tell a host what cannot be saved than hand back a guest who sounds like a robot.
So what we do with the gaps, when there are gaps, is make an editing decision, a human one. Sometimes the guest repeated the point a moment later and we can cut to the clean version. Sometimes the host can record a short line in the studio that bridges it. Sometimes the right answer is a small on-screen caption for the missing phrase so a viewer can follow along. And sometimes the answer is that a two minute stretch goes, because it was not adding anything anyway. A silence detector cannot make a single one of those calls, and that is exactly why, at Pixel Samy Podcast, the person editing your episode hears it from the first second to the last before making any cut.
What does our process look like for a show with remote guests?
Nothing about the basic rhythm changes because the guest was on a bad line, every source file goes into the folder, a first cut shows up forty-eight hours on, your notes go back in a single batch, and the fixes are done one working day later.
The difference for a remote guest show is that the cleanup happens inside step three, right, not as a separate project you have to commission and wait for.
For the mastering part, we work toward the loudness that platforms ask for, and Apple publishes its audio requirements for podcasts, recommending an overall loudness of around minus 16 LKFS with a true peak no higher than minus 1 dB FS, which is roughly the target we keep in mind so your rescued guest does not suddenly jump out louder or quieter than the rest of the feed. Every step is written out on how it works, and the one exception I will flag before you upload is an unusually long episode, a heavily illustrated one or a four-camera shoot, which can need a day more than normal, whereas a rough guest track on its own does not.
Is it worth finding a podcast editor in Anchorage itself?
You do not need one for the editing, because the edit happens on files that reach Dubai as easily as they reach someone across town, so a local person is only worth it if you need help on recording day itself.
To be very honest, if what your show is really missing is a person who drives out to the hangar, clips microphones on your guests and runs the cameras, then hire a local freelancer for that and I will happily tell you so, because nobody on our team is in Anchorage, all of us work out of Dubai, editing shows from every corner of the map. After the recording is made, though, distance stops being a factor, and what you care about is skill, reliability and turnaround, which is the argument in why a local podcast editor matters less than people think. Does that match how your show is actually made, mostly in the edit and not on the day? For most Anchorage hosts I speak to, it does.
How does the time difference between Anchorage and Dubai work?
Through the Alaska winter we are 13 hours ahead of you, and while American summer time is in force the gap is 12 hours, which means the episode you upload in the Anchorage evening arrives just as our morning begins.
In practice, 7 pm in Anchorage is 8 am in Dubai in winter and 7 am in summer, so if you upload after dinner, right, your episode is waiting at the start of our day and the work runs while you sleep. We never change our clocks in Dubai, so the hour that moves each spring and autumn is yours, and the current time in Dubai is easy to check if you lose track. How the async handover runs for hosts in each part of the country is covered in remote podcast editing for any US time zone, and the post on Honolulu shows working across a 14 hour gap shows the one place in the US that is even further from us than you are.
What does podcast editing cost for an Anchorage show?
A one camera Anchorage show of up to an hour sits on our Starter plan at 199 dollars an episode, and the part I want you to notice is what that price does not change with, right, a guest calling from a fishing camp on a terrible line costs you the same as a guest sitting in your studio, because rescuing the audio is part of the edit and not an extra invoice.
A lot of remote guest shows end up being audio first, or audio only, because the video from a weak connection is not worth showing, and those are edited too, with the price set on the call once I have heard what you are working with. If you do keep video, my practical advice is to decide per guest rather than per show, so a guest with a clean picture stays on screen and a guest on a frozen feed becomes a still photo with their name under it, which is honestly kinder to them. Packs, monthly plans, clip prices and the rest of the options are on the pricing section.
When is another option the better choice for you?
If your show is entirely remote guests on bad connections and you only publish now and then, a cheaper option might genuinely serve you better, and I would rather say that than oversell.
A solo freelancer who knows audio well can do a lot for an occasional audio-only show, the structural trade-off being that one person has no backup when they are busy. Automatic editing apps are quick and inexpensive and do well enough on relaxed chats, the catch here being that they trim by silence, so the pause where a bush pilot weighs up an answer, which is often the best moment in the whole episode, is the first thing to go. A full-time editor on staff becomes sensible for a bigger aviation or freight company running several shows each week, and the price of that is a salary and someone to manage. We suit the Anchorage host who wants a person deciding every cut, a price known in advance, and enough people behind the show that one awful guest track never delays the schedule, and with more than 400 episodes going through our team each month, I am pretty sure we have heard every way a remote call can break.
What should I send for the first Anchorage episode?
Share links to a few episodes that show your look, the original files from every source, including any recording a guest made on their own end, and a short note on names, sponsors and anything that must not be cut.
Continuity matters, right, so whatever opening, name captions, pace and colour your audience already knows will carry over unchanged. Remote guest shows benefit from a short list of guest names and aircraft, company or place names, because getting a lower third wrong is an easy way to lose a technical audience. The footage, the projects we build and the finished episodes all remain yours, so if you ever change editors you take working project files with you instead of starting again.
If you want to test us, email samy@pixelsamy.com with your roughest guest episode on purpose, or bring it to a 15 minute call, and I will listen and give you an honest view and a price before we hang up. At the end of the day, a remote guest on a slow connection is not a reason to stop making the show, it is a reason to have a human who knows what can be saved. So yeah. That's my way of saying it.