![]() ![]() ![]() Just made a fresh install of 2.6.0 and it works almost perfect. From my ignorance I could relate the bug to the latest updates and their behaviour in LPX but just saying. I tested if the error happened in the standalone version also but it's working flawlessly, no crashes. The most common scenario is when I'm navigating through the patch browser (with autoplay enabled) until I choose this venomous patch (a random patch in fact) and it just crashes and shuts the entire DAW all in a sudden as if it was the minesweeper leaving the OS X message to notify Apple about the problem, relaunch the app, and so on. I'm having issues lately with Omnisphere (first in 2.6.1 and since a couple days in 2.6.2) in Logic Pro X 10.4.4 (on Sierra 10.12.6). Click a file name to download the file.First things first, I hope this thread is posted where it should be.Click a Pro Tools 12 product in your list.Avid Accounts will have the current version for eligible products.Upgrades from earlier versions of Pro Tools can be purchased from the Avid Store or Avid Reseller.Review the Read Me and other docs before installing or updating Pro Tools for known issues that could impact your workflow.Not all Audio Interfaces have been qualified with El Capitan, Sierra, and later macOS versions.Click here for Pro Tools 12.x Satellite Link and Video Satellite compatibility updates.See the Windows Read Me for limitations with WASAPI support (added in v12.0).DigiTest firmware update process with an HD OMNI doesn't appear to finish, but canceling before the HD OMNI reboots can leave the interface unrecognizable by Pro Tools (blank scribble strips).The firmware update was tested for backwards compatibility with Pro Tools 10.3.6 and later. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |