Configure the Media Cache Storage on Mac OS X

It is recommended to store media on a drive other than your system drive, ideally a direct attached storage (DAS) device or a storage area network (SAN). You can store media on the system drive but performance will not be as good, and is not a recommended setup.

Note: The recommended filesystem on Mac OS X is HFS+, but you can use another filesystem. In addition to implementing POSIX file system semantics, such filesystem must support both hard and symbolic links, 64 bit file sizes and offsets, direct I/O, and timetamps with at least 1 second precision. Finally, directories must support at least 4 billion entries.

Configuring the Media Cache storage:

  1. Ensure the disk array or SAN storage used for the Media Cache is connected to your workstation and powered up.
  2. Boot your workstation and log in.
  3. Open the Service Monitor, Applications > Autodesk > [Product] > Utilities > Service Monitor.
  4. In the Service Monitor, open the Components tab and Stop Stone+Wire. Wait for the Status light to turn red.
    Note: Some other components' status light might change to red: this is normal behavior.
  5. Launch the Setup applicationApplications > Autodesk > [Product] > Utilities > [Product] Setup.
  6. In the Media Storage tab, click Add and follow the instructions.

    If you need to create mount points for your media cache storage, a procedure below shows you how to do this.

  7. Once the storage appears in the Media Storage list, click Apply.

    The setup application restarts some services.

  8. Close the Setup application.
  9. Back in the Service Monitor, open the Components tab and Start Stone+Wire. Wait for the Status light to turn green.
    Note: Other components' status light should change back to green. If not, Start them.
  10. Verify that the new media cache storage is available. In the terminal, type:
    /usr/discreet/sw/sw_df

    Any project created in your application after this point can now use new media cache storage. Any pre-existing projects are unaffected by this setting and remain associated to their respective partitions.