Configure Creative Finishing Software

Configure a direct attached storage or SAN as Media Storage

You can use your application with the following storage configurations (but not the system drive):

• A standard UNIX-compatible filesystem on a DAS (such as an Autodesk-recommended Dot Hill or XR-series disk array)
• A SAN. When attached to a CXFS SAN declared as a standard filesystem partition to Stone and Wire, Creative Finishing workstations running the current release have shown optimal (real-time) performance with version 4.02 of the CXFS client, and the following mount options for the CXFS volume: rw,noatime,filestream,inode64.
• A standard UNIX-compatible filesystem on a Network Attached Storage (NAS) based on the Network File System (NFS) protocol. The fact that all I/O operations occur over the network makes it impossible to reliably predict steady performance for NAS filesystems. Also that the NFS protocol features built-in cache and time-out mechanisms, which may cause several workstations working on the same media source to appear de-synchronized.

Configure your application to use the media storage filesystem

1. Ensure the disk array or SAN storage is connected to your workstation and powered up, and that a UNIX-compatible filesystem exists on the storage.
2. In a terminal, as root, stop Stone and Wire with the command: /etc/init.d/stone+wire stop
3. Create the Managed Media Cache directory or directories:
   • Create a point for your storage e.g. mkdir -p /mnt/StorageMedia. Do not use the reserved word “stonefs” in the directory name. For a DAS, the DKU installer should have already created a mount point for it at /mnt/StorageMedia (for HP Z800 workstations) or /mnt/stoneMedia (for older workstations).
   • Mount the filesystem e.g. mount -av -t xfs -o rw,noatime,inode64 /dev/vg00/lvol1 /mnt/StorageMedia. To automatically mount at boot, create an entry for it in the /etc/fstab.
   • On the mounted filesystem create the Managed Media Cache directory. The name should include the partition name and the hostname. Set permissions for the directory to be readable, writable, and searchable by the owner and its group, and readable and searchable by all:
     1. mkdir -p /mnt/StorageMedia/smoke1/p7
     2. chown -R root:users /mnt/StorageMedia/smoke1/p7
     3. chmod -R 775 /mnt/StorageMedia/smoke1/p7
   • Optionally create separate mount points and Managed Media Cache directories for each additional volume. The DKU only creates the mount point and /etc/fstab entry for the initial volume /dev/vg00/lvol1.
4. Configure Stone and Wire by editing the the following keywords in /usr/discreet/sw/cfg/stone+wire.cfg. Usage is documented in comments in the file:
   • Path
   • Name
   • Shared
   • [DefaultFileFormats]
   • SymlinkAcrossFilesystems
5. If this is the first filesystem you are configuring for this workstation: Get the FRAMESTORE ID, e.g. grep "FRAMESTORE" /usr/discreet/sw/cfg/sw_framestore_map and use the ID value to update /usr/discreet/sw/cfg/sw_storage.cfg e.g.

   [Framestore]
   ID=myworkstation

6. Optionally Configure bandwidth reservation.
7. Restart Stone and Wire with: /etc/init.d/stone+wire restart
8. Check the filesystem is mounted: /usr/discreet/sw/sw_df.

Any project created in your application after this point has the new standard filesystem partition as its primary partition. Any pre-existing projects are unaffected by this setting and remain associated to their respective partitions.

Set up the Wire network

• Wire is a component that enables the high-speed transfer of uncompressed video, film, and audio between Autodesk workstations, over industry-standard TCP/IP and InfiniBand networks.
• Wiretap is a networking protocol that allows products that do not run Stone and Wire to access the filesystem of a Creative Finishing product.

Stop all Stone and Wire daemons before editing any of the following configuration files.

1. In a terminal, as root, stop Stone and Wire services with: /etc/init.d/stone+wire stop
2. Specify the network interfaces to be used by Wire in /usr/discreet/sw/cfg/sw_framestore_map according to the instructions in the sw_framestore_mapman page.
3. Configure Wire self-discovery in /usr/discreet/sw/cfg/sw_probed_cfg file in a text editor. Ensure the value of the Port keyword matches the value used by the other workstations in your network and SelfDiscovery is set to “yes”. If these values are set properly, Stone and Wire uses its self-discovery mechanism to locate all other Wire hosts on your network and make their framestores accessible to your application.
4. To enable remote access to clip libraries, in /etc/exports specify all directories you want remote hosts to be able to access. You can export the entire/usr/discreet directory to enable remote access to all clip libraries, projects, user preferences and setups. Or you can export only certain subdirectories, such as/usr/discreet/clip or /usr/discreet/project. For example, to export the /usr/discreet/clip directory, add the following line to the end of the exports file: /usr/discreet/clip *(rw, sync, no_root_squash). Save the updated exports file, and run the command exportfs -a to apply the changes.
5. To configure the Wiretap server edit /usr/discreet/wiretap/cfg/wiretapd.cfg. The house network IP address should already be present in the file, as it is added automatically during installation. Specify any additional IP addresses Wiretap should broadcast for self-discovery, for example: IP1=10.10.0.1IP2=10.10.11.200. Optional: If your network comprises Windows or Mac OS X systems that will use Wiretap to access media from your workstation, configure the Wiretap Path Translation service so that media paths are accurately translated between operating systems. See Wiretap path translation.
6. To restart and test Wire: /etc/init.d/stone+wire restart. To test Wire is working: /usr/discreet/sw/tools/sw_framestore_dump which should show all Wire hosts discovered on your network.

Upgrade projects to the current version

You do not need to do this if you are applying a service pack.

It is recommended to use the copyProjects script to upgrade your projects to the current version, rather than manually re-creating projects, as it is quicker and less prone to human error. copyProjects 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.

1. Iin a terminal, as root. run /usr/discreet/<product_home>/bin/copyProjects.
2. It detects all projects from previous versions, and prompts you to continue.
   • If the version returned by the script is the newly installed version, answer Yes and confirm. It creates a copy of each project for the current version. The string _copy is appended to the end of the new project name. Then use the network library to transfer media into the copied projects.
   • Otherwise, change the application version to which projects are copied:
     1. In a terminal, as root, Open a terminal and log in as root, run /usr/discreet/<product_home>/bin/selectWiretapVersion.py.
     2. Select the version you want to copy projects to.
     3. When finished, run the copyProjects script.

Transfer clip libraries to current projects

To access clip libraries from projects created with any Creative Finishing software between the 2007 version and the current one, you must transfer the clip libraries to a project created in the current version. You can install the current version and use Wire to transfer the clip libraries to a current project. See your application help. For a Linux system where you do not wish to install the current version, or for IRIX systems, you can also use the following procedure to transfer media to the current version.

1. Use Backdraft Conform 2007 or later application to create a project and a clip library on the 2013.1 system. See your application help. The project and library is formatted for the software version it was created with.
2. Use the 2007 or later application to move clips over the network into the previously created project on the 2013.1 system. You can use Background Wire to help free up the resources of the workstation running the older version of the application. See your application help.
3. Create a new project on the current version system. If you have many projects, use the copyProjects script.
4. Use the current application to open the library created in step 1 (the library is read-only).
5. Use Dual View to drag the clips into the 2013.1 project and library.
6. Use the older application version to remove the project created in step 1. 2013.1 applications cannot remove projects created with previous versions because they are read-only.