The Joint Collaborative Team on Video Coding (jct-vc) of itu-t wp3/16 and iso/iec jtc 1/sc 29/wg 11 held its second meeting during 21-28 July, 2010 at the itu-t premises in Geneva, ch

Plans for TMuC software development:

By the end of this meeting – some bug fixes and VLC integration should be ready for release. Within 7-10 days after, can include intra harmonization per JCTVC-B100, edge-based intra prediction, motion vector scaling, and block merging – and hopefully JCTVC-B074. Somewhat later, adaptive loop filter refinement integration is planned (not affecting the default behavior).

Experiments should use the best software that is available by 9 August or some later more-improved version – both for experiments on evaluation of tools already in the TMuC and additional proposed aspects.

Anchor data from that software will be made available (bitstreams, checksums, Excel spreadsheet) shortly after the corresponding version of the software is made available. This task is assigned to Software integration AHG, and BBC has volunteered to provide an ftp site.

Each proponent who performs an integration that materially affects the software beyond that version (other than fixing a clear error) needs to provide an analysis of the effect of that change.

It is desirable to measure TMuC progression beyond that version. In particular, the “low priority” tools have not been integrated in TMuC so far, but should be tested against the default under the same conditions. should be documented by reporting results as in a TE.

In principle, it is agreed that it should be possible to switch off any coding "tool", either in the config file or in TypeDef.h.

The following issues were raised during the discussion:

• 
  Software copyright handling – noted as an issue, as further discussed in JCTVC-B001.
  
• 
  How do we bring subjective quality more into our process?
  
• 
  Improving encoder descriptions in the TMuC document.
  

The following additional information was brought during the discussion:

MDDT may need to be further optimized, possibly mapping needs to be changed when the harmonization of JCTVC-B100 is implemented.

Loop filter (ALF) modifications are expected to take somewhat longer (2weeks+). Major modifications to VLC encoder (including operational version of RDOQ) most probably only by end of August.

Another discussion was conducted Monday 14:00 on default config files for which a draft was previously submitted via the reflector.

The usage of only B frames for inter-predictive coding was confirmed both for the random access (in that case, forward predictive B rather than P) and low delay cases.

One issue discussed was the potential usage of only one reference frame for L0 and L1 – each would be better in coding efficiency as it would avoid potentially unnecessary encoding of refidx; this would however disable opportunities of multi-hypothesis prediction (B prediction from 2 areas of same frame).

It was suggested that the rate variation measure (RVM) that was used in the CfP testing should be implemented in the software.

It was reconfirmed that interpolation filter type 4 is used for the high complexity case as discussed on Friday.

Currently only one case is known where a tool cannot be switched on and off. The goal is to have all tools switchable (either as config file option or in typedef as compile option).

NRF=1 and hierarchical coding should be set to zero for low-delay case.