Multiview Video Track Texture Depth View Indication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current video storage methods lack efficient and flexible ways to indicate the presence of texture and depth views, dependencies between views, and spatial resolutions in multiview video streams, particularly when using the MVC file format for MVC+D content.
Innovation Solution
The introduction of new boxes and sample entry types within the ISOBMFF framework, such as the View Identifier box, 3VC Depth Resolution Box, and 3VC Scalability Information SEI Message Box, allows for explicit indication of texture and depth views, view dependencies, and spatial resolutions, enabling efficient storage and decoding of multiview video streams with depth.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the MVC file format is used for storing multiview video streams, then video compression and storage efficiency is improved, but the ability to explicitly indicate the presence of texture and depth views, dependencies, and spatial resolutions is insufficient
Solution Approach 1:
The patent segments the multiview video stream information into distinct components by introducing separate box types (e.g., TextureViewBox, DepthViewBox, ViewDependencyBox) within the ISOBMFF structure. Each box type specifically handles a particular aspect (texture presence, depth presence, dependency relationships), allowing for precise and organized indication of various view characteristics without mixing information types.
Solution Approach 2:
The patent introduces intermediary data structures (boxes and sample entries) that act as mediators between the raw multiview video data and the decoding process. These intermediaries carry metadata about view presence, dependencies, and resolutions, enabling the decoder to properly interpret and process the multiview stream without requiring complex parsing logic embedded in the video data itself.
2Productivity
If new boxes and sample entry types are introduced in ISOBMFF framework, then the flexibility and efficiency of storing and decoding multiview video streams is improved, but the device complexity increases
Solution Approach 1:
The patent employs dynamic parsing where the decoder adapts its processing based on the actual content of the stream. Rather than implementing rigid handling of all possible box types, the decoder dynamically processes only the box types present in each specific stream, using type identifiers to route processing appropriately. This reduces actual runtime complexity while maintaining full functionality.
Solution Approach 2:
The patent uses parameter-based differentiation where boxes are identified and processed based on their type parameters (box types, sample entry types). This allows a single processing framework to handle multiple view configurations (texture-only, depth-only, combined) by changing processing parameters based on the indicated box types, rather than requiring separate processing logic for each configuration.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for encapsulating video streams containing multiple coded views in a media file are described herein. In one example, a method includes parsing a track of video data, wherein the track includes one or more views. The method further includes parsing information to determine whether the track includes only texture views, only depth views, or both texture and depth views. Another example method includes composing a track of video data, wherein the track includes one or more views and composing information that indicates whether the track includes only texture views, only depth views, or both texture and depth views.