WEBVTT

00:00:01.819 --> 00:00:06.799
The FCC just banned consumer -grade routers.

00:00:07.160 --> 00:00:10.939
Not just the cheap, sketchy ones you find on

00:00:10.939 --> 00:00:13.539
Amazon. Not just the brand that's been in the

00:00:13.539 --> 00:00:16.519
news for all the wrong reasons. New consumer

00:00:16.519 --> 00:00:19.899
-grade routers manufactured outside of the United

00:00:19.899 --> 00:00:23.019
States. Which, if you've looked on the back of

00:00:23.019 --> 00:00:26.239
any of them, it's pretty much all of them. And

00:00:26.239 --> 00:00:28.339
if you're running a broadcast facility and you've

00:00:28.339 --> 00:00:32.159
got one of those little TP links or a net gate

00:00:32.159 --> 00:00:34.600
doing something really important somewhere in

00:00:34.600 --> 00:00:37.479
the building, I'd probably pay attention to this

00:00:37.479 --> 00:00:40.840
one. This is the Tyler Woodward project. Today

00:00:40.840 --> 00:00:43.140
I'm talking about the router band and what you

00:00:43.140 --> 00:00:46.500
can do about it. A local ownership win out of

00:00:46.500 --> 00:00:49.100
South Dakota. A New Jersey AM station getting

00:00:49.100 --> 00:00:52.759
a very uncomfortable letter from the FCC. the

00:00:52.759 --> 00:00:55.520
HD radio digital power changes that are worth

00:00:55.520 --> 00:00:58.579
knowing about, and why the C -band situation

00:00:58.579 --> 00:01:01.820
is going to hurt a lot of stations a lot more

00:01:01.820 --> 00:01:04.359
than others. We've got a full plate. Let's get

00:01:04.359 --> 00:01:15.560
into it. OK, so the FCC added consumer -grade

00:01:15.560 --> 00:01:17.980
foreign -manufactured routers to what's called

00:01:17.980 --> 00:01:23.079
the quote -unquote covered list. That's their

00:01:23.079 --> 00:01:25.680
running list of telecom equipment that's been

00:01:25.680 --> 00:01:29.219
flagged as a national security risk. Their reasoning

00:01:29.219 --> 00:01:34.620
is that foreign adversaries have been using compromised

00:01:34.620 --> 00:01:39.019
consumer routers as a way into US networks. And

00:01:39.019 --> 00:01:41.859
the FCC decided the right move was to cut off

00:01:41.859 --> 00:01:47.719
the supply of any new equipment. Existing gear

00:01:47.719 --> 00:01:50.329
that's in your rack If it's already in your rack,

00:01:50.670 --> 00:01:52.870
it's already in your building, it's not going

00:01:52.870 --> 00:01:55.849
to go anywhere. Your grandfather did, but new

00:01:55.849 --> 00:02:00.329
models where any significant part of the production

00:02:00.329 --> 00:02:03.670
process happened outside of the United States,

00:02:04.189 --> 00:02:06.849
it now needs government approval before they

00:02:06.849 --> 00:02:12.370
can be sold here. That part, it's still a little

00:02:12.370 --> 00:02:17.090
murky to me because brands like, you know, Ubiquiti

00:02:17.090 --> 00:02:21.710
in Cisco, They're American companies, but they

00:02:21.710 --> 00:02:26.229
manufacture overseas. So does this catch them

00:02:26.229 --> 00:02:29.550
in this mess too? Honestly, that's still getting

00:02:29.550 --> 00:02:32.409
sorted out. Manufacturers are trying to figure

00:02:32.409 --> 00:02:35.629
out their path forward. And the fine print is

00:02:35.629 --> 00:02:37.870
still being read by a lot of lawyers right now,

00:02:37.990 --> 00:02:41.770
which is kind of the standard for this sort of

00:02:41.770 --> 00:02:47.490
thing. If your station is running on proper enterprise

00:02:47.490 --> 00:02:50.569
gear, you know, think Fortinet, Juniper, Palo

00:02:50.569 --> 00:02:55.590
Alto, whatever your IT team chose when someone

