Autodesk Visual Effects and Finishing 2010 Edition ® Installation and Configuration Guide
© 2009 Autodesk, Inc. All rights reserved. Except as otherwise permitted by Autodesk, Inc., this publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose. Certain materials included in this publication are reprinted with the permission of the copyright holder.
Disclaimer THIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AUTODESK, INC. “AS IS.” AUTODESK, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE REGARDING THESE MATERIALS. Published by: Autodesk, Inc.
Contents Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 About This Guide . . . . . . . Intended Audience . . . Notation Conventions . . . . Related Documentation . . . . Contacting Customer Support Safety Guidelines . . . . . . . Chapter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Installing Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Do I Need to Reinstall Linux? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Linux Installation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Linux Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Chapter 5 Installing the DKU and the AJA OEM-2K Firmware . . . . .
Modifying Project Configuration Files . . . . . . . . . . . Software Initialisation File Keywords . . . . . . . . . . . . . . . DiskHealthNotify . . . . . . . . . . . . . . . . . . . . . . MemoryApplication . . . . . . . . . . . . . . . . . . . . . Working with 4K 12-bit Film . . . . . . . . . . . . . Cannot Allocate Memory Buffer Messages . . . . . . Memory Panic . . . . . . . . . . . . . . . . . . . . . Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DviRamp . . . . . . . . . . . . . . . .
viii
Introduction 1 Topics in this chapter: ■ ■ ■ ■ ■ About This Guide on page 1 Notation Conventions on page 2 Related Documentation on page 2 Contacting Customer Support on page 2 Safety Guidelines on page 2 About This Guide This guide provides information about installing the current version of Autodesk® Inferno®, Autodesk® Flame®, Autodesk® Flint®, Autodesk® Smoke®, and Autodesk® Backdraft® Conform.
If you plan to reconfigure your workstation or your storage, knowledge of computer hardware, storage and networking in a professional video/film production environment is recommended. Do not attempt to carry out the procedures in this guide if you are not familiar with the concepts they present. Contact Autodesk Media and Entertainment Customer Support if you require further assistance.
■ Place all components in an air-conditioned environment. All hardware components generate heat and must be kept cool. ■ Make sure the rack on which hardware components are mounted is open or well ventilated. Follow the ventilation specifications that apply to your system. ■ Keep all hardware components in a clean, dust-free location. ■ Minimize vibration and humidity. ■ Do not block the vents on the component housing.
4
Installation Workflows 2 Topics in this chapter: ■ ■ ■ ■ Overview on page 5 Workflow for Upgrading the Software on page 6 Workflow for Reinstalling from Scratch or Upgrading Linux on page 7 Workflow for Connecting New Stone Direct Storage on page 8 Overview Your system is shipped with the operating system and the software already installed. This chapter highlights three common installation workflows that you may need to perform, and lists the documentation relevant to each.
For details on the workstation hardware setup, it is recommended that you visit www.autodesk.com/me-documentation, select your application and version, and download the Hardware Setup Guide for your workstation model. Workflow for Upgrading the Software Follow this workflow to to upgrade your software to a new version, service pack, or extension without reconfiguring your hardware or upgrading your operating system.
Workflow for Reinstalling from Scratch or Upgrading Linux Follow this workflow when you need to completely rebuild your system: from cross-connecting the hardware peripherals and storage arrays, to installing the operating system, and installing, licensing, and configuring the software components. Most of this workflow also applies when you need to upgrade the operating system without changing your hardware or storage setup.
7 Update the AJA OEM-2K card firmware on your workstation if necessary. Refer to the latest Release Notes for the required firmware version and for update instructions. Firmware update instructions are also available in Upgrading the AJA OEM-2K Firmware on page 30. 8 If you are using a new Stone® Direct storage array, configure the RAID volumes, mount the storage, and format it. See Configuring Storage on page 33 for LUN creation instructions and XFS filesystem creation instructions. 9 Install the software.
Setting Up Your Workstation Hardware 3 Topics in this chapter: ■ ■ ■ ■ ■ ■ ■ Overview on page 9 Connecting Peripherals on page 12 Connecting Video Components on page 13 Connecting Audio Components on page 14 Connecting Media Storage on page 15 Connecting Archiving Storage on page 20 Configuring your System BIOS on page 21 Overview This section contains peripherals, video, and storage wiring diagrams, as well as BIOS settings for the HP Z800 workstation.
■ If you need to call Customer Support, familiarity with the hardware setup helps you assist in diagnosing problems. ■ If you want to move your system at any time, or upgrade certain components, this chapter contains crucial information. Power and Air Conditioning Requirements The values for power consumption and heat output were recorded on an Autodesk certified system with all of the required peripherals and certified components.
Typical System Configuration The following diagram illustrates a typical Autodesk Visual Effects and Finishing system configuration, including the Wacom® Intuos® pen tablet and optional components. Workstation Peripheral Options WACOM Tablet Video Options AJA BOB (breakout box) AES/EBU Audio Video MonitorOut In Out Ch. 1/2 In Ch. 3/4 In Ch. 5/6 In Ch. 7/8 In Ch. 1/2 Out Ch. 3/4 Out Ch. 5/6 Out Ch. 7/8 Out Ch. 1/2 In Out Ch. 3/4 In Out Ch. 5/6 In Out Ch.
Connecting Peripherals The following diagram illustrates how to connect peripherals, such as the graphics monitor, keyboard, mouse, Wacom Intuos pen tablet, and house network, to the HP Z800 workstation. It is recommended you connect all hardware peripherals as instructed in this section before booting the workstation for the first time.
Connecting Video Components The following diagram illustrates how to set up video I/O by connecting the hardware components included in your shipment. The only video hardware you must provide are a sync generator, VTR, HD/SDI-ready broadcast monitor and patch panel (if desired). NOTE Do not use an SD (NTSC or PAL) sync generator for HD projects. Always use a tri-level sync generator for HD projects. Using the wrong sync generator for a project may impact the stability of your workstation.
Connecting Audio Components Your application uses the Discreet Native Audio subsystem. Discreet Native Audio uses the following hardware components: Lucid ADA 88192 Audio Converter audio I/O devices. Converts signals between the workstation and all digital or analog NOTE You can control the converter either locally or remotely through the audio preferences of the application (recommended).
Connecting Media Storage The workstation can be connected to two types of media storage. ■ Stone Direct disk arrays are Autodesk's high-performance direct-attached storage (DAS) devices designed to address the different real-time playback requirements of various workflows. Direct attached storage devices provide storage to individual workstations, and can be made available to other workstations via the Autodesk Wire network.
{ FC loop 2 To storage assembly FC loop 3 { FC loop 4 (Optional) To storage (4 loop), FC loop 1 archiving device or SAN 16 | Chapter 3 Setting Up Your Workstation Hardware
Autodesk Stone Direct XR-series disk arrays provide two types of enclosures: a RAID enclosure (also called an XR enclosure), and an EBOD enclosure (also called an XE enclosure). Each disk array contains twelve 146 GB, 300 GB, or 450GB hard drives. Autodesk Stone Direct uses hardware RAID to provide high performance, reliability, and protection against data loss. Hardware RAID storage configurations require either one RAID enclosure (for 2-loop) or up to two RAID enclosures (for 4-loop).
To FC adapter on workstation To FC adapter on workstation XR RAID Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure Cabling for additional enclosures The following diagram illustrates a 4-loop hardware RAID storage configuration with a single XR RAID enclosure. Dotted lines represent cabling for additional enclosures.
To FC adapter on workstation To FC adapter on workstation To FC adapter on workstation To FC adapter on workstation XR RAID Enclosure (F6412E) ! 0 FACTORY USE ONLY ! 0 FACTORY USE ONLY XE (EBOD) Expansion Enclosure 0 0 1 0 1 ID 0 ID XE (EBOD) Expansion Enclosure 0 0 1 0 1 ID 0 ID XE (EBOD) Expansion Enclosure 0 0 1 0 1 ID 0 ID XE (EBOD) Expansion Enclosure 0 0 1 0 1 ID 0 ID Cabling for additional enclosures The following diagram illustrates a 4-loop hardware RAID storage c
First storage assembly Second storage assembly To FC adapter on workstation To FC adapter on workstation To FC adapter on workstation To FC adapter on workstation XR RAID Enclosure XR RAID Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure Cabling for additional enclosures Connecting Archiving Storage Visual Effects and Finishing applications support archiving to USB 2.
Configuring your System BIOS HP Z800 BIOS Settings After wiring the workstation and before installing Linux, turn the workstation on and check the BIOS version and BIOS settings. WARNING If BIOS settings are not set up correctly before installing Linux, you will need to reinstall the OS. The certified BIOS version for your workstation is 1.06. Make sure the BIOS version number that appears on screen while booting the workstation matches the certified version.
BIOS Menu Submenu Item Value Slot 1 PCIe2 x8(4) Option ROM Download Disable Slot 3 PCIe2 x8(4) Option ROM Download Disable Slot 4 PCIe2 x16(8) Option ROM Download Disable Slot 6 PCI32 Option ROM Download Disable Restoring BIOS to Default Factory Settings If necessary, perform the following procedure to restore the BIOS settings to factory defaults. To restore default factory BIOS settings: 1 Press F10 while booting the workstation to enter the system BIOS.
9 In the File menu, select Save Changes and Exit. The workstation reboots. 10 Press F10 to enter the BIOS again. 11 In the File menu, select Flash System ROM. A dialog box prompts you to select between USB and CD-ROM. NOTE If the CD-ROM option does not appear, SATA emulation was not set correctly. Reboot your machine and redo this procedure from step 4. 12 Select CD-ROM and press F10 to confirm. 13 Select the .bin file. A confirmation dialog box appears. 14 Press F10 to confirm. 15 Press any key.
24
4 Installing Red Hat Enterprise Linux Topics in this chapter: ■ ■ ■ Do I Need to Reinstall Linux? on page 25 Linux Installation Workflow on page 26 Linux Post-Installation Tasks on page 27 Do I Need to Reinstall Linux? Sometimes, when upgrading to a new version or service pack of your software, you might need to also upgrade the operating system. Use the following table to determine the correct version of Red Hat Enterprise Linux required for your hardware platform for the current version.
If your system is not currently running the correct version of Red Hat Enterprise Linux, upgrade your operating system to the required version. Linux Installation Workflow Perform the following procedure to prepare your system and install the customized Autodesk distribution of Red Hat Enterprise Linux. To install the Autodesk distribution of Linux: 1 Locate the installation media. The DVD containing the customized Autodesk distribution of Red Hat Enterprise Linux is included with your shipment.
6 Power on your system. 7 When the system starts to boot, press F10 to enter the BIOS and make sure the BIOS settings reflect the recommended values in Setting Up Your Workstation Hardware on page 9. The BIOS must be correctly configured before installing Linux. NOTE If the keyboard is connected to the system through a KVM switch, you may have to press F10 repeatedly or hold it down to enter the BIOS. 8 Save the correct BIOS settings and reboot the system.
■ Networking Configuration File Description /etc/sysconfig/network Contains global networking settings. /etc/sysconfig/network-scripts/ifcfg-, where specifies your ethernet adapter Contains interface-specific configuration. /etc/resolv.conf Contains DNS server information. Enable multicasting if you are planning to access the system from a remote workstation.
Installing the DKU and the AJA OEM-2K Firmware 5 Topics in this chapter: ■ ■ Installing the DKU on page 29 Upgrading the AJA OEM-2K Firmware on page 30 Installing the DKU Before installing your software, you must install the required version of the DKU . See the Release Notes for the required DKU version for this version. For major releases, the DKU is available on optical media or as a download from Autodesk. For extensions and service packs, the DKU is only available for download.
The disc mounts on the /mnt/cdrom directory. The DKU installation directory is located at the top level directory of the disc. ■ Otherwise, download the latest DKU tar file from the download link provided in the release announcement, then go to the directory where the tar file was downloaded, and unpack it by typing: tar -zxvf DKU_.tar.gz The DKU tar file is unpacked into a new directory. 4 Go to the DKU installation directory and launch the DKU installation script: .
cat /proc/driver/aja If the PCI version line in the output lists a different version than the required one, perform the following steps to upgrade the firmware. NOTE Before upgrading the AJA firmware, make sure you have upgraded the DKU, and that you have restarted the system. 2 Go to the /usr/discreet/DKU/current/Utils/AJA_firmwareUpdate directory. 3 Run the AJAfw_update utility to scan the AJA current firmware and, if required, update to the latest firmware version. Type: .
32
Configuring Storage 6 Topics in this chapter: ■ ■ ■ ■ ■ ■ ■ Overview on page 33 Connecting to the RAID Controller for the First Time on page 34 Creating Hardware LUNs on page 35 Partitioning Disks or LUN devices as LVM-type Primary Partitions on page 37 Assembling the Disk or LUN Devices into a Logical Volume on page 38 Creating the XFS Filesystem on the LVM device on page 40 Creating a Mount Point and Mounting the Storage on page 41 Overview This chapter describes how to connect a direct-attached stora
Connecting to the RAID Controller for the First Time Powering Up Your Storage Powering your system and storage up or down should be done in a proper sequence. This will ensure that the system functions properly. WARNING An incorrect power up sequence can mean your system does not recognize all drives. To power up your system: 1 Make sure your workstation is shut down. 2 Power up the storage expansion enclosures. 3 Power up the storage RAID controller units.
■ Select the Preferences tab. ■ Enter hostname and IP information and click APPLY. Creating Hardware LUNs LUNs, also referred to as Logical Units or Logical Drives, are groups of disk drives that are striped together to provide optimal performance and RAID protection. Once configured, LUNs are seen by the Linux operating system as if they were single disk drives. To create the LUNs on your XR-series storage, use the XR Configurator utility supplied by Autodesk.
NOTE For systems having 2XR or 2XR + 2XE, you have to configure one XR at a time with the XR Configuration Utility. Connect the first XR and use the utility to configure. When done, disconnect the first XR and connect the second XR. When the second XR is configured re-connect the two XRs. To configure LUNs on XR-series storage: 1 Open a terminal and log in as root. 2 Go to the directory /usr/discreet/DKU/current/Utils/Storage/current/, and run the XR configuration utility by typing: ./XR_config.
Partitioning Disks or LUN devices as LVM-type Primary Partitions To achieve optimal performance, each disk or LUN in the DAS array should be partitioned as a single primary partition of type “Linux LVM”. NOTE If your storage arrays use 450GB drives, skip this section and continue with Assembling the Disk or LUN Devices into a Logical Volume on page 38. To re-partition disk or LUN devices as LVM-type primary partitions: 1 Open a terminal and log in as root. 2 Reload the drivers for the fibre channel card.
9 Type t to set the partition type. You are prompted to enter the hexadecimal code of the partition type to be created on the LUN. 10 Type 8e to set the partition type to Linux LVM. fdisk sets the partition as Linux LVM and the following output appears: Changed system type of partition 1 to 8e (Linux LVM) 11 Type w to save the new partition table. 12 Repeat steps 2 through 9 for each disk or LUN device identified in step 1.
Physical volume "/dev/sdb" successfully created Physical volume "/dev/sdc" successfully created Physical volume "/dev/sdd" successfully created Physical volume "/dev/sde" successfully created TIP You can use the command pvremove to delete any erroneously entered devices. 3 Verify that the physical volumes were initialized correctly. Type: pvscan -v A list of all of the physical volumes you created appears. Each volume should contain “lvm2”.
Logical volume “lvol1” created NOTE If the command outputs several lines about a file descriptor leaked on lvdisplay invocation, ignore them.
4 Run the mkfs.xfs command again to create the XFS filesystem on the device /dev/vg00/lvol1 using the value calculated in one of the previous steps. Type: mkfs.xfs -d agsize= -f /dev/vg00/lvol1 For example (your values will vary): mkfs.xfs -d agsize=4369068032 -f /dev/vg00/lvol1 The filesystem is created on the storage array. NOTE If the command fails, redo your calculations starting from step 1.
42
Installing the Application 7 Topics in this chapter: ■ Installing the Application on page 43 Installing the Application Use the following procedure to install or upgrade your application. NOTE To ensure optimal performance, it is recommended that only Autodesk Visual Effects, Finishing and Colour Grading applications and required Red Hat Enterprise Linux packages be installed on the workstations. To install the application: 1 Log in to your workstation as root and open a terminal.
mount /mnt/cdrom cd /mnt/cdrom ■ If you are installing from a downloaded application tar file, unpack the tar file: tar -zxvf The file is uncompressed and an installation directory is created on your system. 6 Go to the installation directory, and start the installation script by typing: ./INSTALL_ where is in upper case. For example, if you are installing Smoke, type: .
■ If you are installing the application for the first time, the init.cfg file appears in a text editor. ■ If you are upgrading the application, the old (previous) and new init.cfg files appear beside each other in an xxdiff window. The left panel displays the old init.cfg file. The right panel displays the new init.cfg that is installed with your application. The vertical bar on the right side indicates where differences exist between the two panels. 11 Scroll through the init.
WARNING The /etc/X11/xorg.conf file contains specific parameters for the graphics display, tablet, and other external devices for running the application. It is customized prior to shipping to reflect your configuration. It is strongly recommended that you never manually edit this file, as incorrect entries may result in peripherals that do not function properly, or an inability to launch the user interface. Use xxdiff to move entries from one version of the file to another. 14 If you modified the xorg.
Post Installation Tasks 8 Topics in this chapter: ■ ■ ■ ■ ■ ■ Do I Need to Perform These Tasks? on page 47 Configuring Your Storage Filesystem as Media Storage on page 47 Setting up the Wire Network on page 51 Setting Up Background Wire and Background Proxy Generation on page 53 Upgrading Projects to the Current Version on page 53 Installing Additional Utilities on page 54 Do I Need to Perform These Tasks? If you are just upgrading your Autodesk Visual Effects and Finishing application, you have already
Autodesk recommends using a properly configured and maintained XFS filesystem installed on Stone Direct XR-series disk arrays. Concepts and Terminology If this is the first time you are configuring an Autodesk Visual Effects and Finishing filesystem, familiarize yourself with the following key concepts. If you are already familiar with these concepts, continue with Configuring your Application to Use the Media Storage Filesystem on page 49.
becomes soft-imported and unmanaged media. If the publish destination resides on the same volume as the Managed Media Cache, and the format of the published files is the same as the one defined by the media preferences for the volume, only hard links to the managed media are created. This media becomes accessible to other applications and unmanaged by the Visual Effects and Finishing application.
5 To make your application aware of the standard filesystem volumes, define the Managed Media Cache of each volume as a partition in the Stone and Wire configuration file, and set its preferences: ■ Open the file /usr/discreet/sw/cfg/stone+wire.cfg in a text editor. The settings for each partition are defined in a [Partition] section of the file, for example [Partition7]. NOTE By default, the stone+wire.cfg file contains only one [Partition] section.
7 Optional: To prevent other Visual Effects and Finishing tools and applications (such as background Wire, Wiretap™, or remote Visual Effects and Finishing applications) from impacting the performance of your local application, configure bandwidth reservation for your partition in the /usr/discreet/sw/cfg/sw_bwmgr.cfg file. For details and examples, see the comments inside the /usr/discreet/sw/cfg/sw_bwmgr.cfg.sample file. 8 Restart Stone and Wire by typing: /etc/init.
NOTE The interfaces are listed in the order of preference. Wire tries to connect to hosts using the first interface in the list first. For example: [INTERFACES] FRAMESTORE=kamloops PROT=IB_SDP IADDR=192.168.0.1 DEV=1 PROT=TCP IADDR=10.0.0.5 DEV=1 ■ The FRAMESTORE keyword sets the name that identifies the framestore when remote hosts attempt to connect to it. ■ The PROT keyword defines the network protocol used to communicate to the framestore: TCP for TCP/IP or IB_SDP for InfiniBand.
Setting Up Background Wire and Background Proxy Generation Background Wire transfers and proxy generation rely on Backburner. The Backburner Server that automatically installs with the Autodesk Visual Effects and Finishing application communicates with a Backburner Manager on the Wire network to accomplish background transfers or generate the proxies. Use the following procedure to set up background Wire transfers and proxy generation.
Using this tool instead of manually re-creating your projects is the recommended approach, as it reduces the time needed to migrate multiple projects, and prevents human error. NOTE The copyProjects tool does not copy any media. It only re-creates projects and copies their settings and setups to the current version. You still have to transfer your media using the network library. To copy projects using the copyProjects tool: 1 Open a terminal and log in as root.
NOTE You can obtain the latest version of the guides mentioned in this section by going to www.autodesk.com/me-documentation. ■ If you do not wish to use the automatically-installed WiretapCentral or Wiretap Gateway on your local workstation, you can install these components on dedicated systems in your facility network. For system requirements and installation instructions, see the Autodesk WiretapCentral Installation Guide.
56
Licensing and Starting the Application 9 Topics in this chapter: ■ ■ ■ ■ ■ ■ Licensing Workflow on page 57 Determining the Licenses You Require on page 58 Obtaining the Host ID on page 58 Requesting License Codes on page 58 Entering License Codes on page 60 Starting the Application for the First Time on page 60 Licensing Workflow If you have purchased subscription and are upgrading to a new release, your new license is sent to you by the Autodesk Media and Entertainment department.
3 Request temporary license codes. See Requesting License Codes on page 58. 4 Install the temporary license codes. See Entering License Codes on page 60. 5 Start the application and accept the license agreement. See Starting the Application for the First Time on page 60. 6 When you receive permanent license codes, install those codes. See Entering License Codes on page 60. Determining the Licenses You Require You may need more than one license code.
NOTE For emergencies, you can acquire an immediate temporary license code by going to the Autodesk Registration Web page at www.autodesk.com, clicking the Services & Support link, selecting your product, then clicking Request a Short-term License, and following the step-by-step instructions. A 4-day license code is e-mailed to the address you provide. To obtain license codes by e-mail: 1 On your workstation, log into the user account you want to use your application with.
Entering License Codes The easiest way to enter the license codes for your application is to use the License Wizard. This wizard automatically appears when you start an unlicensed application. To launch an unlicensed application and enter license codes: 1 On your workstation, log into the user account you want to use your application with. 2 Double-click the application icon on the Linux Desktop to start the application. After a few moments, the License Wizard appears. 3 Click Next.
To start the application the first time: 1 Log into your workstation. 2 Do one of the following: ■ If this is the first time you are starting the application on a new system, open a terminal and type /usr/discreet//bin/startApplication -v to initialize the framestore and start the application. For example: /usr/discreet/flame2010/bin/startApplication -v WARNING The -v option deletes all material on the framestore.
62
Uninstalling the Application A Topics in this chapter: ■ Using rmsoft to Uninstall your Application on page 63 Using rmsoft to Uninstall your Application The rmsoft utility enables you to easily uninstall Autodesk Visual Effects and Finishing or Colour Grading applications from your workstation. To uninstall your application using rmsoft: 1 If you are logged in as the application user in KDE, log out and log back into KDE as root.
a b c d e 3 Select the RPM packages you want to uninstall in the RPM list on the left (click Select All to select all the packages), then click to move them to the RPM uninstall list on the right. 4 Click Next. The Choose folders window appears. 5 Select the application directories you want to remove from the /usr/discreet directory, and click Next. A confirmation dialog appears. 6 Click Uninstall & Remove to confirm the removal of the selected packages and directories.
The uninstallation starts and rmsoft displays details on the process. 7 When the operation completes, click Exit to close rmsoft. 8 Optional: You can also delete the log files associated with a given application version in the /usr/discreet/log directory.
66
B Configuration Files Topics in this chapter: ■ ■ ■ ■ ■ Overview on page 67 About the Software Initialisation Configuration File on page 67 About Project Configuration Files on page 70 Software Initialisation File Keywords on page 72 Project Configuration File Keywords on page 90 Overview Configuration files are ASCII text files that define the working environment for your application.
peripherals, workstation display settings, and environment directory paths. These parameters are independent of the project you select from the Project Management menu when you begin a session. NOTE For information on each keyword in the software initialisation configuration file, see Software Initialisation File Keywords on page 72. When you first install the software, you are prompted to edit the default software initialisation configuration file.
NOTE If you saved your custom software initialisation configuration file in a directory other than /usr/discreet//cfg, be sure to use the full directory path. If the custom file is not found, the application automatically uses the default init.cfg file.
About Project Configuration Files A project configuration file is a text file that is parsed when you select a project in the application. A project configuration file uses the same name as the project, but with a .cfg extension. For example, the project configuration file for a project called “my_project” uses a project configuration file called my_project.cfg. Project configuration files are located in the /usr/discreet/project//cfg directory.
The configuration file template: Sets parameters for projects to work with: 1920x1080@23976psf_free.cfg 1920x1080@24000psf_free.cfg 1920x1080@25000psf_free.cfg 1920x1080@50i_free.cfg 1920x1080@5994i_free.cfg 1920x1080@6000i_free.cfg 1280x720@5994p.cfg 1280x720@6000p.cfg 1920x1080@23976psf.cfg 1920x1080@24000psf.cfg 1920x1080@25000psf.cfg 1920x1080@50i.cfg 1920x1080@5994i.cfg 1920x1080@6000i.cfg The corresponding HD standard on workstations. The external sync source corresponds with the HD format.
Here are some basic guidelines for modifying project configuration files: ■ Do not modify the template project configuration files. These are used by the software to generate new project configuration files and should not be altered. Create a copy of the desired project .cfg file, and modify that in a text editor as needed. ■ Create a backup of the project configuration file before making any changes to it. ■ Modified project configuration files must end with _custom.cfg.
MemoryApplication 400 Working with 4K 12-bit Film Even with the recommended amount of RAM, working with 4K 12-bit film puts great demands on memory management. Set the RAM allocated for buffering frames to between 2000 and 4000. The ability to mix different resolutions in a 4K 12-bit film project increases memory requirements even further.
Video AJA_OEMLH, Serial1 Video AJA_OEM2K, Serial1 DviRamp The DviRamp keyword enables control of the Miranda DVI-Ramp external device. The DVI-Ramp outputs a standard definition serial digital video signal (SMPTE-259M-C) or a high-definition serial digital video signal (SMPTE-292M). NOTE Enable this keyword only if you are using the Miranda DVI-Ramp external device. The DviRamp keyword is automatically commented out if the application installation script detects an NVIDIA® SDI card connected to the system.
The VideoPreviewDevice uses the following syntax VideoPreviewDevice , , , , , , [, , Where: Is: A string describing the resolution and sync configuration of the video preview device: ntsc, pal, or an HD resolution and timing. The graphics-to-video configuration for your system. Set to dviramp (if you are using a DVI ramp), nvidia (if you are using an NVIDIA SDI card), or readback.
The TabletDriver keyword uses the following syntax TabletDriver wacom MidiDevice The MidiDevice keyword identifies MIDI devices that are used with Autodesk Visual Effects and Finishing systems. Only one device is recognized at a time. The MidiDevice keyword uses the following syntax MidiDevice , , , , , [, ] Where: Is: The name by which you want to identify the MIDI device in the application.
, , [, , , , , ] Where: Is: The VTR control protocol (SONY, NONE). The name by which you want to identify the VTR in the Input Clip and Output Clip menus (D1, DigBeta, D1 BTS, D5, and DVCpro, for example.). The video input format. Set to Serial1 to input using a single-link (4:2:2) connection from a device.
Where: Is: The delay in milliseconds after a vertical sync, before requesting the VTR timecode. This value should only be set or changed with the help of technical support. NOTE The value '99' is a special case to be used strictly with HDCAM-SR/720P and AJA. It is not to be used in other circumstances unless specified by technical support. The delay in frames before the edit sync point to send the ON command. This parameter is optional and it applies only to BVW50.
, , , Where: Is: The name for the emulator. The video input format. For a list of the video formats supported by your workstation, see Video on page 73. The video resolution and timing of the VTR to be emulated. The colourspace mode for video transfers. The video output format.
ClipMgtDevice The ClipMgtDevice keyword defines the devices used for archiving. The following archiving devices are supported: ■ VTR ■ HDCAM ■ Tape (SAIT and DTF2 fibre archiving devices only) ■ File Using the guidelines for setting ClipMgtDevice keywords in this section, you can set multiple archiving devices for use with the application. The first device that is defined will be the default device. ClipMgtDevice VTR You can specify only one VTR for a VTR clip management device.
ClipMgtDevice Tape You can specify several tape devices for clip management. SCSI tape archiving devices are not supported. Use only fibre channel archiving devices, specifically, SAIT and DTF2 devices. To use a tape device for archiving, you must define the filename, the block size, and the name for the device you are using.
The software also uses this keyword to determine whether there is enough free hard drive space available at start-up. To start the software, you must have at least 10 megabytes of free hard drive space in addition to the value set by this keyword. The size of your libraries can be determined using the following command in a terminal: ls -lh /usr/discreet/clip/*/*/*.000.clib The MaxLibrarySize keyword uses the following syntax MaxLibrarySize where is the maximum library size in megabytes.
Example of use Menu ~/menu, menu where the ~ in the directory path stands for /usr/discreet/. Model The Model keyword specifies where 3D models used by Action are stored. The Model keyword is one of the environment directory keywords which specify the paths to directories for resources shared by all projects. These directory paths should not be modified. Example of use Model ~/dve where the ~ in the directory path stands for /usr/discreet/.
FontDPSBase The FontDPSBase keyword identifies the directory in which PostScript® fonts are stored. At initialisation, the application creates links in the /usr/discreet/font directory that point to fonts in the directory identified by this keyword. The FontDPSBase keyword uses the following syntax FontDPSBase where identifies the directory in which fonts are stored.
Where: Is: ... Up to four (for a total of five) more Unicode values for the font proxy string. Example of use FontProxyLowString 0x41, 0x61 This example displays the default proxy string, “Aa”. FontProxyHighString The FontProxyHighString keyword, along with the FontProxyLowString keword, specifies which characters to draw in font proxies. By default, the proxy string is “Aa”.
Image File Extensions This list defines the supported image and movie file formats that the application can input or output. These extensions are used to filter files of the corresponding format when you use the file browser. This list may be edited to suit your particular needs.
Audio Format Extension MPEG-1 Layer3 mp3 WiretapCentralUrl The WiretapCentralUrl keyword sets the URL that opens in the default Web browser when you click the WiretapCentral button in the Import Image menu of the application. The WiretapCentralUrl keyword points to the WiretapCentral server on the local machine by default. You only need to modify this keyword if you relocated the WiretapCentral server to another system in your network.
BackburnerManagerHostname The BackburnerManagerHostname keyword serves two functions: ■ It locates the Backburner Manager on your rendering network. Enable this keyword if you are running an Autodesk Backburner Distributed Queueing System in your facility or will be using Cleaner® XL to encode jobs exported from the application. All four BackburnerManager keywords must be set correctly for jobs to be sent to the rendering network.
BackburnerManagerGroupCapability The BackburnerManagerGroupCapability keyword specifies wether the nodes in your rendering network are equipped with GPU-accelerated graphics cards or not. Based on the value of this keyword, the Visual Effects and Finishing application enables or disables the submission of jobs that require a GPU (such as floating point jobs) to the rendering network.
NOTE Make sure the folder to which the path points exists and is accessible from the Windows workstation where Cleaner XL jobs will be encoded. Also make sure that this folder has write privileges and has enough space to accommodate encoded jobs. Example of use CleanerDestinationPath C:\Cleaner\exported LogDailyReports The LogDailyReports keyword specifies the number of application log files that are kept.
where is 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60 frames per second. Example of use Framerate 29.97 Timecode The Timecode keyword sets the default timecode format used by the project. The Timecode keyword uses the following syntax Timecode [, DF] Where: Is: One of the following timecode formats: 23.976, 24, 25, 29.97, 30, 50, 59.94, or 60. DF An optional parameter indicating drop-frame timecode for 29.97 or 59.94 fps timecode formats.
■ If you are using a non-integer frame rate (for example, 29.97), set the refresh rate to the nearest integer (in the previous example, 30). The Hires keyword uses the following syntax Hires [Custom,] Where: Is: Custom An optional parameter that overrides the application's refresh rate. For example, you may choose to override the 60-Hz refresh rate for an NTSC project by using the Custom option with a value of 30Hz. The refresh rate of the graphics monitor.
ArchiveLibrary Online HTML and ASCII tables of contents will be saved to the filesystem. You can specify the destination directory by setting this keyword. Its default value is /usr/discreet/archive. You can make the target directory relative to the project directory by prefixing the path with a tilde (e.g. ~/archive). NOTE This keyword, if set, will take precedence over the ArchiveLibrary keyword in the init.cfg file.
Resource Path Resource File Extension Composite ~/composite .composite Compound ~/compound .compound Correct ~/correct .correct Cutout ~/paint/cutout .sgi Deal ~/deal .deal DeGrain ~/degrain .degrain DeInterlace ~/deinterlace .deinterlace Desktop ~/desktop .desk Difference ~/difference .diff Dissolve ~/dissolve .dissolve Distort ~/distort .distort Documentation ~/documentation .pdf DVE ~/dve .dve Edge ~/edge .edge EDL ~/edl .edl Export ~/export .
Resource Path Resource File Extension Interlace ~/interlace .interlace Key ~/key .key Keyer3d ~/keyer3d .key3d LensDistort ~/lensDistort .lensDistort Letterbox ~/letterbox .letterbox LogicOp ~/logicop .logicop Lumkey ~/lumkey .lumkey Lut ~/lut .lut Mask (Paint) ~/paint/mask .sgi MasterKeyer ~/masterkeyer .mkeyer Mix ~/mix .mix Moncal ~/monitor .monitor ModularKeyer ~/modularKeyer .modularKeyer Mono ~/mono .mono Morf ~/morf .
Resource Path Resource File Extension Repeat ~/repeat .repeat Resize ~/resize .resize Restore ~/filmrestore .restore Spark ~/sparks .spark Stabilizer ~/stabilizer .stabilizer Text ~/text .ttg Timewarp ~/timewarp .timewarp VectorViewer ~/vectorViewer .vectorViewer Wipe ~/wipe .
Index A air conditioning requirements 10 application entering license codes 60 installing 43 licensing 57 starting 60 uninstalling 63 ArchiveLibrary keyword 82, 92 audio Discreet Native Audio 14 hardware components 14 audio converter 14 audio file extensions 86 Audiodevice keyword 45, 79 B BackburnerManagerGroup keyword 53, 88 BackburnerManagerGroupCapability 88 BackburnerManagerHostname keyword 53, 87 BackburnerManagerPriority keyword 53, 88 background Wire transfers 53 C Cleaner XL license 58 CleanerDes
K keywords Audiodevice 45 BackburnerManagerGroup 53 BackburnerManagerHostname 53 BackburnerManagerPriority 53 DVIRamp 45 TabletDriver 45 Video 45 VideoPreviewDevice 45 VTR 45 L license codes Cleaner XL 58 di 58 editing the license file 60 entering application 60 requesting 58 required and optional 58 Linux version 25 LogDailyReports keyword 89 Lucid ADA 88192.See audio converter M managed media defining 48 Managed Media Cache defining 48 manager.
W X Wire transfers, background 53 WiretapCentralUrl 87 workflow licensing 57 storage configuration 33 workflow, hardware setup and software installation X server configuring 45 restarting 46 xxdiff, using 45 22 Index | 99
100
