EP1869645A2

EP1869645A2 - Animation method using an animation graph

Info

Publication number: EP1869645A2
Application number: EP06726331A
Authority: EP
Inventors: Gaspard Breton; David Cailliere; Danielle Pele
Original assignee: France Telecom SA
Current assignee: Orange SA
Priority date: 2005-04-11
Filing date: 2006-04-10
Publication date: 2007-12-26
Also published as: WO2006108990A3; US20090009520A1; WO2006108990A2

Abstract

The invention relates to a method for animating a scene graph (M), characterized by comprising the following steps: creating (e1) an animation graph instance (G) comprising animation modules (MA1,..., MA10) and composition modules (MC1,..., MC4) organized in an arborescent manner, the animation modules being lower leaves of the trees of the graph and the composition modules enabling the composition of the results of their child modules, said child modules being any of the animation or composition modules; executing (e3) the animation while successively executing the animation and composition modules of the graph in such a manner that the execution of a composition module uses the results of the executions of its child modules.

Description

Animation process using an animation graph

The present invention generally relates to the field of image processing, and in particular the animation of graphic scenes using an animation engine.

In addition, the invention is focused primarily on the animation of characters in three dimensions, but its method is also used on any other type of graphic scene in two or three dimensions.

The current animation engines implement a single animation method each, for example a parametric system, a muscular system, or a system based on key images. Moreover, in these animation engines, all the modules necessary for the animation, as well as their interactions, are known in advance and can not be modified. These animation engines are therefore generally built in one block, in the form of a compiled executable code.

Therefore, when using a motor or animation program on a machine, it must have the power required to implement the animation process used. The current animation engines do not make it possible to choose an animation method when the engine is started, nor to adapt the power required to an animation by choosing to animate only an independent subset of a scene. or a three-dimensional character. In particular, they do not make it possible to carry out tests by choosing a particular animation method to animate only part of a face. Each test requires a different animation engine.

The present invention aims to solve the disadvantages of the prior art by providing an animation method acting on a scene graph, a term commonly used to refer to a collection of three-dimensional graphic meshes, and an animation graph to execute different phases of the same animation.

To this end, the invention proposes a method of animating a scene graph characterized in that it comprises the steps of:

Creation of an animation graph instance comprising animation and composition modules organized in a tree-like manner, the animation modules being sub-tree sheets of the graph and the composition modules making it possible to compose the results of their son modules, these being indifferently modules of animation or composition,

Execution of the animation by successively executing the animation and composition modules of the graph, so that the execution of a composition module uses the results of the executions of its child modules.

The invention makes it possible to reuse the animation modules of the same animation engine in different configurations, without requiring coding different assemblies of modules in different programs for each configuration. Thus, the animation engine according to the invention adapts to the power of the machine that uses it, by choosing an appropriate animation method. It also allows you to test different animation processes, without recompiling animation modules of the animation engine for each different configuration test. The use of an animation graph to produce an animation makes it possible to modify the characteristics of the animation by choosing only the appropriate animation modules, among those that exist and are already compiled in the animation engine.

According to a preferred characteristic of the method according to the invention, the algorithm used by at least one of said composition modules does not does not depend on the parts of the mesh on which its son animation modules act.

This makes it possible, when you want to change the animation module son composed by a composition module in the animation graph, to reuse the same composition module, although the new son animation modules act on parts of mesh different from the old son animation modules.

According to a preferred characteristic, the algorithm used by at least one of said composition modules of the graph does not depend on the animation method used by its son modules.

The use of very generic composition modules makes it possible to test animation modules of different processes by reusing the same composition modules.

According to a preferred characteristic, the step of creating an animation graph instance comprises reading a configuration file describing said animation graph.

The grouping in a configuration file of the characteristics needed to create an animation graph facilitates the realization of various configuration tests. For each configuration test, for example, a configuration file is defined and makes it possible to create the animation graph corresponding to this test in the animation engine.

The invention also relates to an animation graph for executing one or more animation phases using the method according to the invention, characterized in that: each animation phase is described by a sub-tree of which it is the root in the animation graph, said subtree including animation modules and possibly composition modules,

In said subtree, the animation modules and the possible composition modules are organized in a tree-like manner, the animation modules being sheets of said sub-tree and the modules of the sub-tree. composition allowing the composition of the results of their son modules, these being indifferently modules of animation or composition.

The invention also relates to an animation engine characterized in that it comprises dynamic configuration means using an animation graph according to the invention.

The invention also relates to the use of an animation graph according to the invention for the execution of an animation, characterized in that when the animation graph contains several phases, they are executed sequentially.

Finally, the invention also relates to a computer program characterized in that it comprises instructions for implementing the method according to the invention, when said program is executed in a computer system. The animation graph, the animation engine and the computer program have advantages similar to those of the method.

Other characteristics and advantages will appear on reading a preferred embodiment described with reference to the figures in which: FIG. 1 represents an animation graph according to the invention,

FIG. 2 represents the steps of the method according to the invention,

FIG. 3 represents the binding of a face in three dimensions, intended to be animated,

FIG. 4 represents the composition of animation results by a composition module,

FIG. 5 represents a user interface,

FIG. 6 represents the execution step of the method according to the invention,