00:02:55.590 --> 00:02:59.870
had an actual budget, you're probably okay. That

00:02:59.870 --> 00:03:02.689
sort of stuff isn't what this band is aimed at

00:03:02.689 --> 00:03:07.629
anyways. But if you're a smaller station, or

00:03:07.629 --> 00:03:10.729
even a medium market station that's been patching

00:03:10.729 --> 00:03:12.810
things together for years because the budget

00:03:12.810 --> 00:03:17.219
never quite lined up with the need, This is the

00:03:17.219 --> 00:03:20.639
moment to look at what you've actually got going

00:03:20.639 --> 00:03:24.900
and decide if it's something you want to keep

00:03:24.900 --> 00:03:30.060
depending on. Here's the thing, there are real

00:03:30.060 --> 00:03:33.639
options that don't cost a ton of money. At my

00:03:33.639 --> 00:03:39.159
last gig, we ran PF Sense on an old Dell desktop,

00:03:39.719 --> 00:03:44.780
just a regular old PC with a decent Intel card.

00:03:45.229 --> 00:03:50.569
We had five open VPN tunnels on it. I think somewhere

00:03:50.569 --> 00:03:55.750
up to 13 VLANs snort running for Intrusion detection

00:03:55.750 --> 00:04:00.710
we had the DHCP DNS all the all the spiffy features

00:04:00.710 --> 00:04:03.969
turned on off a ton of firewall rules a lot of

00:04:03.969 --> 00:04:07.189
netting rules You know and as I mentioned it

00:04:07.189 --> 00:04:09.889
was all open VPN too because wire guard really

00:04:09.889 --> 00:04:12.169
wasn't a thing yet I mean it was kind of on the

00:04:12.169 --> 00:04:16.000
radar, but wasn't matured like it is now And

00:04:16.000 --> 00:04:18.379
if you've got the option for a wire guard, wire

00:04:18.379 --> 00:04:22.519
guard is now very much a thing, and it's pretty

00:04:22.519 --> 00:04:25.100
good. I use it personally. And if you got the

00:04:25.100 --> 00:04:27.980
option at your station, I'd use that for your

00:04:27.980 --> 00:04:32.180
remote staff. It's pretty rock solid. And speaking

00:04:32.180 --> 00:04:35.300
of rock solid, PF Sense itself was rock solid.

00:04:35.540 --> 00:04:39.800
Now, when we eventually had the budget to get

00:04:39.800 --> 00:04:43.860
a NetGate appliance, which is all it really is,

00:04:43.879 --> 00:04:47.480
is a purpose built piece of equipment an actual

00:04:47.480 --> 00:04:51.259
I guess it's sort of enterprise router level

00:04:51.259 --> 00:04:55.540
that came with PFSense Plus on it and had actual

00:04:55.540 --> 00:04:58.420
support behind it we still kept the old Dell

00:04:58.420 --> 00:05:01.540
around because it was still solid it was just

00:05:01.540 --> 00:05:04.860
on the older side and you know it needed to be

00:05:04.860 --> 00:05:06.959
phased out but we kept it as a backup because

00:05:06.959 --> 00:05:11.560
the thing still ran and if something goes wrong

00:05:11.560 --> 00:05:14.220
at midnight and you need to swap in a known good

00:05:14.220 --> 00:05:19.029
router The ugly old box suddenly becomes the

00:05:19.029 --> 00:05:21.930
most important thing in that building. Another

00:05:21.930 --> 00:05:27.569
option you can look at is OpenSense. It's a fork

00:05:27.569 --> 00:05:30.629
of PF Sense. Same general ideas, same packages,

00:05:30.810 --> 00:05:37.529
same features. But, in my opinion, the UI is

00:05:37.529 --> 00:05:40.370
a lot easier on the eyes. And there's none of

00:05:40.370 --> 00:05:42.790
the weirdness around PF Sense Plus versus the

00:05:42.790 --> 00:05:46.120
free Community Edition. With OpenSense, you're

00:05:46.120 --> 00:05:51.160
not wondering what's behind the paywall. It's

