Win7 drivers for 002/003

[bcwiz]

Ok I'll start.
There has been an ongoing issue with the Digi 002/003 drivers on Win7, specifically the glitch heard when punching in/out (not to mention the delayed reverb tails when transport stops). Documented in this thread; http://duc.avid.com/showthread.php?t=310286 also http://protools.ideascale.com/a/dtd/.../85922-3779and others.
The last we heard from DigiTechSupport was the problem was recognized but no known cause. Is there any possibility that this will ever get fixed? It has been two years since the last Windows driver update for the 002/003 family.

regards

[sunburst79]

Originally Posted by bcwiz

Ok I'll start.
There has been an ongoing issue with the Digi 002/003 drivers on Win7, specifically the glitch heard when punching in/out (not to mention the delayed reverb tails when transport stops). Documented in this thread; http://duc.avid.com/showthread.php?t=310286 also http://protools.ideascale.com/a/dtd/.../85922-3779and others.
The last we heard from DigiTechSupport was the problem was recognized but no known cause. Is there any possibility that this will ever get fixed? It has been two years since the last Windows driver update for the 002/003 family.

regards

Despite the Blue Blazes I havent heard a peep on what they are doing with this. That they were able to repo it means its been logged for a fix. How soon? Who knows. Given the fact that the Windows drivers don't needed to be updated nearly as often as Mac drivers I would expect to see this in a future update to 10.3.X OR more likely rolled into a Windows 8 Driver upgrade. The latter would make the most sense. Or PT11 whenever that drops.

[Paul_S]

Originally Posted by bcwiz

Ok I'll start.
There has been an ongoing issue with the Digi 002/003 drivers on Win7, specifically the glitch heard when punching in/out

regards

Could you try buffer 512 or higher and LLM enabled (as workaround for now)? Let me know if that helps

[bcwiz]

Originally Posted by Paul_S

Could you try buffer 512 or higher and LLM enabled (as workaround for now)? Let me know if that helps

Well believe it or not that actually makes things worse. The glitch is more pronounced using LLM. The problem is improved slightly at higher buffer when not using LLM but it is there regardless of buffer settings.
Anyway, unusable for me.
I have to use a third party interface to overdub with 'cause I'm tired of having to explain to clients that it's not a problem. It would be really really great if this got fixed (soon).

thanks

[Paul_S]

Please specify couple things for me:

1. Is the glitch recorded to the audio or it's just a monitoring issue?
2. Sample rate you work with
3. How often does the glitch occur, in all takes?

[bcwiz]

Originally Posted by Paul_S

Please specify couple things for me:

1. Is the glitch recorded to the audio or it's just a monitoring issue?
2. Sample rate you work with
3. How often does the glitch occur, in all takes?

The glitch is not recorded, monitor only, affects playback tracks
I believe some folks reported this being recorded but it's never happened to me

I work at 24/48k
Interesting to note that at 44.1 the problem goes away at buffer settings above 256 regardless of LLM

The glitch occurs every time I punch in/out and regardless of how record is initiated

[Paul_S]

Sure, LLM has nothing to do with the problem. On my setup the issue disappears on buffer 512 and above at 48k. I'm pretty sure that this will work on most other setups as well.

Anyway, the bug will be logged and I'll keep you posted on the results

[bcwiz]

Originally Posted by Paul_S

the bug will be logged and I'll keep you posted on the results

Any news/rumors on driver updates?

[Paul_S]

Originally Posted by bcwiz

Any news/rumors on driver updates?

Bug logged, work in progress

[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