FIG. 7 represents a set of parameters defining an example of a profile making it possible to configure an animation engine. According to one embodiment of the invention, the method according to the invention is implemented in an animation engine in a software way. The software used has a set of predefined modules whose instantiation in the form of a tree is controlled by an animation graph. The method dynamically configures the animation engine using the animation graph. This engine configuration, or animation graph, is specified in a configuration file called profile.

The modules of the animation engine are animation and composition modules, intended in this embodiment to animate a scene graph representing a face in three dimensions. Nevertheless, the method according to the invention is also applicable to any other type of graphic scene, using animation and composition modules adapted to this other type of scene. These modules are organized in a tree-like manner in the animation graph G shown in FIG. 1, configured so as to produce a three-dimensional animation of the face.

When using the animation engine, these modules are generally already compiled because of a previous use. The use of the method according to the invention does not require the recompilation of these modules, even when the configuration of the graph is modified, for example to use animation modules corresponding to another animation method that the animation modules precedents.

The process has three main steps, shown in Figure 2 and summarized below. Step e1 is the creation of an animation graph instance corresponding to a configuration of the animation engine. This configuration is selected using a profile, or configuration file describing the animation graph G, from among a set of profiles available in the animation engine. It defines the animation process used and the choice of corresponding modules to use. As previously explained, these modules are usually pre-compiled. The animation engine creates this animation graph instance from the reading of the selected configuration file. It creates an instance of each module of the graph, and the links defined by the structure of the graph of animation G, between these instances of modules. These links are used during the execution stage of the animation.

The next step e2 is the parameterization of each animation module of the graph with input parameters specific to each of these modules and the face to be animated, and with control parameters specific to the modules and the animation itself. even. These parameters are indeed often to be modified, for example when the animation engine is used on a different face than that of the previous use. The parameterization uses, for example, parameter files giving the values for each face of all the parameters necessary for the animation engine animation modules, one file per face being available in the engine. The profile selected in step e1 also contains default parameters for the animation modules of the animation graph G, which are used in step e2 to parameterize the animation modules, in the case, for example, where the parameter files are incomplete. The next step e3 is the execution of the animation. It allows the animation of the face in three dimensions by following the indications of the control parameters given during step e2 of parameterizing the modules of the animation graph.

The parameters of the animation modules, as well as the step e3 of execution, will be more fully detailed below.

The structure of the animation graph G, as well as the various modules composing it, are now detailed.

The animation modules are sheets of the graph G tree, while the composition modules are parents of modules of animation or composition in the graph tree G. The graph G tree of the animation engine is rooted in the sequence S, which has for girls one or more phases, which will be executed sequentially one after the other. other. In the example of Figure 1 these phases are the phases P1 to P3. This first level of the tree thus makes it possible to describe the temporal aspect of the animation, while the following levels describe the organizational aspect of the engine.

Each animation module MA1, MA2, ..., MA10 is used, during a three-dimensional animation of the face, to animate a part of the three-dimensional mesh that forms this face.

It should be noted that an animation module is specific to a particular animation process, but is not always specific to the part of the mesh on which it acts. In the example of FIG. 3, the animation modules Mu1 and Mu2 acting on the scene graph or M-mesh of the face in three dimensions use a method of muscle animation. This animation process consists of deforming the vertices of a part of the mesh in a similar way to the deformation that would be caused by a muscle on the corresponding part of the face, also called zone of influence of the muscle. Each module can therefore be likened to a muscle. Thus the Mu1 module corresponds to a frontal muscle whose functioning is that of an ordinary muscle, also usable on other parts of the face, for example as a risorius muscle, while the Mu2 module corresponds to a mouth muscle whose operation is more specific because it should not deform the lower lip of the face.

The positioning of an animation module on the three-dimensional mesh is determined by input parameters to this module, configured during step e2 of setting the animation graph. For an animation module using a muscular process, these parameters define, for example, the point of attachment of the muscle to the bone. of the face, its point of insertion in the flesh of the face, or its opening angle.

The animation modules MA1, MA2 MA10 shown in FIG. 1 therefore make it possible to modify the geometrical properties of the three-dimensional mesh by displacing certain vertices, or the colorimetric properties by modifying the materials or textures used for the illumination of the face by three dimensions. In addition, an animation module is activated either locally or globally:

- A module is activated locally when it acts on only one vertex of the mesh to modify the position or the colorimetric properties. The result returned by the module then contains the new position of the vertex in the mesh, and possibly other parameters of color or composition.

- A module is globally enabled when it processes all the vertices of a mesh at the same time. In this case, the returned result is, for example, a new temporary mesh that does not contain composition parameters.

The composition modules MC1, MC2,..., MC4, represented in FIG. 1, make it possible to compose the results of the animation modules that work together, for example the results of modules corresponding to pseudo-muscles operating simultaneously. A composition module in the graph G composes the results of the animation or composition modules of which it is the parent in the animation graph G. Thus:

- The MC1 composition module is used to compose the result of the MC3 and MC4 composition modules,

- The composition module MC2 makes it possible to compose the result of the modules of animation MA4 and MA5, - The composition module MC3 makes it possible to compose the result of the modules of animation MA6, MA7, and MA8,

