ISO/IEC 23090-14:2025/FDAmd 1

• Status: Not Published
• ICS: 35.040.40 - Coding of audio, video, multimedia and hypermedia information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29/WG 3 - MPEG Systems
• Current Stage: 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
• Start Date: 22-Sep-2026
• Completion Date: 22-Sep-2026

• Amends: ISO/IEC 23090-14:2025 - Information technology — Coded representation of immersive media — Part 14: Scene description
• Effective Date: 24-Aug-2024

Overview

ISO/IEC 23090-14:2025/FDAmd 1 is an amendment to the international standard for the coded representation of immersive media, with a specific focus on scene description. Developed by ISO/IEC JTC 1/SC 29, this amendment adds support for MPEG-I immersive audio, advanced scene understanding, and introduces various extensions to enhance interoperability and scene description capabilities within immersive and extended reality (XR) environments.

The amendment targets implementers and content creators working with MPEG-I systems, providing updates that facilitate richer, more interactive, and spatially aligned user experiences in immersive media applications.

Key Topics

• MPEG-I Immersive Audio Integration

  • Enables linking MPEG-I immersive audio streams with 3D scenes.
  • Supports mapping between visual scene nodes and audio nodes for accurate spatial rendering.
  • Introduces mechanisms to synchronize and align audio-visual experiences for users.

• Scene Understanding and Spatial Computing

  • Describes new scene representation features for improved anchoring and interaction with the physical environment.
  • Adds capabilities to specify spatial descriptors, scan options, light extraction, and semantic labels (e.g., “table”, “wall”) for objects.
  • Supports dynamic updating of scene parameters in response to real-world changes.

• Physics and Interactivity Extensions

  • Expands the scene description language to include precise definitions for physics simulations at both scene and node levels (e.g., gravity, friction, restitution).
  • Allows rich interactivity definitions, supporting multi-user environments and real-time triggers/actions.
  • Enables behavior programming such as collision detection, proximity-based triggers, and user input.

• Data Format and Extension Support

  • Updates support for glTF models, including binary and JSON formats.
  • Defines schema URLs and JSON schema updates for various scene description and extension components.
  • Integrates extensions for advanced lighting models and material properties, crucial for photorealistic rendering.

• Gaussian Splatting Support

  • Introduces specifications for representing Gaussian splats in scene descriptions, supporting progressive streaming and efficient point cloud visualization.

Applications

ISO/IEC 23090-14:2025/FDAmd 1 enables and enhances a wide range of immersive media applications, including:

• Virtual Reality (VR) and Augmented Reality (AR) Content

  • Creates highly interactive and context-aware virtual scenes that respond to user input and environmental factors.
  • Supports advanced audio rendering for spatially correct immersive sound experiences.

• Interactive Media and Gaming

  • Provides a foundation for real-time simulation, physics, and user interactivity that underpin gaming and XR content.
  • Facilitates synchronized audio-visual experiences and realistic scene dynamics.

• Collaborative XR and Training

  • Enables multi-user scenarios and shared experiences, essential for training simulations and remote collaboration.
  • Supports scene state sharing and complex interaction logic crucial for professional applications.

• Multimedia Authoring and Content Distribution

  • Standardizes how immersive content is described, facilitating compatibility across devices, tools, and platforms.
  • Improves interoperability in the creation, editing, and playback of immersive 3D content and audio.

Related Standards

ISO/IEC 23090-14:2025/FDAmd 1 is part of the broader MPEG-I family of standards. Key related standards include:

• ISO/IEC 23090-2: MPEG-I Scene Description - Core standard for describing immersive scenes.
• ISO/IEC 23090-4: MPEG-I Immersive Audio - Standard for immersive audio coding and metadata.
• ISO/IEC 23003-3: MPEG-H 3D Audio - Underlying codec technology for 3D audio experiences.
• glTF Specification: Reference data format for 3D models and scenes, widely used in immersive applications.
• ISO/IEC 23090-xx: Additional extensions and parts addressing other immersive media needs (e.g., video, point clouds, compression).

For schema definitions and further technical resources, visit the ISO scene description schemas directory.

---

This amendment marks a significant advancement in standardizing immersive scene descriptions and supporting robust, interactive user experiences in modern multimedia and XR environments.

FINAL DRAFT
Amendment
ISO/IEC
23090-14:2025/
FDAM 1
ISO/IEC JTC 1/SC 29
Information technology — Coded
Secretariat: JISC
representation of immersive
Voting begins on:
media —
2026-09-22
Part 14:
Voting terminates on:
2026-11-17
Scene description
AMENDMENT 1: Support of MPEG-I
audio, scene understanding and other
extensions
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
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
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.
Reference number
ISO/IEC 23090­14:2025/FDAM 1:2026(en) © ISO/IEC 2026

FINAL DRAFT
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Amendment
ISO/IEC
23090-14:2025/
FDAM 1
ISO/IEC JTC 1/SC 29
Information technology — Coded
Secretariat: JISC
representation of immersive
Voting begins on:
media —
Part 14:
Voting terminates on:
Scene description
AMENDMENT 1: Support of MPEG-I
audio, scene understanding and other
extensions
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.
© ISO/IEC 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/IEC 23090­14:2025/FDAM 1:2026(en) © ISO/IEC 2026

© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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 23090 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.

© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Information technology — Coded representation of
immersive media —
Part 14:
Scene description
AMENDMENT 1: Support of MPEG-I audio, scene understanding
and other extensions
7.3.2
Replace the third bullet in the first paragraph with the following:
— It shall contain a PrimaryItemBox which declares as primary item a resource of type 'model/gltf+json' or
'model/gltf-binary'.
In the fifth bullet of the first paragraph, add the following as a new level 3 bullet:
— for JSON format (.gltf), content_type shall be set to 'model/gltf+json'; For binary format (.bin),
content_type shall be set to 'application/gltf-buffer'; For glTF stored in a GLB container (.glb)
content_type shall be set to 'model/gltf-binary'.

8.1.1
Add the following new paragraph, after the first paragraph:
Once anchored, the elements of the scene may interact with the physical environment. The anchoring
extension also specifies how the representation of this environment may be provided to manage these
interactions and to reach expected AR experience.

8.1.2, Table 28
Add the following new row at the bottom of Table 28:
recommendedSpatial- object O N/A Provides a set of recommended parame-
ComputingConfig ters specifying the needed spatial descrip-
tion. The semantics of this object are given
in Table 59.
Add the following new tables after Table 28:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Table 59 — RecommendedSpatialComputingConfig Object
Name Type Usage Default Description
scanOptions array O N/A Array of options (enumeration) for the scan computa-
tion: possible values are given in
Table 60.
scanDetails object O N/A Specifies the required level of detail for the rep-
resentation. The semantics are presented in Table 61.
scanUpdate object O N/A Specifies the frequency at which the spatial descrip-
tion must be updated (Table 62).
scanVolumes array O N/A Array of bounding volumes that determine the spaces
where scanned objects must be provided. Real scan
objects that intersect one or more of the bounding
volumes should be provided, and all other objects ig-
nored. The semantics for these volumes are presented
in Table 63.
realSemantic array O N/A Semantic descriptions of nodes that are needed
(“table”, “room”, “chair”, “wall”, “light”, “freespace”,
etc.)
lightOptions array O N/A Array of option (enumeration) for the light extraction:
possible values are given in Table 64.
lightUpdate object O N/A Specifies the frequency at which the extraction of real
light must be updated (Table 62).
Table 60 — Possible values for a scanOptions item
Enumeration value Description
PLANE = 0 Request plane data for scanned objects
PLANAR_MESH Request planar meshes for scanned objects
VISUAL_MESH Request 3D visualization meshes for scanned objects
COLLIDER_MESH Request 3D collider meshes for scanned objects
FREE_VOLUME Request to get the available space around a trackable
BOUNDING_BOX Request a simplified collider mesh
TEXTURED_MESH Request mesh with a texture
Table 61 — Semantics for the scanDetail object
Name Type Usage Default Description
primitivesNumber number O N/A Gives the quantity of geometric primitives per cubic
meter (m )
textureOption enumeration O 0 Gives the resolution of the texture of textured meshes.
Possible values are R512X512 (0), R1024X1024 (1) or
R2048X2048 (2).
© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Table 62 — Semantics of a scanUpdate or lightUpdate object
Name Type Usage Default Description
occurrence enumeration O ONCE An occurrence value:
— ONCE = 0: the update is performed only once, for
instance in case of a static real scene,
— N_FRAME: the update is performed periodically,
every N rendering frames, N depending on the
dynamism of the real scene. The N value is provided
in the frameNumber parameter.
— AUTO: the update frequency is managed by
the module that computes the representation.
This module may perform an analysis to detect
significant changes in the real world and start an
update. This analysis may be performed from raw
images data, like RGB images from a camera or
depth images from a depth sensor.
numberOfFrames number O N/A Indicates the periodicity, in number of frames, of the
update, when the occurrences value is N_FRAME.
Table 63 — semantics for a scanVolumes item
Name Type Usage Default Description
type enu mer a- M SPHERE=0, BOX, FRUSTUM
tion
If (type == SPHERE)
center array M 3D coordinates of the center of the sphere
radius number M Radius of the sphere in meters.
If (type == BOX)
pose matrix M 4*4 matrix representing the center position and
orientation of the box
extents array O Edge-to-edge length of the box along each dimension.
If (type == FRUSTUM)
pose matrix M 4*4 matrix representing the position and orientation
of the tip of the frustum
fov vec4 M Angles of the four sides of the frustum
far number M Positive distance of the far plane of the frustum
near number M Positive distance of the near plane of the frustum
3D coordinates are expressed in the XR space related to trackable associated to the anchor.
Table 64 — Possible values for a lightOptions item
Enumeration value Description
DirectionalLight = 0 Request the extraction of directional lights
EnvLight Request the extraction of environment lights
PointLight Request the extraction of point lights
SpotLight Request the extraction of spot lights
AreaLight Request the extraction of area lights

8.1.3
Add the following new paragraphs at the end of the subclause:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
When processing the MPEG_anchor extension, if a recommendedSpatialComputingConfig object is present,
the Presentation Engine checks if it can retrieve the recommended spatial description, specified in the
parameters such as scanOptions, scanDetails, scanUpdate, scanVolumes, scanSemantic, lightUpdate and
lightOptions. If all the recommended parameters are not satisfied, the Presentation Engine may continue the
rendering of the scene with the available spatial description, but possibly with a degraded XR experience.
At runtime, the Presentation Engine may then request elements of the spatial description according to the
recommendedSpatialComputingConfig parameters.