00:05:51.160 --> 00:05:53.579
all there for the taking. You can turn whatever

00:05:53.579 --> 00:05:55.860
options on and off you want, install whatever

00:05:55.860 --> 00:05:59.199
packages you want, within reason. You don't want

00:05:59.199 --> 00:06:03.740
to overload the thing. And if you've got a smaller

00:06:03.740 --> 00:06:08.240
site or a simpler type of deployment, think of

00:06:08.240 --> 00:06:11.300
a remote site, a transmitter shack, something

00:06:11.300 --> 00:06:15.050
that just needs basic routing, Maybe a Wi -Fi

00:06:15.050 --> 00:06:20.529
access point open WRT on a Raspberry Pi can absolutely

00:06:20.529 --> 00:06:24.569
do the job Not everything needs to be a big old

00:06:24.569 --> 00:06:29.569
project and my my honest opinion all of this

00:06:29.569 --> 00:06:33.509
is the one thing you got to watch out for is

00:06:33.509 --> 00:06:37.029
You own it. There's no support when something

00:06:37.029 --> 00:06:39.730
breaks at a bad time probably during the morning

00:06:39.730 --> 00:06:45.149
show that's on you or whoever you may have on

00:06:45.149 --> 00:06:48.350
your staff that handles the networking, which

00:06:48.350 --> 00:06:51.889
is honestly probably you too. So if your team

00:06:51.889 --> 00:06:55.850
isn't in a place to support that, look into a

00:06:55.850 --> 00:06:58.910
local MSP, a managed service provider who can

00:06:58.910 --> 00:07:02.949
wrap a support contract around open source software

00:07:02.949 --> 00:07:06.810
or open source infrastructure for probably a

00:07:06.810 --> 00:07:09.670
lot less than a big vendor wants anyways. It's

00:07:09.670 --> 00:07:14.069
an option. The point isn't to try to do everything

00:07:14.069 --> 00:07:17.430
yourself. The point is to stay on the air. But

00:07:17.430 --> 00:07:20.769
also, I want to let you know, you got options.

00:07:20.870 --> 00:07:26.250
There's plenty of stuff out there. All right,

00:07:26.290 --> 00:07:29.089
this story is a good one. Connoisseur Media,

00:07:29.110 --> 00:07:32.850
they picked up a big chunk of Alpha media stations

00:07:32.850 --> 00:07:36.589
last year. They're selling their cluster in Brookings,

00:07:37.029 --> 00:07:39.990
South Dakota to the people who have actually

00:07:39.990 --> 00:07:43.709
been running the stations. 5 stations in particular.

00:07:44.709 --> 00:07:53.170
KBRK, KBRK -FM, KDBX -FM, KJJQ, and KKQQ -FM,

00:07:53.170 --> 00:07:56.389
I think. The buyer is Cammie Powers, the market

00:07:56.389 --> 00:07:59.110
manager who's been running the place, along with

00:07:59.110 --> 00:08:01.370
her husband Derek and the business manager Chad

00:08:01.370 --> 00:08:04.149
Hoge. They're calling the new company Brookings

00:08:04.149 --> 00:08:09.370
Radio LLC. I love this. Because this is how it

00:08:09.370 --> 00:08:13.750
should work. Local people buying a local cluster.

00:08:14.509 --> 00:08:17.670
They know because they've worked there. Not another

00:08:17.670 --> 00:08:22.689
big media conglomerate. Sorry, I heart, I'm talking

00:08:22.689 --> 00:08:25.970
about you. Not another company with, you know,

00:08:26.110 --> 00:08:28.930
trying to squeeze out every little less cent

00:08:28.930 --> 00:08:31.670
out of the name or out of the place that they

00:08:31.670 --> 00:08:35.429
can. It's actual human beings who know the market.

00:08:35.879 --> 00:08:39.480
They know the advertisers. They know what the

00:08:39.480 --> 00:08:44.720
community cares about. Connoisseur said Brookings

00:08:44.720 --> 00:08:48.259
didn't fit where they wanted to go after the

00:08:48.259 --> 00:08:51.080
Alpha deal. And that's fine. That's totally cool.

