Organisation internationale de normalisation

2.5Administrative documents

2.5.1.1.1JVT-Z000 (Admin) List of documents of Antalya meeting

As listed herein.

2.5.1.1.2JVT-Z001-M (Admin) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errata

General project status was reported verbally as described above (see opening remarks).
The latest version of the meeting report of the Shenzhen meeting (marked as draft 5) had been made available on 4 December 2007 (approximately 6 weeks prior to the meeting).
On errata: The JVT-Y210 output of the previous meeting was produced and made available during the current meeting. Other inputs on errata consisted of JVT-Z025, JVT-Z043, and JVT-Z044.

2.5.1.1.3JVT-Z002 (Admin) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, G. J. Sullivan] AHG Report: JM text, ref soft, bitstream, conformance

This document described the activities of the JM text, reference software and bitstream conformance ad hoc group since the last JVT meeting.
On JM Reference Text: There was no activity to report on the JM reference text.
On JM reference software: The professional profile integration has been finished. Several bugs have been found and been fixed. The bug fixing activity is ongoing.
Software releases JM 13.1 and JM 13.2 have been issued.
The following issues were reported to be the most important (volunteers needed):
As the official H.264/AVC reference software, the JM should be a correct source for checking implementations. This means the decoder should be able to decode all valid H.264/AVC bitstreams and the encoder should never create invalid bitstreams. This is currently not the case.
Depending on the configuration the JM encoder can create invalid bitstreams:

• 
  Level constraints are not properly checked
  
• 
  The 16-bit transform requirement is not checked
  
• 
  In Baseline/Main/Extended profile the restriction of CAVLC syntax elements needs proper handling
  

The software coordinators would like to encourage all H.264/AVC experts to volunteer for fixing these issues.

Known Issues / Reporting bugs: A web based bug tracking system has been set up for keeping track of known issues and missing features. The system is publicly accessible but requires registration for entering bug reports.
The system is located at http://ipbt.hhi.de.
This internet site contains also some usage instructions.
Please note that the bug tracking system is using encrypted/secure http (https) for protecting the user’s login. The used certificate is self signed and has to be imported into the user’s web browser. The SHA-1 fingerprint of the certificate is 69:21:86:d9:3e:72:da:3f:e8:30:df:a8:dd:fa:a5:4c:ed:85:b5:09.
A list of known issues and their state can be found at: https://ipbt.hhi.de/mantis/view_all_bug_page.php.
As an annex to the AHG report, a list of the 34 issues identified as active in the bug tracker system (as of 2008-01-14) was provided.
It was requested that certain rules should be followed before reporting any new bugs:

• 
  The database should be searched on whether the same issue was previously reported. If the problem was reported before, but there is additional information, then this information should be added to the original report.
  
• 
  It should be specified if the problem is related to the encoder, decoder or both.
  
• 
  The version of the software used should be specified.
  
• 
  Description of the problem should be as precise as possible.
  
• 
  The necessary steps to reproduce the problem should be described in detail.
  
• 
  If available, the configuration files or/and command line syntax used to run the software should be provided.
  
• 
  The language of the standard should be used when referencing the text description.
  
• 
  After filing the report, the user should check if he/she is requested to provide additional or other information relating to this issue.
  

Bitstream Exchange Activities: Communications related to bitstream exchange activity have taken place on the bitstream exchange reflector ([e-mail]). However this topic was not so active since the last JVT meeting.

The FTP area for downloading bitstream files is on the main JVT Experts FTP site:

ftp://ftp3.itu.int/jvt-site/bitstream_exchange/

The bitstreams can alternatively be accessed from the following http site.

http://ftp3.itu.int/av-arch/jvt-site/bitstream_exchange/

To volunteer a bitstream for testing, contributors are requested to include it in a zip archive along with related files (trace files, configuration, reconstructed frames) in a zip archive and upload it to the dropbox:

ftp://ftp3.itu.int/jvt-site/dropbox using the user ID "avguest" and password "Avguest".

In general, the following naming convention is being followed for the bitstreams in the exchange:

FeatureCode_Source_VersionLetter

Please refer to the spreadsheet and files on the FTP site for examples.
Once a bitstream is uploaded to the dropbox, e-mail should be sent to [e-mail], and/or the bitstream exchange reflector and it will be made available in the bitstream_exchange directory.
To sign up for the bitstream exchange reflector, use the web address given below.

http://mailman.rwth-aachen.de/mailman/listinfo/jvt-bitstream.

No new bitstreams for non-"professional" profiles had been exchanged since the last meeting.
Conformance bitstreams for professional profiles: New conformance bitstreams for High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, CAVLC 4:4:4 Intra, and High 4:4:4 profile were generated and available at JVT ftp site. Additional bitstreams are available for lossless coding.
However, it was found that the JM software (JM13.0 or later) crashed when decoding some conformance bitstreams. The volunteers investigated the problem and found it seems to be a problem in the JM software. The following problems were found:

1. 
   4:2:0 10-bit intra-only: no encoder/decoder match both for luma and chroma
   
2. 
   4:2:2 10-bit intra-only: decoder crashes
   
3. 
   DC quantization for 4:2:2
   

It was confirmed that problem 1 above was fixed in JM13.1, and that problem 3 should be fixed by the next JM release.

Regarding the conformance bitstreams for 4:2:0 8 bit profiles: There was a report that the conformance stream cama1_vtc_c seems to be missing zero_bytes. However this report was not checked yet. This should be investigated further.
The AHG recommended to continue to collect more conformance bitstreams

2.5.1.1.4JVT-Z003 (Admin) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JSVM text, S/W, conf

This document presented the report of the AhG on JSVM text, JSVM software, and SVC conformance.
The text of Joint Scalable Video Model (JSVM-12) was submitted as JVT-Y202. The text of the Joint Scalable Video Model wasn't modified relative to JVT-X202 (JSVM-11).
The JSVM software was submitted as JVT-Y203 and JVT-Y211. It corresponds to CVS tag "JSVM_9_10_DEVEL2". The reported status is summarized in the following.
The following changes had been implemented relative to JVT-X203:

• 
  correction of position calculation for inter-layer intra and residual prediction (including recent changes according to JVT-X201)
  
• 
  correction of subset SPS (syntax and usage)
  
• 
  correction of prefix NAL unit syntax
  
• 
  correction of slice header syntax
  
• 
  correction of IDR support
  
• 
  correction of SVC profile identifications
  
• 
  correction of SEI message identifiers
  
• 
  several bug fixes
  

Furthermore, an effort had been started to improve the decoder implementation (major rewrite) and remove unnecessary code (e.g. tools that are not supported in the standard) from the decoder implementation.

• 
  removal of RCDO
  
• 
  removal of 4-tap upsampling filters
  
• 
  removal of FGS (remaining code parts)
  
• 
  removal of fragmented NAL units
  
• 
  removal of additional "base layer decoder"
  
• 
  clean up of processing order in decoder
  
• 
  clean processing of access units in decoder
  
• 
  general improvement, simplifications of main decoder classes
  

The clean-up of the decoder implementation had not been finished yet. Some of the tools that were implemented in prior versions of the JSVM software were reported to not be supported:

•