WEBVTT

00:00:00.939 --> 00:00:03.919
So Odyssey just announced they're deploying max

00:00:03.919 --> 00:00:11.439
casting into New York City WCBS FM and WXBK FM

00:00:11.439 --> 00:00:15.800
And I had this embarrassing moment where I realized

00:00:15.800 --> 00:00:17.719
I've been hearing this term for a couple of years

00:00:17.719 --> 00:00:21.739
now I work in broadcasting and I genuinely I

00:00:21.739 --> 00:00:24.579
couldn't explain to someone how it actually works

00:00:24.579 --> 00:00:27.480
if they asked me right now So instead of pretending

00:00:27.480 --> 00:00:30.100
any longer, let's learn this together This is

00:00:30.100 --> 00:00:33.060
the Tyler Woodward Project, and today I'm talking

00:00:33.060 --> 00:00:36.159
about Max Casting, what it is, how it works,

00:00:36.600 --> 00:00:39.460
whether if it's the future of FM radio or just

00:00:39.460 --> 00:00:42.140
a really good marketing tactic from a company

00:00:42.140 --> 00:00:45.100
in Chicago. Because I know you're going to ask,

00:00:45.500 --> 00:00:53.979
how the hell does EAS fit into any of this? Let

00:00:53.979 --> 00:00:56.520
me start with the problem max casting is trying

00:00:56.520 --> 00:00:59.259
to solve because none of this is gonna make sense

00:00:59.259 --> 00:01:03.759
without that FM radio has a dirty secret Your

00:01:03.759 --> 00:01:06.780
main transmitter is on top of the tower somewhere

00:01:06.780 --> 00:01:09.879
pumping out the signal Coverage maps look great

00:01:09.879 --> 00:01:14.120
right big confident circles lots of color but

00:01:14.120 --> 00:01:17.780
those maps were drawn assuming ideal conditions

00:01:17.780 --> 00:01:21.000
and rooftop antennas and That's not where your

00:01:21.000 --> 00:01:24.049
listeners are Real listing is happening down

00:01:24.049 --> 00:01:26.569
in the cars maybe six feet off the ground moving

00:01:26.569 --> 00:01:30.250
through city streets Threading between buildings

00:01:30.250 --> 00:01:35.689
rolling through valleys terrain eats signal buildings

00:01:35.689 --> 00:01:41.170
eat signal Geo broadcast solutions GBS the company

00:01:41.170 --> 00:01:44.170
behind max casting and know this is not sponsored

00:01:44.170 --> 00:01:49.459
says as many as 80 % of FM stations don't Fully

00:01:49.459 --> 00:01:51.719
cover their own license service area because

00:01:51.719 --> 00:01:57.879
of this 80 % So for decades the fix was throw

00:01:57.879 --> 00:02:00.980
up a booster transmitter same frequency as the

00:02:00.980 --> 00:02:05.819
main Extra power fill the gap simple idea the

00:02:05.819 --> 00:02:10.000
problem is in the overlap zone Where the main

00:02:10.000 --> 00:02:12.560
signal and the booster signal are both hitting

00:02:12.560 --> 00:02:15.479
your car radio at the same time from slightly

00:02:15.479 --> 00:02:18.960
different distances They arrive a tiny fraction

00:02:18.960 --> 00:02:22.740
of a second apart. That tiny little misalignment,

00:02:22.780 --> 00:02:26.580
that fraction of a second, turns your audio into

00:02:26.580 --> 00:02:30.500
a muddy, hollow, fluttery mess. Listeners are

00:02:30.500 --> 00:02:33.719
going to tune away. Engineers cringe. Nobody

00:02:33.719 --> 00:02:37.159
wins. That's the problem Max Casting was built

00:02:37.159 --> 00:02:46.639
to solve. Okay, so what actually is it? Maxcasting

00:02:46.639 --> 00:02:50.659
is a system developed by Geo Broadcast Solutions

00:02:50.659 --> 00:02:53.319
in partnership with Gates Air, who makes the

