Can't Change Playback Engine

[Jack Vandal]

Hi all -

I posted just a couple hours ago with a different problem and someone gave me the answer very quickly, so I'm going to see if lightning strikes twice.

I just bought a friends old computer, and want to run PT9 with the 003Rack+. The friend had pt8 already installed, and would not let me in w/o his ilok, so I uninstalled his pt8, and installed my pt9.

I had some difficulty with the unable to located hardware error message, but that is resolved.

Now PT9 won't recognize my 003 (FW light on 003 won't light up) and I am unable to change my playback engine. When I hold N at the PT boot, the Playback Engine is listed as ASIO4ALL v. 2 (which i d/led to help with the prior issue) and there is no drop down box or ANY option to change it.

I'm really in a bind. Hope someone can help.

[Jack Vandal]

I should say that it is the Digi 003 Rack PLUS (yes the correct drivers are installed)

heres my specs:

Computer
Model : nVidia MCP7A
Workgroup : WORKGROUP


Processor
Model : Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Speed : 3.8GHz
Cores per Processor : 2 Unit(s)
Threads per Core : 1 Unit(s)
Type : Dual-Core
Integrated Data Cache : 2x 32kB, Synchronous, Write-Thru, 8-way, 64 byte line size
L2 On-board Cache : 6MB, ECC, Synchronous, ATC, 24-way, 64 byte line size, 2 threads sharing

Computer
Mainboard : DFI LP JR GF9400
BIOS : Phoenix Technologies, LTD 6.00 PG 01/07/2009
Bus(es) : ISA X-Bus PCI PCIe USB i2c/SMBus
Multi-Processor (MP) Support : No
Multi-Processor Advanced PIC (APIC) : No
Total Memory : 4GB DIMM DDR2

Chipset
Model : nVidia MCP79 Host Bridge
Front Side Bus Speed : 4x 400MHz (1.6GHz)
Total Memory : 4GB DIMM DDR2
Memory Bus Speed : 2x 400MHz (800MHz)

Memory Module(s)
Memory Module : G.Skill F2-6400CL5-2GBPQ 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)
Memory Module : G.Skill F2-6400CL5-2GBPQ 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)

Video System
Video Adapter : NVIDIA GeForce 8500 GT (16 SM4.0 1.7GHz, 1GB DDR2 2x400MHz, PCIe 1.00 x16)

Graphics Processor
OpenCL Processor : NVIDIA GeForce 8500 GT (16SP 2C 1GHz, 1GB 2x400MHz)
CUDA Processor : NVIDIA GeForce 8500 GT (16SP 2C 1GHz, 1GB 2x400MHz)
Compute Shader Processor : NVIDIA GeForce 8500 GT (16SP 1.7GHz, 1005.6MB 2x400MHz)