00:08:51.720 --> 00:08:54.500
When big groups sell off smaller markets, this

00:08:54.500 --> 00:08:58.019
is the best possible outcome. The stations land

00:08:58.019 --> 00:09:02.360
with people who actually give a damn. FCC approval,

00:09:02.460 --> 00:09:05.580
it's pending. and hopefully, you know, they hope

00:09:05.580 --> 00:09:12.259
to close sometime early summer. All I gotta say

00:09:12.259 --> 00:09:14.320
is good luck to Cammie and her team. I'm rooting

00:09:14.320 --> 00:09:18.899
for them, man. All right. Now we gotta go from

00:09:18.899 --> 00:09:24.679
the feel good story to, well, feel uncomfortable

00:09:24.679 --> 00:09:30.299
story. Radio World covered a story about WIMG,

00:09:31.200 --> 00:09:34.940
an AM station in Ewing, New Jersey, that got

00:09:34.940 --> 00:09:39.320
inspected by the FCC and came away with a notice

00:09:39.320 --> 00:09:44.740
of violation. And the list of findings is one

00:09:44.740 --> 00:09:47.399
of those things that you read and think, how

00:09:47.399 --> 00:09:51.039
the heck did it get to that point? And honestly,

00:09:51.120 --> 00:09:54.200
we probably know. You'll understand what I mean

00:09:54.200 --> 00:09:57.759
when I rattle off what happened. Tower lighting

00:09:57.759 --> 00:10:02.039
was at the wrong heights. Obstruction lights

00:10:02.039 --> 00:10:06.059
weren't working. The licensee had filed a notum

00:10:06.059 --> 00:10:10.679
with the FAA for the outage, but they never renewed

00:10:10.679 --> 00:10:15.899
it. And the FCC agent actually had to do it during

00:10:15.899 --> 00:10:20.580
the inspection. Brush and vegetation around the

00:10:20.580 --> 00:10:24.100
towers were thick enough to block access to the

00:10:24.100 --> 00:10:27.440
tower bases. The station was running at 900 watts

00:10:27.440 --> 00:10:30.299
daytime instead of its authorized 3200 watts.

00:10:31.240 --> 00:10:34.720
And the real troubling thing is the EAS equipment,

00:10:34.799 --> 00:10:38.720
it wouldn't even turn on. That's a lot of things

00:10:38.720 --> 00:10:42.019
to have wrong at the same time. And I want to

00:10:42.019 --> 00:10:45.080
be clear. I'm not sharing this to pile on to

00:10:45.080 --> 00:10:47.720
the station. They're already having a really

00:10:47.720 --> 00:10:51.759
rough day. I'm sharing it because a lot of us

00:10:51.759 --> 00:10:54.700
broadcast engineers know exactly how this happens.

00:10:55.580 --> 00:10:58.620
It doesn't happen because people are being lazy

00:10:58.620 --> 00:11:03.899
or don't care, it happens because resources are

00:11:03.899 --> 00:11:07.779
getting stretched. One engineer probably covering

00:11:07.779 --> 00:11:10.620
too many sites, one owner trying to keep the

00:11:10.620 --> 00:11:12.940
lights on financially while the lights on the

00:11:12.940 --> 00:11:17.600
tower start to slip. Parts are on order, it's

00:11:17.600 --> 00:11:20.820
on the list, it'll get done after the next thing.

00:11:21.840 --> 00:11:25.299
And the next thing never comes. And then one

00:11:25.299 --> 00:11:30.409
day the FCC shows up. AM directional arrays are

00:11:30.409 --> 00:11:33.850
especially unforgiving here. You've got lighting

00:11:33.850 --> 00:11:36.870
requirements. You've got access requirements.

00:11:37.129 --> 00:11:40.490
You've got operating parameters that are not

00:11:40.490 --> 00:11:45.029
suggestions. And the EAS stuff, that's not optional.

00:11:46.070 --> 00:11:48.649
And the FCC, to their credit, does still show

00:11:48.649 --> 00:11:52.730
up and look at this stuff in the field. So the

