Pro Tools 12.5.1 Download Compatible with OS X El Capitan
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x
This Read Me documents important compatibility information and known issues for Pro Tools® and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x (“Mavericks”), Mac OS X 10.10.x (“Yosemite”), and Mac OS X 10.11.x (“El Capitan”).
Introducing the Avid Artist Community
Avid Artist Community is the new marketplace where you can share and promote your creative work and skills to a large community of audio, film, TV, broadcast, and other media professionals.
Visit apps.avid.com/store/community/help/index.html to find out all the details of how to sign up and start interacting with other Com- munity members. Once you are a registered user, visit ac.avid.com to log in.
Avid can only assure compatibility and provide support for qualified hardware and software configurations.
For the latest compatibility information—including qualified computers, operating systems, and third-party products—visit the Avid website (www.avid.com/compatibility).
Updated EuControl Appset for Artist Control, Pro Tools | Control with Pro Tools 12.5 (PT-213555)
An updated Appset for Artist Control and Pro Tools | Control is provided with Pro Tools 12.5. This includes an improved and more in- tuitive soft key layout as well as additional assignments for newer Pro Tools EUCON commands. For more information on Appsets, please refer to your control surface’s documentation.
iLok USB Key (2nd Generation) and Pro Tools Authorization
An iLok (2nd generation) must be connected at all times while running Pro Tools
Pro Tools requires that an iLok (2nd generation) with the appropriate authorizations be connected to the computer at all times. Do not remove the iLok while running Pro Tools. If the iLok is removed while Pro Tools is running, one of the following will occur:
Pro Tools displays a dialog giving you the following choices:
• Reinsert the iLok and click Save. Pro Tools saves the session and then quits.
• Click Quit. Pro Tools closes the session without saving and then quits. – or – Pro Tools displays a dialog giving you the following choices:
• Reinsert the iLok and click OK to continue working in Pro Tools.
• Click Cancel. Pro Tools closes the session without saving and then quits.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16
9329-65708-00 REV A 1
Avid Application Manager
Use the Avid Application Manager for notifications about Pro Tools software and plug-in updates
When you install Pro Tools 12.x, the Avid Application Manager is also installed. The Avid Application Manager is used to manage your software and entitlements related to your MyAvid account. The Avid Application Manager helps you maintain the most currentPro Tools software and audio plug-in updates that you are entitled to when new versions become available. For more information about the Avid Application Manager, see the Avid Application Manager Guide (available online through the Avid Knowledgebase).
Pro Tools 12 does not support video capture (PTSW-181456)
Pro Tools 12 does not have the ability to record video to the timeline. Co-install Pro Tools 10.3.10 (or higher) on the same system and use an Avid Mojo SDI to record video into Pro Tools 10. The captured video can then be used in Pro Tools 12.
Avid Video Engine (AVE) is not supported with drives that are case-sensitive formatted (UME-1223)
The Avid Video Engine (AVE) will not load on Mac OS X if the OS drive/volume is formatted as Mac OS Extended (Case-sensitive, Journaled). In order for AVE to load, the OS drive/volume must be formatted as Mac OS Extended (Journaled).
Pro Tools 12 does not allow import of WMA files (PTSW-181506)
If you attempt to import a WMA file into a Pro Tools 12 session, Pro Tools cannot convert the file and posts a “file is unreadable” message. Co-install Pro Tools 10.3.10 (or higher) on the same system, import the WMA file, and convert it to a format supported by Pro Tools 12.
After creating a new user account on Mac OS X, you can initially only save a Pro Tools session in a non-local folder called “Documents” (PT-204548)
To avoid this issue, create a folder named "Documents," save a session there, then save the session and all other subsequent sessions wherever you wish.
On Mac OS X 10.10 (Yosemite) only, iTunes does not work with HDX or HD | Native hardware using the Avid Core Audio manager. (PTSW-194693)
The Avid CoreAudio Manager is currently not compatible with Mac OS X 10.10 (Yosemite) and a driver update will be required.
QuickTime Player is not currently compatible with Avid Audio Interfaces on Mac OS X 10.8 and 10.9 (PTSW-163965)
QuickTime Player does not currently support Avid audio devices as output devices with Mac OS X 10.8. Audio will not pass through and playback will not start. Please use an alternate audio interface for QuickTime Player, or use another software solution for playing back QuickTime files with Avid audio devices as a workaround for this issue.
Pro Tools 12 sessions that use more than 4 gigabytes of RAM will cause Pro Tools 10 or lower to quit unexpectedly (PTSW-181963)
If you attempt to open a Pro Tools 12 session that uses more than 4 gigabytes of RAM in Pro Tools 10 or lower, Pro Tools will quit un- expectedly. To open such sessions in Pro Tools 10 or lower, first reduce the amount of session RAM usage to less than 4 gigabytes in Pro Tools 12 by removing virtual instruments that take up system memory.
Nudge Selected Clip Gain shortcuts may conflict with the default Mac OS X shortcuts for Mission Control (PT-210366)
Performing the Nudge Selected Clip Gain Up/Down shortcuts may trigger Mission Control functions in some versions of Mac OS X. To avoid this conflict, click the ?Keyboard? icon in System Preferences, select the ?Shortcuts? tab and then ?Mission Control? from the sidebar. Disable or reassign the ?Mission Control? and ?Application Windows? shortcuts.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 2
Enable Spotlight for best performance when relinking files and indexing in the Workspace (PTSW-183818)
For best performance with relinking and Workspace indexing, enable Spotlight. While enabling Spotlight is not required, it will improve performance in this area with Pro Tools.
When Spotlight is enabled, long record passes (over 50 minutes) may stop recordings after 50+ minutes. Consider disabling Spotlight for long recording sessions and then re-enable it when you are done recording.
OMF files that contain video are not compatible with Pro Tools 12 (PTSW-184397)
OMF sequences that contain video cannot be imported into Pro Tools 12. OMF sequences that contain embedded or referenced audio files can be imported into Pro Tools 12. To import a sequence that contains video media, use a linked AAF sequence.
Pro Tools session file formats version 4.x and lower are not supported in Pro Tools 11 and higher (PTSW-181049)
Pro Tools session files from Pro Tools versions 4.x and lower are not recognized in Pro Tools 11 and higher. In the Pro Tools Work- space, these files are listed as “unknown,” and cannot be opened. Co-install Pro Tools 10.3.10 (or higher) on the same system and open the session files in Pro Tools 10. Save the session in the current Pro Tools session format, then open the session in Pro Tools 12.
Pro Tools | HDX Systems
Some Mac Pro computers with certain video cards may not have power connections available for Pro Tools | HDX cards (PTSW- 156545)
Some video cards require power from the motherboard, which is also a requirement for HDX cards. If you have a video card that re- quires both power connections on the motherboard, a power connection for your HDX cards will not be available. To avoid this prob- lem, use a video card that does not require more than one power connection to the motherboard.
Pro Tools | HD Native PCIe Systems
With Mac OS 10.6.8 or higher, it may not be possible to update the firmware on an HD Native PCIe card (PTSW-146374)
When launching Pro Tools HD with an HD Native card on Mac OS 10.6.8 or higher, a –1164 error may occur. This error indicates that the firmware for the HD Native card cannot be updated from version 1.0 to version 1.02 or 1.03. If this error occurs, you can only update the firmware using Mac OS X 10.6.7 or lower. The firmware update can also fail when using a Thunderbolt MacBook Pro. To avoid this error, use a Mac without Thunderbolt and use the Avid NativeCardFlasher utility to update the HD Native firmware,
For more information on updating Native card firmware, refer to the following Avid Knowledge Base articles: http://avid.force.com/pkb/articles/en_US/troubleshooting/en419331 http://avid.force.com/pkb/articles/en_US/troubleshooting/en429831
Eleven® Rack Guitar Window not available in Pro Tools 12 (PTSW-184398)
Pro Tools 12 does not provide the Guitar Window for Eleven Rack that is available in Pro Tools 10 and lower. Avid has made available a 64-bit standalone version of the Eleven Rack Control Window found in Pro Tools 10 and earlier. Please see the following page for more information about the 64-bit standalone Eleven Rack Editor: http://apps.avid.com/eleven-rack/
Restarting a VENUE console, including the changing of system configurations, leads to an audio interface timeout with a connected HD Native system (PTSW-183745)
When connecting a HD Native system (PCIe or Thunderbolt) to a VENUE live sound system, VENUE HDx cards acting as your inter- face to Pro Tools timeout when restarting the VENUE console. This includes changing the VENUE system input configuration between stage and HDx sources (Virtual Soundcheck). After timing out, Pro Tools cannot record or playback until you quit and relaunchPro Tools.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 3
When multiple E3 engines are connected together (as part of a shared input VENUE S3L-X system), and at least one E3 engine in the system is connected to a Pro Tools computer, only one of the available E3 engines may be listed twice in the Playback Engine pop-up menu of the connected computer. (VSW-9462)
To workaround this issue in a shared input configuration, make sure that only one E3 engine is checked in the Audio MIDI Setup > Net- work Device Browser of any computer used for recording/playback with the S3L-X system. It is highly recommended that you make connections between E3s (or between E3s and any switches) after you have established connections between each E3 and its corre- sponding Pro Tools system. See the VENUE | S3L-X System Guide for more information.
The following sections document known issues you may encounter when using Pro Tools and Pro Tools HD 12.5.1, along with workarounds if they exist.
General Pro Tools Issues
Pro Tools quits unexpectedly while loading plug-ins on launch. (PT-206888)
On Pro Tools systems with several hundred plug-ins installed, Pro Tools may quit unexpectedly on launch. If this occurs, try the fol- lowing:
• Move approximately 100 plug-ins (or more) from the Plug-Ins folder to the Plug-Ins (Unused) folder (/Library/Application Sup- port/Avid/Audio/).
• Launch Pro Tools.
• Quit Pro Tools.
• Move the plug-ins back from the Plug-Ins (Unused) folder to the Plug-Ins folder.
• Launch Pro Tools. Pro Tools does not play back immediately after importing a large and complex AAF sequence (UME-905) Importing a complex AAF sequence that contains many video files and edits may cause Pro Tools to be in a Play/Pause state after all files have finished linking. This may also happen when reopening the session. If you encounter this, stop the transport, wait 30 seconds, and then attempt playback again. To avoid this problem completely, you can bounce the video and re-import, or request that the video editor flatten the video upon export. Offline Bounce takes much longer than expected (PT-202888) Offline Bounce times can increase significantly in sessions that have output and input assignments cascaded across tracks (for example: Track 1 output is assigned to Track 2 input, Track 2 output is assigned to Track 3 input, and so on). When importing session data, automation is replaced instead of overlaid when using Adjust Session Start Time to Match Source Start Time (PTSW-149273) Automation can sometimes be replaced instead of overlaid when using Adjust Session Start Time to Match Source Start Time when im- porting session data. This issue may occur if the source session start time (of the session being imported) is earlier than the current ses- sion start time. This issue can be avoided if you instead import the session data from the session with the later start time into the session with the earlier start time. You must also not enable the Adjust Session Start Time to Match Source Start Time option, and select Main- tain Absolute when prompted. Automatic Delay Compensation cannot not be applied to tracks recording from different types of sources (PTSW-157960) Automatic Delay Compensation cannot compensate for cascaded records that use both I/O and bus inputs to recording tracks. An ex- ample of this is feeding an audio track (in record) from an audio input, and then bussing the output of the track to another audio track also in record. The first audio track will be compensated but the second cascaded track will not be. (This is not a common workflow.) Audio scrubbing is offset by the overall system delay when Automatic Delay Compensation is enabled (PTSW-150138) With Automation Delay Compensation enabled, when scrubbing audio the output is offset by the overall system delay (displayed in the Session Setup Window). Large system delays cause a noticeable offset. To avoid this issue, you can disable Automatic Delay Compen- sation when you want to scrub audio for editing.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 4
Cannot run Reason as ReWire clients if they have not first been launched and set up as a standalone application (PTSW-133070)
Reason needs to be launched and setup as a stand-alone applications before running them as a ReWire clients with Pro Tools. Do the following:
• Launch Reason in stand-alone mode and follow the on-screen instructions.
• Quit Reason.
• Launch Pro Tools and insert Reason as a ReWire plug-in on an audio, Auxiliary Input, or Instrument track. Exporting interleaved BWF files from Pro Tools 10 or higher and importing into Pro Tools 9.0.x and lower may cause Pro Tools to quit unexpectedly (PTSW-151579) When exporting any greater-than-stereo multichannel interleaved WAV (BWF) files other than 5.1 from Pro Tools 10 or higher and then importing them into Pro Tools 9.x or lower, Pro Tools quits unexpectedly. To avoid this problem, export audio files for import into lower versions of Pro Tools in another file format (such as AIFF or multi-mono). AAF files that contain AMA-linked audio cannot be imported (PTSW-182322) Pro Tools cannot import AAF files that contain AMA-linked audio files. AMA-linked audio must be imported or transcoded in Media Composer before the AAF is exported. Unrendered mix and match AAFs will not properly import (PTSW-181825) If the error “A video file and its associated clips were removed because its timecode rate is incompatible with the project type” appears, it is likely that your AAF contains unrendered mix and match video. To avoid this, render mix and match AAFs from Media Composer before or during export. Auxiliary Input tracks can be inadvertently switched to “Frames” view (PT-211962) When simultaneously switching the track views of Auxiliary Input tracks and any other track types, it is possible for the Aux tracks to display “Frames” view. Should this issue occur, manually select the desired track view from the Track View selector menu since the track view keyboard shortcuts may not operate on the affected Aux tracks. Clip names appear incorrect after selecting Field Recorder channel matches, or expanding to new tracks. (PTSW-136012) This can occur if the file name of a Field Recorder channel match contains a hyphen followed by a number greater than zero. Pro Tools names new clips by incrementing the number after the hyphen. If a field recorder file is already named in this way (such as “Filename- 01”), then new clips created by selecting a Field Recorder channel match or by expanding a track may have names different from the parent file. To avoid this situation, avoid using hyphens in Field Recorder file names. Field Recorder matches appear offset after AudioSuite rendering if the session timecode rate does not match the file timecode rate (PTSW-152147) If a portion of a file has been rendered with an AudioSuite plug-in, an offset can occur when expanding field recorder matches in cases where the session timecode rate does not match the timecode rate of the audio file. To avoid this issue, you can either render the whole file with AudioSuite (rather than only a portion of the file), or use Whole File mode when rendering AudioSuite processing. External Field Recorder matches do not show up after an initial index pass (PTSW-180659) If external field recorder matches do not show up on a field recorder track after the initial index pass, save and reopen the session. Projects and Collaboration Creating or receiving new projects or tracks may result in a “Permission denied (13)” dialog (PT-212334) When creating or receiving new projects or tracks, a “Permission denied (13)” dialog may be displayed. Should this issue occur, open the “Operation” tab in the Pro Tools Preferences window and, in the “User Media and Settings Location” pane, click the Project Media Cache “Change” button to set a new location for the Project Cache. The new location should be a folder either outside of the default Pro Tools folder or off of the startup disk if possible.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 5
Switching user accounts may not refresh all information in the Dashboard (PT-213430)
In some cases switching accounts can cause account data to linger in the Dashboard, showing storage usage from the previously signed in user. To ensure the latest data is being reflect, quit and relaunch Pro Tools and sign in to the desired user.
It is strongly recommended that you do not log in to the same project on multiple systems using the same Avid Master Account login
When you are connected to the internet and then you open a Pro Tools Project, Pro Tools checks to see if there are any other machines that are logged in to the same Avid Master Account and both with the same project open. If the project is detected as being open on an- other system it should be closed. This prevents the project bundle on the cloud from becoming corrupted by competing updates from multiple systems using the same account. To avoid this situation, it is strongly advised that you close projects when leaving systems idle if it is possible that you will be working on the same project from another computer with the same Avid Master Account.
Collaboration may be impeded for users with projects of the same name (PT-213948)
If a user accepts the invitation to collaborate on a Project with the same name as an owned Project in their account, it may be possible for only the owned Project to appear in their Dashboard and Artist Chat windows. To avoid this issue, be sure that no Project name con- flicts exist before accepting invitations to collaborate.
Assertions and AAE errors may occur when Project Media Cache exists on multiple identical volumes (PT-213652)
Assertions and AAE errors may occur when the Project Media Cache folder exists on multiple identical volumes. To avoid this issue, ensure that the Project Media Cache remains set to different locations on each volume, rename each volume if possible, or unmount any identical volumes while working with projects in Pro Tools.
Disconnecting from the internet or closing a project during project synchronization can result in failed project synchronization. (PT-202643)
To prevent potential synchronization with projects, do not disrupt the project synchronization while it is in progress. Avoid disconnect- ing from the internet, turning off WiFi, shutting your laptop, or quitting Pro Tools | First during this time. To monitor the progress of project synchronization, choose Window >Task Manager.
Change the default Project Media Cache location so that it is not on your system drive (PT-212755)
Projects in Pro Tools 12.5 default to storing cached project data in a common location in your local Documents folder. It is recom- mended that you change the default location of your Project Media Cache on the system drive to another location on any Avid-qualified storage. You can Change the location of the Project Media Cache in the User Media and Settings Project Media Cache preference in the Pro Tools Operation Preferences. Any form of Pro Tools compatible storage, including shared storage, is a valid location to cache your project data and media. However, at this time, multiple individual Pro Tools systems in a networked facility cannot refer to a shared cached project bundle on shared storage. If there are multiple systems in a facility with shared storage, each Pro Tools system must download its own project bundle to the specified local Project Media Cache bundle location.
Removing a collaborator from your project may not relinquish ownership of tracks claimed by that collaborator (PT-211627)
When a collaborator who has ownership over shared tracks is removed from a project that you own, their track ownership may not be automatically relinquished. Should this issue occur, click the Track Ownership button for these tracks and ownership should be returned to you after about five minutes.
Project uploads may pause while Shuttle Lock is active (PT-213277)
Entering Shuttle Lock mode while project uploads are in progress may temporarily prevent uploads from finishing until the playhead comes to a stop. To avoid this issue, confirm that all uploads have completed in the Task Manager before using Shuttle Lock mode in a project.
“Expand Alternates To New Playlists” may not trigger track or project uploads (PT-212809)
When a track has loop-recorded alternates that are not on any playlists, choosing to “Expand Alternates To New Playlists” may not trig- ger an auto-upload or allow manual uploading using the Track or Toolbar upload buttons. If this issue is encountered, making any change or edit to the track or its playlists will enable uploading with the Track upload button.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 6
Destructive Punch record passes are not transmitted to collaborators (PT-212577)
Using Destructive Punch to update a shared file does not transmit a track change and the file is not updated on collaborator systems.
Changed Display Name in Artist Chat is not updated in the Dashboard until signing out and signing back in (PT-209796)
After making a change to the Display Name in your Artist Chat profile, the Pro Tools Dashboard is not updated with the new user name until you sign out and sign out and back in.
Artist Chat messages of 1,800 characters or more may not be received or even sent (PT-211701)
Attempting to send an Artist Chat message of 1,800 or more characters can appear to send but may not be received by other users in the chat or they may not be sent at all. The actual maximum limit for Artist Chat messages is 2 kilobytes per message. It is recommended that uncommonly long messages be posted in shorter segments.
Dropped Keystrokes in Artist Chat and Sign On Window (PT-211627)
In some cases keyboard keystrokes will fail to be transmitted to the Sign On and Artist Chat windows.
Pasting a text string inside of the "< >" characters into Artist Chat results in a blank entry (CLOUD-3285)
Any text in contained by "<" and ">" is disallowed for security reasons. Please do not use these characters in Artist Chat messages.
When sharing a track with plug-ins such as Melodyne or Space, only the waveform cache inside the plug-in is uploaded and shared, but not the referenced audio file (PT-212607)
Media assets for Plug-ins (such as Melodyne or Space) that use external media, like a waveform cache or impulse responses, may not always be copied with the shared tracks to the cloud for use by other collaborators.
Master Faders assigned to mapped output busses function only on that specific bus, not for the output channel as a whole (PTSW-127517)
Because a Master Fader works on a bus, not on an output path or output channel, there may be certain configurations in which the level sent to the physical I/O is not reflected on any meters in the Pro Tools application. If the configuration includes output subpaths or has multiple busses assigned to a single output path, the overall signal level from these combined sources (including any clipping indication) will only be displayed on the interface itself. You can avoid using multiple output paths or output busses simultaneously by routing your sources to a single mapped output bus and assign a Master Fader to that.
Session templates retain Bus settings and some preferences, display settings, and window layouts (PTSW-47133)
Pro Tools session templates retain the bus settings and some of the preferences, display settings, and window layouts from the system on which the template was created. Consequently, creating a new session based on a template restores several session properties from the original system. These properties are retained by Pro Tools until you change them, or another session or template is opened that re- places them. This also means that if a new blank session is created after using a template, the properties from the template will be used for the new session.
The properties retained from templates include default track height, view settings, window size and position, and bus settings. You can update templates by making the desired changes, using the File > Save as Template command (be sure to select the “Install template in system” option), and then selecting the template you want to replace.
Opening a session saved to .ptf (Pro Tools 7–9) from Pro Tools 12.x or higher in Pro Tools 8.1 or lower results in incorrectly mapped IO (PTSW-194443)
For any session saved to .ptf (Pro Tools 7–9) from Pro Tools 12.x or higher requires that IO Settings be manually corrected when open- ing that session with Pro Tools versions 8.1 and lower. Manually map the correct IO settings in the IO Setup before playing back the session.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 7
File and Disk Management
After Relinking files the Relink window does not retain its “revealed/open” status (PTSW-178130)
Although the checkbox remains selected, the reveal status of volumes is not retained if the Relink window is automatically reopened. Be sure to reveal the volumes so that the enabled checkboxes are visible in order to reliably relink to missing files.
When relinking audio files, mismatched channel widths are not found (PTSW-189868)
When relinking audio files, it is possible to link files with different channel widths. This is not a supported workflow and may have un- predictable results. Ensure that the channel width of linked files match the channel widths of clips in the session to avoid this issue.
Maintaining phase coherency with Elastic Audio pitch processing (PTSW-20602)
When there is Elastic Audio Pitch processing enabled on a track, switching from Polyphonic, Rhythmic, or X-Form to Monophonic or Varispeed can disrupt phase coherency. To preserve phase coherency in this case, be sure to clear all Elastic Audio Pitch processing from the track before switching to the Monophonic or Varispeed algorithm.
Drift in an audio file may occur when using Elastic Audio and the Monophonic or X-Form algorithms (PTSW-33768)
Drift in an audio clip may occur when using elastic audio depending on how much the clips is expanded or compressed when using the Monophonic or X-Form algorithms. If you are using elastic audio with material that contains transient information in it that you would like to keep from drifting, you should use the Polyphonic or Rhythmic algorithms.
Default Input Gain preference is only for Elastic Audio imported at session tempo (PTSW-34096)
The Default Input Gain preference in the Elastic Audio section of the Processing Preferences page is for Elastic Audio Imported at Ses- sion Tempo only. This preference option will not function unless Preview in Context is enabled in Workspace, and/or “Drag and Drop from Desktop Conforms To Session Tempo” is enabled in the Processing Preferences page.
Displayed Timebase is incorrect after importing Elastic Audio tracks (PTSW-46897)
The incorrect timebase is displayed after importing Elastic Audio tracks to existing tracks with opposite timebase. You will need to man- ually select the correct timebase for the affected tracks.
Elastic Audio clips on Playlist lanes are not rendered (PTSW-47311)
In Playlists View, any Elastic Audio clips on Playlist lanes are not rendered (waveform is “off-line”) when changing the track’s Elastic Audio processing from Real-Time to Rendered. Using the object grabber to select any off-line clips, promoting them to the main playlist or copying and pasting the clips in place will render using the selected Elastic Audio algorithm.
Clip Groups containing Elastic Audio are not recognized as Elastic if the Clip Group itself has not had any Elastic functions applied (PTSW-34335)
If a clip group contains Elastic Audio inside it, but no Elastic Audio operations have been performed on the outermost level of the clip group itself, then the clip group will not register as Elastic Audio. When used to create a new track, the track will not automatically be Elastic Audio–enabled, and the elastic audio inside the clip group will be rendered using the default Elastic Audio plug-in for the ses- sion. As a workaround, add a warp marker to the clip group to force it to register as an elastic clip. Or, create an Elastic Audio–enabled track first, then add the clip group to it.
Cannot import Elastic Audio tracks with the Consolidate From Source Media option (PTSW-33894)
Use Copy from Source Media to import Elastic Audio tracks.
Timing inaccuracy in audio files converted from CAF and MP3 with Preview In Context enabled (PTSW-46707)
Audio files converted from CAF and MP3 with Preview In Context enabled can cause timing inaccuracies (gaps in the audio and inner- clip asynchronous transients issues). This is inherent with compressed file formats.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 8
Track Commit and Track Freeze
Frozen Tracks are opened in a partially frozen state in certain versions of Pro Tools 12 (PT-208260)
Opening sessions created in Pro Tools 12.4 that have frozen tracks in Pro Tools 12.0 to 12.2.1 will result in graphical issues for "frozen" clips (such as waveforms overlaying clip boundaries, missing clip boundaries, or clip boundaries that move without waveforms), tracks and inserts (inserts can be in an inactive/frozen state and cannot be activated). In versions of Pro Tools 11.3.2 and earlier, or Pro Tools 12.3, these problems do not occur and the track is opened in it's unfrozen state.
Relinking to missing rendered “frozen” Auxiliary Input tracks does not yield any results when reopening a session (PT-210026)
If there is missing rendered audio from frozen Auxiliary Input tracks, they cannot be relinked after first time of reopening a session. Task Manager will report: “Some Files to relink Not Found.” To correct this issue, close and reopen the session, and try to relink to the missing files again.
`Frozen tracks are not translated by AAF and Interplay unless committed (PT-210128)
Only the unprocessed source audio on frozen tracks is translated by AAF and Interplay To ensure that the desired track audio processing is translated accurately for AAF sequences (and Avid Interplay), commit those tracks rather than freeze them.
Committing clips on Instrument tracks by dragging them to audio tracks with the Downmixer plug-in may render an incomplete clip. (PT-207317)
Committing MIDI clips on Instrument tracks by dragging them to audio tracks with Downmixer may render an incomplete clip. Using the Grabber tool on these incomplete clips may not function over the incomplete areas of the clip. To avoid this issue, Commit Instru- ment track clips to new Audio tracks before inserting the Downmixer plug-in.
When committing from two or more Instrument tracks in a session with tempo changes by dragging and dropping to audio tracks, and where the Instrument tracks include a mix of sample-based and tick-based tracks, the tick-based committed clip is trimmed to matched the source MIDI original duration even though the audio committed from tick-based MIDI follows the tempo changes. (PT-208300)
To avoid this issue, use the Trim tool to reveal the rest of the committed audio or commit sample-based MIDI clips and tick-based clips separately.
When recording MIDI, Wait for Note does not respond to MIDI input from ReWire (PTSW-30511 and PTSW-34550)
When performing a MIDI record, Wait for Note will not respond to any MIDI received from ReWire. If you are recording MIDI gen- erated from a ReWire application, you will have to start the transport manually or use a countoff instead of Wait for Note.
When using Import Session Data on a MIDI track with Real-Time Properties enabled and set to using Diatonic transposition, transposition is based on the first key signature in the session only (PTSW-49297)
When importing session data from a session that includes multiple key signatures and a MIDI or Instrument track with the “Transpose in Key” Real-Time property enabled, the transposition will be based only on the first key in the session. This can be corrected by tog- gling the Real-Time Properties off and on; then the diatonic transposition will be correct for each key.
Clip outlines do not resize when moving or copying tick-based midi clips across tempo changes (PT-208692)
Clip outlines do not resize when moving or copying tick-based midi clips across tempo changes. Additionally, if View > Clip > Trans- parency is enabled, MIDI notes are misaligned with clip boundaries.
For known issues about specific plug-ins, see the Audio Plug-Ins Read Me.
When opening legacy sessions, the 4-band EQ III plug-in is converted to the 7-band EQ III plug-in
The AAX EQ III plug-in does not have a 4-band option. Pro Tools will automatically convert 4-band EQ III instances into 7-band in- stances if you are using only AAX plug-ins.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 9
When replacing one plug-in with another, the new plug-in inherits previously auto-enabled parameters. (PT-202826)
With the Plug-in Controls Default to Auto-Enabled preference enabled, all available automation parameters become unexpectedly re-en- abled (merged) after replacing one instance of the plug-in with another. Disable this preference before replacing one plug-in with an- other to avoid this issue.
On Mac OS X 10.10.x, Avid Core Audio Plug-in causes audio disruption with Native Instrument plug-ins (PT-201944)
You cannot launch Native Instruments plug-ins if the Avid Core Audio plug-in is installed. To avoid this issue, remove the Avid Core Audio plug-in from the Audio/Hal folder.
Custom location for Avid Virtual Instrument content is not remembered (PTSW-187501)
When installing AIR Creative Collection, if you choose a custom location for the content, that location is not remembered, resulting in error messages when you try to use a virtual instrument plug-in (Boom, Mini Grand, or Xpand) that references a “.big” content file. The location is not remembered after quitting and relaunching Pro Tools.
To avoid this error, move or reinstall the AIR Creative Collection content to the default location.
"One or more plug-ins could not be made active because there is not enough free DSP (AAE error ?7050 was encountered)" (PT-210405)
The following Audio Engine error appears even though the "Open Unresourced DSP Plug-ins as Native" preference is enabled: "One or more plug-ins could not be made active because there is not enough free DSP (AAE error ?7050 was encountered)." Running out of DSP resources while working in a session or project can result in a state where Pro Tools is unable to convert unresourced DSP Plug- ins to Native automatically. To resolve this issue, ensure that the "Open Unresourced DSP Plug-ins as Native" preference is enabled and then close and reopen the session or project: or manually convert each of the unresourced DSP plug-ins.
Some plug-ins require exclusive use of a DSP chip on HDX hardware-accelerated systems (PTSW-154614)
Certain plug-ins, such as ReVibe and Reverb One, use direct memory access (DMA) on HDX cards. DMA plug-ins cannot share HDX DSP chips with other plug-ins. Additionally, even though DMA plug-ins of the same type can share a single HDX DSP chip (for ex- ample, multiple ReVibe plug-ins can use the same HDX DSP chip), they must be of the same channel width (DMA plug-ins of the same type cannot share the same HDX DSP chip if they have different channel widths).
Pro Tools stops working when opening a session with Structure Free (PTSW-131965)
When opening a Pro Tools session that uses Structure Free, Pro Tools may hang temporarily if Structure Free is looking for files in a directory where the files are not present.
AudioSuite and Clip Groups (PTSW-57457)
AudioSuite plug-ins handle Clip Groups in the Clip List slightly differently than audio files. With audio files, an AudioSuite process can be applied to all copies of a unique audio file which appear in your session by selecting your target as Clip List in the AudioSuite plug- in window and selecting Use in Playlist. However, if your target is set to Clip List in the AudioSuite plug-in window while you have a Clip Group selected, Pro Tools does not recognize the Clip Group as processable audio and will present a No Audio was Selected error. This is because a Clip Group is not treated as audio until it is actually used in a track.
To apply an AudioSuite process to all copies of a Clip Group in a session at once, do the following:
. 1 Select the Clip Group to be processed.
. 2 From the Clip List menu, select Ungroup All. All elements of the group will remain selected.
. 3 Perform AudioSuite processing.
. 4 From the Clip List menu, select Regroup.
. 5 When prompted, select Modify to apply the AudioSuite Process to all copies of the Clip Group in the session, or Copy to apply it only to the selected Clip Group.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 10
Pro Tools does not play back when an invalid Word Clock or AES/EBU sync source is selected on SYNC HD (PTSW-156651)
When attempting to initiate playback, playback will fail if a SYNC HD is connected to an HDX card and an Avid audio interface with no connections to either the word clock or AES/EBU ports. Ensure that the clock is set to a working clock source to resolve this issue.
In Avid DigiTest, the reported slot number may not correspond to the physical slot number in the computer (PTSW-155373)
In Avid DigiTest, the slot number reported for HDX cards starts from 0 on up. For example, “Slot 1” does not necessarily correlate to the first physical slot in the machine. If you have an HDX card that is having problems, match the Serial Number ID on the back of the card with the Serial Number ID displayed on the Slot Info page in Avid DigiTest.
Pro Tools does not use HDX hardware if a Core Audio application is using HDX hardware (PTSW-155010)
When launching Pro Tools HD on an HDX hardware accelerated system, Pro Tools will use the Pro Tools Aggregate I/O as the Play- back Engine if a Core Audio application has already engaged the HDX hardware. Be sure to quit all Core Audio applications before launching Pro Tools HD to ensure that Pro Tools HD can use HDX hardware.
Assertions occur when opening a Pro Tools 12 session that uses the Native format of HEAT in Pro Tools 11.x and assigning track outputs. (PT-204124)
A session saved from Pro Tools HD 12 on a Native system with HEAT enabled might not display DSP usage for HEAT when opened on Pro Tools 11.x on an HDX system. To avoid these assertions and see DSP usage for HEAT on the HDX system, turn HEAT off and then back on.
HD Native PCIe Systems
Audible pops and clicks occur when changing buffer sizes (PTSW-125715)
Pops and clicks may occur when changing the Hardware Buffer Size (H/W Buffer Size) in the Playback Engine dialog while monitoring live audio through HD Native hardware. Avid recommends not changing the Hardware Buffer Size while monitoring live audio to avoid this problem. If you must change the Hardware Buffer Size while monitoring live audio, be sure to lower the monitoring volume to avoid any possible damage to your speakers.
There is no visual indication of bypassed plug-ins when Low Latency Monitoring is enabled with HD Native PCI. (PT-202108)
When using Low Latency Monitoring on a system with HD Native PCI, there may be no visual indication for bypassed plug-ins. Despite this, enabling the Low Latency Monitoring option will in fact bypass all plug-ins in the session.
HD Native Thunderbolt Systems
HD Native Thunderbolt headphone output stops working when low latency monitoring is enabled (PTSW-169936)
The headphone output on the HD Native Thunderbolt does not function when low latency monitoring is enabled. In this case, use alter- native monitoring source such, as an Avid HD OMNI.
HD Native Thunderbolt prevents the computer from waking after sleep (–9171 error) (PTSW-169172)
Pro Tools HD and HD Native Thunderbolt do not support the sleep function of Mac OS X. If encountered, disconnect HD Native Thun- derbolt to wake the computer. Disable all sleep functions in System Preferences (except display) and shut down the computer. Recon- nect HD Native Thunderbolt and start the computer.
HD Native Thunderbolt reports a clock error at higher sample rates (PTSW-168819)
With some computers, you may encounter an audio clock error when recording at higher sample rates (such as 96 kHz) and with lower HW Buffer Size settings (such as 128 samples or less). In general, higher HW Buffer Size settings are recommended at higher sample rates. For example, at 96 kHz, a HW Buffer Size setting of 256 samples or higher is recommended.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 11
HD Native Thunderbolt is only supported as the first or second thunderbolt device in a thunderbolt chain at sample rates up to 96 kHz, and it must be the only Thunderbolt device in a chain at any sample rate above 96 kHz (PTSW-168229)
HD Native Thunderbolt is only supported as the first or second Thunderbolt device in a Thunderbolt chain at sample rates up to 96 kHz, and must be the only thunderbolt device in a chain at any sample rate above 96 kHz. Visit the compatibility pages on the Avid website for more information (www.avid.com/compato).
Pro Tools quits unexpectedly when selecting HD Native Thunderbolt in the Playback Engine (PTSW-167511)
After disconnecting and reconnecting HD Native Thunderbolt from your computer, Pro Tools quits unexpectedly when selectingHD Native Thunderbolt in the Playback Engine. After disconnecting and reconnecting HD Native Thunderbolt, restart your computer to avoid this problem.
Using the HD Native Thunderbolt headphone output with surround monitoring (HDM-13)
Headphone monitoring with HD Native Thunderbolt is set to mirror Pro Tools output channels 1 and 2 on the first audio interface. To use HD Native Thunderbolt headphone monitoring with sessions that use surround formats (such as 5.1),change the surround monitor- ing path in I/O Setup so that the Left channel is mapped to Output channel 1 and the Right channel is mapped to Output channel 2.
Stereo panning is not available with Pro Tools | Control and Pro Tools 12.3 using EuControl version 3.3.1. (EUCON-4282)
When using EuControl 3.3.1 there is no stereo pan available on Pro Tools | Control for stereo tracks in Pro Tools. Pan controls appear on Pro Tools | Control for mono tracks only. Avid is working to provide an update to EuControl as soon as possible that will address this issue.
Selecting a track in Pro Tools auto-scrolls to the first track when going past the bank limits of an Artist series controller. (EUCON-3852)
When the Edit Window follows Bank Selection or the Mix Window follows Bank Selection preference is enabled, if you select a track in Pro Tools that is beyond banking limits of an Artist control surface, that track auto scrolls to the top of the Edit window or far left of the Mix window. In order to avoid this behavior, de-select the corresponding preference, either Edit Window follows Bank Selection or the Mix Window follows Bank Selection.
Trim Scrub and Trim Shuttle don’t work on clips with fades (PTSW-46911)
If a clip has fades, Trim Scrub and Trim Shuttle don’t work when trying to trim using a control surface. To work around this problem, remove any fades on the clip, then execute the Trim Scrub or Trim Shuttle, and then restore the fades.
Used HW output path indication (101095)
In Assign Matrix mode on your control surface, Insert mode used for the hardware output path will not have amber background indi- cating that it's already assigned after switching to a different insert on the same track.
Color indication on plug-in controls in Learn mode (PTSW-18480)
When a plug-in is in Learn mode and the track with this plug-in is not focused on the main ICON unit, all automation LEDs in the plug-in window will be red if the track is in one of auto write modes. This conflicts with red color indication on the plug-in control, which is armed for mapping. The workaround is to set the track with plug-ins to Read automation mode.
SignalTools meter ballistics on control surfaces (PTSW-52799)
SignalTools RMS, VU, BBC, Nordic and DIN meters will display inaccurate decay times when viewed on a control surface. Unaffected types are Peak, VENUE, and Peak + RMS, which only reports the Peak meter to the control surface. The attack times of the affected me- ters are not affected, only the decay times. All meter types display accurately in the plug-in window.
Channel Strip plug-in Expander/Gate meters appear in the Compressor/Limiter meter Instead of in the Expander/Gate meter in D-Control Dynamics section (Main Unit) (PTSW-150897)
The Avid Channel Strip plug-in uses shared meters for Expander/Gate and Compressor/Limiter processing. Because of this, both Ex- pander/Gate and Compressor/Limiter metering appear only in the Compressor/Limiter meter in D-Control Dynamics Section (Main Unit).
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 12
Pro Tools transport must be stopped when recalibrating ICON faders (78074)
The transport in Pro Tools must be stopped when recalibrating faders on D-Command and D-Control. If one or more faders need cali- bration do the following: Stop playback, enter Utility mode, press TEST, press FADER, and press RECAL. After recalibrating faders. exit Utility mode.
Adjusting Clip Gain with the Jog Wheel on a EUCON control surface can result in Pro Tools quitting unexpectedly (PTSW-155028)
Adjusting Clip Gain using the Jog Wheel on a EUCON control surface during playback can result in Pro Tools quitting unexpectedly. You can avoid this issue by using the mouse or key commands to adjust clip gain instead.
Video Engine may fail to initialize for non-administrator accounts (UME-1246)
For non-administrator OS X users, the Video Engine may not initialize if it has never been initialized under an admin account first. To avoid this issue, launch Pro Tools as an admin and initialize the Video Engine in a session before doing so as a non-admin user.
Playback of QuickTime video in Pro Tools may stutter or drop frames
When monitoring QuickTime playback in the Pro Tools Video Window on the computer screen, the video image may stutter or drop frames. To improve results with QuickTime playback, try any of the following:
• AsecondProTools,MediaComposer,orSymphonyDXVideoSatelliteoptionoffersguaranteedperformanceforAvidvideoplay- back with a primary HDX or HD Native system. QuickTime files that contain multiple CODECs may not import (UME-835) If the Pro Tools tells you that a file cannot be imported because it may be unsupported, check to see if the file contains more than one CODEC. This can be done by opening the file in QuickTime player and examining the file properties. QuickTime files that contain more than one CODEC are not officially supported for import into Pro Tools. Playback of PhotoJPEG-encoded video experiences dropped frames or stuttering (PTSW-183056) PhotoJPEG is not a preferred CODEC for video playback in Pro Tools. It you experience performance issues with this CODEC, please transcode to a preferred Avid CODEC, such as DNxHD or DV25. This can be done by bouncing the file to QuickTime from within Pro Tools and choosing the “Advanced Settings” in the bounce window. Video pull factor may become invalid when video hardware is enabled (PTSW-180554) If a software video pull factor of 0.1% is set while video hardware is disabled, enabling the video hardware may create an illegal pull setting. Video hardware only supports 0.1% pull ups at 24pPAL rates, and 0.1% pull downs at 25pPAL rates. If the pull rate is set to 0.1% at any other rate while video hardware is enabled, manually select an available option from the pull menu, which may be “none.” Video may not stay in sync when video hardware is attached and Pro Tools is locked to an external clock (PTSW-178722) If both Pro Tools and an attached video peripheral are each resolved to an external clock, but the clock is not derived from the same source, video will not stay in sync. An example of this would be if the video peripheral is locked to black burst, and the audio peripheral is locked to an audio clock not derived from the same video black burst, such as SPDIF. In this scenario, setting the video peripheral to lock to its own internal clock will allow Pro Tools to compensate for video drift over time. Unsupported QuickTime video formats (PTSW-52140, PTSW-52155, PTSW-52156, PTSW-53625, 72961) Several video formats supported in QuickTime are not supported in Pro Tools. These include .DivX, .flc, .m4v and .3gp format movies. Attempting to import these will generate errors or will fail to import.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 13
True 30 and 60 Frame per Second video files cannot be properly Bounced to QuickTime (PT-214070)
Pro Tools does not support QuickTime (or Avid) video media of a true 30 or 60 frames per second playback rate. Clips of such rates can- not be bounced to a supported video frame rate using Pro Tools to convert the file. You will need to convert the file to 29.97 or 59.94 frame rates in another application before using them in Pro Tools.
QuickTime files that contain multiple CODECs may not import (UME-835)
If the Pro Tools tells you that a file cannot be imported because it may be unsupported, check to see if the file contains more than one CODEC. This can be done by opening the file in QuickTime player and examining the file properties. QuickTime files that contain more than one CODEC are not officially supported for import into Pro Tools.
“Error reading video in the QuickTime files” when importing some MPEG 1 and 2 video files in Pro Tools (PTSW-178017)
Some MPEG1 and MPEG2 files cannot be opened by Avid applications, including Pro Tools. Transcode these files to one of our pri- mary CODEC such as DNxHD or AppleProRes for use in Pro Tools to avoid this issue.
3G2 file extension is not supported for video import (PTSW-178015)
Pro Tools 11 and higher provides support for the .3GP file type extension for video import. These are video files often created on mobile phones. The second generation of this format uses the file extension of .3G2. Files with the .3G2 file extension will be filtered out as unavailable for video import. These .3G2 files may be available for import if their file extension manually changed to .3GP. If the files remain unavailable for import after changing their extension, they will need to be converted to an explicitly supported format such as DNxHD or AppleProRes for use in Pro Tools.
Video I/O Settings Pane appears inactive after editing video track during play (PTSW-183106)
If you edit video during playback, the I/O Setting pane for the Video track appears inactive during playback, preventing you from open- ing the track’s Output Setting tab. To access I/O settings for the track, stop playback.
Third-Party Video Peripherals
The following issues may occur with third-party video hardware. Please contact your hardware vendor for support.
u In some cases, video will not stay in sync over time if the video peripheral is not, or cannot, lock to video reference. If you experience this, a workaround is to set the Pro Tools clock to internal. This will cause the video peripheral to slew overtime and stay in sync with Pro Tools. (THPV-2)
u When Pro Tools is running with a Blackmagic DeckLink II Extreme or Intensity video capture and playback PCI-e card installed, launching Blackmagic Design’s Deck Capture utility, Final Cut Studio, or any other application which supports Black Magic hardware for video output, can result in system instability. To avoid any potential system instability only use one Blackmagic DeckLink–aware application at a time. (PTSW-19486)
u With some peripherals video playback will be one frame out of sync with Pro Tools audio. To compensate for this, choose Setup > Video Sync Offset and enter a 1 frame offset. (THPV-9)
u Some video peripherals will lose AV Sync when playback is attempted from a 9-pin controller when linked with other Pro Tools or Media Composer Satellites. To avoid this issue, attach the 9-pin controller to a Pro Tools Satellite that does not have a third-party video peripheral attached. (PTSW-187385)
u With some video peripherals, the video output will be scrambled when video is not loaded in Pro Tools, or when the video peripheral is disabled. (THPV-32)
23.976 or 24 fps Sequence Start Time Ending In Digits Other than “:00” Causes Time Code Offset
Media Composer uses NTSC or PAL time code when setting the sequence start time regardless of the format selected by the user for display. When you are working on a video satellite project at 23.976 or 24 fps, a Media Composer sequence with a start time that ends in a value other than :00 causes an offset between Pro Tools and Media Composer at the session start. For example, the start time 45:02:10:15 (ending in :15) would cause an offset, but the start time 45:02:10:00 (ending in :00) would not.
As a workaround, always set your Media Composer sequence start time to a time code value ending in 00.Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 14
Cueing from Media Composer in a 720p Project Causes 1-Frame Offset (Item # 98460)
In 720p projects, Media Composer counts at 50 or 60 (59.94) progressive fps—depending on the project type—while Pro Tools counts at 25 or 29.97 frames per second. When you cue a sequence from the video satellite in a 720p project, the Pro Tools edit cursor can be offset by as much as one frame.
As a workaround, cue and play back from Pro Tools when working with a 720p project in a video satellite system. This ensures that the two applications are always in sync. It is not possible to cue to odd 50 or 60 frame boundaries (for example, frame 47) from Pro Tools.
Audio and video may drift out of sync In Satellite Mode in certain conditions (Items # UDevC00090064, UDevC00090078, UDevC00088666, UDevC00089437, UDevC00087542)
When operating in Satellite mode, audio and video output from Media Composer may drift out of sync by as much as one frame in any of the following conditions:
• Whenviewingvideofullscreenin1394mode.Thisisduetothedifferencebetweenthemonitor'srefreshrateandthevideoreference rate.
• WhentheEditPlayRateofthevideodiffersfromtheframerateofthevideoreferencesignal.(Forexample,thisoccurswitha24p NTSC project with 23.976 Edit Play Rate and NTSC reference signal.)
• WhenloopingaselectionthatisnotalignedtovideoframeboundariesinProTools.Asaworkaround,makeyourselectioninPro Tools using Grid mode with the Grid value set to 1-frame increments—especially when it is necessary to loop several times with- out stopping. When scrubbing with a Video Satellite, video may be offset by several frames (UME-870) Audio/video sync is not frame accurate when scrubbing a Video Satellite. An offset of several frames may be seen between the Media Composer system and the Pro Tools system. To monitor frame accurate video when scrubbing, use the Pro Tools Video window. When done scrubbing, you can continue to monitor frame accurate video on the Video Satellite. General Localization AAF/OMF sequences with non-English characters import with garbled clip names or won't relink (PTSW-33569, PTSW-99570, PTSW-33826) If an AAF/OMF sequence containing files or clip names with non-English characters is exported from a Mac-based Pro Tools 7.3.1 sys- tem (or lower), it may not import correctly into Avid Media Composer, or Pro Tools 7.4 and higher systems on Windows or Mac. Con- versely, AAF/OMF sequences with non-English characters exported from any Pro Tools 7.4 or higher system (or higher) may not im- port correctly into a Mac-based Pro Tools 7.3.1 (or lower) system. To relink the files, select “Manually Find and Relink,” then deselect all options except “Find by file ID.” Clip names may appear garbled. Known Issues with CoreAudio Hardware Drivers Limitations of the Avid CoreAudio driver with CoreAudio Manager The 003 systems have the following limitations: Pro Tools HD and Pro Tools with 003 systems require exclusive access to Pro Tools hardware. You cannot use CoreAudio applications and Pro Tools with these systems at the same time. To use Pro Tools, make sure you quit any CoreAudio applications before launching Pro Tools on these systems. To use a CoreAudio application with these systems, make sure you quit Pro Tools before starting the CoreAudio application. u The Digi CoreAudio Driver cannot be used to preview sound files from the Mac Finder while Pro Tools is running. When a sound file is located in the Mac OS X navigation window, a QuickTime transport bar is displayed next to it. The QuickTime transport bar lets you audition the sound file. With USB audio interfaces, you can preview sound files from the Mac Finder as long as Pro Tools is not run- ning. Regardless, with FireWire and Avid HD audio interfaces, the sound will always play back though the Mac built-in audio controller (through the Mac speaker or headphone jack). However, if you double-click a sound file, the QuickTime application will launch, which can use the Digi CoreAudio Driver for playback. The CoreAudio Driver cannot be used for playback of Mac System Sounds.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 15
Pops when changing sample rates (PTSW-58770)
With the CoreAudio Manager, your Pro Tools hardware may produce a “pop” or “click” sound if Pro Tools was last used at a sample rate different from the one the new CoreAudio client is set to use.
Audio streaming problems when using very low H/W Buffer Sizes with 3rd party Core Audio applications (such as Logic) (PTSW-154719)
You may experience audio streaming problems when using Avid hardware with 3rd party applications such as Cubase or Logic and playing back at the lowest buffer size. The lowest supported buffer sizes when using Avid hardware are 64 at 44.1 and 48 kHz sessions, and 128 at 88.1 and 96 kHz.
Buffer sizes incompatible with Pro Tools hardware (39542)
In Cubase, Traktor, Live, and certain other applications, you can select Buffer Sizes that may be incompatible with your Pro Tools hard- ware. Selecting incompatible buffer sizes results in distorted sound and may cause other problems. Please make sure to select Buffer Sizes listed in the following chart:
Cubase SX Buffer Sizes Supported by Avid Audio Hardware
Pro Tools reports a –6101 error connecting or disconnecting headphones or audio cables from the audio output jack on your computer while using Pro Tools (PTSW-159325)
You may encounter a –6101 error when connecting or disconnecting headphones or audio cables from the audio output jack on your computer while using Pro Tools. To avoid this problem, quit Pro Tools before connecting or disconnecting your headphones or audio cables.
Known Issues with Audio Interfaces
Noise in the output signal from HD OMNI with digital input (PTSW-1614)
If HD OMNI is connected to a digital source with a mismatched clock and Sample Rate Conversion (SRC) is not enabled, you will hear noise (including loud “pops”) in the output signal. To correct this problem, either enable SRC or ensure that the clock of the digital source and HD OMNI are matched correctly.
HD OMNI front panel Setup menus are unresponsive after Pro Tools quits unexpectedly (PTSW-125692)
HD OMNI will not automatically recover “stand-alone” mode if Pro Tools quits unexpectedly (or if you disconnect the DigiLink cable from HD OMNI while Pro Tools is running). As a result, some of the SETUP functions accessible from the front panel will be unavail- able. Power cycle HD OMNI to recover stand-alone mode.
Graphic redraw problems in the Hardware Setup dialog (PTSW-122690, PTSW-1346, and PTSW-1235)
When changing the Hardware Setup configuration for HD OMNI, it is possible to encounter graphics redraw problems in some cases. To force a graphics redraw of the Hardware Setup dialog, close and reopen the Hardware Setup dialog.
No sound on output after hardware reset (PTSW-126575)
After resetting the HD OMNI interface to the default factory settings using the front panel controls, the HD OMNI interface stops emit- ting sound in sessions where the outputs are not assigned to the Monitor output path. To correct this problem, press the ALT monitor button to switch to the ALT Monitor path, and then press it again to switch back to the Main Monitor path.
Avid Audio Hardware
Supported Buffer Sizes
128, 256, 512, 1024
128, 256, 512, 1024
003, 003 Rack, 003 Rack+, Eleven Rack
64, 128, 256, 512, 1024
Mbox® and Mbox 2-series interfaces
32, 64, 128, 256, 512, 1024
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 16
Loss of Monitor path when launching Pro Tools with HD OMNI off or disconnected (PTSW-127313)
When launching Pro Tools and opening I/O Setup after powering off HD OMNI or disconnecting it from the system, the inactive Mon- itor path is not present in Output tab. You may need to restore the default I/O Settings and remap the corresponding Output Busses.
Output paths are not automatically created in the Output page of the I/O Setup after disabling the corresponding Monitor path in the Monitor page of the Hardware Setup and re-assigning the Outputs from “None” to physical outputs in the Main page of the Hardware Setup (PTSW-127559)
After disabling the Monitor path in the Monitor page of the Hardware Setup and re-assigning the corresponding Outputs from “None” to physical outputs (such as “A 1-2”) in the Main Page of the Hardware Setup, these Output paths are not automatically created in the Output Page of the I/O Setup. You will have to manually create the appropriate Output paths in the I/O Setup (or click Default).
Changing Monitor path Output assignments in the Hardware Setup does not update the Output paths in the Output page of the I/O Setup (PTSW-127563)
When changing Monitor path Output assignments in the Monitor page of the Hardware Setup (such as setting the Monitor path Format to None or assigning the Monitor to different physical outputs), the Output paths in the Output page of the I/O Setup do not reflect the corresponding changes. You will have to manually create the appropriate Output paths in the I/O Setup (or click Default).
When creating new sessions, using the I/O Settings selector can result in unexpected Output assignments if HD OMNI has an assigned Monitor path (PTSW-123896)
If HD OMNI has an assigned Monitor path, Output paths created by the selected I/O Settings option in the New Session dialog may be offset by the channel width of the Monitor path. If this happens, you will have to manually create the appropriate Output paths in the I/O Setup (or click Default).
I/O Setup Bus page erroneously adds monitor paths (PTSW-127739)
With both MAIN and ALT Monitor paths declared, toggling one of the CR Monitor paths from the current format to “None” and then back to the starting Monitor format from within the Hardware Setup Monitor page, causes the Bus page in I/O Setup to erroneously add an extra Monitor path with the abbreviation with “(1).” This can happen numerous time and each new Monitor abbreviation increments accordingly.
003 Series Interfaces
Reconnecting an 003 after losing the connection with Pro Tools (PTSW-20351)
If your 003 series interface loses its connection with Pro Tools, increasing your buffer size may bring the device back online without having to close Pro Tools or restart your computer.
Importing .PIM Files on an 003 System with a C|24 (PTSW-46401)
When importing a custom map .PIM file created on a 003 to another 003 system with a C|24, 003 displays “<No Track>” on the scribble strips instead of staying in Plug-in Edit mode with a restored newly imported Plug-in Map. You will need to switch to another mode on 003 and then re-enter Plug-in Edit mode to correct this.
Pro Tools appears unresponsive with Mbox Pro (PTSW-184498)
Avid recommends connecting the Mbox Pro before powering up the computer. If Pro Tools appears to be unresponsive with Mbox Pro, check to ensure that the Mbox Pro is synchronized to the proper clock source (Setup > Hardware), and that the clock source and your Pro Tools session have matching sample rates. If Mbox Pro encounters a problem with the clock source (such as mismatched sample rates between the clock source and the session), Pro Tools may become unresponsive.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 17
Pro Tools Aggregate I/O (Mac Built-In Audio)
–6101 error when previewing audio with Pro Tools Aggregate I/O (PTSW-132996)
When previewing audio in the Import Audio dialog with Pro Tools Aggregate I/O selected as the Current Engine (in the Playback En- gine dialog), and with the Mac OS File view is set to Columns view, you may encounter a –6101 error. Try changing the Mac OS file view from Columns to List or Icons view, or use any of the built-in audio devices instead of Pro Tools Aggregate I/O to avoid this prob- lem.
Changing sample rates in Audio MIDI Setup can cause Aggregate I/O to disappear in I/O Setup, resulting no audio output (PTSW-132281)
When Pro Tools Aggregate I/O is selected as the Current Engine in the Playback Engine dialog, changing sample rates in Audio MIDI Setup can cause the Pro Tools Aggregate I/O to be removed from I/O Setup resulting in no audio output. To correct this problem, click the Default button on the Output page of the I/O Setup.
Error messages when opening a session with a different sample rate from the Aggregate I/O sample rate setting (PTSW-131779)
Pro Tools may indicate that a given Aggregate I/O device has not automatically adjusted its sample rate when a session with a different sample rate is opened. You may subsequently be presented with a dialog indicating that the session needs to be closed and reopened to update the sample rate setting of the Aggregate I/O device.
Renaming Pro Tools Aggregate I/O driver in AMS corrupts the driver (PTSW-131383)
If you rename the Pro Tools Aggregate I/O driver in Audio MIDI Setup (AMS), the driver be corrupted the next time you launchPro Tools. If this happens, quit Pro Tools and delete the Pro Tools Aggregate I/O device from AMS. Pro Tools will re-create the driver the next time it is launched.
Pro Tools quits unexpectedly when enabling the built-in digital I/O (PTSW-132189)
When enabling built-in digital I/O for Pro Tools Aggregate I/O in Audio MIDI Setup, Pro Tools quits unexpectedly. To avoid this prob- lem, enable the built-in digital I/O in Audio MIDI Setup before launching Pro Tools.
Third-Party Core Audio Devices
Using low buffer sizes with Studio Monitor Express may result in Pro Tools quitting unexpectedly with a loud burst of noise (PTSW-132513)
Using Studio Monitor Express with some Core Audio Devices may result in Pro Tools quitting unexpectedly along with loud bursts of noise. Studio Monitor Express is not recommend for use with Pro Tools at this time.
Error –1150 (PTSW-144422)
When launching Pro Tools HD on HDX hardware, if you encounter a –1150 error, quit Pro Tools, shut down your computer, and ensure that the HDX TDM cable is properly connected.
If you repeatedly encounter –6042 errors, open the System Usage window and check the PCI gauge. If the gauge is peaked, you will need to reset the PCI bus. To reset the PCI bus, make all tracks inactive and start playback. If you still encounter a –6042 error, quit and relaunch Pro Tools, open the Playback Engine dialog, and change the Number of Voices setting to use fewer voices per DSP.
Error –9073 without reaching the 2 GB file limit
If you encounter a –9073 error, and you have not reached the 2 GB file size limit, please refer to the Knowledge Base for possible causes and solutions (www.avid.com/onlinesupport).
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 18
In sessions with high sample rates (96 kHz or higher), you may need to set the Hardware Buffer Size to 512 or more to avoid –9128 er- rors during playback with Native plug-ins or dense automation.
Error –9131 (92747a, 20843)
GUID partitioned drives will not allow you to record beyond the third partition when running on OS X. A workaround is to partition au- dio drives using Apple Partition Map instead of GUID.
– or –
Recording to or playing from a UNIX File System (UFS) formatted drive is not supported in Pro Tools.
Error –9132 (32397)
If a –9132 error occurs during Bounce To Disk (even with the highest Hardware Buffer setting selected), bus the appropriate tracks to the appropriate number and format of audio tracks, and record to disk. You can then use the resulting audio files as you would have used bounced files.
In sessions with high sample rates of 96 kHz or more, you may need to set the Hardware Buffer Size to 512 or more to avoid –9155 er- rors during playback with dense automation.
Pro Tools and Pro Tools | HD Software 12.5.1 on Mac OS X 10.9.x, 10.10.x, and 10.11.x — 5/20/16 19