Win7 drivers for 002/003

[bcwiz]

Originally Posted by a100man

In the meantime, I've been using the 8.0.4b drivers with PT9 or 10. This issue doesn't seem to be present in that release, but there might be other problems since it's a really old beta driver. But it's been ok for me. I am looking forward to a new driver that fixes this

Ok I tried these drivers (8.0.4b) with an 003 console and the 'punch glitch' and broken reverb tails do not happen.

There's a clue there for tech support.

[philip888]

Originally Posted by bcwiz

Ok I tried these drivers (8.0.4b) with an 003 console and the 'punch glitch' and broken reverb tails do not happen.

There's a clue there for tech support.

Ok where can I find this driver (8.0.4b)?

Thanks

[a100man]

They're kind of hard to find. Go to the bottom of the page:

http://avid.force.com/pkb/articles/e...875?popup=true

[bcwiz]

Well I would be skeptical that all is well with the 8.0.4b drivers as a100man says they are old but so are the current drivers. The caution was that LLM did not work properly. I didn't check that I don't use LLM. Worked fine in PT10 on 003 console at a buffer of 64 with convol reverb (reverberate)running. I'll check it on the 003R today.
Hopefully tech support will pick up on this as there is a definite clue to the punch glitch/reverb tail thing.

[bcwiz]

Could not get the 003R to work with 8.0.4b as it would not roll back the firmware from PT10 (v9xxx). The 003 console firmware was v7xxx and works fine with firmware v8xxx. If I put the 003R on a PTLE7 or LE.8 rig it will roll back the firmware.
I'll have to go to the studio for that.

[a100man]

The 9.0.5 drivers just released seem to have similar behavior. Under 256 samples the broken reverb tails exist. At 64 samples, the Audio becomes erratic and for lack of a better term, "Staticy" This is on an 002 Console

[deeepi]

same issue "bug" here 003rack+win7prox64+cubase7.0.4 32 and 64bit
tested drivers: 9.0, 9.0.2.65, 9.0.5, 9.0.7...same issue for all drivers
issue found:
1) asio audio track playback output crakling (click'n'pops) at every buffer size
2) windows starts without find 003 soundcard (need to turn off and turn on 003rack)
3) midi input of 003rack don't work

the only one driver that works for audio and midi, after the v7, in 2013 is 8.0.4b, but the 003rack sometimes freeze, need to turn off and turn on the 003.

bad story

[bcwiz]

Originally Posted by a100man

The 9.0.5 drivers just released seem to have similar behavior. Under 256 samples the broken reverb tails exist. At 64 samples, the Audio becomes erratic and for lack of a better term, "Staticy" This is on an 002 Console

Yep, just tested the 9.0.5 drivers on 003 console and nothing has changed.
The current 003 drivers are still broken. I would like to know what "Miscellaneous bug fixes" that tech worked on. Tech has clearly not done a damn thing about these driver issues. I thought for sure it would be fixed for PT11.
Tech support has insisted that the 003 is supported. This is not support!
It has been over two years for a Win 7 driver update and the drivers have been broken since 8.0.5. Pretty sad guys.
The 8.0.4.223 driver from 2009 does not have the quick punch/reverb tail issue and tech support have been told this. I really don't get it.

[bcwiz]

Originally Posted by deeepi

same issue "bug" here 003rack+win7prox64+cubase7.0.4 32 and 64bit
tested drivers: 9.0, 9.0.2.65, 9.0.5, 9.0.7...same issue for all drivers
issue found:
1) asio audio track playback output crakling (click'n'pops) at every buffer size
2) windows starts without find 003 soundcard (need to turn off and turn on 003rack)
3) midi input of 003rack don't work

the only one driver that works for audio and midi, after the v7, in 2013 is 8.0.4b, but the 003rack sometimes freeze, need to turn off and turn on the 003.

bad story

Sounds like you may have a firewire problem? (just sayin')
Nevertheless the current drivers are NFG

[deeepi]

Originally Posted by bcwiz

Sounds like you may have a firewire problem? (just sayin')
Nevertheless the current drivers are NFG

I do not think that I have a firewire problem, and in any case if I would like to solve this problem.

when I was using windows xp 32bit with driver v7, the 003 was connected to the firewire on the motherboard (Via chipset) and everything worked well, especially not had the problems described above.

now use windows7 64bit, with the driver 8.0.4b (the only one that works to 80%) and 003 is connected to the new motherboard (always Via chipset firewire)

I do not think that using a PCI firewire card with texas instruments chipset for it to resolve the problems described the drivers, also because I believe that other people using a card texas instruments have the same problems.