PT12HD AAE -6101 Error

[Carl Sealove]

This is the first project with VIs I have tried using PT12HD.
Cannot work in PT12HD with Omnisphere 2 without show stopping CPU AAE -6101 Errors. 4 midi tracks only. nothing else in session. 48k 24bit. (Have not tried other VIs yet, but somehow expecting the worst). Buffer at 1024. Dynamic Plugin Processing enabled. System Usage Meter shows only Core #4 being accessed. Core 4 goes up to 50%, but Total CPU meter at top goes all the way up to high 90s then - AAE -6101 Error.

Very disappointing......

Saved standard midifile.
Tried same exact session with Omni 2 in Logic Pro X.
Not a hiccup!

Any help or thoughts would be appreciated.
Thanks!

PT12HD 12.0.0
UA Apollo 8 Thunderbolt
iMac Retina 5k
4GHz Intel Core i7
24GB RAM
1TB fusion drive (I thought these were okay now)
Plenty of Disk Space
Omnisphere 2 Library on Sample Drive (not system drive)

[ArKay99]

Originally Posted by Carl Sealove

This is the first project with VIs I have tried using PT12HD.
Cannot work in PT12HD with Omnisphere 2 without show stopping CPU AAE -6101 Errors. 4 midi tracks only. nothing else in session. 48k 24bit. (Have not tried other VIs yet, but somehow expecting the worst). Buffer at 1024. Dynamic Plugin Processing enabled. System Usage Meter shows only Core #4 being accessed. Core 4 goes up to 50%, but Total CPU meter at top goes all the way up to high 90s then - AAE -6101 Error.

Very disappointing......

Saved standard midifile.
Tried same exact session with Omni 2 in Logic Pro X.
Not a hiccup!

Any help or thoughts would be appreciated.
Thanks!

PT12HD 12.0.0
UA Apollo 8 Thunderbolt
iMac Retina 5k
4GHz Intel Core i7
24GB RAM
1TB fusion drive (I thought these were okay now)
Plenty of Disk Space
Omnisphere 2 Library on Sample Drive (not system drive)

I was getting them for a while, then I downloaded all my plug ins latest and haven't had the issue since.

[Carl Sealove]

I put all plugins except for Omnisphere 2 and the PT essential installed plugs in the unused folder. Trashed all prefs, plist, etc..
"Ignore Errors during Playback/Record" (in Playback Engine setup) seems to help, but I recall it can cause some delay compensation issues.
If I turn that setting off still get AAE -6101 errors. Maybe this is an Omni 2 issue relating specifically to PT12 - not sure.

It is hard to imagine that a brand new iMac 4GHz i7 with 24GB of RAM should exhibit any CPU overload issues with anything but the most demanding sessions.
Still, it appears that CPU overload errors are rampant in PT11 and 12 for many users.

And, to reiterate, Logic Pro X has no such issues with an identical session using Omni 2. I do understand that Logic uses Audio Units version and PT uses AAX version, so could be a coding issue.

[john1192]

wow .. still doing the One Processor Spike thing .. disappointing .. i have that since PT11 .. why should we expect more than not perfect ... lol but no funny

[Carl Sealove]

The cpu load lessens a bit and spreads out over more processors when Omni multichannel outputs are assigned to separate aux busses. It is worst when everything is playing through a single instrument track.

[john1192]

carl, that sucks .. i feel like we are one step forward and 2 steps back ..

[Carl Sealove]

I have been working with customer support - (Brandon - very nice and helpful!)

At his suggestion:
I tried Blue Cat MB-7 Mixer(Latest version) - does not help at all with CPU AAE -6101 errors. In fact seems worse.
Not a terribly good work around anyway as it does not allow separate outputs to be routed from Omni 2 to Auxes.

I tried completely uninstalling and reinstalling PT12HD and the same with Omni 2. Same problem persists. This is a bummer!

Instantiating 7 separate instances of Omni 2 - 1 for each patch I am using spreads the processor load out over all 8 processors and does not trigger error -6101.

Does it make sense that 7 instances with 1 patch each utilize less resources than 1 instance with 7 patches?? I am not sure this will allow enough resources for other larger sessions with more VIs.

Are we supposed to stop using Multitimbral VIs now? Kontakt too???

[mesaone]

Originally Posted by Carl Sealove

Does it make sense that 7 instances with 1 patch each utilize less resources than 1 instance with 7 patches??

It doesn't make sense at all. Slightly less CPU usage is supposed to be one of the benefits of using multi-out.

Do you experience the same thing with other multi-out virtual instruments? Maybe try the free Kontakt Player if you don't currently own any others, just to help narrow down whether this is caused by Pro Tools itself or by the instrument.

[Carl Sealove]

I don't think 7 instances of OMNi 2 are using less resources than 1 instance of OMNI 2 with 7 patches in multi timbal mode. I think it's just spreading the load over more processors to have 7 instantiations.

Processor 4 gets nailed really hard by multi timbal mode and that causes the CPU overload error.

[innesireinar]

I would not use sample based VI in sessions at sample rate other than 44.1 because all samples were recorded at this SR. If you use other SR, plugins need to convert their samples in real time. Hope this helps