I have just renewed my annual upgrade plan for Pro Tools Ultimate and spotted that Avid has released 2018.12, which is solely made up of bug fixes and support for the latest version of High Sierra macOS 10.13.6 but no support yet for macOS Mojave.

Pro Tools 2018.12 System Requirements

• macOS High Sierra (10.13.6), macOS Sierra (10.12.6), and Mac OS 10.11.6 (El Capitan)

• Mac OS 10.10 Yosemite is not supported with Pro Tools 2018.1 and later due to graphical artifact issues--Upgrade to a supported OS before installing Pro Tools 2018.12

• Windows 10 64-bit, Windows 8.1 64-bit

• Additional Compatibility Articles

Pro Tools 2018.12 Bug Fixes

Atmos Workflows

• Height automation is no longer zeroed out after importing session data, choosing to match tracks, and overlaying playlists

• Adjusting the height panning parameter will no longer write automation when "Allow Latch Prime in Stop" is enabled and Pro Tools is stopped

Commit

• Resulting clips after a commit operation will once again be named based on the previous clip name, rather than the track name.

Control Surfaces

• Artist Mix faders now raise simultaneously when opening a Pro Tools session.

• 'Add EQ' and 'Add Dyn' buttons are no longer available for non-applicable track types.

• Pro Tools now grabs the EUCON monitor controls at the appropriate times.

• Audio no longer stays muted when simultaneously pressing and turning the knob on the Avid Artist Control.

• The S6 Pan Function and Aux Pan front/rear link (Sel) switch is no longer out of sync with Pro Tools.

• 'In' and 'Sel' switches now function across all knob page tables.

• CDM waveform meters no longer appear in red on macOS.

• The Cut LED on the S6 and Dock will no longer become lit when Opt+Clicking the Monitor Knob to set unity gain.

Crashes and Errors

• Fixed a crash when Option/Alt+clicking on a group-linked panner.

• Fixed a crash when switching between rendered/audio files folders during while a waveform calculation process is running.

• Fixed a crash that would occur after freezing a track and switching the timebase between samples and ticks.

• Fixed a crash that would occur when doing various operations after freezing many tracks, such as save copy in or navigating in the Workspace Project Browser.

• Fixed a crash that could occur when clicking on the input selector of a track with a missing input.

• Fixed an issue where a session would not allow saving after importing from another session.

Field Recorder

• Fixed an issue where field recorder files would end up with incorrect or missing channel names after being transcoded to MXF by Media Composer and sent to Pro Tools.

• Field recorder files with non-adjacent channel numbers will now correctly spot on the timeline.

• Fixed an issue where expanding field recorder matches could expand onto the wrong tracks with incorrect edits.

Import

• Importing session data from a session, with automation breakpoints beyond the bounds of the destination session, will now drop those breakpoints upon import, preventing downstream issues.

• 5.1 and 7.1 BWAV exports from Media Composer will once again import as surround clips, rather than mono channels.  Exports must be done with Media Composer 2018.10 and up..

UI

• Fixed an issue where grid lines in the Edit Window timeline looked faint on retina displays of some iMac and MacBook Pro models.

Performance

• Fixed an issue that caused performance degradation on High Sierra for certain machines.

• Fixed an issue where importing an embedded AAF was slower on an SMB volume than an AFP volume.

Miscellaneous

• Fixed an issue where record pass was delayed with QuickPunch/TrackPunch if Pre-roll was enabled

• Fixed an HD Core Audio driver issue where the user cannot access any tabs in Hardware Setup other than Main while setting up an HD OMNI.

• Window configurations are correctly remembering their saved monitor and location in a multi-monitor configuration.

• Fixed an issue where certain Korean words failed to return results in a Clips List search.

Customer Support Enhancements

• Cancelling the crash report window will now save a .crash file in a default location.  This allows it to be sent to Customer Support at a later time, minimizing workflow disruption.

  • macOS: /Users/<username>/Library/Logs/Avid/Crashlog/ 

  • Windows: C:/Users/<username>/AppData/Local/Avid/Logs/Crashlogs/

• Digitrace logs (.dlogs) are no longer encrypted.

What Do Think?

Has this update fixed the bugs that were causing you concern?