Organisation internationale de normalisation

Alternative procedure for handling complicated feature adoptions

The following alternative procedure had been approved at a 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.

5. Common Conditions for HEVC Coding Experiments

Other than the addition of a Chinese text editing sequence to the TGM category of the CTC (see the notes for JCTVC-U0150 (later uploaded as JCTVC-U0188) and the AHG report JCTVC-U0010), no particular changes were noted w.r.t. the prior CTC.

6. Software development

Software coordinators were asked to work out the detailed schedule with the proponents of adopted changes.

Any adopted proposals where software is not delivered by the scheduled date will be rejected.

The planned timeline for software releases was established as follows:

• 
  HM 16.6 available prior to the meeting.
  
• 
  SCM 5.0 (based on HM 16.6 or newer) should be available within 3 weeks after the meeting.
  
• 
  SHM 10.x U1013 (DAM, based on HM 16.2 or newer) should be available within 5 weeks after the meeting.
  

At a previous meeting (Sapporo, July 2014), it was noted that it should be relatively easy to add MV-HEVC capability to the SHVC software, and it was strongly suggested that this should be done. This remains desirable.

8.