Introduction
QTVR basically is just another kind of media to HUMA, that you can build scenes with as with video or flash. There are some fundamental differences however: QTVR does not go into the main project movie, but is treated as external media. The HUMAtagger can, at the time being, only import complete VR scenes, you can not import separate panorama or object nodes and combine them in the program, but will have to use an external editor as Apple's QTVR Authoring Suite or Industriual Strength's VRWorx to do that. The number of nodes on the other hand is not limited and you can separately address every node in HUMA.
QTVR is imported just like any other piece of media (see creating projects ) allthough its media is not imported to the project movie but virtually linked into it a runtime. The single nodes appear as segments in the segment bin.You can create a new scene and define it by a VR node as usual. The scene will appear in the scenes' bin as any other and you can link it there with other scenes as usual.
As QTVR is not linear media most of the editing elements for VR scenes differ quite a bit from those of usual linear media scenes. The initial playback page for instance does not show any playback controls for VR, but let's you define the initial view of the scene - that is: the viewing angle that will be displayed when the scene is called. Use the QTVR movie itself to adjust the view, then click 'set' to grab the pan, tilt and zoom values.
All motion and interraction settings for VR scenes are done in the scene editor's 'HUMA' page, where you will find three tabs, that provide access to all parameters. The first one 'MotionControl' let's you decide which of the three axises usually available are to be animated autiomatically and which are to be user controlled. Select the auto checkbox and adjust the speed slider for automatic actions. The sign of the speed value determins the direction. Negative values for pan for instance would make the panorama/object spin counterclockwise while positive values would result in clockwise motion
User Control options include the assignment of control to either the sensor's x or y axis and let you decide if you want control to be mapped absolute or relative. Both options can be separately inverted (which will affect all targets the control is mapped to). Additionally you can adjust the stepwidth for relative control and an offset for absolute mapping (which is destined to multiscreen scenarios, where each screen would show parts of a panorama and all would be controlled by one sensor stream.
The second tab, 'constraints', lets you set limits over that the panorama's/object's view will not extend. Use this if you want to restrict the possibility to zoom into a node too far for instance. Position your movie, then click the 'min' and 'max' buttons to grab the values. 'From movie' will reset constraints to the values that have been authored into the movie. HUMA constraints are playback parameters only. They are not saved into the VR movie. HUMA constraints can not exceed movie immanent constraints. If the view is limited by the author, it's limited...The third tab 'HUMAhotspots' is for setting HUMA links. You define pan angles, tolerances and zoom and time thresholds that, when conditions meet, will trigger links a - d. QTVR internal Hotspots can only be used for mousecontrol in the moment.