00:11:52.730 --> 00:11:56.990
takeaway, it's not complicated. Go walk the site.

00:11:57.259 --> 00:12:02.559
Check the lights. Make sure the EAS box actually

00:12:02.559 --> 00:12:05.860
does what it's supposed to do. Look at the logs.

00:12:06.159 --> 00:12:08.100
Make sure you're running those required weekly

00:12:08.100 --> 00:12:10.220
tests. Make sure you're relaying the required

00:12:10.220 --> 00:12:14.480
monthly tests. Confirm you're also running at

00:12:14.480 --> 00:12:17.519
the right power. Clear the brush. Hire a company

00:12:17.519 --> 00:12:22.460
if you have to. Do the boring stuff before it

00:12:22.460 --> 00:12:25.320
becomes a federal violation because once the

00:12:25.320 --> 00:12:29.059
feds are involved the boring stuff is now very

00:12:29.059 --> 00:12:33.940
expensive boring stuff all right let me tell

00:12:33.940 --> 00:12:36.059
you about a rule change that doesn't get enough

00:12:36.059 --> 00:12:39.279
attention right now the fcc updated the rules

00:12:39.279 --> 00:12:43.879
for hd radio digital power and it's genuinely

00:12:43.879 --> 00:12:46.980
useful and good news for fm engineers the big

00:12:46.980 --> 00:12:52.659
thing is asymmetric sidebands your hd signal

00:12:53.049 --> 00:12:55.929
has two digital sidebands, one above your carrier,

00:12:56.509 --> 00:12:59.690
one below your carrier. Before this rule change,

00:13:00.190 --> 00:13:02.529
if a neighboring station needed protection on

00:13:02.529 --> 00:13:06.450
one side of you, you had to pull both sides down

00:13:06.450 --> 00:13:12.149
to match. Now, you can run each sideband at a

00:13:12.149 --> 00:13:14.850
different power level. Protect where you need

00:13:14.850 --> 00:13:18.470
to protect, push further where you have the room.

00:13:18.730 --> 00:13:21.429
More coverage, more flexibility, less compromise.

00:13:21.879 --> 00:13:26.179
The FCC also made it a lot easier to run your

00:13:26.179 --> 00:13:30.500
digital power up to 10 % of your analog power.

00:13:31.740 --> 00:13:37.700
Minus 10 dBc. That used to need special authorization

00:13:37.700 --> 00:13:41.799
or an STA. Now it's just a notification. File

00:13:41.799 --> 00:13:49.779
2100, schedule 335 -FM. And you're eligible.

00:13:50.360 --> 00:13:54.929
You're running. Assuming the FCC doesn't push

00:13:54.929 --> 00:13:59.570
back, which at minus 10 dBc, they probably won't.

00:14:00.029 --> 00:14:03.450
One catch though, right now this supplies to

00:14:03.450 --> 00:14:08.169
stations at 106 .9 MHz and below. If you're at

00:14:08.169 --> 00:14:14.629
107 .1 or higher, you're still under the old

00:14:14.629 --> 00:14:18.470
framework because of concerns about interference

00:14:18.470 --> 00:14:23.440
near the air band at 108. The NAB is working

00:14:23.440 --> 00:14:27.279
on that and it sounds like the rules could expand

00:14:27.279 --> 00:14:31.220
within the next year or so. But if you're already

00:14:31.220 --> 00:14:34.919
on HD radio and you qualify, this is worth a

00:14:34.919 --> 00:14:38.799
conversation with your consultant engineer. One

00:14:38.799 --> 00:14:43.360
form, potentially meaningful, better digital

00:14:43.360 --> 00:14:48.500
coverage. That's a pretty good deal, right? And

00:14:48.500 --> 00:14:51.539
this brings me to our last story, Bob Weller.

00:14:51.659 --> 00:14:54.580
at the NAB who had a really good piece in radio

00:14:54.580 --> 00:14:58.500
world that I think is required reading if you're

00:14:58.500 --> 00:15:01.179
a broadcast engineer paying attention to where

00:15:01.179 --> 00:15:03.860
the infrastructure of broadcasting is heading.

