a Avid Unity™ MediaNet for Pro Tools® Release Notes File Manager Release 1.2.1 PT and Pro Tools Macintosh Client Release 1.2.2 Important Information Avid recommends that you read all the information in these release notes thoroughly before installing or using any new software release. For information about the Pro Tools Macintosh v5.1U software and late changes to these release notes, see the ReadMe files included on the Pro Tools Macintosh v5.1U CD-ROM.
Release Notes Contents MediaNet for Pro Tools Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 What’s New in MediaNet Release 1.2.1 PT . . . . . . . . . . . . . . . . . . . . . . . 3 Supported Pro Tools Hardware and Software . . . . . . . . . . . . . . . . . . . . 4 Unsupported Pro Tools Hardware and Software . . . . . . . . . . . . . . . . . 6 MediaNet Workgroup Requirements . . . .
Release Notes 3 Symbols and Conventions These installation notes use the following special symbols and conventions: ✔ ✘ A check mark indicates a bug that has been fixed. An X indicates a known bug or limitation. Where appropriate, a workaround is provided. n A note provides important related information, reminders, recommendations, and strong suggestions. c A caution means that a specific action you take could cause harm to your computer or cause you to lose data. What’s New in MediaNet Release 1.
Release Notes Supported Pro Tools Hardware and Software Digidesign offers a range of Pro Tools products for both Macintosh operating system and the Windows NT operating system. At present, only Digidesign’s Pro Tools|24 MIX workstations are supported in a MediaNet workgroup. These workstations must be Macintosh-based, and running the Pro Tools v5.1U software and the MediaNet for Pro Tools Release 1.2.2 client software.
Release Notes 5 Supported Pro Tools Platform MediaNet for Pro Tools supports Pro Tools workstations using the following Apple Macintosh platforms. Table 1 shows the layout of the Digidesign boards in the Macintosh chassis. • n Power Macintosh G4 with AGP graphics The multiprocessor Power Macintosh G4 is not currently supported for Pro Tools. • Mac OS 9.0.4 or 9.
Release Notes Table 2 Pro Tools Expansion Chassis Slot Layout Slot Board Backplane Slot Chassis Interface Board Slot 4 (at the far right when viewing the front of the chassis) MIX core board Slots 5-9 Additional MIX farm boards (if needed) Slots 4-7 (second PCI bridge) Additional MIX farm boards or DSP 2 farm boards (if needed) Slot 8 Empty or the Digidesign SCSI-64 board Slot 9 (second PCI bridge) Meridien Digital Media Board Slot 10 (second PCI bridge) JNI A4 Fibre Channel adapter boa
Release Notes 7 Unsupported Digidesign Hardware MediaNet for Pro Tools does not support the following Digidesign hardware: • Pro Tools III and Pro Tools d24 hardware • AVoption is not qualified Unsupported Software and Features MediaNet for Pro Tools does not support the following software or features: • ABVB video support using the AVoption • QuickTime Video Playback, including floating window, the Miro board, and the Fuse board • Import Audio From Other Movie, except for CD ripping to MediaNet
Release Notes MediaNet Workgroup Requirements The following sections describe the MediaNet hardware and software required to connect a Pro Tools workstation to a MediaNet workgroup. File Manager Hardware MediaNet for Pro Tools supports any of the following qualified File Managers: c • Avid File Manager (desktop): 400 MHz PII, 500 MHz PIII, or 600 MHz PIII; 768-MB RAM; Windows NT Workstation 4.0 with Service Pack 5 • IBM M Pro (minitower): 400 MHz PII; 768-MB RAM; Windows NT Workstation 4.
Release Notes 9 MEDIArray Drives MediaNet for Pro Tools supports 9-GB, 18-GB, 50-GB, and 73-GB MEDIArray drives.
Release Notes Avid Workstation Requirements MediaNet for Pro Tools currently supports some Macintosh-based Avid Composer products and all Windows NT-based Avid Composer products in a mixed workgroups with Pro Tools. n Pro Tools clients with the AVoption|XL currently only support JFIF video resolutions generated by the Meridien I/O box. They do not support Avid’s older AVR video resolutions.
Release Notes 11 n Make sure that your Avid workstation is running the latest release of the Avid Composer Products software. Contact your Avid reseller or Avid Customer Support to obtain information about the latest software releases. Supported Configurations MediaNet for Pro Tools enables collaboration between Pro Tools workstations and Avid Composer workstations. The following sections describe the requirements necessary to create a MediaNet for Pro Tools workgroup.
Release Notes Sharing Media Between Clients Within Allocation Groups You can share audio and video files among several MediaNet clients. You must, however, remember the following restrictions when you are sharing files: • Each single-user video allocation group must connect directly to a MEDIASwitch port. • Audio files for Pro Tools clients should be in a separate audio allocation group from the video files.
Release Notes 13 • Only one Pro Tools client can access a single-user allocation group containing 1:1 video files, provided the allocation group is not being used by a video editing client and the Pro Tools client plays only a single stream of video. • Up to three Pro Tools clients can access an allocation group containing 3:1 or higher compressed video files and share the files in the allocation group while they are being used by a video editing client.
Release Notes The maximum number of audio tracks that each MediaNet client can use. • The minimum number of MEDIArray enclosures. • The number of MEDIASwitches and the MEDIASwitch sizes in the configuration. • The host file name that should be used to configure the MEDIASwitches. MediaNet for Pro Tools environments require the File Manager to have 768 MB of memory.
Release Notes 15 e. Single-streams of 3:1 video. MEDIArray enclosures MEDIASwitch Cables To 1 MediaNet client (Pro Tools system using single-stream 1:1 video) To File Manager Figure 1 Configuration 1a MEDIASwitch MEDIArray enclosures Cables To 3 MediaNet clients (Pro Tools system using single-stream 3:1 video) To File Manager Figure 2 Part 0130-04819-01 Rev.
Release Notes Administration MEDIArray enclosures To 1 MediaNet client (Pro Tools system using single-stream 1:1 video) MEDIASwitch Cables To 4 Composer Products clients (Avid systems using dual-stream 1:1 video) To File Manager Figure 3 Cabling Illustrations Configuration 2 Part 0130-04819-01 Rev.
Release Notes 17 Administration MEDIArray enclosures To 6 Composer Products clients (Avid systems using dual-stream 10:1 video) To 3 Pro Tools clients (Pro Tools system using single-stream 10:1 video) MEDIASwitch 2 MEDIASwitch 1 To 2 Composer Products (Avid systems using dual-stream 1:1 video) To File Manager Figure 4 Part 0130-04819-01 Rev.
Release Notes Administration To 3 Pro Tools clients (Pro Tools system using single-stream 3:1 video) MEDIArray enclosures To 5 Composer Products c (Avid systems using dual-stream 3:1 video) MEDIASwitch 2 MEDIASwitch 1 To 4 Composer Products clients (Avid systems using dual-stream 3:1 video) Cables To File Manager Figure 5 Configuration 4 Installing MediaNet for Pro Tools Client Hardware To install the Fibre Channel adapter board in a Pro Tools workstation, follow the Macintosh hardware install
Release Notes 19 Installing MediaNet for Pro Tools The MediaNet for Pro Tools kit contains two installation CD-ROMs. The CD-ROMs are: • MediaNet for Pro Tools CD – updates the MediaNet File Manager (Windows NT) and installs the MediaNet for Pro Tools client software onto the Pro Tools system (Macintosh only). • Pro Tools v5.1U Update CD – installs the Pro Tools v5.1U software Updating the File Manager MediaNet for Pro Tools requires that you update the File Manager to support the Pro Tools clients.
Release Notes 4. Insert the MediaNet for Pro Tools CD-ROM into the File Manager CD-ROM drive. The CD-ROM is set to auto-start and open the Avid Unity V1.2.1 PT window. This takes approximately 1 minute. If the CD-ROM does not auto-start, start the installation manually as follows: a. Double-click My Computer on the desktop. The My Computer window opens. b. Right-click the MN121pt CD-ROM icon and click Open. The CD-ROM window opens. c. Navigate to the \Unity\NT40 folder. d.
Release Notes 21 To install Pro Tools v5.1U: 1. Install Mac OS 9.0 on the Pro Tools client. Follow the installation instructions supplied with the operating system. 2. Install the Mac OS 9.0.4 Update on the Pro Tools client. Follow the installation instructions supplied with the operating system update. 3. If desired, install the Mac OS 9.1 Update on the Pro Tools client. Follow the installation instructions supplied with the operating system update. 4. Install Pro Tools v5.1U on the Pro Tools client.
Release Notes 5. Read the license agreement and click Accept. The Avid Unity for Pro Tools Install window opens. If you click Decline, you will end the installation. 6. Select the Easy Install option to install all of the necessary software on the Macintosh HD drive. 7. Click Install. The MediaNet for Pro Tools client software is installed in the Avid Unity folder on the Macintosh HD drive. 8.
Release Notes 23 • • • Digidesign folder > Pro Tools - Pro Tools 5.1U - Release Note (PDF file in the MediaNet folder) System Folder > Extensions - Avid Unity extension - AvidFibreDriver - JNI Compatibility System Folder > DAE folder - UnityAsynchStreamsLib - DAE Pro Tools Performance Guidelines Normally, users should experience no appreciable difference between working with Pro Tools attached to a MediaNet workgroup or working with Pro Tools attached to local storage.
Release Notes User Interface and Graphics The Pro Tools workstation is tasked in a completely different manner when Pro Tools is recording or playing from MediaNet storage. For this reason, the update speed of the display and the responsiveness of the Pro Tools user interface might differ somewhat when compared to using local storage. When using MediaNet storage, the Pro Tools workstation might periodically be interrupted by bursts of communication with the File Manager.
Release Notes 25 File Open/Close Pro Tools periodically opens and closes files (to buffer them for playback, for example). When using MediaNet storage, the file open/close process is somewhat slower than with local storage. This is most noticeable when first opening an existing session. It can also cause sluggish Pro Tools performance with very large sessions. Maximum Number of Open Files The File Manager can support having up to 15500 files open at one time.
Release Notes Pro Tools Usage Caveats The following sections describe differences when using Pro Tools in a MediaNet workgroup. 32 Voice Playback Engine Pro Tools TDM workstations have two playback modes: 64-voice and 32-voice. For optimum performance in a MediaNet workgroup, you must use the 32-voice engine. To activate the 32-voice engine, choose Playback Engine from the Setups menu. Select the 32-voice engine and click OK.
Release Notes 27 Avid Compatibility Mode also enables OMF "wrapping" after bounce or internal record via bus paths. When enabled, Avid Compatibility Mode causes any media files created using Bounce to Disk (or any recorded files where the signal source was an internal Pro Tools bus) to be OMF media files, directly usable as time-stamped master clips in an Avid sequence. Mac/PC Compatibility Mode Pro Tools v5.1 introduces a session property called Mac/PC Compatibility Mode.
Release Notes Audio File Type Pro Tools v5.1 supports AIFF, WAV, or Sound Designer II audio files natively. Macintosh-based Avid workstations normally work with Sound Designer II or AIFF files. Windows-based Avid workstations normally work with WAV or AIFF files. Table 6 shows the MediaNet clients and the types of audio files that they typically use. Table 6 Supported Audio File Formats Client and Operating System AIFF WAV Sound Designer II Pro Tools v5.
Release Notes 29 Sample Rate Both Pro Tools workstations and Avid workstations can use either 48 kHz or 44.1 kHz audio files. Either sample rate is acceptable in a MediaNet workgroup, but it is preferable for all participants in the workgroup to agree on a standard, universal sample rate to avoid media conversion. Many facilities choose 48 kHz, the industry standard for post production and broadcast applications. Select the Session Sample Rate in the New Session dialog box.
Release Notes Bit depth to 16-bit in the New Session dialog box when you are creating new session files. Session Settings and Preferences are “Sticky” Pro Tools stores all the changes made in the New Session dialog box, the Playback Engine dialog box, and the Preferences dialog box and uses them as the defaults for future sessions.
Release Notes 31 MediaManager Pro Tools v5.1 does not include automatic check-in or check-out of assets controlled by MediaManager. Only manual check-in and check-out are supported. Sharing Session Files To avoid conflicts among multiple users and avoid general performance problems, no two Pro Tools clients should open the same session file at the same time. Only one Pro Tools client should have a particular session file open at any given time.
Release Notes PTSessionLocker only needs to be used when multiple editors are working with the same set of audio files and you want to make sure you don't accidently edit another user’s files. Sharing Video Files Pro Tools clients can share 3:1 or lower resolution video files in an allocation group with other MediaNet clients. It is currently only possible to share JFIF video files. Sharing Audio Files Pro Tools clients can share audio files in an allocation group with other MediaNet clients.
Release Notes 33 Workflow Examples Workflow 1: Composer Sequence to Pro Tools Session In this workflow, a Pro Tools client and a Composer Products client are sharing a workspace and allocation group. 1. On the Composer Products client, when you export a video sequence for use with Pro Tools, make sure that you render all the effects and the transitions before exporting the sequence. 2. Export the video sequence as an OMF2 composition that refers to the existing media files. 3.
Release Notes Workflow 2: Pro Tools Rendered Mix to Composer Clip In this workflow, a flattened Pro Tools session is returned to the Composer Products client as an OMF media file, properly wrapped to include Master Clip metadata. 1. On Pro Tools client, perform a Bounce To Disk. Select the OMFIMediaFiles folder of the Composer Products client as the file destination. 2. On the Composer Products client, choose Refresh Media Directories from the File menu. 3.
Release Notes 35 • This workflow requires DigiTranslator for use in a MediaNet workgroup. • This is an audio-only workflow because DigiTranslator does not represent the video track in its OMF output. • This is a composition and media only workflow because most types of Pro Tools metadata (time stamps, mix automation, plug-ins, etc.) are not exported by DigiTranslator.
Release Notes Known Issues This section describes known issues in the MediaNet for Pro Tools software. When a workaround exists, it appears in the paragraph directly following the bug description. n ✘ If you encounter a problem with the MediaNet workgroup, consult these release notes to see if a known issue or workaround associated with your problem exists before contacting Avid Customer Support.
Release Notes 37 Technical Support Information Avid Customer Support has a variety of technical support options available. Avid Assurance includes annual telephone support, maintenance releases, and advanced hardware exchange (7x24 option available). Assurance customers in North America may contact our Customer Support Center at 800-800-AVID (2843).
Release Notes Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement.
