PT 10 6101 and 9128 errors

[spaceman]

I've seen a few posts on similar errors but still getting no joy with their suggestions.

I am running PT10 on a brand new MBP, i7, 4GB RAM, via an Avastor hard drive for audio and RME Babyface for in/out.

On what are quite light sessions (20% CPU in the bar) I am getting these 6101 and 9128 errors. Sometime so much so I can't even work! The CPU bar and the few number of plugs I am using mean that I am not really hitting the CPU hard at all, but PT is claiming I am and stopping playback.

I have tried all buffer sizes, I have tried selecting aggregate i/o and baby face in playback engine. I am using 7 or my 8 processors on 95%.

Any ideas people? Avid are not responding to emails and we customer support code is not being accepted via the phone.

[ronzie]

Originally Posted by spaceman

I've seen a few posts on similar errors but still getting no joy with their suggestions.

I am running PT10 on a brand new MBP, i7, 4GB RAM, via an Avastor hard drive for audio and RME Babyface for in/out.

On what are quite light sessions (20% CPU in the bar) I am getting these 6101 and 9128 errors. Sometime so much so I can't even work! The CPU bar and the few number of plugs I am using mean that I am not really hitting the CPU hard at all, but PT is claiming I am and stopping playback.

I have tried all buffer sizes, I have tried selecting aggregate i/o and baby face in playback engine. I am using 7 or my 8 processors on 95%.

Any ideas people? Avid are not responding to emails and we customer support code is not being accepted via the phone.

Space, lay out the details for us.... Unfortunately, there's so much crap that goes into a stable install with PT, info is paramount to the solution.

The -6101 error might indicate a firewire thru put issue. Your guess is as good as mine on the -9128 (but I think that's on Avid and their code).

See if you can get it stable on just a stripped down install with the aggregate engine first. I would go against using the outside drive for the moment,and see if you can get the thing going with a butt simple session on the internal drive(provided it's a 7.2k rpm). Go with a click and record tone. And work the external and the rme into that.

Do lots of saving /closing/restarting and go about it in a logical manner. Follow Avid's setup to the law and check your 3rd party plugs.

Ronzie

[Franco1967]

I had the same problem with my digi002R. I went >Setup>Playback Engine>H/W Buffer Size to 1024>Host processors: 8(of 8)>CPU usage limit: 85%> Host engine: checked (THAT´S THE IMPORTANT POINT THAT LET´S IT RUN!)>minimize additional Latency: unchecked. It´s not optimum but at least working. When I need to record external tracks I go to the Digi002 and the back to Aggregate. My settings on Aggregate: 1024>3!(of 8)>99%>unchecked>unchecked. So far for short period fixes. Of course has to do their homework on that. It´s a poor performance yet.

[Franco1967]

I mean: Of course AVID has to do their homework on that. It´s a poor performance yet.

[Franco1967]

By the way 4GB is quite few RAM. I have 12GB. PT has the 3GB limit but the OS needs 2GB to run properly. I would upgrade to RAM.

[spaceman]

cheers folks - will try some of those ideas and get back to you asap!

[spaceman]

Still a bit miffed....took out my UAD Satellite and hard disk and was fine.
Plugged it all back in and was also fine.

It does seem to be intermittent which makes it all the harder. Generally I have found if no other apps are on it works ok. But really I should not have to have it all closed down bar Tools right?

For the record the Avastor is off a 3m esata, UAD via FW, babyface USB, then ilok and e licenser dongles in other USBs.

Weird thing is my bro has exact same set up bar two things.
1. RME (he runs Duet 2)
2. He is PT10 and I am PT10HD. Should that matter?

We did a test and he can get 20 Slate FG-X up before overload and I only got 4!
His rig works perfectly with no errors.

[spaceman]

Spoke to a lovely bloke Renato at Avid today and he suggested this

As discusses during our telephone conversation, the quickest way to troubleshoot DAE Errors -6101 and -9128 is to move all third party plug-ins from the Plug-Ins folder to the Plug-Ins (Unused) folder and test the system in this basic configuration.

If performance will improves dramatically, the next step will be to gradually move your plug-ins back to the Plug-Ins folder.
When performance will degrade again, then you will know which plug-ins might have issues and investigate for possible updates or known issues with the plug-in manufacturers.

Let us know how your testing progresses,

So I will do this and report back. Hopefully this info on troubleshooting these particular DAE errors will help others in the same boat too.

[Basstian]

Originally Posted by spaceman

Spoke to a lovely bloke Renato at Avid today and he suggested this

As discusses during our telephone conversation, the quickest way to troubleshoot DAE Errors -6101 and -9128 is to move all third party plug-ins from the Plug-Ins folder to the Plug-Ins (Unused) folder and test the system in this basic configuration.

If performance will improves dramatically, the next step will be to gradually move your plug-ins back to the Plug-Ins folder.
When performance will degrade again, then you will know which plug-ins might have issues and investigate for possible updates or known issues with the plug-in manufacturers.

Let us know how your testing progresses,

So I will do this and report back. Hopefully this info on troubleshooting these particular DAE errors will help others in the same boat too.

Did you find a solution?
I could not track any plug-in down to cause these errors. still getting them now and than without any visible reason.

Sebastian

[Blackers]

Hi fellas,i'm a pc windows 7 user not a mac pro user but,about this issue 9128 i have a brand new machine with 16 gig of ram,sometimes two track and two plugins open and the error stop the playback due to lack of cpu,saying to increase the buffer etc.I usually track with 128 of buffer.The system informs 15 20% of cpu use.I'm guessing the problem is maybe with some plugins versions,or firewire issue.It seems something is happening behind the scenes.