Skinscape
 Tool Summary
| General Purpose Information | |
|---|---|
|  Year of First Releaseⓘ  The year a tool was first publicly released or discussed in an academic paper.  |  2001 | 
|  Platformⓘ  The OS or software framework needed to run the tool.  |  Protools and Max/MSP | 
|  Availabilityⓘ  If the tool can be obtained by the public.  |  Unavailable | 
|  Licenseⓘ  Tye type of license applied to the tool.  |  Unknown | 
|  Venueⓘ  The venue(s) for publications.  |  N/A | 
|  Intended Use Caseⓘ  The primary purposes for which the tool was developed.  |  Music | 
| Hardware Control Information | |
|---|---|
|  Haptic Categoryⓘ  The general types of haptic output devices controlled by the tool.  |  Vibrotactile | 
|  Hardware Abstractionⓘ  How broad the type of hardware support is for a tool. 
  |  Consumer | 
|  Device Namesⓘ  The hardware supported by the tool. This may be incomplete.  |  V1220 Transducer, Aura Systems Interactor Cushion | 
|  Body Positionⓘ  Parts of the body where stimuli are felt, if the tool explicitly shows this.  |  Arm, Torso | 
| Interaction and Interface Information | |
|---|---|
|  Driving Featureⓘ  If haptic content is controlled over time, by other actions, or both.  |  Time | 
|  Effect Localizationⓘ  How the desired location of stimuli is mapped to the device. 
  |  Device-centric | 
|  Media Supportⓘ  Support for non-haptic media in the workspace, even if just to aid in manual synchronization.  |  Audio | 
|  Iterative Playbackⓘ  If haptic effects can be played back from the tool to aid in the design process.  |  Yes | 
|  Design Approachesⓘ  Broadly, the methods available to create a desired effect. 
  |  DPC, Sequencing | 
|  Interaction Metaphorsⓘ  Common UI metaphors that define how a user interacts with a tool. 
  |  Track, Demonstration | 
|  Storageⓘ  How data is stored for import/export or internally to the software.  |  AIFF | 
|  Connectivityⓘ  How the tool can be extended to support new data, devices, and software.  |  None | 
Additional Information
Skinscape is meant to be a haptic equivalent to a MIDI sequencer. Keyboard inputs are recorded in Max/MSP and mapped to seven haptic actuators, six of which are located on the arms and one on the lower back. This sequence would then be exported and loaded into a traditional audio editing environment (e.g., ProTools) so that it can be combined with existing music.
For more information, consult Eric Gunther’s Masters Thesis.