8.2.1
Add the following new paragraph at the end of the subclause:
When specified, at node and/or scene level, a physics object specifies a set of parameters for the physic
engine, used by the application.
8.2.2.1, Table 32
Replace Table 32 with the following table:
Table 32 — Semantic of the MPEG_scene_interactivity extension
Name  Type  Usage  Default  Description
physics object O N/A Provides a set of parameters at scene
level to be used for the physics sim-
ulation. The semantics of this object
are given in Table 65.
triggers array  M  []  Contains the definition of all the
triggers used in that scene
actions array  M  [] Contains the definition of all the
actions used in that scene
behaviors array  M  [] Contains the definition of all the be-
haviors used in that scene. A behav-
ior is composed of a pair of (triggers,
actions), control parameters of trig-
gers and actions, a priority weight
and an optional interrupt action

Add the following text and new table after Table 32:
The semantics of a physics object at scene level, are defined in Table 65.

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Table 65 — Semantics of a scene level physics object
Name  Type  Usage  Default  Description
recommendedPhysicsHighPrecision boolean O false Determines whether the application
should enable a more deterministic
and precise physic simulation
gravity number O -9.81 Determine the gravity for the whole
scene. In meters per second square
-2
(m.s ), as defined in the international
unit system.
recommendedPhysicsFrameRate number O 50 Provides the recommended frame
rate at which the Physics Engine
should operate. In frame per second,
as defined in the international unit
system.
bounceThreshold number O 1 A contact with a relative velocity
below this threshold will not result
in a bounce. In meter per second
-1
(m.s ), as defined in the international
unit system.
8.2.2.1
Add the following text before Table 33:
Annex I gives extra semantics for user input triggers involving multiple users.

8.2.2.2, Table 52
Replace Table 52 with the following table:
Table 52 — Semantic of the MPEG_node_interactivity.trigger extension
Name Type Usage Default Description
type enumera- M One element of Table 34 that defines the type of
tion the trigger.
if (type == TRIGGER_COL-
LISION){
collider integer M the index of the mesh element that provides the
collider geometry for the current node.
The collider mesh may reference a material.
isStatic boolean M If True, the collider is defined as a static collider.
physics object O N/A Provides a set of parameters at node level to be used
for physics simulation. The semantics of this object
are given in Table 66.
primitives ar- O N/A List of primitives used to activate the proximity or
ray(Prim- collision trigger.
itive)
Semantics are presented in Table 35.
}
…
Add the following text and new table after Table 52:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
The semantics of a physics object at node level, are defined in Table 66.
Table 66 — Semantics of a node level physics object
Name  Type  Usage  Default  Description
needPreciseCollisionDe- boolean O false If true, the physics engine should handle the colli-
tection sion detection more accurately by increasing the
detection rate for this node.
-1 -1
linearDamping number O 0 A non-negative value, in second (s ), as defined
in the international unit system. It defines the
linear drag coefficient which corresponds to the
rate of decrease of the linear velocity over time.

It is used to compute a new velocity value V(t) at
each simulation step (dt):
V(t+dt) = V(t)*(1-linearDamping*dt), the velocity
being clamped to 0.
-1 -1
angularDamping number O 0 A non-negative value, in second (s ), as defined
in the international unit system. It defines the an-
gular drag coefficient which corresponds to the
rate of decrease of the angular velocity over time.
It is used to compute a new velocity value V(t) at
each simulation step (dt):
V(t+dt) = V(t)*(1-angularDamping*dt), the veloci-
ty being clamped to 0.
useGravity boolean M Indicates if gravity affects the object
mass number M Mass of the object in kilogram, as defined in the
international unit system.
restitution number M Provides the ratio of the final to initial relative
velocity between two objects after they collide
staticFriction number M Unitless static friction coefficient as defined in
the Coulomb friction law [10]. Friction is the
quantity which prevents surfaces from sliding
off each other. Static friction is used when the
object is lying still. It will prevent the object from
starting to move.
dynamicFriction number M Unitless static friction coefficient as defined in
the Coulomb friction law. When a large enough
force is applied to the object, a dynamic friction
is used and will attempt to slow down the object
while in contact with another.
}
8.2.3, last two paragraphs
Replace the last two paragraphs with the following:
The application shall handle a physics simulation if a physics object is defined at a scene level or/and at any
of the nodes. When a collision occurs between two nodes, the application should calculate the combination
of the restitution, static friction and dynamic friction values based on the values provided by the physics
objects of the two nodes.
8.4.2.2
Replace the second paragraph with the following text and new table:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
The definition of all objects within the MPEG_lights_punctual extension is provided in Table 67.
Table 67 — Definition of glTF file objects MPEG_lights_punctual extension
Name Type Usage Default Description
lights array M An array of items that describe the punctual light sources,
referenced in this scene description document. The seman-
tics of each item is specified in Table 58.