Storage Devices
WDC WD3200AAJS-22L7A0 (320GB, SATA300, 3.5", 7200rpm, NCQ, 8MB Cache) : 298GB (C:)
TSSTcorpCD/DVDW SH-S183L (SATA150, DVD+-RW, CD-RW, 2MB Cache) : 1GB (D:)

Logical Storage Devices
System Reserved : 100MB (NTFS)
Hard Disk (C:) : 298GB (NTFS) @ WDC WD3200AAJS-22L7A0 (320GB, SATA300, 3.5", 7200rpm, NCQ, 8MB Cache)
3.5" 1.44MB (A:) : N/A
Avid Audio Devic (D:) : 1GB (CDFS) @ TSSTcorpCD/DVDW SH-S183L (SATA150, DVD+-RW, CD-RW, 2MB Cache)

Peripherals
LPC Hub Controller 1 : nVidia GeForce 9400/9300/9200/nForce 730i (MCP79) LPC Bridge
LPC Legacy Controller 1 : ITE IT8718F
Audio Device : 12562 MCP79 High Definition Audio
Audio Codec : Realtek Semiconductor Realtek 885 High Definition Audio
Audio Codec : nVidia 0007h
Serial Port(s) : 1
Disk Controller : nVidia MCP79 SATA Controller
Disk Controller : Jmicron JMB368 IDE Controller
USB Controller 1 : nVidia MCP79 OHCI USB 1.1 Controller
USB Controller 2 : nVidia MCP79 EHCI USB 2.0 Controller
USB Controller 3 : nVidia MCP79 OHCI USB 1.1 Controller
USB Controller 4 : nVidia MCP79 EHCI USB 2.0 Controller
SMBus/i2c Controller 1 : nVidia MCP5+ SMBus 1
SMBus/i2c Controller 2 : nVidia MCP5+ SMBus 2

Printers and Faxes
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)

Network Services
Network Adapter : NVIDIA nForce Networking Controller (Ethernet, 100Mbps)

Power Management
Mains (AC) Line Status : On-Line

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7601 (Service Pack 1)
Platform Compliance : x64

[albee1952]

First thing; using an intel cpu with an nvidia chipset is often a recipe for failure(but if your friend had PT8 working on it, then it may be okay). Next, I only see a single hard drive(you need a separate drive for your sessions). Having said that, my best advice would be to uninstall ASIO4ALL as it hosed my system. Reinstall the 003rack driver(and be aware that there are 2 drivers for the 003 lineup, 1 is for the controller and the other is for the rack version, which is the one you need).

[Jack Vandal]

albee-

Thanks, I will def try that. Is the rack driver I need somewhere other than the device drivers disk that came with PT9?

-Also- I have an external HD. does it need to be internal??

[Jack Vandal]

albee-

First off, its crazy that you actually lived in Greenfield. Small audio world.

Second, I uninstalled asio4all v.2 and once again the "Unable to Locate" error message was back, so I had to reinstall it just to fully boot PT. I should say that before this, I did a complete uninstall of PT, the drivers and plug-ins, and started from square one, following avid's recommended process with my version of PT 8. My thought process was that maybe because of PT 9's streamlined, "no-interface" download process, it could have just been bypassing the 003+ somehow. Maybe if I installed with version 8, it would recognize the 003+. This was unsuccessful. The "Unable to Locate" window was there (even WITH asio4all!!) so after a few attempts to rectify this, I had to do a complete uninstall once again, and start re-installing version 9. It just finished installing, and it loads fine, however it STILL does not recognize my interface and the current playback engine is locked to asio4all with seemingly no possible way to change it.

I have been researching heavily for a while now to no avail.

There's only SO much fun I can have with VI's. I need to mic up some drums or I'm gonna lose it. If anyone can help that would be amazing. AMAZING.

[Jack Vandal]

After hours of frustration, I have tried trashing prefs, downloading drivers, even shutting off windows firewall briefly to see if the 1394 connection was being blocked... nothing.

Could it be that I need the "old" style ilok that I received with the 003?

Is firmware something that is only mac-related?

It just seems that nothing is recognizing the 003. It's not listed in my device manager, devices and printers, the Hardware Setup, Playback Engine, or MIDI studio in pro tools, nowhere. I'm going to swap out the FW cable I am using in hopes that it is just a bum cable, but that will have to wait until tomorrow.

[albee1952]

Start with uninstalling Pro Tools(and ASIO4ALL if you still have it loaded) and rebooting. Then, download the 003 rack driver, or, if you can find drivers on your PT9 disk, it should say that its for 002/003 rack family or 002/003 console family(the downloadable drivers on the website are divided up that way, so if in doubt, grab the download). Install the driver and reboot. Then install PT9(its a complete installer and doesn't need to see PT8 at all). I'll cross my fingers for ya.

Make sure your iLok has the PT9 asset on it(connect to the web and log into your iLok account with the iLok attached to the internet computer). The old iLoks work fine for Pro Tools, but some newer plugins require the new iLok(like the Steven Slate plugins). You may need to update the iLok drivers on the PT machine too.

[CME]

And just asking, I couldn't decipher for sure if you've done this, but have you installed the 003 driver? It is now a separate install from PT9/10. It is no longer automatically installed with pro tools. If you have done so then I'm not sure. Maybe a bad FireWire port or cable? Have you swapped ports and or cables?

[YYR123]

+1 for cme's driver for the 003r+ are seperate from pt for 9

[Jack Vandal]

if the driver you all are referring to is the one found on the "Device Drivers" disk that comes along with PT9, -OR- the one found here http://bit.ly/aEmN3N
(the 002 and 003 family drivers) then yes, I have installed them. Probably 6 or 7 times in the last two days.

Albee- The ilok is updated, I did what you recommended with no success. Could this be a firewire driver issue? How do I access my firewire driver?

I'm not the only one who has had this problem, however, it seems that none of the solutions that worked for the others works for me. Good grief, Avid.

to make matters worse, my tech support code has mysteriously "expired" and I have to purchase a new one if I want help via-phone.