- The MC4 composition module is used to compose the result of the MA9 and MA10 animation modules. More precisely, a composition module makes it possible to determine the final deformation resulting from the actions of its son modules on the three-dimensional mesh. The composition algorithm used by this module is implemented independently of the part of the mesh concerned. It consists in fact in a simple weighting of the deformations caused on the mesh by each of its son modules. The composition parameters provided by each of the child modules to the composition module may, however, be specific to the child modules. These may be, for example, specific weighting coefficients.

For example, for the vertex A of the three-dimensional mesh represented in FIG. 4, the local action of the module MAΘ causes the displacement of the vertex A towards the position B, whereas the local action of the module MA10 causes the displacement of the vertex A to the C position. The simple addition of these displacements results in the position D, which is generally unrealistic for the animation of a face. The composition module MC4 uses a weighting algorithm to give as a result of the composition of the actions of the modules MA9 and MA10 on the vertex A, the position E, which is more realistic.

The composition modules therefore use the results of the local actions of each of their child modules. In order to allow the results of a first composition module to be used by a second parent composition module of this first module, the composition modules are activated either locally or globally, as for the modules of animation. When activated locally, they return the results of their top-by-vertex composition. The results of the modules animation can thus be reassembled to be used iteratively in the tree of the graph G by their different parent modules.

In addition, the composition modules are either specific to an animation method or independent of the animation method used. In the first case, when changing the animation method used, these specific composition modules must be changed in the animation graph G, while in the second case only the animation modules must be changed.

In the embodiment described here the composition modules are very generic because they simply add or weight the results of each of their son modules, and are independent of the animation process used.

In addition, if certain parts of the face function independently, different animation methods can be used on each of these parts. This requires the use of two different types of animation modules, for example muscular animation modules on one part of the face and animation modules using a morphose technique on the other part of the face.

Different configurations of the animation graph G are created in order to respond to these different uses. For example, in one of these configurations, animation and composition modules are hidden so as not to intervene in the animation, although their positions in the organization of the graph are retained for later animation. The choice of a configuration for a given use is made in step e1 of configuration of the animation engine.

As indicated above, the composition modules of the graph G are applied to the animation modules themselves and not to the objects of the three-dimensional scene considered. This makes it easy to reuse the G animation graph on different faces, modifying only the positioning parameters of the animation modules. These parameters are positioned during step e2 of setting the animation graph.

Some of these parameters are numerical values, corresponding for example to a point of attachment of a muscle for a muscle module. Other parameters called elements are modules implementing detection or pretreatment algorithms on the three-dimensional mesh necessary for certain animation modules. Indeed, for example an animation module that treats the operation of eyelids requires knowing where are the eyes of the face. The detection of an eye is then implemented in an element. These elements making it possible to carry out pretreatments or detections of three-dimensional facial areas are for example performed during step e2 of setting the animation graph G.

Other parameters, also positioned during step e2 for setting the animation graph G, are necessary in order to carry out the animation. These control parameters, defined statically, are specific to an expression, they define for example for a muscular animation process, the degree of contraction to be applied to the muscle modeled by an animation module, when the face to animate must smile. These different control parameters are grouped into animation channels. A large number of animation channels can be used, including for example a channel for the movement of the eyes, a channel for the movement of the eyelids, a channel for emotions, a channel for emphases, which are conversational markers, or a channel for speech, more precisely one channel per language.

The animation graph thus created and parameterized during steps e1 and e2 is executed at the time of the animation. Depending on the desired animation system and the power of the target machine, the animation graph G is more or less complex and incorporates different elements and animation modules that do not require the same computing power. In order to facilitate the use of the animation engine, a user interface is implemented in the engine to adjust the parameters of the animation modules, during step e2 of setting the animation graph G. This interface is used together or instead of the parameter files used in step e2. The user interface is divided into two categories, the parameterization interface and the control interface. The parameterization interface makes it possible to adapt the animation modules to the virtual character by positioning the input parameters of these modules. The control interface is used to adjust the static control parameters of the animation modules that will be used during the step e3 of executing the animation.

It should be noted that this user interface is intended for the skilled person using the animation engine according to the invention, and not for any user who uses another type of interface to simply define a sequence of expressions predefined to play for a given animation. Indeed any user intervenes during the e3 execution stage only, for example by asking the animation engine to pronounce the word "Hello" to the face. The animation engine then declines the dynamic control parameters necessary for the pronunciation of the word "Hello", by using the static control parameters positioned by those skilled in the art at step e2 of setting the animation graph G. For this he uses for example a voice synthesis system, which breaks down the word "Hello" into phonemes, each phoneme having one or more associated static control parameters, and deduces the dynamic control parameters to be applied to the face between two phonemes by a interpolation using the static control parameters associated with each of these two phonemes.

The user interface thus makes it possible to position the input parameters of the modules and the control parameters in relation with the corresponding animation modules of the animation engine. For this, each The interface category is organized into pages so that the parameters can be grouped into a convenient form. The pages are organized in one or more horizontal or vertical groups of graphic objects, each of which makes it possible to describe and position a parameter. These groups can be described recursively. For example, a vertical group may consist of several horizontal groups.

Thus, in the example of FIG. 5, the parameterization interface I is composed of three graphical pages TAB1 to TAB3. The first page TAB1 contains a GV vertical group of four graphic objects:

