Different ways of encountering an object

Explore in context#

A geographic interface places an instrument in a landscape of places and relationships. A three-dimensional view instead offers a spatial representation of the object itself. Neither perspective replaces the source record.

Listen and interact#

A playable representation can relate actions to sound, while an auralization can explore the role of a room or listening position. Each depends on a particular dataset and model, and needs to declare those dependencies.

Keep capability explicit#

VAO profiles allow a package to declare the experiences and resources it actually supports. A viewer should respect those declarations rather than implying that every object provides playback, augmented reality or a complete simulation.

Different experiences answer different questions#

Combining these views can make the research easier to explore. The combination should also preserve their differences: rotating a model is not evidence that the same representation supplies a validated acoustic simulation, and a plausible sound does not establish that its control mapping recreates historical playing conditions.

Let unavailable capabilities remain visible#

An interface can show what a package supports, what requires another resource group and what the current runtime cannot execute. That makes a limited but honest experience more useful than a control that appears to work while silently substituting content. Users should be able to return from an interactive action to the resource and interpretation on which it depends.

Evaluate the claim made by the experience#

Use technical tests for technical claims and appropriate empirical methods for perceptual or historical ones. Latency, signal agreement, package conformance and a player’s judgement of touch are different observations. The thesis’s technical demonstrations support bounded implementation and analytical claims; they do not replace participant studies of listening or playability.