Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Software > macOS
Register FAQ Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-25-2024, 09:06 PM
cp2 cp2 is offline
Member
 
Join Date: Jan 2007
Posts: 36
Default CPU Maxing Out with -6101 Error

Hello Forum,

I've researched this all I can and still can't find the solution:

I create a new session with only one instance of Keyscape and Omnisphere, ZERO plug-ins. I very quickly get the 'A CPU overload error occurred... try increasing buffer, etc...'

My buffer is maxed out at 1024. I've tried different cache sizes large to small. 'Ignore Errors' unchecked. Dynamic Plug-in unchecked. I've trashed PT preferences. Video engine disabled. I've closed the session, restarted PT, rebooted the machine. Nothing running in the background. As soon as I start playing pads with Omnisphere the CPU total in my System Usage monitor maxes out and I get the error.

Any help is greatly appreciated, thanks in advance!

Mac Mini 2018, 32GB, Catalina 10.15.7, 6 core Intel i7, Apollo Twin X
Pro Tools 2020.5.0
Reply With Quote
  #2  
Old 01-25-2024, 10:13 PM
Darryl Ramm Darryl Ramm is offline
Member
 
Join Date: Nov 2010
Location: USA
Posts: 19,657
Default Re: CPU Maxing Out with -6101 Error

Uh Keyscape and Omnisphere *are* plugins. You mean no additonal plugins.

Has this worked OK before? What changed? What about Keyscape or Omnisphere alone? What about if you create a new test session just try one pluging, create a new test session, try the other.

What sample rate are you operating at?

And when it comes to plugins it does not necesarlly matter if plugins are used at all, a problematic plugin just being installed in Pro Tools can cause CPU problems.

You need to try tackling this following the standard troubleshooting steps under "help us help you" up the top of each DUC web page.

Use Pete Gates free PT Pres tool to trash prefs, and repeat this between other major tests.

Then make sure you try...

In the playback Engine Dialog -
- Leave ignore errors unchecked
- Check Turbo Boost if you have that option
- You might try toggling on or off dynamic CPU processing

Make sure the Mac is fully optimized, do every last thing.

Test with Mini Grand vs Keyscape/Omnisphere, the default/keyboard VI just to get a baseline comparison.

Test with all .aaxplugin files removed, Pro tools will automatically resintall it's core plugins, then try installing just one of Keyscape or Omnisphere, from the latest newly downloaded installers claimed compatible with your setup.

Test using Built-In Output/speakers as playback engine instead of your UAD interface.

Create a new admin account and test from there.

Still stuck describe what you did/exact results.

Can't make progress you may be facing a test Pro Tools and/or macOS upgrade.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Error AAE-6101 ShortwaveP Pro Tools 11 5 04-23-2015 11:50 PM
Error -6101 6lovemusic RTAS & TDM Plug-ins 1 10-19-2013 08:35 AM
PT 10.3.5 DAE error -6101 Jazzbass56 Pro Tools 10 5 07-03-2013 09:33 PM
-6101 error sykobilly65 Pro Tools M-Powered (Mac) 2 02-15-2012 07:38 AM
Just another CPU, -6101 error... Seraplane macOS 3 02-25-2011 11:37 AM


All times are GMT -7. The time now is 11:33 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com