Huron & SNAP Documentation

↓ To import a Locator script
↓ To record messages from
another application
↓ To edit a scene file
THE SIMULATION TOOLS
1. Select Import from the File menu.
2. Select a file to import from the file dialog.
3. Select the time you wish to paste at. If the Ignore empty
time option is selected then the first event in the script will
be inserted at the given time. Otherwise the first event will
be pasted with whatever offset it has within the script.
The import mechanism will read the script and attempt to match
Locator channels with existing tracks in the current scene. If a
channel is found in the script that doesn’t match the channel of
any existing track in the scene then a new track will be created
with the desired channel.
Within a Locator script, the events mapped to each channel are
assumed to correspond to a single trajectory. So Locator scripts
can’t contain multiple trajectories within a track.
Huron tools such as Locator and Tracker create messages that
can be recorded by pressing the record button in Sonic
Animator. This section assumes that internal synchronisation is
used. See the section on External MTC Synchronisation for
external timing.
When the record button is pressed, Sonic Animator listens for
messages indicating that object locations are changing, and any
messages whose Location Channel Numbers match the channel
number of an existing, armed track will be inserted into a new
trajectory in that track. A message destined for a track that isn’t
armed or doesn’t exist in the scene will be ignored.
The Scene file format uses ordinary ASCII characters and can
be edited using any text editor. The file format uses the same
hierarchical model as the rest of the application.
The first three words of the file must be Sonic Animator Scene
and the next two must be the version information.
After this, the file is organised into keywords and corresponding
data. Most keywords have one data element. See the file
Sample.scene for an example of the allowable keywords and
refer to the Command Reference section of this manual for a
complete list.
The LocationTrack keyword must be followed by a block
section containing all the information for a track. When the file
is parsed, the tracks will be inserted into the scene in the order
they appear in the file.
Similarly, track sections have a set of allowable keywords, one
of which is LocationTrajectory. Note that the start time of a
trajectory is specified relative to the start of the scene. Within
the LocationTrajectory block are the trajectory information
and a list of events. The data for the LocationEvent keyword
consists of a time relative to the start of the trajectory and a
three dimensional Cartesian position.
The keywords within a section may appear in any order and any
unrecognised keywords will be ignored. Comments are
HURON TECHNICAL MANUAL PAGE 127