Haptic Effect Library for Timeline-Based Signal Representation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing haptic file formats are inefficient in terms of data size and flexibility, particularly for immersive systems, as they often require repetitive storage of identical haptic effects and limit the ability to define haptic effects with different frequency bands within a single track.
Innovation Solution
The proposed solution introduces a data structure that utilizes a haptic effect library to define and store haptic effects, allowing for flexible referencing and reuse of haptic effects within a timeline. This approach optimizes data storage by avoiding repetitive data and enabling more flexible frequency band decompositions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If haptic effects are stored repetitively in existing file formats, then haptic effects can be applied multiple times, but the data size increases and storage efficiency decreases
Solution Approach 1:
The patent introduces a library of haptic effects that can be referenced multiple times without copying the actual effect data. Instead of storing complete haptic effect definitions repeatedly, the system stores references (identifiers) to pre-defined effects in the library, significantly reducing data size while maintaining reusability.
Solution Approach 2:
The haptic effect library serves as a universal resource that can be referenced across multiple tracks and time periods. A single effect definition in the library can be applied to multiple different tracks and time intervals through references, making the system multi-functional and eliminating redundant storage.
2Adaptability or versatility
If haptic effects are defined with specific frequency bands in each track, then frequency-specific control is achieved, but the flexibility to define effects varies across tracks is limited
Solution Approach 1:
The patent segments haptic effects into distinct frequency bands (e.g., low frequency, mid frequency, high frequency) and stores them as separate entries in the library. Each track can then selectively reference the appropriate frequency band segments, providing flexible frequency-specific control without requiring complex redefinition for each track.
Solution Approach 2:
The system allows changing the frequency band parameters by selecting different effects from the library rather than redefining them. This parameter-based approach enables flexible adaptation to different frequency requirements while maintaining simpler effect definitions, as the same effect can be referenced with different frequency band assignments.
3Reliability
If haptic effects are stored with full definitions for each occurrence, then complete information is available, but data management efficiency decreases
Solution Approach 1:
Instead of copying full haptic effect definitions for each occurrence, the system creates a centralized library with unique effect definitions and uses references to these definitions. This ensures complete information is available through the library while dramatically improving data management efficiency by eliminating redundant data processing and storage operations.
Solution Approach 2:
The library acts as an intermediary between the haptic effect definitions and their applications in tracks. This intermediary structure maintains complete effect information in the library while providing efficient reference-based access during data management operations, resolving the contradiction between information completeness and management efficiency.
Data Source
AI summary
A data structure storing information representative of haptic effects comprises a set of haptic effects and a timeline. Haptic effects may be defined in a flexible manner, either directly within the timeline or referenced by an identifier within the timeline. A library may store definitions of the effects with associated identifiers. Data restructuring processes are proposed to convert from a streaming-friendly format where the library is not used to an edition friendly format with the use of a library, and vice versa.


