13. Multimedia features

13.1 General

Change the bulleted list below the first paragraph as follows:

This clause describes those features of PDF that support embedding and playing multimedia content. It contains the following subclauses:

  • 13.2, "Multimedia" describes the comprehensive set of multimedia capabilities that were introduced in PDF 1.5.
  • 13.3, "Sounds" and 13.4, "Movies" describe deprecated features superseded by 13.7, "Rich media".
  • 13.6, "3D Artwork" describes the capability of embedding three-dimensional graphics in a document, introduced in PDF 1.6.
  • 13.7, "Rich media" describes rich media annotations providing a common framework for video, audio, animations and other multimedia presentations.

13.2 Multimedia

13.2.3 Renditions

13.2.3.1 General

Change Table 277 as follows:

Table 277 - Entries common to all rendition dictionaries
Key Type Value
N text string

(Optional) A UnicodeUTF-16BE-encoded text string specifying the name of the rendition for use in a user interface and for name tree lookup by ECMAScript actions.

13.2.4 Media clip objects

13.2.4.2 Media clip data

Change Table 285 as follows:

Table 285 - Additional entries in a media clip data dictionary
Key Type Value
CT ASCII string

(Optional; shall not be present for form XObjects) An ASCII string identifying the type of data in D. The string should shall conform to the content type specification described in Internet RFC 2045.
MH dictionary

(Optional) A dictionary whose entries (see "Table 287 — Entries in a media clip data MH/BE dictionary" "Table 289 — Entries in a media clip section MH/BE dictionary") shall be honoured for the media clip data to be considered viable.

...

Delete the single sentence paragraph immediately below Table 286 as follows:

An unrecognised value shall be treated as (TEMPNEVER).

...

13.2.7 Other multimedia objects

13.2.7.2 Media players dictionary

13.2.7.2.1 General

Move the last paragraph to below the heading "13.2.7.2.2 Algorithm: Media Player" as follows:

Since both media clip data and media play parameters dictionaries may be employed in a play operation, and each may reference a media players dictionary, there is a potential for conflict between the contents of the two media players dictionaries.

13.2.7.2.2 Algorithm: Media Player

Since both media clip data and media play parameters dictionaries may be employed in a play operation, and each may reference a media players dictionary, there is a potential for conflict between the contents of the two media players dictionaries.

13.6 3D Artwork

13.6.2 3D annotations

Change the first paragraph as follows:

