HEVC Advanced HDR profile and other clarifications

Profil HDR avancé pour HEVC et autres clarifications

General Information

Status
Published
Publication Date
16-Dec-2021
Current Stage
5060 - Close of voting Proof returned by Secretariat
Start Date
26-Nov-2021
Completion Date
25-Nov-2021
Ref Project

RELATIONS

Buy Standard

Draft
ISO/IEC 23000-22:2019/FDAmd 2 - HEVC Advanced HDR profile and other clarifications
English language
12 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

FINAL
AMENDMENT ISO/IEC
DRAFT
23000-
22:2019
FDAM 2
ISO/IEC JTC 1/SC 29
Information technology — Multimedia
Secretariat: JISC
application format (MPEG-A) —
Voting begins on:
2021-09-30
Part 22:
Voting terminates on:
Multi-image application format
2021-11-25
(MIAF)
AMENDMENT 2: HEVC Advanced HDR
profile and other clarifications
Partie 22: Format pour application à images multiples (MIAF)
AMENDEMENT 2
RECIPIENTS OF THIS DRAFT ARE INVITED TO
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPOR TING
DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC 23000-22:2019/FDAM 2:2021(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
DARDS TO WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS. © ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2021

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on

the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below

or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that are

members of ISO or IEC participate in the development of International Standards through technical

committees established by the respective organization to deal with particular fields of technical

activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international

organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the

work.

The procedures used to develop this document and those intended for its further maintenance

are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria

needed for the different types of document should be noted. This document was drafted in

accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or

www.iec.ch/members_experts/refdocs).

Attention is drawn to the possibility that some of the elements of this document may be the subject

of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent

rights. Details of any patent rights identified during the development of the document will be in the

Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC

list of patent declarations received (see https://patents.iec.ch).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to

the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see

www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,

Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.

A list of all parts in the ISO/IEC 14496 series can be found on the ISO and IEC websites.

Any feedback or questions on this document should be directed to the user’s national standards

body. A complete listing of these bodies can be found at www.iso.org/members.html and

www.iec.ch/national-committees.
iii
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)
Information technology — Multimedia application format
(MPEG-A) —
Part 22:
Multi-image application format (MIAF)
AMENDMENT 2: HEVC Advanced HDR profile and other
clarifications
3.3
Replace the definition with the following:

brand indicating that a MIAF file conforms to additional requirements that apply to all MIAF profiles

and that MIAF readers and MIAF renderers that implement these requirements may process the MIAF

file
Clause 3
Add the following new terms and definitions at the end of the clause:
3.16
CICP colour information

metadata provided by a colour information box or property with colour_type equal to 'nclx'

3.17
ICC colour information

metadata provided by a colour information box or property with colour_type equal to 'prof' or 'rICC'

Clause 5
Replace paragraphs two to six with the following:

Clause 7 specifies general requirements that apply to all MIAF profiles. These requirements are split in

two ways:

— requirements at the file format structure level, and requirements at the 'abstraction layer' that the

file format structures create; and
— requirements for both still images, image sequences and video.
Clause 8 specifies constraints which are shared by one or more MIAF profiles.

Clause 9 specifies the coding format(s) that must be supported in any player, independent of any MIAF

profile.

Clause 10 specifies the MIAF application brands that indicate conformance to the normative

requirements of this document, common to all MIAF profiles (as documented in the clauses preceding

the annexes), and the applicable file extensions.
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)

Annex A specifies the MIAF profiles, each of which imposes a set of specific restrictions which shall be

followed for enabling interoperability between MIAF files and MIAF readers.
6.3
Replace the text with the following:

A MIAF image item is independently decodable and represented by an image item that conforms

a) to the box-level requirements for image items in subclause 7.2.1 and
b) to the requirements for image items in subclause 7.3 and

c) to the requirements of a defined MIAF profile, if it exists, and for which a brand should appear in

the FileTypeBox.
6.4
Replace the text with the following:
A MIAF thumbnail image item is a MIAF image item that
a) is referenced as a thumbnail image from a MIAF master image item;

b) has its image data stored in the same file as the MIAF master image item for which it is a thumbnail.

6.5
Replace the text with the following:
A MIAF auxiliary image item is a MIAF image item that

a) conforms also to the requirements for auxiliary image items in subclause 7.3.5;

6.6
Replace the first dashed item in the first dashed list with the following:
— a file compliant to this document

Replace the third dashed item in the "Outputs of a MIAF reader" dashed list with the following:

— the metadata associated with the output image(s), including the content of the
ColourInformationProperty or ColourInformationBox box(es).

Designate the existing NOTE 3 as NOTE 4 and add the following new NOTE before it:

NOTE 3 All colour properties are expected to be parsed by MIAF readers, including all colour types (on-screen

i.e. colour_type equal to 'nclx', constrained and unconstrained ICC profiles), and passed as metadata to the

