Standardisation Activities Towards ISO/IEC MPEG Sample Clauses

Standardisation Activities Towards ISO/IEC MPEG. Fraunhofer IIS is a main contributor to the standardisation of the MPEG-H 3D Audio codec standard and has therefore made a significant number of contributions to MPEG in the reporting period. However, as the development and standardisation of the MPEG-H audio codec itself is not in the scope of the ORPHEUS project, those codec-related contributions are not covered here. In the following we focus on system-related aspects of object-based audio that are driven by ORPHEUS because of the need for a complete transmission chain. Of particular interest is the distribution over the Internet using DASH, for which important contributions have been made. In October 2015 the discussion about signalling object-based audio in DASH was started with an input document by Fraunhofer at the 113th MPEG meeting in Geneva.2 This document addressed the problem of signalling different elements in an object-based audio presentation in a way that they can be accessed more flexibly and streamed only when needed. For example, instead of simulcasting three languages in a single overall stream, only the required language is selected and combined with the main stream in a multi-stream approach. However, this use case requires that the audio elements are accessible on the DASH-level within the MPD and their relationship can be expressed. It was decided that the proposed extension, like Bundles and Partial Adaptation Sets should be included into Amendment 4 (AMD4) of the DASH specification. The proposal was further discussed within MPEG, revised, and the specification text was submitted by Fraunhofer to the 115th MPEG meeting in May 2016.3 The current status of this standardisation effort is documented in an MPEG Output Document from the 116th MPEG meeting4, which includes the agreed specification text that will become part of the DASH specification.
Sample 1
AutoNDA by SimpleDocs

Related to Standardisation Activities Towards ISO/IEC MPEG

  • Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Human and Financial Resources to Implement Safeguards Requirements 6. The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Drug and Alcohol Testing – Safety-Sensitive Functions A. Employees required to have a Commercial Driver’s License (CDL) are subject to pre-employment, post-accident, random and reasonable suspicion testing in accordance with the U.S. Department of Transportation rules, Coast Guard Regulations (46 CFR Part 16) or the Federal Omnibus Transportation Employee Testing Act of 1991. The testing will be conducted in accordance with current Employer policy.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Drug and Alcohol Testing Permitted Testing is permitted where the Employer has reasonable suspicion to believe.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!