3D annotations (PDF 1.6) are a way to include 3D artwork in PDF documents. Rich media annotations are another method (see 0 "
Rich media"13.7 "Rich media"). "Table 309 — Additional entries specific to a 3D annotation" shows the entries specific to a 3D annotation dictionary. "Table 166 — Entries common to all annotation dictionaries" describes the entries common to all annotation dictionaries.

13.6.3 3D streams

13.6.3.1 General

Change Table 311 as follows:

Table 311 - Entries in a 3D stream dictionary
Key Type Value
ColorSpace name or array (Optional, PDF 2.0) The RGB colour space in which the 3D artwork's colour values are encoded. Valid values are the name DeviceRGB, an array specifying a valid CalRGB color space (see 8.6.5.3 "CalRGB colour spaces"), or an array specifying a valid RGB-based ICCBased color space (see 8.6.5.5 "ICCBased colour spaces"). If the name is DeviceRGB and the page where the annotation referencing the 3D stream is used has a DefaultRGB color space, then the DefaultRGB color space shall be used (see 8.6.5.6 Default colour spaces). If this key is not present, the colour space for the 3D artwork colour values are is considered undefined and a PDF processor may choose any appropriate RGB-based colour space, such as sRGB.
Resources name tree

(Optional; Deprecated in PDF 2.0) A name tree that maps name strings to objects that may be used by applications or scripts to modify the default view of the 3D artwork.

The names in this name tree shall be text strings so as to be encoded in a way that will be accessible from ECMAScript.

NOTE Resources was deprecated in PDF 2.0 because it was insufficiently specified to ensure interoperable implementations.

13.6.4 3D Views

13.6.4.1 General

Change Table 315 as follows:

Table 315 - Entries in a 3D view dictionary
Key Type Value
P dicionary

...

Default value: a projection dictionary where the value of Subtype is PerspectiveP (perspective), the value of FOV is 90, and all other entries take their default values.

NA array

(Optional; PDF 1.7; meaningful only if NR is present) An array ...

13.6.4.3 3D background dictionaries

Insert the following new paragraph before the existing NOTE:

PDF processors that render 3D data streams shall do so directly and without regard to keys and values in the annotation dictionary that define appearance streams or how appearance streams would be rendered onto the page. They shall ignore the values of the C, IC, Border, BS, BE, BM, CA and ca keys from "Table 166 - Entries common to all annotation dictionaries".

...

Change Table 317 as follows:

Table 317 - Entries in a 3D background dictionary
Key Type Value
CS name or array

(Optional) The colour space of the background. The only valid value shall be the name DeviceRGB.

Default value: DeviceRGB.

PDF consumers shall be prepared to encounter other values that may be supported in future versions of PDF.
C (various) array

(Optional) An array of 3 numbers in the range 0.0 to 1.0, representing the The colour of the background in the colour space defined by CS.

Default value: an array [1 1 1] representing the colour white when the value of CS is DeviceRGB.

13.6.4.6 3D cross section dictionaries

Change Table 322 as follows:

Table 322 - Entries in a 3D cross section dictionary
Key Type Value
PV boolean

(Optional) A flag indicating the visibility of the cutting plane. If true, then the cutting plane shall be visible. If false, then the cutting plane shall not be visible.
Default value: true

IV boolean

...

Default value: false true

13.6.4.7 3D node dictionaries

Change Table 323 as follows:

Table 323 - Entries in a 3D node dictionary
Key Type Value
N text string

(Required) The name of the node being described by the node dictionary. All names in the node dictionary shall be unique. Interpretation of this entry shall depend upon the 3D format specified in the Subtype entry in "Table 311 — Entries in a 3D stream dictionary" as described below: and annotation type as defined in Table 323a below.

U3D If the Subtype of the corresponding 3D Stream is U3D, this entry shall correspond to the field Node block name, specified in the Universal 3D file format.

PRC (PDF 2.0) If the Subtype of the corresponding 3D Stream is PRC, this entry shall be the Unique Identifier (UUID) as specified in ISO 14739-1.

NOTE 1 When comparing this entry to node names for a particular convention (such as Universal 3D or PRC)3D model format, PDF processors will need to translate between the PDF text encoding used by PDF and the character encoding specified in the stream specified in the 3D stream.

NOTE 2 The description of the value of the N key was clarified in this document (2020).

Insert this new table below Table 323:

Table 323a - Interpretation of 3D Node Subtype entry
3D model format When using a 3D annotation When using a RichMedia annotation (PDF 2.0)
U3D The Subtype of the corresponding 3D Stream shall be U3D (see Table 311 "Entries in a 3D stream dictionary") and the value of the N entry in the 3D node dictionary (see Table 323 "Entries in a 3D node dictionary") shall correspond to the field Node block name, specified in the Universal 3D file format (ECMA-363). (PDF 2.0) The Subtype of the corresponding Embedded File Specification dictionary (see Table 44 "Additional entries in an embedded file stream dictionary") shall be the registered IANA MIME media type for U3D "model/u3d" (when expressed as a PDF name is model#2Fu3d) and the value of the N entry in the 3D node dictionary (see Table 323 "Entries in a 3D node dictionary") shall correspond to the field Node block name, specified in the Universal 3D file format (ECMA-363).
PRC (PDF 2.0) (PDF 2.0) The Subtype of the corresponding 3D Stream shall be PRC (see Table 311 "Entries in a 3D stream dictionary") and the value of the N entry in the 3D node dictionary (see Table 323 "Entries in a 3D node dictionary") shall be the Unique Identifier (UUID) as specified in ISO 14739-1. (PDF 2.0) The Subtype of the corresponding Embedded File Specification dictionary (see Table 44 "Additional entries in an embedded file stream dictionary") shall be the registered IANA MIME media type for PRC "model/prc" (when expressed as a PDF name is model#2Fprc) and the value of the N entry in the 3D node dictionary (see Table 323 "Entries in a 3D node dictionary") shall be the Unique Identifier (UUID) as specified in ISO 14739-1.
STEP (PDF 2.0; see ISO/TS 24064) Prohibited. (PDF 2.0) The Subtype of the corresponding Embedded File Specification dictionary (see Table 44 "Additional entries in an embedded file stream dictionary") shall be one of the registered IANA MIME media types for STEP ("model/step", "model/step+xml", "model/step+zip", "model/step-xml+zip") and the value of the N entry in the 3D node dictionary (see Table 323 "Entries in a 3D node dictionary") shall be the unique identifier (UUID), specified in the STEP AP 242 stream.

13.6.7 Persistence of 3D measurements and markups

13.6.7.3 3D measurement/markup dictionary

13.6.7.3.6 3D comment note

Modify Table 331 as follows:

Table 331 - Additional entries in a 3D measurement/markup dictionary for a 3D comment note
Key Type Value
S dictionary (Optional; PDF 2.0) A comment reference is an indirect reference to a projection annotation that may be associated with this 3D measurement. See "Table 341 — Entries in a RichMediaContent dictionary". See 13.6.7.4, "3D measurements and projection annotations" .

13.7.2 RichMedia annotations

13.7.2.1 General

Modify the first paragraph as follows:

The annotation subtype RichMedia shares many low-level structural similarities with the 3D Artwork defined in 13.6, "3D Artwork". At the top level, the rich media annotation has two primary custom structures. The RichMediaSettings dictionary is , if present, shall be unique to each annotation, while the RichMediaContent dictionary can be shared across rich-media annotations.

...

Change Table 333 as follows:

Table 333 - Additional entries specific to a RichMedia annotation
Key Type Value
RichMediaSettings dictionary

(Optional; PDF 2.0) A RichMediaSettings dictionary that shall be unique to each annotation and stores conditions and responses that determine when the annotation should be activated and deactivated by an interactive PDF processor and the initial state of artwork in those states. See "Table 334 — Entries in a RichMediaSettings dictionary".

...

13.7.2.2 RichMediaSettings dictionary

13.7.2.2.1 General

Modify the first paragraph as follows:

The RichMediaSettings dictionary has a purpose similar to that of the 3D activation dictionary ("Table 310 — Entries in a 3D activation dictionary") with the 3D Annotation described in 13.6.2, "3D Annotations". The RichMediaSettings dictionary stores the conditions and responses that occur in response to certain events, such as activation and deactivation of the annotation, and contains two dictionaries. It shall be unique to each annotation. "Table 334 — Entries in a RichMediaSettings dictionary" gives the details of the content of this dictionary.

13.7.2.2.2 RichMediaActivation dictionary

Change Table 335 as follows:

Table 335 - Entries in a RichMediaActivation dictionary
Key Type Value
View dictionary

(Optional; PDF 2.0) An indirect object reference to a 3D view dictionary (see "Table 315 — Entries in a 3D view dictionary"13.7.2.3.5, "View dictionary" that shall also be referenced by the Views array within the annotation’s RichMediaContent dictionary (see "Table 341 — Entries in a RichMediaContent dictionary").

Default value: The first element in the Views array of the annotation specified in the RichMediaContent dictionary RichMediaContent dictionary specified in the annotation. If a Views array does not exist, default values for the components of a 3D view dictionary (see "Table 344 — Additional entries in a 3D view dictionary") are used.
Scripts array

(Optional; PDF 2.0) An array of indirect object references to file specification dictionaries, each of which describe a JavaScript file that shall be present in the Assets name tree of the RichMediaContent dictionary. If the array has no elements, no script is executed.

Default value: an empty array.

13.7.2.3 RichMediaContent dictionary

13.7.2.3.1 General

Change Table 341 as follows:

Table 341 - Entries in a RichMediaContent dictionary
Key Type Value
Configurations array

(Optional Required; PDF 2.0) A non-empty array where each element is an indirect object reference to a RichMediaConfiguration dictionary.
Views array

(Optional; PDF 2.0) An array where each element is an indirect object reference to a 3D view dictionary. See "Table 315 — Entries in a 3D view dictionary" for the details of the entries of this dictionary13.7.2.3.5, "View dictionary".

...
13.7.2.3.4 RichMediaInstance dictionary

Change Table 343 as follows:

Table 343 - Entries in a RichMediaInstance dictionary
Key Type Value
Asset dictionary

(Required; PDF 2.0) A dictionary that shall be an indirect object reference to a file specification dictionary that is also may also be referenced in the Assets name tree specified in the RichMediaContent dictionary of the annotation.

NOTE the RichMedia asset itself is not referenced by name, however other assets may be referenced from the RichMedia asset by name and thus need to be in the Assets name tree.

Last modified: 19 July 2024