Skip to main content

EAS support in RI stack and platform (1.1.4-RELB)

6 replies [Last post]
amirn
Offline
Joined: 2009-05-06
Points: 0

Hi,

I have some general question regarding support for EAS message handling both in OCAP RI and the RI platform.

1. How much support is there currently in OCAP stack implementation? In particular what priorities are supported and how the stack is currently handling EAS messages are start-up and when ocap apps are already running.

2. What are the know issues and/or current limitations with 1.1.4-RELB in the OCAP implementations.

3. Is there any support for displaying EAS message on the RI Platform and are there any settings we need to turn on to enable this?

4. Do we have any Ocap QA apps to test this?

Thanks,
Amir.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
amirn
Offline
Joined: 2009-05-06
Points: 0

I have another question:

It appears that DavicEASMamager implementation does not support OOB message.
See the following method:
protected boolean isOutOfBandAlert()
{
return false; // always an in-band monitor
}

The stack is actually correctly receiving and parsing OOB messages. So this looks like a bug.

cpratt
Offline
Joined: 2008-12-18
Points: 0

There are 2 EAS monitors in the DavicEASManager.

The isOutOfBandAlert() on EASInBandMonitor returns false and isOutOfBandAlert() on the EASOutOfBandMonitor returns true.

OOB EAS has been pretty well tested from what I understand - since the author was also on the CTP team. The directions above (modifying fdc-files.txt) should be exercising the OOB code path.

amirn
Offline
Joined: 2009-05-06
Points: 0

So the other question I have in term of compliance.

I thought the RI stack implementation would handle the following 2 requirements (at least MSO requirements):

1. Block UI events from being sent out to applications (via JVM)
2. Block access to frame buffer to prevent accidental repaints from applications.

Are these not in RI, because not part of SCTE-18 proper, or is this something that has been over-looked in the current implementation.

Thanks,
Amir.

scottdeboy
Offline
Joined: 2009-02-02
Points: 0

Some additional information:

There are EAS test streams as well as an EAS host key listener xlet.

You can find the test streams as well as as README file containing information on how to exercise the streams and run the host key xlet here:
/common/resources/fdcdata/eas-test-files

The README will direct you to change mpeenv.ini's mgrmgr.EAS entry as well as the xait.ignore property. You need to define the xait.ignore property in final.properties (in the same folder as mpeenv.ini), but you don't need to provide a mgrmgr EAS entry (it is already defined correctly in base.properties).

The directions for changing logging levels in mpeenv.ini are correct.

amirn
Offline
Joined: 2009-05-06
Points: 0

So, it looks like we should be able to use the simulated EAS messages on the tru2way device as well.

We are currently using DV-TIDE, but not only the capabilities are limited (text only EAS). But the force tune is not working (EAS priority is hard coded to 11 and Channel info reported is always 0).

greg80303
Offline
Joined: 2008-07-03
Points: 0

Unfortunately, we don't have an EAS expert on the project right now, but I'll tell you everything I know.

About 15 months ago, one of our project members brought the stack up to full compliance with SCTE 18 2007. I believe that the graphical pieces of EAS are implemented and have been tested. However due to lack of audio decode support on the PC Platform, there are certainly pieces of the EAS audio functionality that has not been tested.

The PC Platform supports the delivering of SCTE 18 section data via our virtual OOB channel. At any point, you may update your fdc-files.txt file (located in $RICOMMONROOT/resources) to add a new data file that contains SCTE 18 section(s). The next playout of data from that file (the playout interval can be customized in $PLATFORMROOT/platform.cfg -- RI.Platform.OOBtableRequestPeriod) will cause the stacks EAS section filters to match and you should see EAS.

As I said before, I'm not sure about the level of testing (and I'm pretty sure there are no Xlets since EAS is mostly automatically handled by the stack), so as you experiment with EAS, let us know about any bugs you may find and post them on IssueTracker.

G