00:15:04.899 --> 00:15:10.299
The C -band situation. Yeah, it's real. There's

00:15:10.299 --> 00:15:13.720
legislation now. The one big beautiful bill.

00:15:14.480 --> 00:15:17.419
It required the FCC to auction off at least 100

00:15:17.419 --> 00:15:24.990
megahertz of C -band spectrum by mid Weller isn't

00:15:24.990 --> 00:15:27.870
being subtle about it either. If you're still

00:15:27.870 --> 00:15:30.870
dependent on C -band satellite for distribution,

00:15:31.649 --> 00:15:36.610
you need to be working on transitioning. Not

00:15:36.610 --> 00:15:41.389
thinking about it, actively working on it. Now,

00:15:42.590 --> 00:15:45.769
the counter -argument people make is that IP

00:15:45.769 --> 00:15:48.929
delivery is better than it's ever been. Sure,

00:15:49.289 --> 00:15:53.000
and that's true. Fiber infrastructure is better.

00:15:53.080 --> 00:15:56.960
Redundant IP paths are more accessible. Managed

00:15:56.960 --> 00:16:02.240
IP distribution has matured a lot for a station

00:16:02.240 --> 00:16:06.320
and a decent sized market with good carrier options.

00:16:07.039 --> 00:16:09.559
Migrating off a C -band and onto fiber -backed

00:16:09.559 --> 00:16:13.980
IP is a really good option and probably the right

00:16:13.980 --> 00:16:17.519
move anyways. But that's only the story if you

00:16:17.519 --> 00:16:21.679
actually have fiber available. There are stations

00:16:21.679 --> 00:16:24.559
still in this country, in parts of this country,

00:16:25.960 --> 00:16:31.200
that hadn't yet the broadband build -outs. The

00:16:31.200 --> 00:16:33.740
investment, of course, sure, was announced. The

00:16:33.740 --> 00:16:36.159
press releases went out. It all sounded good.

00:16:36.899 --> 00:16:38.799
And then the fibers stopped somewhere before

00:16:38.799 --> 00:16:41.980
it ever got to them. Or they've got one mediocre

00:16:41.980 --> 00:16:47.139
option in town. And nothing that you would want

00:16:47.139 --> 00:16:51.139
to trust your network feed at. especially at

00:16:51.139 --> 00:16:53.259
six in the morning when something is already

00:16:53.259 --> 00:16:59.399
on fire. Those stations are going to feel the

00:16:59.399 --> 00:17:01.679
C -band squeeze harder than anyone, I think.

00:17:02.080 --> 00:17:04.019
They're the ones already running on less anyways,

00:17:04.140 --> 00:17:06.339
less staff, less budget, less infrastructure

00:17:06.339 --> 00:17:09.400
redundancy, and they're often the only local

00:17:09.400 --> 00:17:12.180
media source in their area. When something goes

00:17:12.180 --> 00:17:15.319
sideways, a storm, an emergency, an event that

00:17:15.319 --> 00:17:17.400
actually matters to the people in that county,

00:17:17.799 --> 00:17:20.039
they're the ones who are probably still showing

00:17:20.039 --> 00:17:24.940
up, the ones that people are counting on. And

00:17:24.940 --> 00:17:27.259
the conversation about transitioning off a C

00:17:27.259 --> 00:17:29.559
-band tends to be built around the stations that

00:17:29.559 --> 00:17:33.220
already have good options available to them,

00:17:33.759 --> 00:17:38.400
which means the stations that don't are going

00:17:38.400 --> 00:17:41.799
to have to make noise if they want to be part

00:17:41.799 --> 00:17:44.460
of the conversation and to get this problem solved.

00:17:44.660 --> 00:17:47.910
Because if you don't speak up, It'll get solved

00:17:47.910 --> 00:17:52.930
without you Now here's where I land on all this

00:17:52.930 --> 00:17:56.390
the router band It's a reason to go look at your

00:17:56.390 --> 00:17:58.690
infrastructure. I know you probably haven't thought

00:17:58.690 --> 00:18:01.349
about it in the wild and I don't want you to

