Grass Valley PROFILE FAMILY v.2.5 - Manual (Page 28)

Chapter 1 Introducing the Profile Family
28 Profile Family
Profile Software Development
The Profile Software Development Kit (SDK) provides an application
programming interface (API) for libraries of Profile functions. We recommend
that you call these functions via Microsoft Visual C++ 5.0; however, it is
possible to use other languages that permit calls to C declared functions
(contact your Grass Valley Group representative for more information).
Software developers can use the API to control the Profile from third-party
hardware devices, for example. The API consists of seven libraries:
• The TekCfg library provides an interface to the Profile configuration.
• The TekPdr library furnishes calls that inventory and manage movies in
Common Movie Format (CMF), an internal file format standard for video,
audio, and timecode.
• The TekRem library makes it possible for a remote Windows NT system to
control a Profile disk recorder over an Ethernet LAN.
• The TekVdr library provides an interface for playing and recording video
and audio clips.
• The TekVfs library supports low-level access to individual media files in the
media file system.
• The TekVme library controls the optional video mix effects board.
• The TekXfr library supports media streaming of Fibre Channel connections.
Eight RS-422 serial ports come standard on a disk recorder. A disk recorder can
issue serial commands or receive them from an external device via RS-422
communication lines. The Profile Protocol associates each API call with a
specific number that can be sent over an RS-422 line. The ProLink application
monitors Profile Protocol calls over an RS-422 link, allowing you to use
compatible hardware devices, such as the PRC100 Control Panel, to issue
commands to a Profile unit.
Windows applications are also available to control the Profile system. Your
disk recorder comes with several standard and optional applications. See
“Starting and Closing Profile Applications” on page 31 for more information.
NOTE: Louth and Odetics RS-422 protocols are also supported,
although there is not a one-to-one correspondence between these
protocols and the Profile API. Louth and Odetics protocols do not
allow you full access to the functionality of the Profile system.