5.2.3.1Plan for developing MPEG Reference Encoder for use in Core Experiments
Initially, this is the code base provided by the RM proponent. It is envisioned that this process can result in another Reference Quality encoder. The Audio Subgroup maintains a workplan whose elements are
Define an encoder Block Diagram (e.g. from the WD text)
Define APIs for each block
Designate companies that commit to create source or object code conforming to these APIs
Define a process to check and debug the entire encoder
Additional contributions are welcome
Process for conducting CEs
The CE process of Proposal, Cross-check, Integration are followed. One scenario is that
CE proponent shows the merit of the tool (i.e. listening test results) using the MPEG Reference Encoder
The cross-check shows the merit of the tool (i.e. listening test results) using the RM proponent Reference Quality encoder.
For the CE winner, the proponent is obligated to
Submit informative, but perhaps sub-optimal code for the MPEG Reference Encoder no later than the time of the next MPEG meeting. In addition, this added code must demonstrate an improvement in the performance in the MPEG Reference Encoder (maybe lower performance increment target). However, if the exact code as used in the CE is submitted, the listening test to verify improvement has already been done (as the CE evidence), but a cross-check by other parties on the bitsream generation should be done.
The Chair moved the text in this section to a draft output document for further editing and discussion.