00:02:53.319 --> 00:02:57.759
transmitter hardware. At its core, it's a synchronized

00:02:57.759 --> 00:03:01.560
network of multiple low -power FM booster transmitters,

00:03:01.939 --> 00:03:05.099
strategically placed around a market, all locked

00:03:05.099 --> 00:03:08.379
to the same frequency as your main station, all

00:03:08.379 --> 00:03:11.860
carrying the same content and perfect time alignment

00:03:11.860 --> 00:03:17.300
with each other. The Keyword is synchronized.

00:03:17.780 --> 00:03:20.719
GBS basically borrowed a page from the Cellier

00:03:20.719 --> 00:03:23.759
Network Engineering Playbook. They looked at

00:03:23.759 --> 00:03:26.699
how cell carriers build overlapping coverage

00:03:26.699 --> 00:03:31.580
with node dead zones and said, we can do this

00:03:31.580 --> 00:03:35.699
for FM. The system uses GatesAir Flexiva Transmitters

00:03:35.699 --> 00:03:38.539
and their Intraplex SynchroCast IP distribution

00:03:38.539 --> 00:03:42.599
system to lock every booster node to the same

00:03:42.919 --> 00:03:47.400
audio timing as the main. When your car radio

00:03:47.400 --> 00:03:50.139
moves from the main signal into the booster zone,

00:03:50.340 --> 00:03:53.860
the transition is completely seamless. Your ears

00:03:53.860 --> 00:03:57.759
don't notice, your radio doesn't stutter, your

00:03:57.759 --> 00:04:02.099
PPM meter doesn't miss a beat. And this isn't

00:04:02.099 --> 00:04:05.060
just point some antenna at a city and hope for

00:04:05.060 --> 00:04:07.800
the best. The boosters are, you know, they're

00:04:07.800 --> 00:04:10.530
low to the ground, highly directional. pointed

00:04:10.530 --> 00:04:14.490
precisely where the coverage gap is. GBS does

00:04:14.490 --> 00:04:16.930
all the network design using high -resolution

00:04:16.930 --> 00:04:20.689
terrain data, actual building heights, real -world

00:04:20.689 --> 00:04:23.970
field measurements. And, not only that, but they're

00:04:23.970 --> 00:04:27.250
using vehicular traffic patterns. They're treating

00:04:27.250 --> 00:04:30.949
it like a cell deployment, which means it's actual

00:04:30.949 --> 00:04:34.589
engineering instead of guesswork. Now here's

00:04:34.589 --> 00:04:37.750
why a broadcaster actually cares about this beyond,

00:04:38.310 --> 00:04:42.009
hey, It just sounds better. If your signal is

00:04:42.009 --> 00:04:44.810
too weak or too distorted and part of your market,

00:04:45.370 --> 00:04:47.769
the Nielsen Portable People Meter, the little

00:04:47.769 --> 00:04:50.269
pager -looking device Nielsen uses to measure

00:04:50.269 --> 00:04:54.709
radio listening, it can't decode it. No decoded

00:04:54.709 --> 00:04:58.029
signal means no measured audience. No measured

00:04:58.029 --> 00:05:02.170
audience means those listeners don't exist, as

00:05:02.170 --> 00:05:06.149
far as your ratings are concerned. And no ratings

00:05:06.149 --> 00:05:09.970
means advertisers aren't paying for them. You're

00:05:09.970 --> 00:05:13.970
broadcasting to real people, but they don't statistically

00:05:13.970 --> 00:05:20.110
exist. Maxcasting fixes that. In San Francisco,

00:05:20.629 --> 00:05:23.730
GBS helped Bonneville upgrade three stations,

00:05:24.050 --> 00:05:27.769
and by December 2025, four of the top five FM

00:05:27.769 --> 00:05:31.750
stations in the market were Maxcasting licensees.

00:05:32.029 --> 00:05:43.439
KQED. public radio has held the number one overall

