|General Purpose Information|
| Year of First Releaseⓘ |
The year a tool was first publicly released or discussed in an academic paper.
| Platformⓘ |
The OS or software framework needed to run the tool.
| Availabilityⓘ |
If the tool can be obtained by the public.
| Licenseⓘ |
Tye type of license applied to the tool.
|Hardware Control Information|
| Haptic Categoryⓘ |
The general types of haptic output devices controlled by the tool.
| Hardware Abstractionⓘ |
How broad the type of hardware support is for a tool.
|Interaction and Interface Information|
| Driving Featureⓘ |
If haptic content is controlled over time, by other actions, or both.
| Effect Localizationⓘ |
How the desired location of stimuli is mapped to the device.
| Media Supportⓘ |
Support for non-haptic media in the workspace, even if just to aid in manual synchronization.
| Iterative Playbackⓘ |
If haptic effects can be played back from the tool to aid in the design process.
| Design Approachesⓘ |
Broadly, the methods available to create a desired effect.
|DPC, Process, Sequencing, Library|
| Interaction Metaphorsⓘ |
Common UI metaphors that define how a user interacts with a tool.
Vivitouch is meant to support prototyping of vibrotactile haptics aligned to audio-visual content. Haptic media is created through the use of waveforms and filters mapping the audio content at that moment of time to the vibrotactile channel. These filters, such as a low-pass filter, are meant to aid in synchronizing audio and haptic content. Effects and filters are assigned to different output channels, representing each actuator, and to different haptic tracks. Using multiple tracks allows for layering effects and filters on the same actuator at the same time.
For more information, consult the 2014 World Haptics Conference paper.