Digi 002 rack driver with Pro Tools 12?

[fearofbirds]

Hi,

I'm attempting to use Pro Tools 12 with a Digi 002 rack but keep getting AAE -6101 error. I realise the driver is untested for 12, but it's still available so I hoped it might work.

So - I don't know whether it's a driver issue (given that apart from these crashes every hour or so it works fine) or another issue.

I'm also using a Macbook Pro 15" a couple of years old and this is occurring in sessions with no plugins and just a couple of audio tracks with barely any audio. So - it seems odd that it's struggling buffer wise.

Hope someone can offer some insight into why this is happening and how I might fix it!

Thanks.

[Sparky1]

What Mac OS are you using?

Sparky

[Park Seward]

I don't believe the 002 is supported any longer.

002 has a $500 rebate from Avid:

Have you outgrown your old legacy Pro Tools | HD hardware, 002, 003 or Mbox Pro interface? You’re in luck. For a limited time, you can step up to the sound and power of Pro Tools | HD Native and save big.

http://www.avid.com/en/special-offers/mbox-to-hd-native

[AlexLakis]

I'm running an 002 console on a mid-2012 15" Macbook Pro with Pro Tools 12.1 on OSX 10.8.5 with zero issues. Latest drivers, lotsa plugins. It can be done.

What OSX version are you running? Are you running the latest versions of your plugins (they can screw with your sessions even when there are no instances loaded)?

[fearofbirds]

Thanks for the replies all. I've now tested and this issue happens with my other audio interface AND with no interface at all. So I guess that just leaves the OS (El Capitan latest release) or plugins. I've had the error come up even in sessions where no tracks have inputs at all - no plugins. So unless the problem could occur even just because there are bad plugins installed... I'm lost.

Any other thoughts would be appreciated!

[VRW]

Originally Posted by fearofbirds

Thanks for the replies all. I've now tested and this issue happens with my other audio interface AND with no interface at all. So I guess that just leaves the OS (El Capitan latest release) or plugins. I've had the error come up even in sessions where no tracks have inputs at all - no plugins. So unless the problem could occur even just because there are bad plugins installed... I'm lost.

Any other thoughts would be appreciated!

Your guess may be right. The guy in the previous posting saying he is using the 002 with PT12 successfully is one of the few lucky ones AND he is running it with Mac OSX 10.8.5 Mountain Lion which does make the crucial difference finally.
Besides the hardware issues of 002/003s with some current Macbooksk the main problem/the key is the version of Mac OSX.

Fact is there were tons of issue reports from 002/003 users using OSX Yosemite already, even with the official Avid driver then. Even if I hate to say that but those interfaces are simply legacy for the use with all the latest systems. They were made for completely different generations of Mac OSX and Pro Tools many years ago.
So if you really want to stay with your 002, the best you can do is to run it with a still supported, older version of Mac OSX and an older hardware/Mac (preferably still with FW ports etc.) like AlexLakis above does. That's clever and the only chance to have a trouble free experience.
As long as it is possible to use PT12 with OSX Mountain Lion 10.8.5 or Mavericks 10.9.x, you still can use Pro Tools 12. That's cool.
However you better leave the latest versions of OSX like El Capitan and even Yosemite alone if you decide to stay with your 002.

Or you decide to replace the 002 with a more current interface?

Further I would recommend to restore your system from a backup or even better, make a completely new, clean install of your system. Do not forget to set up all the Pro Tools optimizations
https://www.google.at/search?q=pro+t...&client=safari
and then just install Pro Tools itself, the AIR Effects and Instruments and the XPand at first. Just the basic Pro Tools installation and the driver for your interface.
Then go and check out if this system is running as it is supposed to. If yes, make a backup of it and start to install your 3rd party plugins/VIs just one at a time and always check out if it is still working properly.

If you do not want to set up a new system (which in many cases is the only way to solve such issues though), you may remove all 3rd party plugins and VIs from your Pro Tools plugins folder. Just move it to the -Unused Plugins- folder or to another drive, whatever.
Now check out if the issue still is occurring? If not, put back every single plugin/VI into the Pro Tools plugins folder separately one at a time and find out if/which plugin/VI is causing you troubles.

But again, be aware of that one major problem using a 002/003 nowadays is the version of Mac OSX. Avoid the latest versions like OSX El Capitan and even Yosemite, stay with OSX Mountain Lion 10.8.5 (supported up to PT12.4) or Mavericks 10.9.x and you have a good chance to get a properly working Pro Tools system again.

The best of success to you!