Digi 002 on Windows 10

[secutanudu]

I recently came to get a free Digi 002 rack with ProTools LE 7.4.

I am running windows 10.

The installation seems to have gone ok, but when I launch protools, nothing happens. I do see protools running in the background processes, but nothing actually comes up.

I did have Protools First installed on my machine before installing 7.4. I have since removed it.

Any ideas? Thanks.

[The Weed]

Windows 10 is not qualified for Pro Tools and when it is, it will probably be qualified for PT 12. PT 7.4 won't even work on Windows 7, earliest was PT 8.0.5. You can roll back to Windows XP - joke - or, if the serial number hasn't been used, try to find an upgrade path to PT 12. Again, Pro Tools is not yet qualified for windows 10 although some do have PT 11/12 working on Windows 10.

My Digi 002 Rack works fine on Windows 8.1 and PT 12, although the 002 is not supported past PT 10.

Not qualified doesn't mean won't work and not supported doesn't mean won't work, but your operating system is so far ahead in time from the version of Pro Tools you have that "won't work" is the correct phrase in your case.

Cheers,

[secutanudu]

I was afraid of that. Would the serial number be that on the digi 002 rack itself?

How do i even go about finding an upgrade path?

[AlexLakis]

Originally Posted by The Weed

PT 7.4 won't even work on Windows 7, earliest was PT 8.0.5.

FWIW, I'm running PT 7.4 on Windows 7 with no problems. M-Audio FW-Solo on that rig. I use this rig solely for Elastic Audio (X-Form).

My main rig is Digi 002 Console w/ Pro Tools 12.1 on OSX 10.8.5. Works perfectly!

[secutanudu]

Well I called Avid they gave me some great news - the serial number on this 002 has not been used for an upgrade. So I was able to buy it and activate it for $200.

Problem solved! Now I have access to PT 10, 11, and 12 with a perpetual license plus a year of support and upgrade protection.

Thanks guys.

[secutanudu]

OK still have an issue. I got PT 12.3 running great on windows 10.

But the PC won't recognize my 002 Rack. My motherboard came with a little addon card that has a firewire 400 port on it. When I plug the 002 into that, device manager shows it as:
Unknown USB device (Device Descriptor Request Failed)

I also bought a Syba firewire card - it has one 400 and two 800 ports on it. When I plug the 002 into the 400 port on that card, nothing shows up in device manager at all. The firewire card itself does show up in device manager though.

I have tried every 002 and 003 driver I can find, to no avail.

Any ideas?

Thanks.

[Louis Cyphre]

Firewire is a strange phenomenon. It was originally designed by Texas Instruments in conjunction with Apple. It is an IEEE standard, 1394, but this standard only seems to refer to some of its characteristics and not it's design. Therefore there are many different manufacturers of Firewire cards that some work with audio devices and some not.

Your best bet is always to buy a firewire card that has a Texas Instrument chipset installed, as that is most likely to have the correct design. This is not always the case though.

I would go with this link:
http://avid.force.com/pkb/articles/e...ility/en352647

[watksco]

The SIIG cards seem to be the more popular/successful.

[RAYCMUSIC]

If the FireWire card have via chipset will not work


Sent from my iPad using Tapatalk

I can not confirm that. I have PCMCIA VIA firewire adapter which I used with Windows 8/64bit, Pro Tools 10, 002R. Buying that (for about 15$) solved my problems with built in laptop firewire. That was not problem 002R was not recognized or functional. Only some kind of static noise (maybe jitter artefacts).
Have not used it for two years, but I think it would work in that hardware configuration (Win10, PT12 now).
I also used VIA firewire PCI cards for years with 002R with desktops WinXP - absolutely no issues.

Remember, 002R after couple of years, needs to have its intermal conections cleaned. It is described in couple of threads on DUC.