[EAS] EAS Digest, Vol 13, Issue 54 (force-tune)
Art Leisey
aleisey at trilithic.com
Tue Nov 29 08:21:02 CST 2011
David,
The "force-tune", or more appropriately, the "re-map" command during an
EAS alert on a cable system will be with us for quite a while longer, as
this EAS mechanism was OK'd by the FCC a decade and a half ago and is
hard-coded into millions of analog/digital set-tops, and in many IPTV
set-top architectures. Just about every set-top vendor is well aware of
the issue regarding broadcasters wanting to opt-out of cable system EAS
insertions over their channels, but are powerless to do much about it
until set-tops across the country are either firmware-updated (if
possible) or replaced.
As for analog channels transported directly to a cable-ready set, these
channels normally have EAS applied using baseband, I.F., or RF
substitution on each channel.
Alan,
The suggestion/authorization by FEMA to replace the standard EAN text
with a "test" EAN text came very late in the process. At Trilithic, we
were able to add a one-button "EAN Test" script to our code and allowed
customers to download and upgrade pretty quickly, prior to the Nov. 9th
test, but when code is updated like this, most of the major cable and
Telco labs must take this code in, test it extensively, certify it, and
put it into their release process. There simply was not enough time
before the Nov. 9th test for most major labs to accomplish this. Many
small independents and most broadcasters simply keep their
software/firmware current and rely on the vendor for software integrity.
Some other EAS vendors as well, offered test EAN text but were faced
with the same issues.
Arthur Leisey
Director EAS Division
Trilithic Inc.
________________________________
From: eas-bounces at radiolists.net [mailto:eas-bounces at radiolists.net] On
Behalf Of eas-request at radiolists.net
Send EAS mailing list submissions to
eas at radiolists.net
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.radiolists.net/mailman/listinfo/eas
or, via email, send a message with subject or body 'help' to
eas-request at radiolists.net
You can reach the person managing the list at
eas-owner at radiolists.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of EAS digest..."
Today's Topics:
1. Re: Getting rid of the daisy chain (Barry Mishkind)
2. Re: Cable TV Problems (David Ostmo)
3. Re: Getting rid of the daisy chain (Clay Freinwald)
4. Re: Getting rid of the daisy chain (Clay Freinwald)
5. Re: Cable TV Problems (David Ostmo)
6. Re: Cable TV Problems (Alan Kline)
7. Required Periodic Test (Bill Ruck)
8. Re: No such thing as too much compression (Bill Ruck)
----------------------------------------------------------------------
Message: 1
From: Barry Mishkind <barrym at oldradio.com>
<eas at radiolists.net>
Content-Type: text/plain; charset="iso-8859-1"
At 09:51 AM 11/28/2011, Alex Hartman wrote:
>The broad side of this barn simply cannot be hit with one shot.
>On Mon, Nov 28, 2011 at 10:10 AM, Barry Mishkind <barrym at oldradio.com>
wrote:
>>
>> Repeat after me:
>> One size does not fit all.
>>
------------------------------
Message: 2
From: David Ostmo <dostmo at kabb.sbgnet.com>
<eas at radiolists.net>
Content-Type: text/plain; charset=iso-8859-1
Cable TV operators have a wide variety of equipment in use. Keep in
mind that large cable systems have hundreds of thousands of users.
There are still a large number of cable subscribers who are still using
analog, cable-ready TVs. Analog cable viewers don't have a box to
upgrade. The analog viewers will not see the forced channel tune.
Digital cable boxes are deployed in large quantities with numerous
firmware versions that can react in different ways.
Many small market cable operators are using really old distribution
equipment and can't afford state of the art upgrades due to the limited
size customer base.
The current situation creates a major challenges for the cable operators
large and small.
I totally agree with Clay. Cable operators need to be active
participants in the LECC and SECC. All EAS participants must work
together in the best interest of the public.
David Ostmo
San Antonio, Texas
"Television is the sincerest form of imitation" - Fred Allen
On 11/27/2011 7:08 PM, Clay Freinwald wrote:
>Answer time -
>Do all the cable TV systems in Washington State have the equipment to
carry
>CAP messages like this?
>CF - Cable is another matter with issue of their own, a lot of which is
>based on the type of equipment they purchased and use. This is one
of the
>reasons why Cable needs to be and active participant with SECC's and
LECC's.
>Remember that all of this CAP and Text to Speech stuff is - brand new -
and
>was never considered when this equipment was purchased. We are
certain to
>have a lag as a result.
>Clay
>_______________________________________________
>This is the EAS Forum Discussion List
>Please invite your friends to join our Forum!
>http://lists.radiolists.net/mailman/listinfo/eas
>And, remember the main page: http://eas.radiolists.net
------------------------------
Message: 3
From: Clay Freinwald <k7cr at blarg.net>
<eas at radiolists.net>
Content-Type: text/plain; charset="iso-8859-1"
Good thoughts, Alex -
Also, 99.9991% of the EAS activations in this country originate locally,
not
nationally. Worry about the back yard before you worry about the whole
city,
so to speak. If you can get one state to go with an idea, test it, see
it
work, then you start mirroring it in other states, find the flaws, solve
them, and move on.
The fact is that several states already have addressed this issue and
have
created state and local EAS systems that actually work.
On the flip-side....There are many that have done nothing ....Therein
lies a
big chunk of the problem. I have said, repeatedly, the country looks
like
a checkerboard of functional and dysfunctional EAS systems. There are
a
multitude of places to attach blame.
Clay Freinwald
Washington State SECC
------------------------------
Message: 4
From: Clay Freinwald <k7cr at blarg.net>
<eas at radiolists.net>
Content-Type: text/plain; charset="iso-8859-1"
Amen !!!!
>The broad side of this barn simply cannot be hit with one shot.
>On Mon, Nov 28, 2011 at 10:10 AM, Barry Mishkind <barrym at oldradio.com>
wrote:
>>
>> Repeat after me:
>> One size does not fit all.
>>
------------------------------
Message: 5
From: David Ostmo <dostmo at kabb.sbgnet.com>
<eas at radiolists.net>
Content-Type: text/plain; charset=iso-8859-1
One additional note, from the broadcast TV side we would prefer to have
our channels excluded from forced channel tune, even if it is a national
activation.
David Ostmo
San Antonio, Texas
"Television is the sincerest form of imitation" - Fred Allen
------------------------------
Message: 6
From: Alan Kline <broadcast at snugglebunny.us>
<eas at radiolists.net>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Hear, hear! For one thing, the "force tuning" concept is a little too
"Big Brother" for my taste. For another, we've invested literally
millions in our news and weather operations in order to be the place
where viewers turn in an emergency. It's both good public service and
good business. Having a cable system force-tune our viewers away to a
channel of their choice is counterproductive, both for us and our
audience.
During the National test, our local system force-tuned our audience to a
slate that simply said "This is a national activation of the Emergency
Alert System". That's it. No "TEST" graphic, no audio, no nothing.
Completely useless. Then 3 minutes later, when our DASDEC relayed the
test, we had a proper "TEST" graphic with the audio (such as it was).
The cable system force-tuning our viewers was both superfluous and
confusing to our viewers. The cable graphic did nothing to inform the
viewers of the true nature of what was happening, and if the DASDEC had
fired simultaneously, our viewers would have had no idea what was
happening. (If, of course, they had missed the zillion PSA's and news
stories that preceded the test...)
For Cartoon Network or local access channels or whatever, fine. But
leave us alone to do our job.
Alan
On 11/28/2011 1:46 PM, David Ostmo wrote:
> One additional note, from the broadcast TV side we would prefer to
have our channels excluded from forced channel tune, even if it is a
national activation.
>
> David Ostmo
> San Antonio, Texas
------------------------------
Message: 7
From: Bill Ruck <ruck at lns.com>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Having spent most of this weekend in a turkey and pumpkin pie induced
coma compounded by a head cold I have just been reading the mail.
However, I do have the following suggestion.
We recognize (1) one size does not fit all, (2) tests need to be
meaningful and monitored, (3) parts of the existing system does work
well and (4) this is a chance to start with a blank sheet of paper.
I want to remind all that my goal is "The citizens of the United
States deserve no less than prompt and accurate emergency public
information."
Take a look at this. It is only a rough draft and clearly needs some
of the rough edges cleaned up and the more vague areas clarified.
Eliminate the RWT and RMT and replace it with the Required Periodic
Test (RPT) as follows:
1. Required Periodic Test (RPT) sent on a rotating basis every 15
days starting with the first Monday in January at 12 Midnight. The
next test will be Tuesday at 1 AM; then Wednesday at 2 AM; etc. RPT
rotates through days and hours for a total of 20 tests a year. The
whole nation does the RPT at the same time. (Since the world
revolves around the Beltway use East Coast Time.) Schedule the start
of the RPT for :10 as to not interfere with top of the hour news or
starting programs.
2. Every other RPT (the first test, third, fifth, etc.) will be
originated by a local agency as described in that local operating area
plan.
3. The other RPTs (the second, fourth, sixth, eighth) will be
originated by state and federal agencies on an alternating rotating
basis. The state will originate the second, sixth, tenth, etc., as
described in each state's plan. The feds (White House, FEMA, NWS)
will originate on the fourth, eighth, 12th, etc., as described in the
federal plan.
4. Each RPT will be reported within 72 hours by all
participants. The FCC will set up an intelligent web site (a first
for them) to log the RPTs. Sign in with your Facility ID and
password. Form is pre-filled with identification and
location. Check () YES or () NO. If NO a dialog box appears with
likely sources that can be checked. If OTHER is checked a box
appears to be filled in with the problem. And another box appears
labeled STEPS TAKEN TO RESOLVE PROBLEM.
The data will be mined by the FCC. If a whole area is missing an RPT
then the originating agency for that test gets a visit from the
FCC. If just one participant reports missing the RPT too often they
get a visit from the FCC. The results will be published.
5. Everybody participates. Part 73, cell phones, personal
communications devices, satellite program sources, Internet. Sources
that can not geolocate (e.g. a one way satellite service like Sirius)
is exempt from local and state tests but do have to carry federal
tests. If Earthlink can send emails on how wonderful they are they
can also forward a CAP formatted email message.
6. CAP will be the protocol to be followed.
7. The feds will provide grants to local and state agencies to write
the plan and to support the RPTs. Failure to comply with the plan at
the local and state level will result in the withholding of ALL
federal funding as well as potential loss of ALL Part 90
frequencies. (Justification: Eligibility for Part 90 is "Government
activity protecting life and property." A licensee that fails to
protect life and property by not participating in the plan is no
longer eligible to hold a license.)
8. No broadcast station will originate any RPTs or messages, only
local, state, and federal agencies.
9. Congressional action may be required to implement this plan.
Advantages:
1. All streams to consumers are represented.
2. Both a carrot and a stick are used to encourage local and state
participation.
3. Regular meaningful tests.
4. Tests that are reported.
5. Because each local and state plan can be customized to the needs
of the area and state this is not a "one size fits all" plan.
I know that there are people much smarter than I on this list (like
most of you...) so please improve it.
Bill Ruck
Curmudgeon
San Francisco
------------------------------
Message: 8
From: Bill Ruck <ruck at lns.com>
<eas at radiolists.net>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Clay,
I miss one staff guy at our local NWS office that did his reports in
a perfect Jack Nicholson voice.
NWS now uses pre-recorded words and is much more intelligible.
But CAP will be a free-form text to speech application and that, even
with today's systems, is fraught with complications.
If the voice announcements were in Hawaiian it would be easy to
convert text to voice. But Ahmericun has all sorts of pronunciation
quirks that can not be turned into any look up table.
On the other hand, the audio that I have heard delivered by the CA
state radio system is absolutely unintelligible. Weird sounding
voice is a major improvement.
Bill Ruck
Curmudgeon
San Francisco
PS to Clay: We're in the same general age range. Cranky.
At 09:48 PM 11/27/2011, you wrote:
>Perfect Paul was a very early generation Text Reader that sounded like
Tron.
>
>Bill, great progress has been made with these systems, witness how NWR
>sounds today.
>
>Clay
>(Are you older than me?)
------------------------------
________________________________________________________________________
_______________
This is the EAS Forum Discussion List
Please invite your friends to join our Forum!
http://lists.radiolists.net/mailman/listinfo/eas
And, remember the main page: http://eas.radiolists.net
End of EAS Digest, Vol 13, Issue 54
***********************************
Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged, company confidential and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Information contained in, or documents attached to, this email may contain technology subject to U.S. export control laws. Recipient is solely responsible for ensuring that any export, re-export, transfer or disclosure of this information outside of the United States, or to foreign nationals within the United States, is in accordance with applicable export control laws. If you have received this communication in error, please notify the sender by reply e-mail or collect telephone call and delete or destroy all copies of this e-mail message, any physical copies made of this e-mail message and/or any file attachment(s).
More information about the EAS
mailing list