International organisation for standardisation organisation internationale de normalisation



Download 3.13 Mb.
Page42/51
Date19.10.2016
Size3.13 Mb.
#3850
1   ...   38   39   40   41   42   43   44   45   ...   51

2.5SNHC FAQ


The first time attendants of SNHC subgroup were asked to review the current FAQ and give feedback. There was no feedback received for updating the document. The FAQ is not changed during this meeting.


3AFX activities

3.1Specifications updates


The list of modifications for existing specifications handled by SNHC is as follows.

3.1.1M11859 - Proposed modifications for Face Animation in ISO/IEC 14496-1


Two changes are proposed for face animation.

The first proposal claims that faceSceneGraphNode in FadeDefMesh node should be SFGeometry instead of SF3DNode to allow 2D curves. However, it is clearly stated in the specifications that faceSceneGraphNode points to one of the elements of the faceSceneGraph vector. Since the type of the faceSceneGraph is MFNode, the type of the faceSceneGraphNode has to be SFNode.

The second proposal is about the order of field in FDP node which, after a short discussion, turns out that it is not a problem
Resolution

No changes needed in the current spec.



3.2AFX General issues

3.2.1M11953 – ProceduralTexture Description Scheme


This contribution proposes a higher level description of AFX data. One of the purpose of this contribution is to see if there is interest in new synthetic content description schemes in MPEG-7.
Comments from Video group

This is potentially restrictive circumstances because there are many other procedural texture methods.

There is no similarity measure. It is either “is it the same?” or not.

How it will be used? Is it for retrieval or for representation? We need an application scenario for it.

Conclusion: It is probably beneficial to have such scheme, but it has to be generic. Also, similarity based retrieval should be possible.
Comments from Requirements group


    • We need to know what is the need functionality and what is missing in the current standard?

    • Is there a need in the industry? If so, which companies support this?

    • The technology has to be in the layer of technical excellence and this can be proven through core experiment (generic, compactness, etc)


Resolution

Need big pictures based on functionalities and some application scenarios to make others understand and possibly support this new work.



3.3Profiles

3.3.1M11922 – Proposal of AFX Profile – Simple 3D Compression Profiles


The requirements from Mobile 3D Contents Industry in Korea are introduced.

Following the resolution of the Hong Kong meeting, the object types, profiles and levels have been updated.

The levels are proposed in three parts: Player Constraints, Functionality Constraints and Data constraints. The player constraints are informative recommendation to give picture to the users about the recommended capabilities of the player or device. The functionality constraints limit the specific functionalities of each tool, such as support of normal, back channel, polygons, etc. The data constraints show numbers (maximum of the minimum).

They also propose the way to fit the AFX profile in the MPEG-4 architecture. It follows the Video example to have two scenarios: AFX only scenario and MPEG-4 Systems integrated scenario.


Discussion in SNHC

This proposal is about resource and not scene graph. There seems to be a problem with WSS and BBA because they need base mesh. In the point of conformance, there may be a problem.

The resource should have a definition of a model and texture and animation.

Partial scene graph may be necessary to make complete resource.


The goal of the proponents is not the exchange of resource (compatibility) but to have compression in their application.
The object types, profiles and levels seem OK. (one fix from the contribution wrt Main BBA object types)

The AFX only scenario may need to incorporate object graph.

The Integrated Systems scenario is not supported by the industry. Therefore, there’s no one to implement this scenario. However, this was requested by Systems because there should be a way for each technology in MPEG to blend in to the MPEG systems.
Joint Discussion with Requirements and Systems

The informative recommendation in the levels should be separated (currently, it is misleading)

The signaling can be done the same way as Text profile&level

The way it is integrated to systems is OK

Few more changes have been made to the original proposal:


  • Names are changed for the new dimension and the proposed profile

  • AFX tools and Object types have been redefined.

  • AFX object code in the AFX only bitstream has been changed to object type indication.


SNHC related profiles discussion

Changes are needed to the scene graph and graphics profiles currently under consideration



  • Compression 3D profile  Simple 3D profile

  • Need to remove the list of compression tools because they will be defined in the 3D Compression profiling dimension

  • Back channel removed (not a node)

New name for new dimension = 3D Compression Profile

  • We need to add two more profiles in this dimension

    • Simple 3D = 3DMC + IC + WSS

    • Animated Character = BBA

A new technology (scenario 1) is introduced. Therefore, we need a core experiment to verify the scenario (CE on 3D Compression Stream Design). If the verification is complete by the next meeting, the profile will be included in Amd1. If not, the profile will be a part of Amd2.


3.4Core experiments

3.4.1CE1 – Physics based animation


No contribution for this meeting. The work is in progress but not mature enough to make new contribution to Busan meeting.

3.4.2CE2 – Multi-resolution Footprint-based Representation




        1. M12097 – Result for the CE on Multiresolution Footprint-based Representation – IM1 implementation


This contribution reports the result of the implementation of generic multi-resolution footprint based representation in IM1. Full implementation in IM1 including the adaptation functionality, which was requested from Hong Kong meeting, has been completed.
Resolution

The generic multiresolution footprint-based representation is mature.

Minor editorial fixes to be made in the VM.

Issue a WD to add this technology and the Shadow node.



        1. M11912 – Proposal for FootprintElevation coding with an extension to buildings


This contribution is a proposal for application dependent information that extends the generic multi-resolution footprints. It specifies the Roof and Façade of buildings.
Resolution

Continue the CE to verify if the proposed technology is complete. Implementation is needed.





Download 3.13 Mb.

Share with your friends:
1   ...   38   39   40   41   42   43   44   45   ...   51




The database is protected by copyright ©ininet.org 2024
send message

    Main page