003 driver problem pt11

[sares]

My 003 in PT 11 Shows like Asio003 Firewire.

I Need that my 003 shows an operate like they are originally: A Digi003 (without asio in PT.

Help Me!

[Park Seward]

Can you select the AVID 003 as the audio engine? Did you download the newest 220/003 drivers?

The newest drivers say "Avid" and not "Digi" in the engine dialog.

[albee1952]

I think Park is all over this one. Ever since 9, the driver is a separate download and install. Grab the latest driver and things should get better(but you probably still need to open the Setup>Hardware menu and select the 003 as your audio engine). Holding the N key while opening Pro Tools will take you directly to that window.

[sares]

I Have the 9.0.3 driver.

Avid shows to download a 9.07 driver with "support" to PT11

BUT DONT WORK!!! AFTER INSTALL 9.0.7 driver NOT APPEAR THE UPDATE IN MY w7 device manager the driver after install 9.0 7 still appear the 9.0.3


Curiosly the 9.0.3 have a 16mb of size and 9.0.7 have a 8mb of size.
I´m suspect that the new driver are corrupted

Avid:

[Park Seward]

I guess you are on a PC. The Windows driver is version 9.0.7. Mac is 11.0.0.

http://avid.force.com/pkb/articles/d...02-003-Drivers

I am on a Mac so I don't know about the PC driver version. Perhaps someone else can report on the success or failure of that driver.

When you boot into PT10, does it work there?

[sares]

Yes
PT 10.3.6 Work correctly

[nigelpry]

So, experimenting with the new V11 003 driver on a Mac, and various audio software apps, including PT10.3.6, PT 11.0.0, Logic 9.1.8, Cubase 7.0.3, Wavelab 8.0, Harrison Mixbus 2.3 etc etc

Using a 003 Console (not rack), and choosing 'Avid 003' as the audio interface.

First off, 003 seems to be working well in PT11, all buttons, dials, faders and knobs seem to be working as usual.

In PT10, the 003 now acts as an audio interface, but the console no longer controls Pro Tools. In effect, it acts the same in Pro Tools 10 as it always has done with every other app.

I guess, from this, that when selecting 'Avid 003' in the hardware select box, I'm now selecting its Core Audio Driver, just like I do for other apps.

Also, the previous core audio manager no longer works, it does not detect the 003 with the new driver. Instead, there is a new 003 manager which resides as a utility in system preferences. It does all the same things as the previous core audio manager, but does not automatically open when an app accesses the 003.

There's one noticeable difference though. Whereas with the previous driver, when not using Pro Tools, you got a helpful bit of text in the LCD Display, which either said 'Offline' if nothing was accessing the device, or 'Working' if something was accessing it, now the LCD screen remains blank at all times, except when running Pro Tools 11. That's a shame, as it was a useful bit of info to have visible.

The good news is that, having selected 'Avid 003' as the device. and without any other messing about, all my other DAWs seem to be accessing the audio interface part of the 003 reliably. I can switch from one to the other, switch into and out of either pro tools versions, and there are no issues so far.

However, the lack of PT10 console support is a complete disaster. I'm not surprised its not working, as the driver download page says as much, but its nevertheless a big issue.

Does anyone (Avid?) know, and if so can they say, whether the lack of PT10 support is a temporary thing? Will there be a subsequent driver version released that supports both versions?

It means that, for now, co-install and switching between PT10 and PT11 is a big deal. It's a case of uninstalling the current driver, rebooting, installing the other driver, and rebooting again, if I still want to use the console controls when switching from 10 to 11 or vice versa.

So much so, that, for now, I will be uninstalling the 11 trial, as I use my console controls and need to have a working PT10 installation, given the lack of AAX2 plugins so far. It's a pain, as this means I'm not going to be able to test drive PT11 properly ... my trial days will carry on counting down regardless.

Oh well, at least, for me, this kicks that final decision about upgrading CPTK to HD off into the long grass. PT11 is not really viable for me unless and until all my essential plugins are AAX2 ready.

[albee1952]

For a PC with 003, I recommend removing ASIO4ALL. On my rig, nothing worked correctly with ASIO4ALL on the system. As soon as I removed it, the 003 worked perfectly(and still does today)

[mbat4100]

After a week of iLok licensing problems I have just done CPTK crossgrade and now I am having same problem with 003 with upgrade to 10.3.6

Haven't even got to installing the PT11.

Installed latest 002-003 family driver 11.0 and 10.3.6 and now my 003 only acts as an interface.

Like other users this a complete disaster and must be a mistake.

Any advice from Avid please what to do ? Or what will be done about it?

I made enquiries BEFORE I upgraded and was assured the 003 would work. I assumed that meant with PT10 as well as PT11 given that there was nothing wrong with my PT10/003 system until the upgrade. Certainly that was the implication.

[mbat4100]

As a postscript: This can't be a hardware problem as the 003 worked fine with PT10 before the software/driver upgrade .

It is a few lines of code that someone urgently needs to write to fix the problem surely!