Pro Tools 11 Issues

[andymonize]

I just recently purchased the upgrade from pro tools 10 to pro tools 11 and have been running in to a few problems some of which i have figured out and a few that i can't seem to figure out. First: I cannot find the inputs for my digi 003 rack within an audio track so that I can record guitars etc. The only options are Built in Microphone and Built in input. I'm pretty sure this is a simple fix probably within I/O but have not been able to figure it out. Second: After opening a session that I had created in pro tools 10 I received a prompt saying that certain plug ins were not found because they aren't in my plug ins folder. I have never had an issue with this before when upgrading pro tools and I haven't found a "plug ins folder". How do i resolve this problem? Again, Pro Tools 11 is new to me and I am sure these are easy fixes that I am probably overlooking but I could use some help. Thanks!

[Craig F]

a) did you install the 003's driver for 11? it's a separate install

b) 11 is a whole new plug-in format call AAX64, all previous plugs will not load (RTAS, AAX32). You need to download and install the updates your your plugs

[nst7]

When launching Protools, hold down the "N" key, and you should have the option to choose the 003. You will only have to do this one time, not every time.

[andymonize]

I did install the latest driver for the 003. However, the latest driver is for the PT 11.1.3 and I am running PT 11.2.0. I am not sure if that makes a difference but I am still not getting the inputs I need. Also, I am having another problem now which is that I am constantly getting the error message "A CPU error occured. If this happens again try increasing your HW Buffersize or removing some plug ins." However, I just started the session which only has Superior Drummer on it right now and nothing else. I just started some drum tracks for a brand new session and am already getting the error message. Any suggestions?

[sw rec]

First suggestion: system info! You haven't stated whether you're on a PC or a MAc, or what operating system you're running. That being said, you MUST choose the correct driver, and it's WAAYYY too easy to get the wrong one! The 003 RACK uses a different driver than the 003 CONSOLE, at least on Windows.
From your description, I'm guessing it's defaulting to your onboard soundcard as an audio device. Triple check and make SURE you have the right driver in place. For MAC I see an 11.1.2 driver (which is a different thing than the version of Pro Tools altogether) and for a PC the latest rack driver is the 9.0.8 driver.
http://avid.force.com/pkb/articles/d...02-003-Drivers

Second, what Craig said about your plugins. PT 11 will not "see" RTAS or 32-bit AAX plugins, only 64-bit AAX plugins. You'll have to check with your 3rd party manufacturers and see if they've updated.

System info, please!

[albee1952]

If you are on a PC, I would re-install the driver in this order; power the 003 OFF, uninstall the driver(Control Panel>Remove a Program). Go to the driver installer(be sure you have the correct driver for the rack version or the controller version as they are different), right-click on the setup icon and choose Run as Administrator. When that's done, go to the PT icon on the desktop and right-click>properties. Find the tab with these 2 items:
Always Run as Admin
Disable Desktop Composition
and check both. Power the 003 ON, wait 10 seconds and then open PT while holding the N key(which will take you to the hardware setup page, where HOPEFULLY, you can select the 003 as the audio engine).

If none of this works, can you test the 003 on another system? Hot-patching the FW(connect or disconnect) while its powered ON can fry the FW PCB in the 003

[andymonize]

Sorry I should have specified that earlier. I am running on a IMac with OS 10.9.3. And yes I downloaded the Mac driver 11.1.2. Should I uninstall the driver and try reinstalling it?

[nigelpry]

Did you follow nst7's advice?

Did that allow you to choose 'Avid 003' as your playback engine?

[andymonize]

Sorry I didn't get back sooner. I did find the problem. Avid 003 was an option in the playback engine. However, oddly enough I had to go to I/O and set it back to default settings for it to work. I'm not sure why I had to do this considering that I never touched the I/O settings in the first place. Weird... Thanks for the help anyway!