- The graphic object IF1 makes it possible to position the input parameter "Extra" of an eyelid animation module. This parameter defines the position of the eyelid relative to the radius of the eye.

- The graphic object IF2 makes it possible to position the input parameter "Attenuation" of the same module. This parameter defines the attenuation of the movement of the apices of the eyelid when it opens.

The graphic object IF3 makes it possible to position the input parameter "openMax" of the same module, defining the maximum opening of the eyelid during the animation. The graphic object IF4 makes it possible to provide the eyelid animation module with an "eye" detection element corresponding to either the right eye or the left eye of the face in three dimensions.

Step e3 of execution of the animation graph G is now detailed. Once the e2 parameterization step performed, the animation is started in step e3 of the execution of the animation graph G. The execution of the animation graph G calls the "anime" function of the root sequence S of the G animation graph tree. This execution consists of traversing the animation graph to produce the desired animation. The control parameters of each animation module are applied to the module corresponding during this animation, to produce the expressions that are sent as instructions to the engine during the execution step e3.

It should be noted that each animation channel provides its own control parameters. During the execution step e3 these parameters are mixed according to a so-called "mixing" technique which makes it possible to coordinate the different deformations of the face due to each animation channel, in order to obtain a coherent animation. The animation modules thus receive only a set of control parameters, as if only one animation channel had been defined. For example, for a muscular animation method, an animation module receives only one contraction value of the muscle that it represents at a time.

The operation of the execution step e3 is represented in FIG. 6. The "anime" function applied to the sequence S calls in turn the functions "animates" daughter phases of the sequence S, that is to say say in this embodiment, the functions "animates" phases P1 to P3, in order to execute them sequentially. For the sake of clarity, the operation of the animation of the phase P1 is not shown in FIG.

Each phase P1 to P3 has the list of their son modules, and activates them by the function "animeGlobal". The "animeGlobal" function allows you to activate an animation or composition module in a global way, while the "animeLocal" function allows you to activate an animation or composition module locally.

For animation modules, the "animeLocal" function contains the desired animation algorithm and only works on one vertex. It therefore returns the unit result of its action consisting of the new position of the vertex and a set of parameters useful for the composition, for example weighting parameters. The "animeGlobal" function performs an iteration of the "animeLocal" function on all the vertices of the influence zone of the animation module. Similarly, the "animeLocal" function of a composition module only works on one vertex, but begins by calling the "animeLocal" function of its child modules, which are composition or animation modules. Then the function applies the desired composition algorithm and returns the result. The "animeGlobal" function of a composition module performs an iteration of the "animeLocal" function on all the vertices to be composed by the composition module.

The "anime" function applied to the phase P2 thus causes the animation of its MC2 son module by the call of the "animeGlobal" function, and the "anime" function applied to the phase P3 causes the animation of its child module MA3 by calling the function "animeGlobal". It should be noted that the phases are not composition modules, and are executed sequentially one after the other taking into account the mesh deformed by the preceding animation phase. The son modules of a phase thus allow the calculation of intermediate meshes used during the animation, and are activated globally.

The composition module MC2, when calling the "animeGlobal" function, calls the "animeLocal" function on its child modules, which are the MA4 and MA5 animation modules. For each of the vertices of their respective zones of influence, the modules MA4 and MA5 then each apply their animation algorithm taking into account their input parameters, and their mixed control parameters to take account of the action of each of the animation channels. The MA4 and MA5 modules return vertex by vertex the results r1 and r2 of their actions as well as parameters useful for the composition, to their parent module MC2.

On receipt of the results provided by the modules MA4 and MA5, the composition module MC2 applies its composition algorithm on each of the vertices in the influence zones of the modules MA4 and MA5, and returns the global results r3 of this composition to the phase P2. Finally phase P2 transmits these results r3 to the sequence S. The animation module MA3, at the call of the function "animeGlobal", applies its animation algorithm taking into account its input parameters, and its control parameters, which are mixed to take account of the action of each of the animation channels, on all the summits of its zone of influence. It returns the results r4 of its actions on these vertices to the phase P3, which transmits them to the sequence S.

The results of the actions of animation modules or composition transmitted by the phases to the sequence S allow the animation engine to play the animation. For this, the results of the phases are used phase by phase to deform the mesh of the face. The deformations of the mesh due to the current phase are taken into account by the animation engine to calculate the deformations of the mesh in the following phase. Especially if the first phase for example induces a movement of the eyelids, and the second phase a movement of the head, the motor will combine these two movements.

An example of a profile necessary to enable the animation engine to perform the animation of the face in three dimensions is represented in the table TAB1 of FIG. 7. This profile is produced in the XML language, according to the English "extensible Markup Language ". The first column gives the name of the XML tag described on the line considered, the second column specifies the attributes associated with this tag, and the third column specifies the value to give to these attributes.

For example: - The "Configuration" tag is used to describe the entire configuration of the animation engine, including the optional tags "Engine" and "User interface".