Table 58
Replace the title of Table 58 with: "Definition of item in the lights array of the MPEG_lights_punctual
extension".
A.11
Replace:
MPEG_anchor.anchor schema is downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/
MPEG _anchor/ schema/ MPEG _anchor .anchor .schema .json.
With:
MPEG_anchor.anchor schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/
schemas/ MPEG _anchor .anchor .schema .json.
MPEG_anchor.anchor.recommendedspatialcomputingconfig schema is available at: https:// standards .iso
.org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/ schemas/ MPEG _rec ommendedsp atialcompu tingconfig .schema
.json.
A.13
Replace:
MPEG_scene_interactivity schema is downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/
en/ MPEG _interactivity/ schema/ MPEG _interactivity .schema .json.
With
MPEG_scene_interactivity schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/
amd/ 1/ schemas/ MPEG _interactivity .schema .json.
MPEG_scene_interactivity.physics schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/
en/ amd/ 1/ schemas/ MPEG _interactivity .physicsobject .schema .json.
MPEG_scene_interactivity.trigger.multiuser schema is available at: https:// standards .iso .org/ iso -iec/ 23090/
-14/ ed -2/ en/ amd/ 1/ schemas/ MPEG _interactivity .trigger .multiuserobject .schema .json.

Replace:
MPEG_node_interactivity schema is downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/
en/ MPEG _interactivity/ schema/ MPEG _node _interactivity .schema .json.
With:
© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
MPEG_node_interactivity schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/
1/ schemas/ MPEG _node _interactivity .trigger .schema .json.
MPEG_node_interactivity.physics schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/
en/ amd/ 1/ schemas/ MPEG _node _interactivity .trigger .physicsobject .schema .json.

A.15
Replace:
MPEG_lights_texture_based schema is downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed
-2/ en/ MPEG _lighting/ schema/ MPEG _lights _texture _based .schema .json.
With:
MPEG_lights_texture_based schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/
amd/ 1/ schemas/ MPEG _lights _texture _based .schema .json.

A.16
Replace:
MPEG_light_punctual schema is downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/
MPEG _lighting/ schema/ MPEG _lights _punctual .schema .json.
With:
MPEG_lights_punctual schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/
schemas/ MPEG _lights _punctual .schema .json.
MPEG_lights_punctual.light schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/
amd/ 1/ schemas/ MPEG _lights _punctual .light .schema .json.

Annex A,
Add the following new clauses as follows:
A.19  JSON schema for MPEG_node_mapping
MPEG_node_mapping schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/
schemas/ MPEG _node _mapping .schema .json.

A.20  JSON schema for MPEG_gaussian_splatting_transport
MPEG_gaussian_splatting_transport schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed
-2/ en/ amd/ 1/ schemas/ MPEG _gaussian _splatting _transport .schema .json.

A.21  JSON schema for MPEG_material_stereo
MPEG_material_stereo schema is available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/
schemas/ MPEG _material _stereo .schema .json.

Annex F,
© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
F.1
Replace:
In the example downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ example _MPEG
_media .json, two media items are listed by MPEG_media extension.
With:
In the example available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/ examples/ example
_MPEG _media .json, two media items are listed by MPEG_media extension.

F.4
Replace:
In the example downloadable from https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ example _MPEG
_scene _dynamic .json, the media object includes the patch document format file name and its track index.
With:
In the example available at: https:// standards .iso .org/ iso -iec/ 23090/ -14/ ed -2/ en/ amd/ 1/ examples/ example
_MPEG _scene _dynamic .json, the media object includes the patch document format file name and its track
index.
Annex G
Add the following new clauses as follows:
G.4  Support for MPEG-I immersive audio
G.4.1  General
MPEG-I Immersive Audio has been specified in ISO/IEC 23090-4. The specification assumes the presence
of an MPEG-I immersive audio renderer that will receive the MPEG-I immersive audio bitstream, a set of
MPEG-H audio streams, as well as information about some scene metadata, such as listener’s pose. It will
then use the audio scene metadata in the MPEG-I immersive audio bitstream, the decoded audio data, for
example, from MPEG-H 3D audio (ISO/IEC 23003-3) streams, and the pose information to render the spatial
audio. In case of coded audio data with any other codec, the respective decoder is required.
The support of MPEG-I immersive audio is achieved by referencing an MPEG-I immersive audio stream in a
MPEG-I scene description document.
The MPEG-I immersive audio bitstream contains a description of the audio scene that is independent of
the main scene description consumed by the Presentation Engine. An alignment between the Presentation
Engine and the MPEG-I immersive audio Renderer is needed, that goes beyond the traditional time alignment
but includes also spatial alignment. For that, a mapping need to be established between the node in a MPEG-I
scene description document and the node of the audio scene.
Figure G.4 depicts an example of a mapping between a node that contains a car and an external audio node
in an MPEG-I immersive audio bitstream, with a simplified geometry of that car and the attached audio
sources. This mapping is described in an MPEG node mapping extension.

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Figure G.4 — MPEG-I audio mapping example
This MPEG node mapping extension, identified by MPEG_node_mapping, can be used in a broader scope: It
establishes a mapping between the node in a MPEG-I scene description document and an external entity, e.g.
an MPEG-I immersive audio renderer, that handles a dedicated scene graph, separate from the main scene
description. When present, the MPEG_node_mapping extension shall be included in a node object.
The architecture for the support of such an external renderer is depicted in Figure G.5:
Figure G.5 — Architecture for external render support
The Generic Render Control API is an abstract API that is offered by external renderers to enable applications,
such as Presentation Engines, to control the rendering process by aligning and synchronizing their rendering
state to that of the Presentation Engine. This API is used by the Presentation Engine to configure and update
the status of the external renderer.
G.4.2 Generic Render Control API
Table G.21 describes the functionality provided by the generic render control API:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 23090-14:2025/FDAM 1:2026(en)
Table G.21 — Generic Render Control API
Method Description
init() Initializes the external renderer by providing the related media source information and
their corresponding buffers. It also establishes a session between the Presentation Engine
and the external renderer.
The inputs to this method call should be:
— A media source object that contains a handler to the buffer(s), where the source
media will be made available by the MAF. A description of the media source and the
contents of each buffer shall also be provided.
configure() Configures the external renderer to establish an initial alignment and synchronization
between the Presentation Engine and the external renderer.
The parameters to this method may include:
— A mapping between the initial timestamp of the common Presentation Engine
timeline and that of the media associated with the external renderer. It also
provides information about the clock rate of the Presentation Engine.
— A list of mapped nodes in the source media rendered by the external renderer.
This list shall at least contain one object with a mapping to the main camera of
the main scene description. For audio renderers, this may be the audio listener.
The information is provided by the MPEG_node_mapping extension in the scene
description document. It should also provide the initial pose of the mapped nodes
after applying the 4x4 matrix of the transform parameter provided in the node
mappings.
The external renderer may then subscribe for updates to specific aligned nodes, or it may
specifically ask for current state for these nodes, using the referenceId.
start() Allows the Presentation Engine to control the playback of selected media sources associat-
ed with the external renderer for interactivity purposes.
pause()
resume()
stop()
update() Used by the Presentation Engine to update node positions and orientations for which there
is a mapping with the external renderer. Updates may result from received scene
...

