ISO/IEC 14496-1:2001/FDAM 2
(Amendment)Information technology — Coding of audio-visual objects — Part 1: Systems — Amendment 2: Textual format
Information technology — Coding of audio-visual objects — Part 1: Systems — Amendment 2: Textual format
Technologies de l'information — Codage des objets audiovisuels — Partie 1: Systèmes — Amendement 2: Format textuel
General Information
Relations
Standards Content (Sample)
FINAL ISO/IEC
AMENDMENT
DRAFT 14496-1:2001
FDAM 2
ISO/IEC JTC 1
Information technology — Coding of
Secretariat: ANSI
audio-visual objects —
Voting begins on:
2002-08-29
Part 1:
Systems
Voting terminates on:
2002-10-29
AMENDMENT 2: Textual format
Technologies de l'information — Codage des objets audiovisuels —
Partie 1: Systèmes
AMENDEMENT 2: Format textuel
Please see the administrative notes on page iii
RECIPIENTS OF THIS FINAL DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS, NOTIFI-
CATION OF ANY RELEVANT PATENT RIGHTS OF
WHICH THEY ARE AWARE AND TO PROVIDE
SUPPORTING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC 14496-1:2001/FDAM 2:2002(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 2002
---------------------- Page: 1 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted
under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be
reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,
photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's
member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO/IEC 2002 – All rights reserved
FINAL DRAFT / PROJET FINAL
---------------------- Page: 2 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
In accordance with the provisions of Council Resolution 21/1986, this document is circulated in the
English language only.
© ISO/IEC 2002 – All rights reserved iii
FINAL DRAFT / PROJET FINAL
---------------------- Page: 3 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(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. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
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.
Amendment 2 to ISO/IEC 14496-1:2001 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information.
iv © ISO/IEC 2002 – All rights reserved
FINAL DRAFT / PROJET FINAL
---------------------- Page: 4 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
Information technology – Coding of audio-visual objects
Part 1:
Systems
Amendment 2: Textual format
In subclause 0.2, replace the following sentences:
"
Elementary streams contain the coded representation of either audio or visual data or scene description
information. Elementary streams may as well themselves convey information to identify streams, to describe
logical dependencies between streams, or to describe information related to the content of the streams. Each
elementary stream contains only one type of data.
"
with
"
Elementary streams contain the coded representation of either audio or visual data or scene description
information or user interaction data. Elementary streams may as well themselves convey information to
identify streams, to describe logical dependencies between streams, or to describe information related to the
content of the streams. Each elementary stream contains only one type of data.
"
Then, add the following subclause:
"
0.6.5 Interaction Streams
The coded representations of user interaction information is not in the scope of ISO/IEC 14496. But this
information shall be translated into scene modification and the modifications made available to the
composition process for potential use during the scene rendering.
"
In clause 4, add the following definitions:
"
Interaction Stream
An elementary stream that conveys user interaction information.
Media Node
The following list of time dependent nodes that refers to a media stream through a URL field: AnimationStream,
AudioBuffer, AudioClip, AudioSource, Inline, MovieTexture.
Media stream
One or more elementary streams whose ES descriptors are aggregated in one object descriptor and that are jointly
decoded to form a representation of an AV object.
Media time line
A time line expressing normal play back time of a media stream.
Seekable
A media stream is seekable if it is possible to play back the stream from any position.
Stream object
A media stream or a segment thereof. A stream object is referenced through a URL field in the scene in the form
“OD:n” or “OD:n#” .
"
© ISO/IEC 2002 – All rights reserved
1
FINAL DRAFT / PROJET FINAL
---------------------- Page: 5 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
In subclause 8.2.3.2, replace table 2:
"
Table 2 - List of Class Tags for Commands
Tag value Tag name
0x00 forbidden
0x01 ObjectDescrUpdateTag
0x02 ObjectDescrRemoveTag
0x03 ES_DescrUpdateTag
0x04 ES_DescrRemoveTag
0x05 IPMP_DescrUpdateTag
0x06 IPMP_DescrRemoveTag
0x07 ES_DescrRemoveRefTag
0x08-0xBF Reserved for ISO (command tags)
0xC0-0xFE User private
0xFF forbidden
"
with
"
Table 2 - List of Class Tags for Commands
Tag value Tag name
0x00 forbidden
0x01 ObjectDescrUpdateTag
0x02 ObjectDescrRemoveTag
0x03 ES_DescrUpdateTag
0x04 ES_DescrRemoveTag
0x05 IPMP_DescrUpdateTag
0x06 IPMP_DescrRemoveTag
0x07 ES_DescrRemoveRefTag
0x08 ObjectDescrExecuteTag
0x09-0xBF Reserved for ISO (command tags)
0xC0-0xFE User private
0xFF forbidden
"
After 8.5.5.7.2 (ODExecute), add the following subclause:
"
8.5.5.8 ObjectDescriptorExecute
8.5.5.8.1 Syntax
class ObjectDescriptorExecute extends BaseCommand : bit(8) tag= ObjectDescriptorExecuteTag {
bit(10) objectDescriptorId[(sizeOfInstance*8)/10];
}
8.5.5.8.2 Semantics
The ObjectDescriptorExecute class instructs the terminal that Elementary streams contained therein shall be
opened as the server will transmit data on one or more of the streams. Failure by the terminal to comply may result
in data loss and/or other undefined behavior.
"
© ISO/IEC 2002 – All rights reserved
2
FINAL DRAFT / PROJET FINAL
---------------------- Page: 6 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
In subclause 8.6.4.2 (Semantics), replace Tables 4 and 7 with:
"
Table 4 - sceneProfileLevelIndication Values
Value Profile Level
0x00 Reserved for ISO use -
0x01 Simple 2D profile L1
0x02 Simple 2D profile L2
0x03 Basic 2D profile L1
0x04 Core 2D profile L1
0x05 Core 2D profile L2
0x06 Main 2D profile L1
0x07 Main2D profile L2
0x08 Main 2D profile L3
0x09 Advanced 2D profile L1
0x0A Advanced 2D profile L2
0x0B Advanced 2D profile L3
0x0C-0x7F reserved for ISO use -
0x80-0xFD user private -
0xFE no scene graph profile specified -
0xFF no scene graph capability required -
NOTE — Usage of the value 0xFE indicates that the content described by this InitialObjectDescriptor
does not comply to any scene graph profile specified in ISO/IEC 14496-1. Usage of the value 0xFF
indicates that none of the scene graph profile capabilities are required for this content.
Table 7 - graphicsProfileLevelIndication Values
Value Profile Level
0x00 Reserved for ISO use
0x01 Simple 2D profile L1
0x02 Simple 2D + Text profile L1
0x03 Simple 2D + Text profile L2
0x04 Core 2D profile L1
0x05 Core 2D profile L2
0x06 Advanced 2D profile L1
0x07 Advanced 2D profile L2
0x08-0x7F reserved for ISO use
0x80-0xFD user private
0xFE no graphics profile specified
0xFF no graphics capability required
NOTE — Usage of the value 0xFE may indicate that the content described by this InitialObjectDescriptor
does not comply to any conformance point specified in ISO/IEC 14496-1. Usage of the value 0xFF
indicates that none of the graphics profile capabilities are required for this content.
"
In subclause 8.6.6.2, replace Table 8 with:
"
Table 8 - objectTypeIndication Values
Value ObjectTypeIndication Description
0x03 Interaction Stream
0x04-0x1F reserved for ISO use
"
© ISO/IEC 2002 – All rights reserved
3
FINAL DRAFT / PROJET FINAL
---------------------- Page: 7 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
In subclause 8.6.6.2, replace Table 9 with:
"
Table 9 - streamType Values
streamType value stream type description
0x0A Interaction Stream
0x0B - 0x1F reserved for ISO use
"
In subclause 8.6.7.2 Semantics (of DecoderSpecificInfo), add the following paragraph:
"
For values of DecoderConfigDescriptor.objectTypeIndication that refer to interaction streams,
the decoder specific information is:
class UIConfig extends DecoderSpecificInfo : bit(8) tag=DecSpecificInfoTag {
bit(8) deviceNamelength;
bit(8) deviceName[deviceNamelength];
bit(8) devSpecInfo[sizeOfInstance – deviceNamelength - 1];
}
with
deviceNameLength –indicates the number of bytes in the deviceName field
deviceName –indicates the name of the class of device, which allows the terminal to invoke the appropriate
interaction decoder.
devSpecInfo –is a opaque container with information for a device specific handler.
"
After subclause 8.6.18.13.3 (SegmentDescriptor, MediaTimeDescriptor), add the following new subclauses:
"
8.6.18.14Segment Descriptor
8.6.18.14.1 Syntax
class SegmentDescriptor extends OCI_Descriptor : bit(8) tag=SegmentDescriptorTag {
double start;
double duration;
bit(8) segmentNameLength;
bit(8) segmentName [segmentNameLength];
};
8.6.18.14.2 Semantics
The segment descriptor defines labeled segments within a media stream with respect to the media time line. A
segment for a given media stream is declared by conveying a segment descriptor with appropriate values as part of
the object descriptor that declares that media stream. Conversely, when a segment descriptor exists in an object
descriptor, it refers to all the media streams in that object descriptor. Segments can be referenced from the scene
description through url fields of media nodes.
In order to use segment descriptors for the declaration of segments within a media stream, the notion of a media
time line needs to be established. The media time line of a media stream may be defined through use of media
time descriptor (see 8.6.18.15). In the absence of such explicit definitions, media time of the first composition unit of
a media stream is assumed to be zero. In applications where random access into a media stream is supported, the
media time line is undefined unless the media time descriptor mechanism is used.
start – specifies the media time (in seconds) of the start of the segment within the media stream.
duration – specifies the duration of the segment in seconds. A negative value denotes an infinite duration.
SegmentNameLength – the length of the segmentName field in characters.
© ISO/IEC 2002 – All rights reserved
4
FINAL DRAFT / PROJET FINAL
---------------------- Page: 8 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
segmentName – a Unicode [3] encoded string that labels the segment. The first character of the segmentName
shall be an alphabetic character. The other characters may be alphanumeric, _, -, or a space character.
8.6.18.15MediaTimeDescriptor
8.6.18.15.1 Syntax
class MediaTimeDescriptor extends OCI_Descriptor : bit(8) tag=MediaTimeDescrTag {
double mediaTimeStamp;
};
8.6.18.15.2 Semantics
The media time descriptor conveys a media time stamp. The descriptor establishes the mapping between the
object time base and the media time line of a media stream. This descriptor shall only be conveyed within an OCI
stream. The startingTime, absoluteTimeFlag and duration fields of the OCI event carrying this
descriptor shall be set to 0. The association between the OCI stream and the corresponding media stream is
defined by an object descriptor that aggregates ES descriptors for both of them (see 8.7.1.3).
mediaTimeStamp – a time stamp indicating the media time (MT, in seconds) of the associated media stream
corresponding to the composition time (CT) of the access unit conveying the media time descriptor. Media time
values MT(AU ) of other access units of the media stream can be calculated from the composition time CT(AU ) for
n n
that access unit as follows:
MT(AU ) = CT(AU ) – CT + MT
n n
with MT and CT being the mediaTimeStamp and compositionTimeStamp (converted to seconds) values,
respectively, for the access unit conveying the media time descriptor.
Note – When media time descriptor is used to associate a media time line with a media stream, the notion of “media time zero”
does not necessarily correspond to the notion of “beginning of the stream.
"
Replace subclause 9.2.1.6 with:
"
9.2.1.6 Time
9.2.1.6.1 Stream Objects
A Media Stream consists of one or more elementary streams whose ES descriptors are aggregated in one object
descriptor and that are jointly decoded to form a representation of an AV object. Such streams may be streamed in
response to player requests, in particular in the case of Media nodes that control play back of media. Streams may
be seekable, in which case the stream can be played from any (randomly accessible) time position in the stream, or
they may be non-seekable, in which case the player has no control over the playback of the stream, as is the case
in broadcast scenarios.
9.2.1.6.2 Time-dependent Media Nodes
This specification defines the notion of a Media Node. Such nodes control the opening and playback of remote
streams and are time-dependent nodes.
The url field of a media node shall contain at most one element which must point to a complete media stream, i.e.
it is of the form “OD:n”. Media Nodes may become active or inactive based on the value of their startTime and
stopTime fields. The mediaTime of the played stream is controlled by a MediaControl node, and is not dependent
on the startTime and stopTime in the media Node.
The semantics of the loop, startTime and stopTime exposedFields and the isActive eventOut in time-
dependent nodes are as described in ISO/IEC 14772-1:1998, subclause 4.6.9 [10]. startTime, stopTime and
loop apply only to the local start, pause and restart of these nodes. In the case of media Nodes, these fields affect
the delivery of the stream attached to media nodes as described below. The following media nodes exist:
AnimationStream, AudioBuffer, AudioClip, AudioSource, MovieTexture, TimeSensor.
© ISO/IEC 2002 – All rights reserved
5
FINAL DRAFT / PROJET FINAL
---------------------- Page: 9 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
When a media node becomes active and the stream associate with that media node is already active, the media
node simply joins the session. If the stream is not active when the media node becomes active, the stream
becomes active; i.e. it is played.
When a media node becomes inactive, the stream shall become inactive if there are no other active media nodes
referring to that stream, otherwise the stream remains active.
Loop and speed in a MediaControl node shall over-ride the same fields, when they exist, in any media node
referencing the controlled stream. These fields retain their semantics when no controlling MediaControl node is
present in the scene.
9.2.1.6.3 Time fields in BIFS nodes
Several BIFS nodes have fields of type SFTime that identify a point in time at which an event occurs (change of a
parameter value, start of a media stream, etc). Depending on the individual field semantics, these fields may
contain time values that refer either to an absolute position on the time line of the BIFS stream or that define a time
duration.
As defined in 9.2.1.4, the speed of the flow of time for events in a BIFS stream is determined by the time base of
the BIFS stream. This determines unambiguously durations expressed by relative SFTime values like the
cycleTime field of the TimeSensor node. The time base of a stream can be modified by the
TemporalTransform node which is used to synchronize different streams.
The semantics of some SFTime fields is such that the time values shall represent an absolute position on the time
line of the BIFS stream (e.g. startTime in MovieTexture). This absolute position is defined as follows:
Each node in the scene description has an associated point in time at which it is inserted in the scene graph or at
which an SFTime field in such a node is updated through a CommandFrame in a BIFS access unit (see 9.2.1.3).
The value in the SFTime field as coded in the delivered BIFS command is the positive offset from this point in time
in seconds. The absolute position on the time line shall therefore be calculated as the sum of the composition time
of the BIFS access unit and the value of the SFTime field.
NOTE 1 — Absolute time in ISO/IEC 14772-1:1998 is defined slightly differently. Due to the non-streamed nature of the scene
description in that case, absolute time corresponds to wallclock time in [10].
EXAMPLE � The example in Figure shows a BIFS access unit that is to become valid at CTS. It conveys a node that has an
associated media elementary stream. The startTime of this node is set to a positive value �t. Hence, startTime will occur �t
seconds after the CTS of the BIFS access unit that has incorporated this node (or the value of the startTime field) in the scene
graph.
OCR OCR OCR OCR OCR
OCRstream
BIFS time line
0
t
�
CTS
CTS+ t
����
BIFS AU BIFS AU
BIFS stream
0
Media time line
CU CU CU CU CU CU CU CU CU CU CU CU CU CU CU CU
Media stream
Figure 12 - Media start times and CTS
"
© ISO/IEC 2002 – All rights reserved
6
FINAL DRAFT / PROJET FINAL
---------------------- Page: 10 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
The following sentence should be added to subclause 9.2.2.7.1:
"
In the case of InputSensor, the node includes a reference to an object descriptor that indicates which user
interaction stream is associated with the node.
"
Add a new subclause after subclause 9.2.2.7.2 (URL : segment syntax):
"
9.2.2.7.3 Object descriptor references in URL fields
The url fields in several nodes contain references to media streams. Depending on the profile and level settings
(see clause 15), references to media streams are made through object descriptor Ids. The textual syntax for the url
fields in this case is as follows:
“od:” - refers to the object descriptor with the id .
“od:#” - refers to the stream object defined within the object descriptor with the id
that has the name .
“od:#:” - refers to all stream objects defined within the object
descriptor with the id that start at the same time or later as and that and at the same
time or earlier than
“od:#+” - refers to all stream objects defined within the object descriptor with the id
start start at the same time or later as until the end of the media stream.
"
Replace subclause 9.3.7.20.2 (SFUrl Semantics) with:
"
9.3.7.20.2 Semantics
The “od:” URL scheme is used in an url field of a BIFS node to refer to an object descriptor. The integer
immediately following the “od:” prefix identifies the ObjectDescriptorID. For example, “od:12” refers to object
descriptor number 12.
If the SFUrl refers to an object descriptor, the ObjectDescriptorID is coded as a 10-bit integer. If the SFUrl
refers to a segment of a media stream (“od:12#”) and in all other cases the URL is sent as an
SFString.
"
In subclause 9.4.2, insert the following subclause between the specifications of the Inline node and the Layer2D
node:
"
9.4.2.63 InputSensor
9.4.2.63.1 Node interface
InputSensor {
exposedField SFBool enabled TRUE
exposedField SFString buffer ""
url
exposedField SFString ""
eventOut SFTime eventTime
}
NOTE — For the binary encoding of this node see Annex H.3.11.
9.4.2.63.2 Functionality and semantics
The InputSensor node is used to add entry points for user inputs into a BIFS scene. It allows user events to trigger
updates of the value of a field or the value of an element of a multiple field of an existing node.
Input devices are modelled as devices that generate frames of user input data. A device data frame (DDF) consists
in a list of values of any of the allowed types for node fields. Values from DDFs are used to update the scene. For
example, the DDF definition for a simple mouse is:
© ISO/IEC 2002 – All rights reserved
7
FINAL DRAFT / PROJET FINAL
---------------------- Page: 11 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
MouseDataFrame [[
SFVec2f cursorPosition
SFBool singleButtonDown
]]
Note: The encoding of the DDF is implementation-dependent. Devices may send only complete DDF or sometimes
subsets of DDF as well.
The buffer field is a buffered bit string which contains a list of BIFS-Commands in the form of a CommandFrame
(see 9.3.6.2). Allowed BIFS-Commands are the following: FieldReplacement (see 9.3.6.14),
IndexedValueReplacement (see 9.3.6.15) and NodeDeletion with a NULL node argument (see 9.3.7.3.2). The
buffer shall contain a number of BIFS-Commands that matches the number of fields in the DDF definition for the
th th
attached device. The type of the field replaced by the n command in the buffer shall match the type of the n
field in the DDF definition.
The url field specifies the data source to be used (see 9.2.2.7.1). The url field shall point to a stream of type
UserInteractionStream, which “access units” are DDFs.
When the enabled is set to TRUE, upon reception of a DDF, each value (in the order of the DDF definition) is
placed in the corresponding replace command according to the DDF definition, then the replace command is
executed. These updates are not time-stamped; they are executed at the time of the event, assuming a zero-
decoding time. It is not required that all the replace commands be executed when the buffer is executed. Each
replace command in the buffer can be independently triggered depending on the data present in the current DDF.
th
Moreover, the presence in the buffer field of a NodeDeletion command at the n position indicates that the value
th
of the DDF corresponding to the n field of the DDF definition shall be ignored.
The eventTime eventOut carrying the current time is generated after a DDF has been processed.
EXAMPLE � A typical use of this node is to handle the inputs of a keyboard.
9.4.2.63.3 Adding New Devices and Interoperability
In order to achieve interoperability when defining new devices, the way to use InputSensor with the new device
needs to be specified. The following steps are necessary:
define the content of the DDF definition: this sets the order and type of the data coming from the device and
then mandates the content of the InputSensor buffer.
define the deviceName string which will designate the new device.
define the optional devSpecInfo of UIConfig.
Note: the bitstream syntax does not need to change.
9.4.2.63.4 Keyboard Mappings
The KeySensor mapping is defined as follows.
The KeySensor DDF definition is:
KeySensorDataFrame [[
SFInt32 keyPressed
SFInt32 keyReleased
SFInt32 actionKeyPressed
SFInt32 actionKeyReleased
SFBool shiftKeyChanged
SFBool controlKeyChanged
SFBool altKeyChanged
]]
keyPress and keyRelease events are generated as keys which produce characters are pressed and released on
the keyboard. The value of these events is a string of length 1 containing the single UTF-8 character associated
with the key pressed. The set of UTF-8 characters that can be generated will vary between different keyboards and
different implementations.
actionKeyPress and actionKeyRelease events are generated as 'action' keys are pressed and released on the
keyboard. The value of these events are:
© ISO/IEC 2002 – All rights reserved
8
FINAL DRAFT / PROJET FINAL
---------------------- Page: 12 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
KEY VALUE KEY VALUE KEY VALUE
HOME 13 END 14 PGUP 15
PGDN 16 UP 17 DOWN 18
LEFT 19 RIGHT 20 F1-F12 1-12
shiftKeyChanged, controlKeyChanged, and altKeyChanged events are generated as the shift, alt and control keys
on the keyboard are pressed and released. Their value is TRUE when the key is pressed and FALSE when the key
is released.
The KeySensor UIConfig.devSpecInfo is empty.
The KeySensor deviceName is “KeySensor”
The StringSensor mapping is defined as follows.
The StringSensor DDF definition is:
StringSensorDataFrame [[
SFString enteredText
SFString finalText
]]
The StringSensor UIConfig.devSpecInfo contains 2 UTF-8 strings: the first one is called terminationCharacter and
the second one is called deletionCharacter. When no devSpecInfo is provided, the default terminationCharacter is
‘\r’ and the default deletionCharacter is ‘\b’.
enteredText events are generated as keys which produce characters are pressed on the keyboard. The value of
this event is the UTF-8 string entered including the latest character struck. The set of UTF-8 characters that can be
generated will vary between different keyboards and different implementations. If deletionCharacter is provided, the
previously entered character in the enteredText is removed. The deletionCharacter field contains a string
comprised of one UTF-8 character. It may be a control character. If the deletionCharacter is the empty string, no
deletion operation is provided.
The finalText event is generated whenever a sequence of keystrokes are recognized which match the keys in the
terminationText string. When this recognition occurs, the enteredText is moved to the finalText and the enteredText
is set to the empty string. This causes both a finalText event and an enteredText event to be generated.
The StringSensor deviceName is “StringSensor”
9.4.2.63.5 Mouse Mappings
The Mouse mapping is defined as follows.
The Mouse DDF definition is:
MouseDataFrame [[
SFVec2f position
SFBool leftButtonDown
SFBool middleButtonDown
SFBool rightButtonDown
SFFloat wheel
]]
position is specified in screen coordinates, pixels or meter as specified in the BifsConfig. leftButtonDown becomes
true when the left button is down, and false otherwise. Likewise for the middle and right buttons respectively. wheel
values are: 0 when the wheel is inactive, +1 (resp. –1) when the wheel is moved forward (resp. backward) by one
delta.
The Mouse UIConfig.devSpecInfo is empty.
The Mouse deviceName is “Mouse”.
Note: This mouse mapping can be used with mice with 1 button, 2 buttons or 3 buttons, and possibly a
wheel. DDF fields for missing buttons or wheel are simply never activated.
"
© ISO/IEC 2002 – All rights reserved
9
FINAL DRAFT / PROJET FINAL
---------------------- Page: 13 ----------------------
ISO/IEC 14496-1:2001/Amd.2:2002(E)
After 9.4.2.71 (MatteTexture, MediaBuffer, MediaControl, MediaSensor), add the following subclauses:
"
9.4.2.72 MatteTexture
9.4.2.72.1 Node interface
MatteTexture {
field SFNode surfaceA NULL
surfaceB
field SFNode NULL
field SFNode alphaSurface NULL
exposedField SFString operation “”
field SFBool overwrite FALSE
exposedField SFFloat fraction 0
exposedField MFFloat parameter 0
}
NOTE — For the binary encoding of this node see Annex H.6.2.
9.4.2.72.2 Functionality and semantics
The MatteTexture node uses image compositing operations to combine the image data from two surfaces onto
a third surface. The result of the compositing operation is computed at the resolution of surfaceB. If the size of
surfaceA differs from that of surfaceB, the image data on surfaceA is zoomed up or down before performing
the operation.
The com
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.