00:18:01.349 --> 00:18:05.289
panic about it, but Start thinking about it.

00:18:05.390 --> 00:18:09.009
There's good open source options out there. There's

00:18:09.009 --> 00:18:12.490
the net gate appliances There's MSPs who can

00:18:12.490 --> 00:18:15.750
help pick your path start moving Start calling

00:18:15.750 --> 00:18:18.369
people, get an options, get them pricing. Something

00:18:18.369 --> 00:18:21.369
that you can throw at the GM and say, hey, I

00:18:21.369 --> 00:18:23.470
need some help with this. Here's a company that

00:18:23.470 --> 00:18:26.150
can help or here's some options that we can get.

00:18:26.210 --> 00:18:29.269
Raspberry Pis, you know, maybe a really good

00:18:29.269 --> 00:18:31.849
PC from Best Buy that's got an Intel, Nick. Don't

00:18:31.849 --> 00:18:35.029
use Realtek, use Intel. Trust me, go look at

00:18:35.029 --> 00:18:36.990
Reddit. You'll find out what I'm talking about.

00:18:37.049 --> 00:18:41.150
Get an Intel, Nick. And I think you'll be presently,

00:18:41.309 --> 00:18:43.210
you know, I think you'll be pleasantly surprised.

00:18:44.410 --> 00:18:47.269
The brooking cell, that's a really good story.

00:18:47.609 --> 00:18:50.509
Local ownership winning is always worth acknowledging.

00:18:51.309 --> 00:18:52.950
And I've got an episode coming up in a couple

00:18:52.950 --> 00:18:54.970
of weeks where we're going to dive more into

00:18:54.970 --> 00:18:57.750
that. And if you're running an AM directional,

00:18:58.069 --> 00:19:00.650
go walk the site this week. Check the obvious

00:19:00.650 --> 00:19:03.569
stuff. Don't become the next story in radio world.

00:19:04.369 --> 00:19:08.369
And if your FM station qualifies for better HD

00:19:08.369 --> 00:19:11.920
power under the new rules, file the form, what

00:19:11.920 --> 00:19:14.640
do you get to lose? Better HD coverage always

00:19:14.640 --> 00:19:16.779
wins, especially in a lot of cars now. A lot

00:19:16.779 --> 00:19:21.579
of cars now are coming out with HD tuners still,

00:19:21.839 --> 00:19:25.519
so make use of it. Sound good, look good on dash

00:19:25.519 --> 00:19:28.039
too, don't forget about that. And if your station

00:19:28.039 --> 00:19:32.359
still needs C -Band because, well, the fiber,

00:19:32.579 --> 00:19:35.279
the light never quite reached your market, get

00:19:35.279 --> 00:19:38.339
loud. That conversation is happening whether

00:19:38.339 --> 00:19:41.930
you're in it or not. I'm Tyler, this has been

00:19:41.930 --> 00:19:43.470
the Tyler Woodward Project. Thanks for hanging

00:19:43.470 --> 00:19:47.170
out. Follow me on Instagram, bluesky and threads

00:19:47.170 --> 00:19:50.549
at tylerwoodward .me. Make sure you hit up tylerwoodward

00:19:50.549 --> 00:19:52.970
.me also. Got a brand new website up there, got

00:19:52.970 --> 00:19:54.789
a blog, you can check that out. Leave a comment,

00:19:54.970 --> 00:19:58.109
subscribe to the newsletter, get notifications

00:19:58.109 --> 00:20:00.150
when the new episodes come out. And if you're

00:20:00.150 --> 00:20:02.369
listening on Apple Podcasts, Spotify, YouTube,

00:20:02.569 --> 00:20:05.349
or whatever other flavor of podcasting at, give

00:20:05.349 --> 00:20:09.099
the show a like and a review. five stars apparently

00:20:09.099 --> 00:20:11.640
that that helps other people find the show or

00:20:11.640 --> 00:20:14.259
so i'm told i'm hoping for the best we'll see

00:20:14.259 --> 00:20:17.680
what it does and i'll catch you next time thanks

00:20:17.680 --> 00:20:18.099
for listening