- The "Engine" tag is used to describe the engine and contains mandatory "Channel", "Phase" and "Element" tags, which respectively make it possible to describe an animation channel, a phase and an element of detection or detection. pretreatment on a may three-dimensional face wrap. For a given animation, several of these tags are present depending on the number of animation channels, phases and elements necessary for the animation. - The "Channel" tag allows you to specify animation channels of the animation engine that will be active. The first attribute of this tag, "Name", allows to give a name to the channel. For example, for facial animation, the following channel names are used: o "ManipReplay" means a manipulator channel for replaying an animation, where "ManipNeck" is a manipulator channel for controlling the head, or "ManipEyes" means a manipulator channel for controlling the eyes, o "ManipEyelids" means a manipulator channel for controlling the eyelids, where "ExpE motion" designates an expression channel for controlling emotions, where "ExpMood" designates an expression channel to control moods, o "ConvMarker" refers to an expression channel to activate conversational markers, where "VisemeFrench" refers to a speech channel for French, where "VisemeEnglish" refers to a speech channel for English , o "VisemeSpanish" means a speech channel for Spanish.

The second attribute, "Status", allows you to specify the initial state of the channel, that is, whether it is activated or not.

- The "Element" tag is used to create element instances. This tag is composed of the following attributes: o The "Type" attribute specifies the type of element used, for example an eye detection element. This type is to be matched with the elements actually implemented in the animation engine. o The "Name" attribute gives a name to the instance of the element that will be created by the animation engine, which allows to identify it for reference. o The optional attribute "Dimension" specifies the right or left side of the face to be considered for this element instance, if any. - The "Phase" tag allows you to specify the phase to which you are referring. It has only one attribute, "Number", which is the phase number in the time sequence of the animation. The "Phase" tag contains one or more "Module" tags corresponding to its child modules. - The "Module" tag is used to specify the module used. This can be either an animation module or a composition module. The tag

"Module" itself contains one or more "Module" tags corresponding to its child modules when it represents a composition module, or none if it represents an animation module. It can also contain a list of "Parameter" tags. The "Module" tag has the following attributes: o The "Type" attribute specifies the type of module used. This type is to be matched with the modules actually implemented in the animation engine. It may be for example a module of the "Muscle" type, which is an animation module using a method of non-specific muscular animation to a part of the face. o The "Name" attribute gives a name to the instance of the module that will be created by the animation engine, which allows to identify it for reference. o The optional "Dimension" attribute specifies the right or left side of the face to be considered for this module instance, if any.

- The "Parameter" tag is used to give some parameters of the module default values. The first attribute of this tag, "Name", specifies the name of the parameter and the second attribute, "DefaultValue", contains the default value to use if a corresponding value is not provided in the parametering step e2.

- The "user interface" tag is used to describe the engine's user interface, including the optional tags.

"lntΘrface_de_parametrage" and "lnterface_de_controle".

- The "lnterface_de_ammametrage" tag is used to describe the parameterization interface. For this it contains one or more optional tags "Page", or simply a tag "Group_horizontal" or tag "Group_verticar if all input parameters modules can be viewed on a single graphic page.

- The tag "Control_Interface", in a similar way, describes the control interface. It contains one or more optional "Page" tags, or simply a "Horizontal_group" tag or a "Vertical_group" tag if all control parameters can be viewed on a single graphic page.

- The "Page" tag is used to specify a graphic page in the control interface or in the configuration interface. This tag contains only one attribute "Name" which gives the name to the graphic page thus specified. It also contains a "Group_Horizontal" tag or a "Vertical_Group" tag, which may contain other "Horizontal_Group" or "VerticalGroup" tags, which allows for a large number of possible layouts of the page. The "Vertical_group" or "Horizontal_group" tags specify groups, respectively. vertical or horizontal graphical objects allowing a user to set control or input parameters to the modules.

- The tag "Groupejiorizontal" therefore contains one or more "Interface" tags which each represent a graphic object. The graphic objects thus described will be arranged horizontally. As indicated above, the tag "Groupe_hαrizontal" can itself contain instead of or in addition to this list of graphic objects, one or more tags "Groupe_horizontal" or "Groupe_vertical".

- The "Vertical_group" tag, similarly, contains one or more "Interface" tags representing graphical objects that will be arranged vertically. The "Vertical_group" tag can itself contain, instead of or in addition to this list of graphic objects, one or more "Horizontal_group" or "Vertical_group" tags.

- Finally the "Interface" tag allows you to specify a graphic object to use. This tag contains two attributes. The first "Type" attribute defines a type of graphic object. This type must be mapped to the predefined graphical objects in the GUI system. Indeed for each type of module or specific module are implemented one or more graphic objects, for example drop-down lists or sliders, for positioning the parameters of the module. The second attribute, "Reference", contains the name of the element or module instance that the graphical object should control.

The XML grammar, or DTD according to the English "Document Type Definition", of the profile thus defined is reproduced in Appendix 1.

An example of profit using this grammar is also reproduced in Appendix 2. ANNEX 1

<! - Root element ->

<! ELEMENT Configuration (Engine ?, User Interface?)>

<! - Motor element -> <! ELEMENT Motor (Channel *, Element *, Phase *)> <! - Channel element ->

<! ELEMENT Channel EMPTY> <! ATTLIST Channel Name

<! ELEMENT EMPTY element>

<! ATTLIST Element Type (ZoneLowerLip | Eye) #REQUIRED>

<! ATTLIST Element Name CDATA #REQUIRED> <! ATTLIST Element Rating (Left | Right) #IMPLIED>

