View Single Post
  #5  
Old 05-12-2019, 07:28 PM
sheeptuf sheeptuf is offline
Member
 
Join Date: Sep 2004
Location: Toledo, Ohio
Posts: 81
Default Re: AAE 6101 error - PLEASE HELP

-----First of all thank you so much for your response. You took a lot of time and I appreciate it. I answered all questions with a "-----" before


As already asked, what is the buffer size ...and what is your session sample rates? Both are super critical.

---I have tried it with buffer rates all across. No change. .
---Sample Rate - I just use the default. 44.1?

It won't record without crashing -- what about just playing back prerecorded audio? Drag and drop some existing MP3, or whatever into some audio tracks.

---It only seems to crash while recording. From what I can tell. Though I would have to upload

And while we are here, what *exact* Mac Book Pro model? Model code name e.g. MacBookPro6,1 or better Model number better EMC code. Look for stuff printed on the back of the MBP.

---MacBook Pro (Retina, 13-inch, Early 2015), Model A1502 EMC2835


Confirm what exact playback engine device you have selected in the playback engine. I want to make sure you are not using an aggregate IO device to aggregate your UAD interface with the MBP built-in output or anything else, since this AAE-6101 relates to CoreAudio problems.


---I have used the UAD, a 002, the built in, and pro-tools aggregate on the playback engine -- none of them have worked.


Where are you recording the audio/session to? Hopefully the internal MBP SSD. But check the session content is really going there, not say unintentionally to some slow USB stick etc. Do all the tests below with new empty sessions, not clones, not from templates, recording to the internal SSD.

---I have used the internal HD as a destination & my external hard drive that I have used for a long time. The external HD is a FW800 drive and I have an apple adapter.


Did Pro Tools installed just with ILM and no other drivers or plugins ever work on the original OS install? On the new OS install? i.e. using it just with built-in output and no interface drivers or plugins installed?

---I tried it with just PT and no plug ins installed. No luck.


Has Pro Tools on this MBP ever worked? If so what changed?

---This computer has never worked with PT. I have a supped up 002 (Black Lion) that has worked fine with every computer I have ever owned. Then I got this one, and it never worked. I bought a few different adapters, but no luck. I thought that since PT had just stopped supporting the legacy drivers, that new Apple would no longer worked with them. SO, I upgraded and bought all new stuff (UA). And it did not work with the UA either.



Hopefully you are working at a conservative sample rate, if not do that now and work at 44.1 kHz until you get stuff working. You should have tried increasing the buffer size until things work. Did you try that? So it is still not working at 1024 samples?

-----I tried all the different buffer sizes.

With UAD plugins instantiated in Pro Tools (not the UAD console) you should expect to need to be running at much larger IO buffer sizes that with similar native plugins. You say you are not using plugins, but I want to make sure you understand the issue with the UAD plugin architecture. And don't have say UAD plugins running on hidden tracks. UAD plugins in Pro Tools are for mixing (with large IO buffer settings) more than tracking (with lower IO buffer settings).





Have you tried everything here http://avid.force.com/pkb/articles/e...-Pro-Tools-Mac ?

I did everything on this list. I have to learn more about a discrete graphics card though.


And more basic housekeeping:

Get the mac fully optimized, every last thing on the standard optimization list done. e.g. WiFi disabled bluetooth disabled, etc. If you think it's been done before double check it again..

----I did all this - specifically while I was on the phone with one of the reps. Didn't help.

In the playback engine dialog:
Uncheck ignore errors (you want to see as many errors as possible while troubleshooting)

---I did this.


Set the disk cache to 2GB ("normal" is off).



Unplug all hardware you don't actually need from the MBP. Mice, keyboards, USB hubs, external drives, etc. unplug it all. Just connect the MBP power supply, UAD interface and iLok if you are using one. When testing without the UAD interface unplug that as well.

Make sure other programs, web browsers etc. are not running.

I did this.


If you dont know if other software might have broken Pro Tools when you added it then your job now is to peel everything away until it (hopefully) works.

As always start by trashing prefs and doing that between other main steps below. Use Peter Gates' tool. http://petegates.com/pg-pt-prefs.html

----I did all this. That PG tool is cool.


Move all .aaxplugin files out of the plugin folder. Trash prefs. Start Pro Tools, it will automagically put back the default plugins. If Pro Tools now works OK, move the third party plugins back in batches until you find which ones are bad.

If moving all plugins out did not fix the problem, then don't put them back.
- Uninstall *all* the UAD software. Disconnect the UAD interface.

-----Wouldn't this happen with a completely clean install of PT? With no Waves or anything?


With built-in output as the playback engine just try playing back content.
With an aggregate of built-in output/input try to see if you can record anything (e.g. using the MBP internal mic).

----I have to do this. It only seems to stop when I am recording, but I haven't tried to just listen to stuff.

... still a problem... then maybe do a clean new macOS install. But come back here and tell us the details of what you have done/seen so far (take notes as you do all the above).

---The Mac store completely re-installed 10.13.6 with nothing else on my computer. I downloaded PT and it still happened.

Basic optimization stuff is under troubleshooting links under "help us help you" up the top of each DUC web page.[/QUOTE]

-----I will look at this.

----This might be ill advised, but I am sending it to Apple to have them do a deep dive into the computer itself. I will be without it for 5-7 days, but I can then at least rule out any hardware failure.

Thanks again
Reply With Quote