ISO/IEC JTC 1/SC 29/WG 03 N01800

ISO/IEC JTC 1/SC 29/WG 03
MPEG Systems
Convenorship: KATS (Korea, Republic of)
Document type: Output document
nd
Title: Text of ISO/IEC 23090-14 2 edition FDAM 1: Support of MPEG-I
immersive audio, scene understanding and other extensions
Date of document: 2026-05-01
Source: WG03
No. of pages: 38 (with cover page)
Committee URL: https://isotc.iso.org/livelink/livelink/open/jtc1sc29wg3

ISO/IEC 23090-14:2024/DAM 1:2025 (E)
ISO/IEC 23090-14:2025/FDAMFDAmd 1:2025(en)
ISO/IEC JTC1/SC 29
ISO/IEC JTC 1/SC 29
Secretariat: JISC
Date: 2026-05-0109-07
Information technology — Coded representation of immersive
media — —
Part 14:
Scene description — Amendment 1: Support of MPEG-I audio, scene
understanding and other extensions
AMENDMENT 1: Support of MPEG-I audio, scene understanding and other
extensions
FDIS stage
© ISO/IEC 2025 – All rights reserved
© ISO/IEC 20252026
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
Fax: [phone]
EmailE-mail: [e-mail]
Formatted: English (United States)
Website: www.iso.orgwww.iso.org
Formatted: English (United States)
Published in Switzerland
Formatted: English (United States)
Field Code Changed
© ISO/IEC 2026 – All rights reserved
iii
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
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 23090 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.
© ISO/IEC 2026 – All rights reserved
iv
© ISO/IEC 2026 – All rights reserved
v
ISO/IEC 23090-14:2025/DAM 1:2025(en)
Information technology — Coded representation of immersive media
— —
Part 14:
Scene description — Amendment
AMENDMENT 1: Support of MPEG-I audio, scene understanding and
other extensions
7.3.2
Replace the third bullet in the first paragraph with the following:
— It shall contain a PrimaryItemBox which declares as primary item a resource of type 'model/gltf+json' or
'model/gltf-binary'.
In the fifth bullet of the first paragraph, add the following as a new level 3 bullet:
— for JSON format (.gltf), content_type shall be set to 'model/gltf+json'; For binary format (.bin), content_type

shall be set to 'application/gltf-buffer'; For glTF stored in a GLB container (.glb) content_type shall be set to
'model/gltf-binary'.
8.1.1
Add the following new paragraph, after the first paragraph:
Once anchored, the elements of the scene may interact with the physical environment. The anchoring
extension also specifies how the representation of this environment may be provided to manage these
interactions and to reach expected AR experience.

8.1.2, Table 28
Add the following new row at the bottom of Table 28:
recommendedSpatial object O N/A Provides a set of recommended
ComputingConfig parameters specifying the needed spatial
description. The semantics of this object
are given in Table 59.
© ISO/IEC 2025 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)
Add the following tablenew tables after Table 28:

Table 59 — RecommendedSpatialComputingConfig Object
Name Type Usage Default Description
scanOptions array O N/A Array of options (enumeration) for the scan
computation: possible values are given in
Table 8.1- 260.
scanDetails object O N/A Specifies the required level of detail for the
representation. The semantics are presented in
Table 8.1- 361.
scanUpdate object O N/A Specifies the frequency at which the spatial
description must be updated (Table 8.1- 462).
scanVolumes array O N/A Array of bounding volumes that determine the spaces
where scanned objects must be provided. Real scan
objects that intersect one or more of the bounding
volumes should be provided, and all other objects
ignored. The semantics for these volumes are
presented in Table 8.1- 563.
realSemantic array O N/A Semantic descriptions of nodes that are needed
(“table”, “room”, “chair”, “wall”, “light”, “freespace”
…)”, etc.)
lightOptions array O N/A Array of option (enumeration) for the light extraction:
possible values are given in Table 8.1- 664.
lightUpdate object O N/A Specifies the frequency at which the extraction of real
light must be updated (Table 8.1- 4)62).
Table 60 — Possible values for a scanOptions item
Enumeration value Description
PLANE = 0 Request plane data for scanned objects
PLANAR_MESH Request planar meshes for scanned objects
VISUAL_MESH Request 3D visualization meshes for scanned objects
COLLIDER_MESH Request 3D collider meshes for scanned objects
FREE_VOLUME Request to get the available space around a trackable
BOUNDING_BOX Request a simplified collider mesh
TEXTURED_MESH Request mesh with a texture
Table 61 — Semantics for the scanDetail object
Name Type Usage Default Description
primitivesNumber number O N/A Gives the quantity of geometric primitives per cubic
meter (m )
textureOption enumerati O 0 Gives the resolution of the texture of textured
on meshes.
Possible values are R512X512 (0), R1024X1024 (1)
or R2048X2048 (2).
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
Table 62 — Semantics of a scanUpdate or lightUpdate object
Name Type Usage Defaul Description
t
occurrence enumeratio O ONCE An occurrence value:
n
— — ONCE = 0: the update is performed only once,

for instance in case of a static real scene,
— — N_FRAME: the update is performed
periodically, every N rendering frames, N
depending on the dynamism of the real scene. The
N value is provided in the frameNumber parameter.
— — AUTO: the update frequency is managed by the
module that computes the representation. This
module may perform an analysis to detect
significant changes in the real world and start an
update. This analysis may be performed from raw
images data, like RGB images from a camera or
depth images from a depth sensor.
numberOfFrames number O N/A Indicates the periodicity, in number of frames, of the
update, when the occurrences value is N_FRAME.
Table 63 — semantics for a scanVolumes item
Name Type Usage Default Description
type enumerat M  SPHERE=0, BOX, FRUSTUM
ion
If (type == SPHERE)
center array M  3D coordinates of the center of the sphere
radius number M  Radius of the sphere in meters.
If (type == BOX)
pose matrix M  4*4 matrix representing the center position and
orientation of the box
extents array O  Edge-to-edge length of the box along each
dimension.
If (type == FRUSTUM)
pose matrix M  4*4 matrix representing the position and
orientation of the tip of the frustum
fov vec4 M  Angles of the four sides of the frustum
far number M  Positive distance of the far plane of the frustum
near number M  Positive distance of the near plane of the
frustum
3D coordinates are expressed in the XR space related to trackable associated to the anchor.
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)
Table 64 — Possible values for a lightOptions item
Enumeration value Description
DirectionalLight = 0 Request the extraction of directional lights
EnvLight Request the extraction of environment lights
PointLight Request the extraction of point lights
SpotLight Request the extraction of spot lights
AreaLight Request the extraction of area lights

8.1.3
Add the following new paragraphs at the end of the subclause:
When processing the MPEG_anchor extension, if a recommendedSpatialComputingConfig object is present,
the Presentation Engine checks if it can retrieve the recommended spatial description, specified in the
parameters such as scanOptions, scanDetails, scanUpdate, scanVolumes, scanSemantic, lightUpdate and
lightOptions. If all the recommended parameters are not satisfied, the Presentation Engine may continue the
rendering of the scene with the available spatial description, but possibly with a degraded XR experience.
At runtime, the Presentation Engine may then request elements of the spatial description according to the
recommendedSpatialComputingConfig parameters.

8.2.1
Add the following new paragraph at the end of the subclause:
When specified, at node and/or scene level, a physics object specifies a set of parameters for the physic engine,
used by the application.
8.2.2.1, Table 32
Replace Table 32 with the following table:
Table 32 — Semantic of the MPEG_scene_interactivity extension
Name  Type  Usage  Defaul Description
t
physics object O N/A Provides a set of parameters at
scene level to be used for the
physics simulation. The semantics
of this object are given in table 8.2-
1Table 65.
triggers array  M  []  Contains the definition of all the
triggers used in that scene
actions array  M  [] Contains the definition of all the
actions used in that scene
behaviors array  M  [] Contains the definition of all the
behaviors used in that scene. A
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
Name  Type  Usage  Defaul Description
t
behavior is composed of a pair of
(triggers, actions), control
parameters of triggers and actions,
a priority weight and an optional
interrupt action
Add the following text and new table after Table 32:
The semantics of a physics object at scene level, are defined in Table 65.
Table 65 — Semantics of a scene level physics object
Name  Type  Usage  Default  Description
recommendedPhysicsHighPrecision boolean O false Determines whether the
application should enable a more
deterministic and precise physic
simulation
gravity number O -9.81 Determine the gravity for the
whole scene. In meters per
-2
second square (m.s ), as defined
in the international unit system.
recommendedPhysicsFrameRate number O 50 Provides the recommended
frame rate at which the Physics
Engine should operate. In frame
per second, as defined in the
international unit system.
bounceThreshold number O 1 A contact with a relative velocity
below this threshold will not
result in a bounce. In meter per
-1
second (m.s ), as defined in the
international unit system.
8.2.2.1
Add the following text before Table 33:
The annexAnnex I gives extra semantics for user input triggers involving multiple users.

© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)
8.2.2.2, Table 52
Replace Table 52 with the following table:
Table 52 — Semantic of the MPEG_node_interactivity.trigger extension
Name Type Usage Default Description
type enumer M  One element of Table 34 that defines the type of
ation the trigger.
if (type ==
TRIGGER_COLLISION){
the index of the mesh element that provides the
collider integer M
collider geometry for the current node.
The collider mesh may reference a material.
isStatic boolean M  If True, the collider is defined as a static collider.
physics object O N/A Provides a set of parameters at node level to be
used for physics simulation. The semantics of
this object are given in tableTable 66.
primitives array(Pr O N/A List of primitives used to activate the proximity
imitive) or collision trigger.
Semantics are presented in Table 35.
}
…
Add the following text and new table after Table 52:
The semantics of a physics object at node level, are defined in Table 66.
Table 66 — Semantics of a node level physics object
Name  Type  Usag Default  Description
e
needPreciseCollisionDe boolean O false If true, the physics engine should handle the
collision detection more accurately by increasing
tection
the detection rate for this node.
-1 -1
linearDamping number O 0 A non-negative value, in second (s ), as defined
in the international unit system. It  defines the
linear drag coefficient which corresponds to the
rate of decrease of the linear velocity over time.

It is used to compute a new velocity value V(t) at
each simulation step (dt):
V(t+dt) = V(t)*(1-linearDamping*dt), the
velocity being clamped to 0.
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
Name  Type  Usag Default  Description
e
-1 -1
angularDamping number O 0 A non-negative value, in second (s ), as defined
in the international unit system. It defines the
angular drag coefficient which corresponds to
the rate of decrease of the angular velocity over
time.
It is used to compute a new velocity value V(t) at
each simulation step (dt):
V(t+dt) = V(t)*(1-angularDamping*dt), the
velocity being clamped to 0.
useGravity boolean M  Indicates if gravity affects the object
mass number M  Mass of the object in kilogram, as defined in the
international unit system.
restitution number M  Provides the ratio of the final to initial relative
velocity between two objects after they collide
staticFriction number M  Unitless static friction coefficient as defined in
the Coulomb friction law [10]. Friction is the
quantity which prevents surfaces from sliding
off each other. Static friction is used when the
object is lying still. It will prevent the object from
starting to move.
dynamicFriction number M  Unitless static friction coefficient as defined in
the Coulomb friction law. When a large enough
force is applied to the object, a dynamic friction
is used and will attempt to slow down the object
while in contact with another.
}
8.2.3, last two paragraphs
Replace the last two paragraphs with the following:
The application shall handle a physics simulation if a physics object is defined at a scene level or/and at any of
the nodes. When a collision occurs between two nodes, the application should calculate the combination of
the restitution, static friction and dynamic friction values based on the values provided by the physics objects
of the two nodes.
8.4.2.2
Replace the second paragraph and table title with the following text and new table:
The definition of all objects within the MPEG_lights_punctual extension is provided in Table 5867.
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)
Table 58 —67 — Definition of glTF file objects MPEG_lights_punctual extension
Name Type Usage Default Description
lights array M  An array of items that describe the punctual light
sources, referenced in this scene description document.
The semantics of each item is specified in Table 67 58.

Table 67 —58
Replace the title of Table 58 with: "Definition of item in the lights array of the MPEG_lights_punctual
extension".
A.11
Replace:
MPEG_anchor.anchor schema is downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/MPEG_anchor/schema/MPEG_anchor.anchor.schema.json.
With:
MPEG_anchor.anchor schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_anchor.anchor.schema.json.
MPEG_anchor.anchor.recommendedspatialcomputingconfig schema is available at:
https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_recommendedspatialcomputingconfig.schema.json.

A.13
Replace:
MPEG_scene_interactivity schema is downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/MPEG_interactivity/schema/MPEG_interactivity.schema.json.
With
MPEG_scene_interactivity schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_interactivity.schema.json.
MPEG_scene_interactivity.physics schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_interactivity.physicsobject.schema.json.
MPEG_scene_interactivity.trigger.multiuser schema is available at: https://standards.iso.org/iso-iec/23090/-
14/ed-2/en/amd/1/schemas/MPEG_interactivity.trigger.multiuserobject.schema.json.

© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
Replace:
MPEG_node_interactivity schema is downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/MPEG_interactivity/schema/MPEG_node_interactivity.schema.jsonhttps://standards.iso.org/iso-
iec/23090/-14/ed-2/en/MPEG_interactivity/schema/MPEG_node_interactivity.schema.json.
With:
MPEG_node_interactivity schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_node_interactivity.schema.jsonhttps://standards.iso.org/iso-iec/23090/-
14/ed-2/en/amd/1/schemas/MPEG_node_interactivity.trigger.schema.json.
MPEG_node_interactivity.physics schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_node_interactivity.physicsobject.schema.jsonhttps://standards.iso.org/iso-
iec/23090/-14/ed-2/en/amd/1/schemas/MPEG_node_interactivity.trigger.physicsobject.schema.json.

A.15
Replace:
MPEG_lights_texture_based schema is downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/MPEG_lighting/schema/MPEG_lights_texture_based.schema.json.
With:
MPEG_lights_texture_based schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_lights_texture_based.schema.json.