00:05:43.439 --> 00:05:46.399
station position in san francisco since activating

00:05:46.399 --> 00:05:51.139
max casting odyssey then deployed it on kllc

00:05:51.139 --> 00:05:54.959
and kits and added seven booster nodes that extended

00:05:54.959 --> 00:05:58.600
their reach to another 800 000 people in the

00:05:58.600 --> 00:06:04.170
south bay nationwide GBS claims 13 million incremental

00:06:04.170 --> 00:06:08.430
listeners added across all deployments. And look,

00:06:08.750 --> 00:06:11.490
I take vendor numbers with a grain of salt. But

00:06:11.490 --> 00:06:14.550
when four of the top five stations in a market

00:06:14.550 --> 00:06:18.430
are using your product, something's gotta be

00:06:18.430 --> 00:06:24.850
working, right? So who's actually using this

00:06:24.850 --> 00:06:31.189
thing? As of late 2025, GBS has deployed in 11

00:06:31.189 --> 00:06:35.449
markets. San Francisco, Los Angeles, Chicago,

00:06:35.910 --> 00:06:39.670
San Diego, Miami, Baltimore, Boston, Cleveland,

00:06:40.230 --> 00:06:44.550
Las Vegas, San Jose, and St. George, Utah. New

00:06:44.550 --> 00:06:47.649
York City and Atlanta are in the design phase

00:06:47.649 --> 00:06:51.529
right now. Six of the top 10 Nielsen radio markets

00:06:51.529 --> 00:06:54.350
either have it or are working on getting it.

00:06:54.569 --> 00:06:57.910
And it's not just commercial radio either. WYPR

00:06:57.910 --> 00:07:01.629
in Baltimore, an NPR affiliate, deployed Maxcasting

00:07:01.629 --> 00:07:06.949
to link WYPR on 88 .1 FM in Baltimore with WYPF

00:07:06.949 --> 00:07:10.290
on 88 .1 FM in Frederick, covering the I -70

00:07:10.290 --> 00:07:13.410
corridor between the two cities. Before Maxcasting,

00:07:14.050 --> 00:07:16.569
those two same frequency transmitters were fighting

00:07:16.569 --> 00:07:20.189
each other in the overlap zone. Now they're synchronized.

00:07:20.389 --> 00:07:24.029
Problem solved. The deployment spans Bonneville.

00:07:24.170 --> 00:07:27.589
Audacity, Spanish Broadcasting System, The Educational

00:07:27.589 --> 00:07:30.329
Media Foundation, West Virginia Radio Corporation,

00:07:30.949 --> 00:07:35.449
a genuinely broad mix of group owners and independents.

00:07:36.870 --> 00:07:41.069
Alright, how complicated is this for engineers?

00:07:42.069 --> 00:07:47.230
Be honest. Well, the honest answer is, it's a

00:07:47.230 --> 00:07:51.430
real project, not a plug and play box. GBS does

00:07:51.430 --> 00:07:54.930
do the heavy network design work, terrain modeling,

00:07:55.490 --> 00:07:58.209
propagation tuning, interference zone analysis,

00:07:58.910 --> 00:08:01.470
and they're treating it like a cell network design,

00:08:01.829 --> 00:08:06.310
which means it's sophisticated. At each booster

00:08:06.310 --> 00:08:08.709
site, you need a Gates Air Flexiva transmitter,

00:08:10.290 --> 00:08:12.970
a directional antenna at a deliberately low height,

00:08:13.569 --> 00:08:16.810
and a stable, dedicated IP connection back to

00:08:16.810 --> 00:08:19.370
the main station for the SyncroCast synchronization

00:08:19.370 --> 00:08:23.699
to lock. That distribution path needs to be a

00:08:23.699 --> 00:08:26.899
reliable managed IP circuit not the public internet

00:08:26.899 --> 00:08:29.720
Because the timing requirements are tight and

00:08:29.720 --> 00:08:33.480
you can't have jitter messing with it Each booster

