hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4 Application Description | The Application Description provides full information on an application, its parameterization, the required activation state of it etc. Specifications based on GEM shall permit the signalling of multiple applications per service, without any arbitrary upper bound less than 255. Data in the Application Description allow... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.1 Application Description transmission and monitoring | It shall be possible to arrange for signalling such that the maximum time interval between the moment the Application Description is updated and the moment the new version is detected by the terminal will be no more than 30 seconds. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.2 Visibility of Application Description and tuning | If an application tunes away from a transport stream where its signalling is carried without selecting a new service, it shall be permitted to continue running even if the Application Description is no longer available to the GEM terminal. GEM terminal specifications for packaged media targets may not support a tuner. ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.3 Content of the Application Description | The Application Description describes applications and their associated information. It shall contain information sufficient to derive the following: Table 11: Application description Function Type application_type enumeration organisation_id 32 bit unsigned integer application_id 16 bit unsigned integer application_co... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.3.1 DVB-J application control codes | The application control codes for DVB-J applications are listed in table 15. Table 15: DVB-J application control code values Code Identifier Semantics 0x00 Reserved_future_use. 0x01 AUTOSTART The file system element(s) (e.g. an Object Carousel module) containing the class implementing the Xlet interface is loaded, The ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.3.2 Application icons descriptor | Zero or one instance of this descriptor shall be included in the application information of an application. It allows icons to be associated with the application. The content format for these possible icons shall be restricted PNG as specified in clause 15.1, "PNG - restrictions". Table 16 shows the syntax of the appli... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.3.3 Graphics constraints descriptor | The graphics constraints descriptor defines the circumstances under which an application can work (or has been tested to work). These circumstances are: • which full screen graphics resolutions an application supports; • whether an application can work when its video is controlled (e.g. scaled to less than full screen ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.4 Applications from previously selected services | If an application with a service_bound_flag of 0 is running when a service selection is performed, it shall continue to run in a newly selected service if the same application is signalled in the new service. NOTE: To efficiently support this feature on services that do not contain the application code, it may be desir... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5 AIT File | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5.1 Syntax | The interaction channel encoding of the Application Description into the AIT File is as follows: • A single file shall contain all of the data. • The file shall contain a concatenation of Application Information Sections (specified in MHP [1], clause 10.4.6, "Syntax of the AIT"). • The possibly multiple sections shall ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5.2 Syntactic restrictions | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5.2.1 Transport protocols | The only allowed transport protocol type has id value 0x0003. The protocol_id is an identifier of the protocol used for carrying applications. The values of the protocol_id are shown in table 21. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 108 Table 21: Protocol_id Protocol_id Description 0x0000 Reserved_future_use. 0x0001 t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5.3 Semantics | The AIT File shall be loaded once during service selection. There is no requirement to monitor or poll the AIT File for any subsequent changes except as part of a subsequent service selection operation referring to the same AIT File. Consequences of this are: • Only the AUTOSTART and PRESENT application control codes (... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.4.5.4 MIME type | The MIME type for an AIT File shall be "application/vnd.dvb.ait". The file extension shall be ".ait". Earlier versions of GEM and derived specifications defined the MIME type for AIT file as application/dvb.ait without the vnd. prefix. This type name is deprecated and its use is strongly discouraged. If a GEM terminal ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.5 DVB-J specific Application Description | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.5.1 General | Additional signalling specific to DVB-J applications shall be present in GEM terminal specifications. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 109 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.5.2 Content of DVB-J Application Description | For each Application Description that refers to a DVB-J application, it shall be possible to signal information sufficient to derive the following. Table 22: DVB-J Application Description Function Type for (i=0; i<N; i++) { dvbj_app_parameter String } base_directory Locator for (i=0; i<N; i++) { classpath_element (opti... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.6 Constant Values | GEM terminal specifications that include the functional equivalent named "Application Signalling" as defined in clause 15.6, "Functional equivalents" and that define additional descriptors in the Application Description shall register the descriptor tag values with the DVB. For information purposes current registration... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.7 Plug-in signalling | Two signalling scenarios are defined for delegated applications and plug-ins: • Native signalling scenario. • GEM signalling scenario. GEM terminal specifications may substitute functionally equivalent signalling, if required. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.7.1 Native signalling scenario | In this scenario it is sufficient for the plug-in to be signalled as a normal GEM application. Optionally it could also be signalled as a plug-in using the Plug-in descriptor (see clause 10.7.4). |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.7.2 GEM signalling scenario | In this scenario GEM plug-in signalling can replace some or all of the native signalling of the delegated application. The GEM signalling allows the GEM terminal to: • Identify that one (or more) delegated applications are available. • The plug-in that is required. • How to start the plug-in. • How to introduce the del... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.7.3 Delegated application descriptor | Zero or one instance of this descriptor can be placed in the Application Description of the delegated application. This optional descriptor allows one or more specific plug-ins to be identified for this delegated application. This overrides the default identification of the plug-in based on the application type signall... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.7.4 Plug-in descriptor | One or more plug-in application descriptors shall be placed in the Application Description of each plug-in. This descriptor defines, for an application that implements a plug-in, the set of delegated application formats that it supports. The descriptor identifies both the type of delegated application supported and the... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8 Stored Applications | GEM terminal specifications may substitute functionally equivalent signalling, if required. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.1 Use of stored application signalling | A GEM terminal that does not provide storage or does not recognize these extensions will perceive storable applications as viable applications that potentially can be run from the service-bound connection. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.1.1 Stored broadcast service related applications | For stored service-bound applications the service-bound Application Description information shall be used when launching the stored application. So, little information from the Application Description needs to be stored with the application. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.1.2 Stored stand-alone applications | For stored stand-alone applications, the Application Description information used when launching the application shall come from a stored representation of the Application Description. While a stored service is being presented in a service context, the following apply: • The applications database shall be populated wit... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.2 Application storage descriptor | The application storage descriptor advertises that an application can be stored and provides some indications of its properties. The presence of this application storage descriptor indicates that an Application Description File is provided for the application (see clause 10.8.3). For a storable application a single app... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.3 Application Description File | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.3.1 Description | The Application Description File provides the list of files that need to be installed as well as other related necessary information. The notation uses an XML-based syntax. For those applications that can be stored, an Application Description File file shall be placed in the same carousel as the application. NOTE: The ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.3.2 Application Description File name and location | The application description file shall be located in the base directory of a DVB-J application (as signalled in the dvb-j application location descriptor). By convention, the name of an ADF is: 'dvb.storage.oooooooo.aaaa' where: oooooooo is the organisation id of the application as a 8 character hexadecimal string aaaa... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.3.3 Syntax | The syntax of the Application Description File is defined by the following XML DTD. The PublicLiteral to be used for specifying this DTD in document type declarations of the XML files is: "-//DVB//DTD Application Description File 1.0//EN" and the URL for the SystemLiteral is: "http://www.dvb.org/mhp/dtd/applicationdesc... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.8.3.4 Semantics | version: A decimal integer denoting the version number of this application. Must not contain leading zeros (unless it is "0"). Must match the version number signalled in the version field of the application storage descriptor in the Application Description entry of this application otherwise the application description... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.9 Signalling for providers | If a GEM terminal includes support for providers, appropriate signalling for a provider export descriptor and a provider usage descriptor must be defined in the GEM terminal specification. The provider export descriptor is used in the Application Description for an application which exports (contains) an XletBoundProvi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11 DVB-J platform | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.1 The virtual machine | The Java platform is defined in PBP 1.1 [4]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2 General issues | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.1 Basic Considerations | Unless otherwise specified, GEM implementations are not required to include any classes or methods marked as deprecated in those API specifications which are either referenced by or included in the present document. Where a class is defined by the present document as implementing a specific interface, and that interfac... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.2 Approach to Subsetting | Where a class included in the present document has methods, fields or constructors with signature dependencies on classes not included in the implemented profile, these methods are not required to be present in an implementation. A compliant implementation choice may require these methods and classes to be present. Whe... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.3 Class Loading | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.3.1 Fundamental principles | The DVB-J application environment shall be written such that each application appears to run within its own classloader or classloader hierarchy for all classes that are not a part of the platform. As a consequence, two applications will never be able to access the same copy of any application-defined static variable. ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.3.2 Class loading and providers | For GEM terminal specifications that include the optional provider APIs (see clause 11.7.9), the above requirement for the classes to be signed with a specific certificate is modified as follows: The classes of the provider shall be signed by a certificate where the organisation_id in the subject field of the certifica... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.4 Unloading | NOTE: Class unloading as required by PBP 1.1 [4] is required. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.5 Event listeners | In org.dvb and org.davic all methods to remove event listeners shall have no effect if the listener is not registered. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 119 NOTE: The number of threads used to send events to event listeners is intentionally implementation dependent. Applications should not block in event listeners ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.6 Event model in DAVIC APIs | Events defined in DAVIC APIs DAVIC 1.4.1p9 [17] which currently directly extend java.lang.Object shall extend java.util.EventObject. Event listeners defined in DAVIC 1.4.1p9 [17] shall extend java.util.EventListener. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.7 Event model in DAVIC and DVB APIs | Each class in org.dvb and org.davic inheriting from java.util.EventObject is just a container for these fields and no validity checks are done for the parameters by this constructor. Instances of these classes are intended to be constructed by the platform implementation and not by applications. The platform implementa... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.8 Tuning as a side-effect | This clause applies only to GEM terminal specifications which include a tuner. No GEM API shall cause tuning unless explicitly specified as such. For example, if a locator that requires tuning is received by the DVBClassLoader it shall behave as if the specified file is not available. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.9 Intra application media resource management | Where an application makes conflicting requests for limited media decoding resources, the media decoding resources that are requested most recently are presumed to be the ones that are most wanted. This applies between MPEG-2 I-Frames, MPEG-2 Video "drips" and streaming video. Similarly, this applies between streaming ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.2.11.1 Text encoding in Service Information | This clause applies only for GEM terminal specifications that include the functional equivalent named "SI" as defined in clause 15.6, "Functional equivalents". Where methods of the DVB SI API or Java TV APIs access strings encoded in the SI tables and return them to applications as String objects, the following charact... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3 Fundamental DVB-J APIs | The present document does not require a particular text encoding for locators, however terminal specifications are required to define such a text encoding. The entities for which a text encoding is required are specified in clause 14.8. Where a locator text encoding is required, a locator may be constructed from the te... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1 Java platform APIs | NOTE: The following packages are defined in PBP 1.1 [4]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1.1 java.lang package | The java.lang package is supported with the following notes and requirements. a) The following fields shall not be used by inter-operable applications: - System.in. b) Applications shall be able to use: - System.out; - System.err; - Runtime.traceInstructions(); - Runtime.traceMethodCalls(); for debugging without any ad... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1.2 java.void | As specified in PBP 1.1 [4], the constants in the java.util.Locale class do not imply support (or otherwise) for these Locales. Locales supported in GEM are specified in profiles (see clause 15.4, "Locale support"). Inter-operable applications shall not call the java.util.TimeZone.setDefault method. The behaviour if th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1.3 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1.4 java.io, javax.microedition.io | The deprecated method java.io.ObjectInputStream.readLine() shall not be called by inter-operable applications. The classes and interfaces in this package relating to files and file systems have additional semantics defined for GEM specific file systems as follows. • For broadcast carousels in clause 11.5.1.1, "Constrai... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.1.5 java.net | Consistent with PBP 1.1 [4], support is required for at least one implementation dependent java.net.URL protocol. Platform methods that return a URL to access resources, such as Class.getResource, ClassLoader.getSystemResource and ClassLoader.getResource shall return instances of java.net.URL using such a protocol wher... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.2 GEM platform APIs | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.2.1 org.dvb.lang | The org.dvb.lang package is supported as defined in Annex I, "DVB-J fundamental classes". Where no parent is specified at creation, the delegation parent classloader of DVBClassLoader shall be the original classloader of the calling application. Classloader delegation is defined in the specification for java.lang.Class... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.2.2 org.dvb.event | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.2.2.1 Generic description | The org.dvb.event package is supported as defined in Annex J, "DVB-J event API". When sending events from a org.dvb.event.EventManager to listeners, the implementation shall ensure that any single listener shall only be sent one platform generated event instance at one time. If a new event is generated before the liste... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.2.2.2 Additional semantics for org.dvb.event | Privileged applications (and no others) shall be able to exclusively reserve the user input events defined in table 87 "Additional input events required by privileged applications". Attempts by applications without this permission to reserve these user input events shall fail. These events shall not be delivered via th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.3.3 Java TV | The Java TV APIs are defined in Java TV [16]. NOTE: This includes the packages javax.tv, javax.media and their subpackages. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4 Presentation APIs | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1 Graphical User Interface API | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.1 The Core GUI API | Property names for use with the getProperty method on java.awt.Image and its sub classes beginning "dvb." are reserved for future use. Applications shall be able to use Toolkit.beep without any adverse effects to the application. The output is not required to be audible to normal end users and shall not conflict with a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.2 TV user interface | The packages org.havi.ui and org.havi.ui.event defined in HAVi [49] shall be supported with the following modifications. The following HAVi UI widgets and supporting classes and interfaces are not required by GEM: • org.havi.ui.HAnimateEffect • org.havi.ui.HAnimateLook • org.havi.ui.HAnimation • org.havi.ui.HDefaultTex... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.3 Extended graphics | See Annex U, "Extended graphics APIs". The class org.dvb.ui.DVBTextLayoutManager is not required by the present document. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.4 Television viewing mode | GEM includes two ways for applications to receive input events: the normal AWT method in java.awt.Component and the org.dvb.event package (see clause 11.3.2.2, "org.dvb.event"). Via the normal AWT method, the application normally receives all input events when the component has the focus. The minimum set of input event... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.5 Font bindings | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.5.1 PFR0 | For fonts in the PFR0 format clause 7.4.1, "PFR", the bindings between the Java APIs relating to font metrics and the font format itself shall be as follows. The return values of the methods FontMetrics.getMaxAscent and FontMetrics.getMaxDescent shall be yOffsetTop and yOffsetBottom respectively as defined in clause D.... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.1.5.2 OpenType | For fonts in the OpenType format as described in clause 7.4.2, "OpenType", the binding between the Java API relating to font metrics and the font format itself shall be as follows. The return values of the methods FontMetrics.getMaxAscent, FontMetrics.getMaxDescent, FontMetrics.getAscent, FontMetrics.getDescent and Fon... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2 Streamed Media API | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.1 Framework of solution | The javax.media and javax.media.protocol packages from Java TV [16] shall be implemented with the clarifications, extensions and restrictions as defined in the corresponding clauses below. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.2 Clarifications | The JMF "time base time" when playing MPEG content delivered in MPEG transport streams is used as a constantly progressing time whose rate may be synthesized from the Program Clock References / the System Time Clock in MPEG or by some other appropriate method. The value does not have any direct relation to the value of... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.3 Default media player behaviour | For a JMF player which is presenting a service, the following rules will be followed in the order given to decide which service components will be presented when multiple audio, video or subtitle components are present in a service: a) For audio and subtitle streams in different languages, user preferences will be used... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.4 Required controls for video drips | The following controls are supported for GEM terminal specifications that support video drips (see clause 7.1.3, "MPEG-2 Video "drips""): • javax.tv.media.AWTVideoSizeControl • org.dvb.media.BackgroundVideoPresentationControl |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5 Extensions to the Framework | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.1 DVB specified extensions | The classes and interfaces defined in Annex N, "Streamed media API extensions" of the present document are included, with the exception of the following: • org.dvb.media.SubtitlingEventControl • org.dvb.media.SubtitleAvailableEvent • org.dvb.media.SubtitleListener • org.dvb.media.SubtitleNotAvailableEvent • org.dvb.med... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.2 Extensions in org.davic | The following classes and interfaces will be included from the org.davic.media package, as defined in Annex L of DAVIC 1.4.1p9 [17]. • MediaPresentedEvent • MediaLocator • MediaTimePositionControl • ResourceWithdrawnEvent • FreezeControl • ResourceReturnedEvent • MediaTimePositionChangedEvent • LanguageNotAvailableExce... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.3 Extensions in javax.tv | In javax.tv.media.MediaSelectControl the InsufficientResourcesException is thrown by the select() method if selecting any service component fails due to a lack of system resources. In javax.tv.media.AWTVideoSize.equals(), the "data members" shall be considered to be the "source" and "dest" parameters used to create the... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.4 Required controls for broadcast profiles and packaged media profiles | The following controls are supported for the broadcast streaming formats specified in clause 7.2, "Media streaming formats": • org.davic.media.LanguageControl • org.davic.media.AudioLanguageControl ETSI ETSI TS 102 728 V1.2.1 (2011-09) 133 • org.davic.media.SubtitlingLanguageControl • org.davic.media.FreezeControl • ja... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.5 Clarifications | In SubtitlingLanguageControl, subtitling being presented shall be defined as the subtitle decoder running. It does not require subtitles to be visible on screen at that time. See clause 13.5, "Subtitles". When a PresentationChangedEvent is generated, the Player in question should re-evaluate the list of controls return... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.6 Component-based JMF players | JMF Players start as background players. Players which do not provide a org.dvb.media.ComponentBasedPlayerControl can only be used to present video in the background and their getVisualComponent method shall always return null. Players that provide an implementation of the org.dvb.media.ComponentBasedPlayerControl are ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.7 Streaming Monitoring API | The Streaming Monitoring API is required in the OTT target. The classes and interfaces are defined in Annex "N.3 Streaming Monitoring API" of the present document. The Streaming monitoring API is used to expose to applications information about streamed CoD played by JMF Player. This API is applicable with Adaptive Str... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8 Media Stream Synchronization API | The media stream synchronization API is an optional extension of the GEM core APIs, which enables to establish a synchronization link between multiple JMF players. It enhances the JMF player model as defined in JavaTV [16], which already defines a limited master/slave concept (See the section "managing controllers" in ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.1 API behavior in border cases | If an application calls a method with a null parameter instead of an object instance, the method throws a NullPointerException. Methods which return an array of elements return an empty array if no element is available. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.2 Establishing a Master/Slave Relationship | A master/slave relationship is a temporary synchronization relationship between JMF players. A player obtains the master role, i.e. it contains the reference clock to which other slave players can be synchronized. The master/slave relationship is established dynamically by adding a player as a slave to another player. ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.3 Adding a Slave | When a slave has been added, the master Player: • Invokes setTimeBase on the slave with the master Player's TimeBase. If this fails, addSlave throws an IncompatibleTimeBaseException. • Synchronizes the slave with the Player using setMediaTime, setStopTime, and setRate. • Takes the added slaves latency into account when... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.6.8.4 Removing a Slave | When a slave is removed from a master Player's control, the master Player: • Resets the slave’s TimeBase to its default. • Recalculates its duration and posts a DurationUpdateEvent if the master Player's duration is changed. • Recalculates its start latency. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.5 Starting a Master Player | In accordance with the behavior for managed players as described in JavaTV, the start behavior is as follows: When you call start on a master Player, all of the slaves managed by the Player are transitioned to the Prefetched state. When the slaves are Prefetched, the master Player calls syncStart with a time consistent... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.6 Setting the Media Time and Rate of a Master Player | In accordance with the behavior for managed players as described in JavaTV, the event handling is as follows: When you call setMediaTime on a master Player, its actions differ depending on whether or not the Player is Started. If the master Player is not Started, it simply invokes setMediaTime on all of the slaves it i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.7 Loss of Synchronization | The API permits to set a synchronization tolerance time value, within which the different Media streams may deviate from the master. If the master/slave player cannot keep the players synchronized within the tolerance value, this condition is reported with a SyncStateChangedEvent. After the synchronization is re-establ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.5.8.8 Event Handling | In accordance with the event behavior for managed players as described in JavaTV, the event handling is as follows: Most events posted by a slave are filtered by the master Player. Certain events are sent directly from the slave through the master and to the listeners registered with the master. To handle the events th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.6 Restrictions on the Framework for Broadcast | Controls that are supported by GEM need not have an associated GUI component. Any calls to Control.getControlComponent() may return null. Developers of GEM applications should not rely on the presence of the following classes or interfaces: • javax.media.CachingControl (unless returned by a call to a JMF method). ETSI ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8 Intersection between Streamed Media API and TV User Interface API | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8.1 Basic Principles | The receiver's output picture shape and/or WSS signalling is normally derived from the configuration of the HVideoDevice and the decoder format conversion being applied, as in "TV behaviour control". When an application has the HGraphicsDevice reserved, the picture shape and/or WSS signalling shall be derived solely fr... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8.2 TV Behaviour Control | The "TV Behaviour Control" in figure 31, "Format control in the presence of a JMF player", is the default video transformation behaviour for JMF players which have none other set. Setting the VideoTransformation to DFC_PLATFORM shall set the video format control to TV behaviour control mode. NOTE 1: In this mode, any c... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8.3 Application Behaviour Control | When a GEM application is controlling video presentation through BackgroundVideoPresentationControl (for video in the background) or VideoPresentationControl and methods on java.awt.Component (for video in a component), the application is responsible for monitoring the incoming video format and changing the video prese... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8.4 Dynamic Behaviour | A JMF player shall attempt to reserve the HVideoDevice instance on entry to the Prefetched state from any state except the Started state. A JMF player in the prefetched or started states which does not have the HVideoDevice reserved shall attempt to reserve it only when the application which created the JMF player call... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.4.2.8.5 Resource Management Details | Inter-operable applications shall not call any of the methods on the instance of ResourceClient returned by HVideoDevice.getClient when a JMF player has reserved that HVideoDevice instance. Inter-operable applications are allowed to call HVideoDevice.releaseDevice or HVideoDevice.setConfiguration directly. GEM terminal... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.