A.16
Replace:
MPEG_light_punctual schema is downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/MPEG_lighting/schema/MPEG_lights_punctual.schema.json.
With:
MPEG_lights_punctual schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_lights_punctual.schema.json.
MPEG_lights_punctual.light schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_lights_punctual.light.schema.json.

Annex A,
Add the following new clauses as follows:
A.19  JSON schema for MPEG_node_mapping
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)
MPEG_node_mapping schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_node_mapping.schema.json.

A.20  JSON schema for MPEG_gaussian_splatting_transport
MPEG_gaussian_splatting_transport schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_gaussian_splatting_transport.schema.json.

A.21  JSON schema for MPEG_material_stereo
MPEG_material_stereo schema is available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/schemas/MPEG_material_stereo.schema.json.

Annex F,
F.1
Replace:
In the example downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/example_MPEG_media.json, two media items are listed by MPEG_media extension.
With:
In the example available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/examples/example_MPEG_media.json, two media items are listed by MPEG_media extension.

F.4
Replace:
In the example downloadable from https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/example_MPEG_scene_dynamic.json, the media object includes the patch document format file name
and its track index.
With:
In the example available at: https://standards.iso.org/iso-iec/23090/-14/ed-
2/en/amd/1/examples/example_MPEG_scene_dynamic.json, the media object includes the patch document
format file name and its track index.

Annex G
Add the following new Clauseclauses as follows:
G.4  Support for MPEG-I immersive audio
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
G.4.1  General
MPEG-I Immersive Audio has been specified in ISO/IEC 23090-4. The specification assumes the presence of
an MPEG-I immersive audio renderer that will receive the MPEG-I immersive audio bitstream, a set of MPEG-
H audio streams, as well as information about some scene metadata, such as listener’s pose. It will then use
the audio scene metadata in the MPEG-I immersive audio bitstream, the decoded audio data, for example, from
MPEG-H 3D audio (ISO/IEC 23003-3) streams, and the pose information to render the spatial audio. In case of
coded audio data with any other codec, the respective decoder is required.
The support of MPEG-I immersive audio is achieved by referencing an MPEG-I immersive audio stream in a
MPEG-I scene description document.
The MPEG-I immersive audio bitstream contains a description of the audio scene that is independent of the
main scene description consumed by the Presentation Engine. An alignment between the Presentation Engine
and the MPEG-I immersive audio Renderer is needed, that goes beyond the traditional time alignment but
includes also spatial alignment. For that, a mapping need to be established between the node in a MPEG-I scene
description document and the node of the audio scene.
The following figureFigure G.4 depicts an example of a mapping between a node that contains a car and an
external audio node in an MPEG-I immersive audio bitstream, with a simplified geometry of that car and the
attached audio sources. This mapping is described in an MPEG node mapping extension.

Figure G.4 — 1: MPEG-I audio mapping example

This MPEG node mapping extension, identified by MPEG_node_mapping, can be used in a broader scope: It
establishes a mapping between the node in a MPEG-I scene description document and an external entity, e.g.
an MPEG-I immersive audio renderer, that handles a dedicated scene graph, separate from the main scene
description. When present, the MPEG_node_mapping extension shall be included in a node object.
The architecture for the support of such an external renderer is depicted in the following figureFigure G.5:
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2024/DAM 1:2025 (E/FDAmd 1(en)

Figure G.4 — 2:5 — Architecture for external render support

The Generic Render Control API is an abstract API that is offered by external renderers to enable applications,
such as Presentation Engines, to control the rendering process by aligning and synchronizing their rendering
state to that of the Presentation Engine. This API is used by the Presentation Engine to configure and update
the status of the external renderer.
G.4.2  Generic Render Control API
Table G.21 describes the functionality provided by the generic render control API:
Table G.21 — Generic Render Control API
Method Description
init() Initializes the external renderer by providing the related media source information and
their corresponding buffers. It also establishes a session between the Presentation Engine
and the external renderer.
The inputs to this method call should be:
— — A media source object that contains a handler to the buffer(s), where the

source media will be made available by the MAF. A description of the media source
and the contents of each buffer shall also be provided.
© ISO/IEC 20252026 – All rights reserved
ISO/IEC 23090-14:2025/DAMFDAmd 1:2025(en)
Method Description
configure() Configures the external renderer to establish an initial alignment and synchronization
between the Presentation Engine and the external renderer.
The parameters to this method may include:
— — A mapping between the initial timestamp of the common Presentation Engine

timeline and that of the media associated with the external renderer. It also
provides information about the clock rate of the Presentation Engine.
— — A list of mapped nodes in the source media rendered by the external renderer.
This list shall at least contain one object with a mapping to the main camera of the
main scene description. For audio renderers, this may be the audio listener. The
information is provided by the MPEG_node_mapping extension in the scene
description document. It should also provide the initial pose of the mapped nodes
after applying the 4x4 matrix of the transform parameter provided in the node
mappings.
The external renderer may then subscribe for updates to specific aligned nodes, or it may
specifically ask for current state for these nodes, using the referenceId.
Allows the Presentation Engine to control the playback of selected media sources
start()
associated with the external renderer for interactivity purposes.
pause()
resume()
stop()
update() Used by the Presentation Engine to update node positions and orientations for which there
is a mapping with the external renderer. Updates may result from received scene updates,
user interactions, animations, physics simulations, or any other events. The Presentation
Engine uses this update() method when one or more mapped nodes need to be spatially
synchronized,
...