International organisation for standardisation

8.4Alternative procedure for handling complicated feature adoptions

The following alternative procedure had been approved at the preceding meeting as a method to be applied for more complicated feature adoptions:

1. 
   Run CE + provide software + text, then, if successful,
   
2. 
   Adopt into HM, including refinements of software and text (both normative & non-normative); then, if successful,
   
3. 
   Adopt into WD and common conditions.
   

Of course, we have the freedom (e.g. for simple things) to skip step 2.

8.5Common Conditions for HEVC Coding Experiments

Preferred Common Conditions for experiment testing that are intended to be appropriate for both CEs and other experiments were selected by the group and described in output document JCTVC-F900.

8.6Software development

The software coordinator had already started integrating bug fixes on top of HM 3.3 software, and had strongly recommended for proponents of adopted proposals to re-implement them in HM 3.3 and test in this environment before integrating them into HM 4.x. All tools were planned to again be thoroughly tested after integration in HM 4.x.

HM 4.0 should be available within 4 weeks after the meeting, and will be used for CEs. HM 4.1 is planned to be available 3 weeks later.