<! - Phase element ->

<! ELEMENT Phase (Module *)> <! ATTLIST Phase CDATA Number #REQUIRED>

<! - Module element ->

<! ELEMENT Module (Parameter *, Module *)> <! ATTLIST Module Type

<! ATTLIST Module Name CDATA #REQUIRED> <! ATTLIST Module Dimension (Left | Right) #IMPLIED>

<! - Element parameter ->

<! ELEMENT Parameter EMPTY> <! ATTLIST Parameter Name CDATA #REQUIRED>

<! ATTLIST Parameter Default Value CDATA #REQUIRED> <! - User Interface element ->

<! ELEMENT User Interface

(Interface_de_parametrage ?, Interface_de_controle?)>

<! - Interface_de_parametrage and Interface_de_controle elements ->

<! ELEMENT Parameter_Interface (Page * | Horizontal_group | vertical_group)>

<! ELEMENT Control_Interface (Page * | Horiz_group | Vertical_group)>

<! - Element page ->

<! ELEMENT Page (Horizontal Group | Vertical Group)>

<! ATTLIST Page Name CDATA #REQUIRED>

<! - Horizontal group and vertical group elements ->

<! ELEMENT Horizontal_group (Interface | Horizontal_group | vertical_group) *>

<! ELEMENT vertical_group (Interface | Horizontal_group | vertical_group) *>

<! - Interface element ->

<! ELEMENT Interface EMPTY> <! ATTLIST Interface Type CDATA #REQUIRED>

<! ATTLIST Interface Reference CDATA #REQUIRED>

ANNEX 2

<? xml version = "1.0" encoding = "iso-8859-l"?> <! DOCTYPE Configuration SYSTEM "FaceEngineCfg.dtd">

<Motor>

</ Module>

</ Module>

</ Module> <Module Type = "Eyelid" Name = "Right_Eyelid" Rating = "Right">

<Parameter Name = "Extra" DefaultValue = "0.2" /> <Parameter Name = "Fade" DefaultValue = "45.0" /> <Parameter Name = "OpeningMax"

DefValue = "45.0" />

</ Module>

</ Phase>

</ Module>

</ Phase> <Phase Number = "2">

<Module Type = "CompMuscleAdd" Name = "Global_Muscles_Group"> <Module Type = "CompMuscleConj"

Name = "Frontal_Leg Left Up Group" Dimension = "Left">

<Module Type = "Muscle"

Name = "Left_Frontalis_Outer" Dimension = "Left"> <Parameter Name = "Disp"

DefValue = "0.0" />

<Parameter Name = "AlphaV" DefaultValue = "45.0" /> <Parameter Name = "AlphaZ"

DefValue = "0.0" />

</ Module>

<Parameter Name = "Start" DefaultValue = "O .8" /> <Parameter Name = "End"

DefValue = "1.2" />

</ Module> <Module Type = "Muscle"

Name = "Left_Frontalis_Inner" Rating = "Left">

<Parameter Name = "AlphaH" DefaultValue = "35.0" /> <Parameter Name = "AlphaV"

DefValue = "35.0" />

</ Module>

<Parameter Name = "Disp" DefaultValue = "0.0" /> <Parameter Name = "Start"

DefValue = "0.8" />

<Parameter Name = "End" DefaultValue = "1.2" /> <Parameter Name = "AlphaH"

DefValue = "35.0" />

</ Module>

<Module Type = "Muscle"

Name = "Right_Frontalis_Inner" Dimension = "Right"> <Parameter Name = "Disp"

DefValue = "0.0" />

<Parameter Name = "AlphaV" DefaultValue = "35.0" /> <Parameter Name = "AlphaZ"

DefValue = "0.0" />

</ Module>

<Parameter Name = "Start" DefaultValue = "0.8" /> <Parameter Name = "End"

DefValue = "1.2" />

</ Module> <Module Type = "Muscle"

Name = "Left_Up_Obicularis_Oculi" Rating = "Left">

<Parameter Name = "AlphaH" DefaultValue = "50.0" /> <Parameter Name = "AlphaV"

DefValue = "50.0" />

</ Module>

<Module Type = "CompMuscleConj"

Name = "Frontal_Law_Down_Group" Rating = "Right">

<Parameter Name = "Disp" DefaultValue = "O .0" /> <Parameter Name = "Start"

DefaultValue = "O.8" />

<Module Type = "Muscle"

Name = "Right_Up_Obiculari s_Oculi" Rating = "Right">

<Parameter Name = "AlphaV" DefaultValue = "30.0" /> <Parameter Name = "AlphaZ"

DefaultValue = "O .0" />

</ Module>

<Parameter Name = "Start" DefaultValue = "O .0" /> <Parameter Name = "End"

DefValue = "3.0" />

<Parameter Name = "End" DefaultValue = "3.0" /> <Parameter Name = "AlphaH"

DefValue = "40.0" />

<Parameter Name = "FeatureLowerLlp"

Default value ^≈ "ZoneLowerLip"/>

</ Module> <Module Type = "MuscleHigh" Name = "Right_Levator_Labii" Dimension = "Right">

<Parameter Name = "Disp" DefaultValue = "l .0" /> <Parameter Name = "Start"