00:08:33.480 --> 00:08:36.559
site also needs to be licensed with the FCC as

00:08:36.559 --> 00:08:39.779
a booster facility Standard process, but it adds

00:08:39.779 --> 00:08:43.519
a little lead time GBS handles most of the FCC

00:08:43.519 --> 00:08:48.720
filing support as part of the process So it's

00:08:48.720 --> 00:08:51.720
not Two engineers in a weekend, but it's also

00:08:51.720 --> 00:08:54.899
not a two -year custom engineering odyssey. It

00:08:54.899 --> 00:08:57.879
lives in the significant project with expert

00:08:57.879 --> 00:09:01.899
support category. For programmers and traffic

00:09:01.899 --> 00:09:06.159
people? In its base form, max casting requires

00:09:06.159 --> 00:09:10.440
exactly zero changes to your workflow. Every

00:09:10.440 --> 00:09:13.740
booster carries the same audio as the main. In

00:09:13.740 --> 00:09:16.679
perfect sync, your automation system, your play

00:09:16.679 --> 00:09:19.789
out, your traffic logs, completely untouched.

00:09:20.509 --> 00:09:22.710
The transmitters are just invisibly extending

00:09:22.710 --> 00:09:25.710
your signal, completely transparent to the programming

00:09:25.710 --> 00:09:30.769
side of the house. Now that changes if you move

00:09:30.769 --> 00:09:34.409
up to Zone Casting, GBS's next level product

00:09:34.409 --> 00:09:39.009
that the FCC fully greenlit last year. Zone Casting

00:09:39.009 --> 00:09:41.710
lets you originate up to 3 minutes per hour of

00:09:41.710 --> 00:09:44.230
different content on specific booster zones.

00:09:45.090 --> 00:09:47.940
Think localized ads, neighborhood traffic, whatever

00:09:47.940 --> 00:09:52.120
you can think of. That does require automation

00:09:52.120 --> 00:09:54.940
integration to schedule and insert zone specific

00:09:54.940 --> 00:09:58.200
content, but that's an optional upgrade, not

00:09:58.200 --> 00:10:03.320
the base product. Now let's talk about the emergency

00:10:03.320 --> 00:10:06.820
alert system, because I knew this was coming.

00:10:07.779 --> 00:10:11.980
In a standard max casting deployment, EAS works

00:10:11.980 --> 00:10:15.299
exactly the way it always has. The main transmitter

00:10:15.299 --> 00:10:18.179
carries the alert, the boosters relay it in perfect

00:10:18.179 --> 00:10:22.120
sync. Listeners everywhere in your coverage area

00:10:22.120 --> 00:10:25.559
hear the alert simultaneously. From an EAS standpoint,

00:10:25.759 --> 00:10:28.360
the system behaves like one big giant radio station.

00:10:28.519 --> 00:10:32.220
No gap, no delay, no problem. The complication

00:10:32.220 --> 00:10:36.340
enters with zone casting, where a booster is

00:10:36.340 --> 00:10:39.240
originating its own content during those short

00:10:39.240 --> 00:10:43.399
local windows. The concern, and it's a fair one,

00:10:43.600 --> 00:10:48.000
is what happens if an EAS alert fires while a

00:10:48.000 --> 00:10:50.899
booster zone is airing localized content instead

00:10:50.899 --> 00:10:56.840
of the main feed. GBS's answer is that EAS overrides

00:10:56.840 --> 00:11:00.899
the zone content immediately. The FCC requires

00:11:00.899 --> 00:11:05.220
EAS compliance for all originating boosters and

00:11:05.220 --> 00:11:08.080
found in its review that properly engineered

00:11:08.080 --> 00:11:10.879
systems handle this without disrupting alert

00:11:10.879 --> 00:11:15.259
delivery. The NAB's counter -argument is that

00:11:15.259 --> 00:11:19.759
GBS tested this under controlled conditions with

00:11:19.759 --> 00:11:23.919
a small number of sites. Large -scale real -world

