Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
  • G06T17/00—Three-dimensional [3D] modelling for computer graphics
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
  • G06T2200/00—Indexing scheme for image data processing or generation, in general
  • G06T2200/24—Indexing scheme for image data processing or generation, in general involving graphical user interfaces [GUIs]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
  • G06T2210/00—Indexing scheme for image generation or computer graphics
  • G06T2210/61—Scene description
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
  • G06T2219/00—Indexing scheme for manipulating 3D models or images for computer graphics
  • G06T2219/20—Indexing scheme for editing of 3D models
  • G06T2219/2012—Colour editing, changing, or manipulating; Use of colour codes

Definitions

• the present invention relates to scenegraphs and more particularly to the accessibility and control of parameters during the rendering of a scenegraph.
• a scenegraph is a hierarchical structure composed of nodes, also called Objects, which can be either grouping nodes (intersection between branches) or leaves.
• nodes also called Objects, which can be either grouping nodes (intersection between branches) or leaves.
• Such structure is usually used as storage for 2D or 3D Graphics information (e.g., Geometrical Model) and their composition in order to render them.
• a scenegraph can include animation information formed by either temporal interpolation means or frame based animation (e.g., in the case of Macromedia Flash). It can also contain sensors representing allowed User Interactions with the scene or objects composed within. Such animation must be fully described and interaction triggers routed correctly within the scenegraph in order to operate correctly.
• Scenegraphs in the Computer Graphics domain has been generalized for several years.
• 3D Authoring Tools e.g., Autodesk 3D Studio or Maya
• 3D Rendering engines e.g., Pixar RenderMan
• scenegraphs as data structures and as file formats for interchange (e.g., VRML, COLLADA).
• User controls during the rendering of a scenegraph are relatively limited, due to the fact their description must be embedded in the scenegraph. That is, unfortunately, there is no easy means in currently available technologies for defining direct Application User Interface controls for animations and parameters within a scenegraph or during rendering of the same.
• Embodiments of the present invention provide an easy means to enable control of the parameters of a scenegraph and a method to treat those controls and present them to the user at the application level. Embodiments of the present invention also enable the definition of constraints for the user interaction, using value ranges, increments, defaults, and user or platform profiles for allowing or not allowing certain controls.
• a method for controlling a scenegraph includes redefining a set of elements within a scene graph, accessing selected information in the scenegraph in accordance with the redefined elements, and providing means for controlling the selected information.
• a system for controlling a scenegraph includes a means for redefining a set of elements within a scenegraph, a means for accessing selected information in the scenegraph in accordance with the redefined elements, and a means for controlling the selected information
• Figure 1 depicts a flow diagram of a process for enabling the control of scenegraph parameters in accordance with an embodiment of the present invention
• Figure 2 depicts a graphical representation of a scenegraph and corresponding controls in accordance with an embodiment of the present invention
• Figure 3 depicts a flow diagram of a method for accessibility and control of parameters in a scenegraph in accordance with an embodiment of the present invention
• Figure 4 depicts a flow diagram of the re-defining step of the method of Figure 3 in accordance with an embodiment of the present invention.
• Figure 5 depicts a flow diagram of the linking step of the method of Figure 4 in accordance with an embodiment of the present invention.
• the second solution described above includes using a prototype as defined in VRML/X3D (see VRML handbook).
• This solution, as described in the VRML handbook is "A protection mechanism that allows an author to limit what can be done to an object". The problem, however, is that this "prototype node” technique does not allow.
• the third technique described above uses a Scenegraph Access Interface (SAI) such as X3D specifications for the SAI.
• SAI Scenegraph Access Interface
• Such Interfaces are either bound to a language, (i.e., VRML EAI is a Java binding).
• VRML EAI is a Java binding
• the technique here is then to develop a specific User Interface to get access to the scenegraph information.
• This technique allows access to any member of the scenegraph.
• accessing all the fields means the user must know the whole scenegraph structure and have knowledge of all its structural elements (nodes, fields, etc).
• names in the scenegraph might not be clear enough to a user, due to the name of their grammatical composition, e.g. the space character is not allowed.
• Embodiments of the present invention can apply to any existing scenegraph description language (e.g., textual or XML), provided the implementation matches the chosen scenegraph file format grammar.
• a parser can then decide to treat or not treat the nodes defined by the present principles, allowing or not allowing the feature of the present invention.
• the application can also choose not to display the User Interface controls defined by the present principles. For example, not treating the new feature of the present invention would be very straight forward on the parsing side, as all nodes have bounds, sometimes represented as brackets (e.g., ' ⁇ ' and ' ⁇ ') or XML tag brackets (e.g., ' ⁇ node>' and ' ⁇ /node>').
• Embodiments of the present invention include a set of additional components or nodes (depending on the scenegraph structure) needed to enable the access to the selected scenegraph information from the Application User Interface without modifying the original scenegraph description.
• the new components or nodes enable the redefining of the targeted scenegraph information's semantic to be presentable to the user, for example, with a comprehensible name and modifier on the user interface. This information can then be controlled through a newly created Graphical Interface widgets provided to the user through their graphical user interface.
• Feature Identifiers can be represented with matching closing and opening brackets, defined in compliance with the scenegraph grammar.
• Profiles Identifiers can be represented by a list of strings or identifiers describing the profiles.
• a profile can include a user, for example, describing access rights, or platform, for example, describing capabilities and/or profile. Containment of those profile identifier strings can be application dependant, or either a name description or a numeric value. If this list of strings is empty, all defined controls will be available to all users or platforms.
• Embodiments of the present invention may not use this information at all (i.e., instances in which profiles are not present on a platform, such like a decoder STB - Set Top Box — ), while other embodiments can manage profiles at a separate layer in the application (i.e., in the case of static profiles in a platform, like a switcher).
• Embodiments of the present invention can further include a List of controlled items in the scenegraph for each of them.
• the identifiers in the scenegraph include a list of strings or identifiers which define the targeted information in the scenegraph and are usually composed of the node's name definition or identifier and the node's field's name or identifier to be controlled.
• an identifier is not found at the current parsing level in the scenegraph, its control should not be activated.
• the application can then retrieve the field value type (e.g., float, integer) as a result of its definition in the scenegraph.
• This field is essentially a list of strings that allow grouped modification, for example, several color fields at the same time, under a single User Interface component. It is therefore necessary that the fields listed are of the same type.
• Embodiments of the present invention can further include a name appearing on the application User Interface. This will usually be different from the identifier name mentioned in the previous paragraph, as usually identifiers in a scenegraph are syntactically restricted in the grammar (no space or specific character) and may not present an appropriate description (i.e., these identifiers are usually automatically generated by the graphics modeling tool).
• a reset or factory value can include a value to set the parameter when a "reset" or "factory default” button is activated on the User Interface. This value may be different from the value in the scenegraph itself, since the scenegraph stores values at a specific instant. Even further, minimum and maximum values can be included which define a range of values valid for the parameter. The minimum and maximum values define limits for the User Interface controls.
• the Application of embodiments of the present invention can further include a Step
• Increment which corresponds to a stepwise increment (absolute value) to apply to a parameter (positively or negatively) on the User Interface by, for example, pushing a '+' or '- * button, and defined Profiles for which this control is enabled. That is, selected profiles identifiers (e.g., those listed above or other application defined identifiers) for which this control is enabled can be listed here.
• all values are represented in the field type numeric domain. If the chosen scenegraph does not provide a generic field type, for representing, for example, Floating values and Booleans, the largest domain can be used to define those parameters. For example, a float representation can be used and the value can be cast as an integer or boolean. In accordance with embodiments of the present invention, all values can be an array of numbers, as many parameters can be composed of more than one element or component, for example, a color with RGB values (Red, Green and Blue).
• the system will only use the 3 first elements and leave the last one unused.
• the User Interface control linked to this node can be deactivated or destroyed as well.
• Embodiments of the present invention also allow controlled items to be grouped. This allows for the grouping of a list of parameters on the User Interface in a more natural way, for example, a "car” composed of "wheels", or allows for an override of the scenegraph natural hierarchical structure for presenting the information to the user. This grouping feature can be named as well, and can recursively contain other groups.
• Embodiments of the present invention can be implemented on any existing scenegraphs, with the only restrictions being those inherent to each scenegraph model.
• VRML 2.0 does not provide a generic field type, thus only "SFFloat" can be used as the largest domain.
• VRML 2.0 nodes implementation of the present invention can be represented as follows:
• ControlProfiles nodes can be discarded if profiles are defined at the application layer.
• the "items” field can contain a list of “Controlltems” (see below) or other "ControlGroup” nodes.
• the "name” field defines the group name to be presented to the user, for example, "car”.
• the "profiles” field as presented overrides the profile designation on the individual items in the "items” list, allowing the profile to easily control the whole group.
• the "profiles” list contains a list of profiles as defined by the "ControlProfiles” node or application-dependant values.
• a PROTO structure concept within VRML 2.0 implementation can be represented as follows:
• an X3D nodes implementation of the present invention can be represented as follows:
• FIG. 1 depicts a flow diagram of a process for enabling the control of scenegraph parameters in accordance with an embodiment of the present invention.
• the process 100 of FIG. 1 begins with an Authoring or Modeling Tool 102 including the control methods of an above described embodiment the present invention.
• a content creator exports a subject scenegraph. If the scenegraph has the controls enabled, the process continues to step 108. If the authoring/modeling tool does not supply such functionality to the scenegraph a specific module can be created to add the controls afterwards. For example, when the authoring modeling tool 102 does not supply such functionality, an author exports the scenegraph 104, to module 106 for adding the necessary controls. The scenegraph with the controls is then enabled 108 and loaded into the application block 110. The Application 112 then loads the scenegraph to render it 114 and can now create the controls 116 (and make them available to the user) on the Graphical User Interface.
• the application 112 can directly embed the create controls module 116 to add the user controls. This can be useful for a content creator to verify correct execution and rendering of the scenegraph and its corresponding controls.
• Figure 2 depicts a graphical representation of a scenegraph and corresponding controls in accordance with an embodiment of the present invention.
• the embodiment of Figure 2 shows a rendering of a scenegraph 200 (simple cube in this case) and its controls (simple RGB color selection in this case) by an application which supports the methods of the present invention.
• the scenegraph includes a white background 202, a light-blue cube 206 displayed on the application rendering window 208 and the controls window 204 created by the application with respect to the interpretation of the VRML nodes embodiment.
• the scenegraph example used in Figure 2 is written using VRML 2.0 Scenegraph, with the profiles being deactivated.
• the VRML 2.0 description of the scenegraph can be represented as follows:
• the application 112 uses the Control Item to establish a binding between the name "Color” from the Control Group “Cube” and the scenegraph field "diffuseColor", part of the "MAT" node, which type is SFColor in the VRML 2.0 specifications, and thus functionally supports the desired controls (i.e., 3 editable fields for Red, Green, and Blue color levels).
• This is shown by the controls window 204 in Figure 2 where the individual R, G and B controls are shown.
• Figure 3 depicts a flow diagram of a method for accessibility and control of parameters in a scenegraph in accordance with an embodiment of the present invention.
• the method 300 of Figure 3 begins at step 302 in which a set of elements within the scenegraph are initially redefined. The method then proceeds to step 304.
• step 304 once redefined the selected information in the scenegraph is accessed in accordance with the redefined elements. The method then proceeds to step 306.
• step 306 when the selected information has been accessed, means are provided to control the selected information.
• Figure 4 depicts a flow diagram of the re-defining step 302 of the method 300 of Figure 3 in accordance with an embodiment of the present invention.
• the set of elements for which control is to be provided is identified at step 310.
• additional control information is linked to the corresponding identified set of elements to the existing structure in the scenegraph.
• Figure 5 depicts a flow diagram of the linking step 312 of the method of Figure 4 in accordance with an embodiment of the present invention.
• the additional information there is an initial seeking of the component or node presence within the scenegraph at step 320.
• another determination of the information data type from the standard grammar used in the scenegraph is made at step 324.
• the type and point to the data can be stored into the application for receiving user events.
• the various aspects, implementations, and features may be implemented in one or more of a variety of manners, even if described above without reference to a particular manner or using only one manner.
• the various aspects, implementations, and features maybe implemented using, for example, one or more of a method, an apparatus, an apparatus or processing device for performing a method, a program or other set of instructions, an apparatus that includes a program or a set of instructions, and a computer readable medium.
• An apparatus may include, for example, discrete or integrated hardware, firmware, and software.
• an apparatus may include, for example, a processor, which refers to processing devices in general, including, for example, a microprocessor, an integrated circuit, or a programmable logic device.
• an apparatus may include one or more computer readable media having instructions for carrying out one or more processes.
• a computer readable medium may include, for example, a software carrier or other storage device such as, for example, a hard disk, a compact diskette, a random access memory (“RAM”), or a read-only memory (“ROM").
• a computer readable medium also may include, for example, formatted electromagnetic waves encoding or transmitting instructions.
• Instructions may be, for example, in hardware, firmware, software, or in an electromagnetic wave. Instructions may be found in, for example, an operating system, a separate application, or a combination of the two.
• a processor may be characterized, therefore, as, for example, both a device configured to carry out a process and a device that includes a computer readable medium having instructions for carrying out a process.

Landscapes

• Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Computer Graphics (AREA)
• Geometry (AREA)
• Software Systems (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• User Interface Of Digital Computer (AREA)
• Processing Or Creating Images (AREA)

Priority Applications (8)

Applications Claiming Priority (2)

Related Child Applications (2)

Publications (1)

Family

ID=39227420

Family Applications (1)

Country Status (6)

Families Citing this family (2)

Citations (2)

Family Cites Families (12)

• 2007
  • 2007-06-28 CA CA002680009A patent/CA2680009A1/en not_active Abandoned
  • 2007-06-28 EP EP07796584A patent/EP2137702A1/en not_active Withdrawn
  • 2007-06-28 WO PCT/US2007/015149 patent/WO2008115196A1/en not_active Ceased
  • 2007-06-28 JP JP2009553557A patent/JP5010000B2/ja not_active Expired - Fee Related
  • 2007-06-28 US US12/450,125 patent/US9292964B2/en active Active
  • 2007-06-28 CN CN200780052188A patent/CN101647045A/zh active Pending
• 2016
  • 2016-02-12 US US15/043,290 patent/US9911227B2/en not_active Expired - Fee Related
• 2018
  • 2018-01-29 US US15/882,356 patent/US10311632B2/en active Active
• 2019
  • 2019-06-03 US US16/430,268 patent/US11087530B2/en active Active
• 2021
  • 2021-08-02 US US17/444,261 patent/US11734881B2/en active Active

Patent Citations (2)

Non-Patent Citations (5)

Also Published As

Similar Documents

Legal Events