HP SVA V2.1 Parallel Compositing Reference Guide

Figure 1-1 Relationships Among Library Entities
system application
session
program
host
context
framelet
frame
output
result
Key
1
runs
0..n
1..n
1 1
0..n
0..n
0..n
0..n
0..n
1..n
1..n
1..n
0..1
1
share
owner
client
entity 1
part
supplier
entity 2
relates
channel
1..n
Order of Function Calls
Applications that use the Library typically create a sequence of images. In Library terminology,
each image is denoted as a frame. As described in Section , each host in a set of hosts produces
a part of each frame, ultimately resulting in the complete frame or image. Consequently, calls to
the Library functions usually follow a certain sequence.
Table 1-1 outlines the steps that an individual host typically performs. In a distributed application,
each host will likely be implemented by a program running on a different node in a cluster. In
a multi-threaded application, each host will likely be implemented on a different thread of the
same program on single node. Either way, the following sequence of calls will likely occur.
Table 1-1 Typical Call Sequence
CommentStep
1. Initialize the Library.
The pcSystemInitialize function initializes and loads
the Library.
1a. Load the Library.
Using pcSystemGet… functions, you can determine the
properties of the Library, if desired, for example, the
Library version.
1b. Discover Library properties.
The pcSessionCreate function creates a session.
2. Create a session.
14 Main Areas of the Parallel Compositing Library