00:11:23.919 --> 00:11:28.899
deployment across complex RF environments hasn't

00:11:28.899 --> 00:11:34.179
been independently vetted at scale. That's not

00:11:34.179 --> 00:11:38.960
an unreasonable concern to raise. The NAB had

00:11:39.500 --> 00:11:42.600
A lot of feelings about zonecasting in general.

00:11:43.360 --> 00:11:46.720
49 state broadcaster associations signed a letter

00:11:46.720 --> 00:11:49.919
against it. Now that's a whole separate episode.

00:11:51.000 --> 00:11:54.460
For the pure maxcasting simulcast case, which

00:11:54.460 --> 00:11:57.139
is what most deployments are right now anyways,

00:11:57.740 --> 00:12:01.139
there's no EES concern worth losing any sleep

00:12:01.139 --> 00:12:06.019
over. The engineering side just works. For zonecasting,

00:12:06.429 --> 00:12:09.549
The override mechanism needs to be solid and

00:12:09.549 --> 00:12:16.110
the design needs to be done very carefully. So

00:12:16.110 --> 00:12:21.210
is Max casting the future of FM radio? Honestly,

00:12:21.210 --> 00:12:26.750
it's a really practical bridge. It doesn't reinvent

00:12:26.750 --> 00:12:31.330
radio. It doesn't solve the streaming problem

00:12:31.330 --> 00:12:35.820
or make FM cool again by itself. What it does

00:12:35.820 --> 00:12:39.580
is recover the audience FM was supposed to have,

00:12:40.139 --> 00:12:44.539
the people inside your license contour, who just

00:12:44.539 --> 00:12:49.399
can't hear you clearly enough to count. That's

00:12:49.399 --> 00:12:53.440
a revenue argument as much as a technical one,

00:12:53.480 --> 00:12:56.659
to be honest. For engineers, it's real work,

00:12:56.899 --> 00:13:01.700
but it's a well -supported product with a methodology

00:13:01.700 --> 00:13:05.009
behind it. For programmers, in its base form,

00:13:05.789 --> 00:13:08.990
it's completely invisible, which is kind of an

00:13:08.990 --> 00:13:12.129
elegant solution, really. For listeners, they'll

00:13:12.129 --> 00:13:14.789
just notice that a station sounds better in the

00:13:14.789 --> 00:13:16.970
neighborhood where it used to cut in and out.

00:13:17.470 --> 00:13:20.529
In the zone casting piece, geo -targeted local

00:13:20.529 --> 00:13:23.730
content, hyper -local ads, neighborhood -specific

00:13:23.730 --> 00:13:27.669
information, that's where it gets genuinely interesting

00:13:27.669 --> 00:13:32.519
and genuinely controversial. That's one... I'll

00:13:32.519 --> 00:13:36.960
save for a future episode. For now, max casting

00:13:36.960 --> 00:13:40.399
is what happens when someone finally applied

00:13:40.399 --> 00:13:44.460
a cellular network thinking mindset to an FM

00:13:44.460 --> 00:13:46.720
booster problem that's been annoying engineers

00:13:46.720 --> 00:13:50.299
for well over 40 years. I'm Tyler. Thanks for

00:13:50.299 --> 00:13:52.480
listening to the Tyler Woodward Project. Follow

00:13:52.480 --> 00:13:55.600
me on Instagram, Blue Sky and threads at tylerwoodward

00:13:55.600 --> 00:13:58.529
.me. make sure you head over to Tyler Woodward

00:13:58.529 --> 00:14:00.990
.me check out the brand new website you can get

00:14:00.990 --> 00:14:04.529
in touch with me over there and whatever podcast

00:14:04.529 --> 00:14:06.870
app you're listening to this on apple podcast

00:14:06.870 --> 00:14:11.690
spotify amazon music youtube pandora leave a

00:14:11.690 --> 00:14:14.990
review a like subscribe all that stuff it it

00:14:14.990 --> 00:14:16.970
helps i'll catch you next time