MIAF renderer.
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)
Replace the last dashed item before the existing NOTE 5 with:

— Otherwise, selectedIds is either empty or a list that has one and only one list element that is set

equal to seedId.
Replace the first paragraph after the existing NOTE 5 with the following:
A MIAF reader concludes an error when any of the following occurs:
Renumber the existing NOTE 5 as NOTE 6 and the existing NOTE 6 as NOTE 7.
Replace the last paragraph and existing NOTE 7 with the following:

For each output image, the MIAF reader returns metadata, such as colour information.

NOTE 8 Decoding of an image item can involve image derivation, or the application of transformative

properties applied in sequence. MIAF readers are expected to only use CICP colour information during decoding,

derivation, transformation or colour conversion, and to ignore ICC colour information.

6.7
Replace the third dashed item in the first dashed list with the following:
— the metadata associated with the output image(s), including the content of the
ColourInformationProperty or ColourInformationBox box(es).
Replace the third paragraph with the following:

MIAF profiles or MIAF application brands may specify the operation of the MIAF renderer. When MIAF

profiles or MIAF application brands do not specify the operation of the MIAF renderer and no other

information of the MIAF renderer operation is available, the MIAF renderer should operate as follows:

Move NOTE 1 after the first bullet point.
Replace NOTE 2 with the following:

NOTE 2 Colour properties and other descriptive properties are expected to be used to enable display

matching. MIAF renderers are expected to use the various colour information from the MIAF reader in the

following order of preference (from most preferred to least preferred): ICC profile information, if available; CICP

colour information, if not set to unknown; application-provided colour information, if available; default CICP

colour information, as defined in 7.3.6.4.
7.2.1.2
Replace the text with the following:

The FileTypeBox should contain, in the compatible_brands list, the 'mif1' brand (specified in ISO/

IEC 23008-12). Some MIAF profiles mandate the presence of this brand.
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)

The FileTypeBox should also contain brands that identify the MIAF profile(s), to which the file conforms

(specified in Annex A or externally), and possibly other brands to which the file conforms.

Files that contain multiple MIAF-compatible tracks or items that comply to different MIAF profiles

should use the TrackTypeBox (in tracks) and the BrandProperty (in items) declaring the MIAF profile of

the track or item, to enable determining to which tracks or items the brands declared in the FileTypeBox

apply.
7.2.1.3, first paragraph
Replace the second sentence with the following:

Any editing operation on the file which changes box sizing or placement is expected to update this index

or remove it to produce a file conformant to ISO/IEC 23001-14.
7.2.1.6
Replace the text with the following:
MIAF profiles may limit the use of data references for image items.
7.2.2.1
Replace the text with the following:

MIAF profiles may limit the use of data references for image sequences and video.

7.2.2.2
Replace the text with the following:

Content protection may be used in a valid MIAF file only if the following is true: if all the protected

content is removed from the file, the remaining file conforms to this document.
7.3.2
Replace the text with the following:
The primary item shall be a MIAF master image item.

When a MIAF profile specified in Annex A or defined in external specifications is listed in the

FileTypeBox, there shall be an image item that conforms to that MIAF profile and is among the set of

items comprised of the primary item and its alternates.
NOTE 7.2.1.8 requires that MIAF image items be unprotected.
7.3.3, last paragraph
Replace the paragraph with the following:
© ISO/IEC 2021 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 23000-22:2019/FDAM 2:2021(E)

There shall be no greater than a factor of 200 between the total number of pixels in a MIAF thumbnail

image item and the next larger MIAF thumbnail image item. There shall be no greater a factor of

200 between the largest thumbnail image item and the associated MIAF master image item.

7.3.5.1, fourth paragraph
Replace the last sentence in the paragraph with the following:

Limits and requirements on auxiliary images may be expressed by specific MIAF profiles.

7.3.5.2, dashed list
Add the following list item at the end of the list:

— Given the semantics above, if a CICP colour property is associated with an alpha auxiliary image

item, full_range_flag shall be set to 1.
7.3.6.4
Replace the text with the following:

All image items, both coded and derived, should be associated with at least one colour information

property.

The handling of colour information by the system (i.e. colour management) is outside the scope of this

document; a renderer takes this information into account when rendering the image(s).

If a coded image has no associated CICP colour property, the default property is defined as having

colour_type equal to 'nclx' with properties as follows:
— colour_primaries equal to 1,
— transfer_characteristics equal to 13,
— matrix_coefficients equal to 5 or 6 (which are functionally identical), and
— full_range_flag equal to 1.

NOTE 1 Any colour information in the bitstream is ignored by the MIAF reader and MIAF renderer processing

models. The colour information property whether explicit or default, takes precedence over any colour

information in the image bitstream.

NOTE 2 When creating a colour property with colour_type equal to ‘nclx’, authors are encouraged to set t

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.