DefaultValue = "O .0" />

<Parameter Name = "AlphaZ" DefaultValue = "0.0" /> <Parameter Name = "FeatureLowerLip"

DefValue = "ZoneLowerLip" />

</ Module>

<Parameter Name = "Start" DefaultValue = "0.8" /> <Parameter Wom = "End"

DefValue = "1.2" />

</ Module> <Module Type = "Muscle"

Name = "Right_Zygomatic_Major" Rating = "Right">

<Parameter Name = "AlphaH" DefaultValue = "20.0" /> <Parameter Name = "AlphaV"

DefValue = "20.0" />

</ Module> </ Module>

<Module Type = "Muscle"

Name = "Left_Angular_Depressor" Rating = "Left">

<Parameter Name = "Disp"

DefaultValue ^≈ '0.0 "/><Parameter Name =" Start "

DefValue = "0.8" />

<Parameter Name = "End" DefaultValue = "l .4" /> <Parameter Name = "AlphaH"

DefValue = "35.0" />

</ Module>

<Module Type = "MuscleLow"

Name = "Left_Depressor_Labii" Dimension = "Left"> <Parameter Name = "Disp"

DefaultValue = "l .0" />

<Parameter Name = "End" DefaultValue = "3.0" /> <Parameter Name = "AlphaH"

DefValue = "20.0" />

</ Module> <Module Type = "MuscleLow"

Name = "Med_Depressor_Labii">

<Parameter Name = "AlphaH" DefaultValue = "40.0" /> <Parameter Name = "AlphaV"

DefaultValue = "40.0" />

</ Module>

</ Module> <Module Type = "CompMuscleAdd"

Name = "Others_Group">

<Parameter Name = "Start" DefaultValue = "O .8" /> <Parameter Name = "End"

DefValue = "1.5" />

</ Module> <Module Type = "Muscle"

Name = "Right_Down_Obicularis_Oculi" Rating = "Right">

<Parameter Name = "AlphaH"

DefaultValue = "80.0" /> <Parameter Wom = "AlphaV"

DefValue = "30.0" />

</ Module>

<Parameter Name = "Disp" DefaultValue = "O .0" /> <Parameter Name = "Start"

DefaultValue = "O.8" />

<Parameter Name = "End" DefaultValue = "1.2" /> <Parameter Name = "AlphaH"

DefValue = "20.0" />

</ Module>

<Module Type = "Muscle" Name = "Left_Risoris" Dimension = "Left"> <Parameter Name = "Disp"

DefaultValue = "l .0" />

<Parameter Name = "AlphaV"

DefaultValue = "10.0" /> <Parameter Wom = "AlphaZ"

DefaultValue = "O .0" />

</ Module>

<Parameter Name = "Start" DefaultValue = "l .0" /> <Parameter Name = "End"

DefaultValue = "l.7" />

</ Module> <Module Type = "MuscleOO"

Name = "Left_Obicularis_Oris" Rating = "Left">

<Parameter Name = "Start" DefaultValue = "1.2"/> <Parameter Name = "End"

DefaultValue = "1 .2" /> <Parameter Name = "AlphaH" DefaultValue = "0. 3" /> <Parameter Name = "AlphaV" DefaultValue = "0. 3" /> <Parameter Name = "AlphaZ"

DefaultValue = "O .0" />

</ Module>

<Parameter Name = "Start"

DefaultValue = "1.2" /> <Parameter Name = "End" DefaultValue = "1.2" /> <Parameter Name = "AlphaH" DefaultValue = "0.3" /> <Parameter Name = "AlphaV" DefaultValue = "0.3" /> < Parameter Name = "AlphaZ"

DefValue = "0.0" />

</ Module>

<Parameter Name = "Start"

DefaultValue = "0.0" /> <Parameter Name = "End" DefaultValue = "l .0" /> <Parameter Name = "AlphaH" DefaultValue = "0.2" /> <Parameter Name = "AlphaV" DefaultValue = "0.2" / > <Parameter Name = "AlphaZ"

DefValue = "0.0" />

</ Module>

</ Module> </ Module></Phase><Phase Number = "3">

</ Phase>

</ Phase>

</ Motor>

<Interface_utilisateur>

<Parameters_interface><Page Nora = "Muscles"> <Groupe_vertical>

<Groupe_horizontal>

<Interface Tγpe = "MuscleParam"

Reference = "Left_Frontalis_Outer" /> <Interface Tγpe = "MuscleParam"

Reference = "Droit_Frontalis_Outer" />

</ Horizontal group> <Horizontal group>

</ Horizontal_group> <Horizontal_group> <Interface Type = "MuscleParam"

Reference = "Gauche_Frontalis_Inner" />

</ Horizontal_group> <Horizontal_group>

</ Horizontal_group> <Horizontal_group>

<Interface Type = "MuscleParam" Reference = "Left_Down_Obicularis_Oculi" /> <Interface Type = "MuscleParam"

Reference = "Droit_Down_Obicularis_Oculi" />

</ Horizontal group> <Horizontal group>

<Interface Type = "MuscleParam"

Reference = "Droit_Nasalis" />

</ Horizontal_group><Horizontalgroup> <Interface Tγpe = "MuscleParam" Reference = "Med_Levator_Labii"/>

</ Horizontal_group> <Horizontal group> <Interface Type = "MuscleParam"

Reference = "Gauche_Levator_Labii" />

</ Horizontal_group> <Horizontal group>

<Groupe_horizontal>

</ Horizontal_group> <Horizontal group>

<Interface Type = "MuscleParam" Reference = "Left_Angular_Depressor" /> <Interface Type = "MuscleParam"

Reference = "Droit_Angular_Depressor" />

</ Horizontal_group> <Horizontal_group>

</ Horizontal group> <Horizontal group> <Interface Type = "MuscleParam"

Reference = "Med_Depressor_Labii" />

</ Horizontal_group> <Horizontal_group>

</ Horizontal group> <Horizontal group> <Interface Type = "MuscleParam"

Reference = "Front_Obicularis_Oris" />

</ Groupe_horizontal>

</ Groupe_vertical> </ Page>

</ Horizontal_group> </ Page>

<Horizontal Group> <Interface Type = "NeckParam"

Reference = "Neck" />

</ Groupe_horizontal>

</ Page>

</ Horizontal_group> </ Page>

<Horizontal Group> <Interface Type = "EyelidParam"

Reference = "Gauche_Eyelid" />

</ Groupe_horizontal>

</ Page>

</ Control_Interface> <Control_Interface>

<Groupe_vertical>

<Groupe_vertical> <Horizontal group>

</ Horizontal_group> <Horizontal_group>

<Interface Tγpe = "MuscleControl" Reference = "Left_Frontalis_Major" /> <Interface Tγpe = "MuscleControl"

Reference = "Droit_Frontalis_Major" />

</ Horizontal group> <Horizontal group>

</ Horizontal_group> <Horizontal_group> <Interface Type = "MuscleControl"

Reference = "Gauche_Lateral_Corrugator" />

</ Horizontal_group> <Horizontal_group>

</ Horizontal_group> <Horizontal_group>

<Interface Type = "MuscleControl" Reference = "Left_Nasalis" /> <Interface Type = "MuscleControl"

Reference = "Droit_Nasalis" />

</ Horizontal group> <Horizontal group>

</ Horizontal_group> <Horizontal_group>

</ Horizontal_group> <Horizontal group> <Interface Type = "MuscleControl"

Reference = "Gauche_Zygoraatic_Major" />

</ Horizontal_group> <Horizontal group>

<Groupe_horizontal>

</ Horizontal_group> <Horizontal group>

<Interface Type = "MuscleControl" Reference = "Left_Depressor_Labii" /> <Interface Type = "MuscleControl"

Reference = "Droit_Depressor_Labii" />

</ Horizontal_group> <Horizontal_group>

</ Horizontal group> <Horizontal_group>

<Interface Type = "MuscleControl" Reference = "Left_Obicularis_Oris" /> <Interface Type = "MuscleControl"

Reference = "Droit_Obicularis_Oris" />

</ Horizontal_group> <Horizontal_group>

</ Groupe_horizontal>

</ Vertical_group> <Horizontal_group>

<Groupe_horizontal>

</ Horizontal_group> </ Horizontal group>

<Groupe_horizontal>

<Horizontal_group> <Tγpe interface = "EyeControl"

Reference = "Gauche_Eye" />

</ Horizontal group> <Horizontal_group>

</ Groupe_horizontal>

</ Vertical_group> </ Control_Interface>

</ Interface_utilisateur>

</ Configuration>

Claims

1. A method of animating a scene graph (M), characterized in that it comprises the steps of:

- Creation (e1) of an animation graph instance (G) comprising animation modules (MA1 MA10) and composition modules (MC1 MC4) organized in a tree-like manner, the animation modules being sheets of subtrees of the graph and the composition modules allowing the composition of the results of their son modules, these being indifferently modules of animation or composition,

Execution (e3) of the animation by successively executing the animation and composition modules of the graph, so that the execution of a composition module uses the results of the executions of its child modules.

2. A method of animating a scene graph (M) according to claim 1, characterized in that the algorithm used by at least one of said composition modules does not depend on the parts of the mesh on which its modules of son animation.

3. A method of animating a scene graph (M) according to claim 1 or 2, characterized in that the algorithm used by at least one of said composition modules of the graph does not depend on the animation method used by its son modules.

4. A method of animating a scene graph (M) according to any one of claims 1 to 3, characterized in that the step of creating (e1) an animation graph instance (G) comprises reading a configuration file describing said animation graph.

Animation graph (G) for executing one or more animation phases (P1 P3) using the animation method according to claim 1, characterized in that:

Each animation phase is described by a subtree of which it is the root in the animation graph, said subtree comprising animation modules and possibly composition modules. In said subtree the animation modules and the possible composition modules are organized in a tree-like manner, the animation modules being sheets of said sub-tree and the composition modules making it possible to compose the results of their son modules, these being indifferently animation modules or composition.

6. Animation engine characterized in that it comprises dynamic configuration means using an animation graph according to claim 5.

7. Use of an animation graph (G) according to claim 6 for the execution of an animation, characterized in that when the animation graph contains several phases (P1, ..., P3), those These are executed sequentially.

8. Computer program characterized in that it comprises instructions for implementing the method according to any one of claims 1 to 4, when said program is executed in a computer system.