Digi 002 Drivers Download

The Digidesign 002 Rack / Console is still a very common audio interface, mainly because of its high quality. The driver installation in Windows 7 though can be a bit tricky. At first you need the correct driver from here. Be sure to download the correct driver for your interface. As of now it looks like this: 9.0.8. – latest version for 002 Console 9.0.6.

– latest version for 002 Rack After downloading the driver simply install click the exe file and install them. In most cases the Windows Device Manager will still show you the Digidesign 002 & 003 device with no driver installed.

Then you have to do the following; – open the device manager – right click the digidesign device – choose update driver – search the computer for a driver – choose for a list of drivers on this computer – all devices =>next – have disk amd point to this directory C: Programms Avid 003 (Console) Streaming – select the “Avid00Console.inf” file, select Digidesign 002, ignore all the Windows warnings – check the device manager again =>the device should now be listed at audio,video & gamecontrollers Posted on Author Categories Tags,,,.

Digi 002r and X3 - driver issues? Hi I'm new to sonar and have just closed a thread where I was experiencing a time line freeze. I assumed I was just doing something wrong but it appears that there may be an issue with the digi 002r drivers, hence the new thread. From what I've been able to find, there are a range of possible fixes, from 'disable multicore support' all the way to 'just get a new interface'! I'm not great with all the various driver type issues and diving deep into settings etc but I'm hoping that someone out there may be able to help me.

Any ideas guys? I was thinking of installing the newest digi drivers even though they state that they do not support the 002r. Worth a shot?

Digidesign ASIO Driver: The Digidesign ASIO Driver is a single-client, multichannel sound driver that allows third-party audio programs that support the ASIO Driver.

Brightside Just loaded up the 003 drivers from the digi site and it seems to run ok in WDMKS. I only had time for a very quick check but the only problem I could see (playback only - haven't tried any recording or synth playing) was a delay of about 2 seconds before play back starts after hitting play.

Any ideas on the delay, or maybe this is just a 'feature' of my set up with those drivers? The delay can be 4 things. You have a pre-count for the metronome 2. You have your WDM slider settings to high 3. Your drivers are horrible for the DIGI 4. Your PC MOBO and your sound card drivers do not like each other CJ.

CJaysMusic The delay can be 4 things. You have a pre-count for the metronome 2. You have your WDM slider settings to high 3. Your drivers are horrible for the DIGI 4.

Your PC MOBO and your sound card drivers do not like each other CJ Thanks CJ. I had another look over things: 1. I hadn't thought of something so obvious as a silent pre-count! I checked, but it's not that. I'm assuming you mean the buffer her Dune Buggy Blueprints Pdf Free. e. If that's the case then I've tried various values with no success. They are Digi win7 64 standalone drivers i.e.

For use with Digi002r on software other than PT. I've tried a few different variations of them now on my system, all with the same results. Not possible for me to quantify this.

So, other than the second or 2 delay on hitting play, everything else appears to work and the sound quality is great using WDMKS. Conversely, when I switch to ASIO, the playback starts immediately on hitting play, but I only get a second or so of audio before it drops out (timeline also stops)! If anyone has has any further ideas, then I be very grateful to hear them. Meanwhile, I'll try to live with the delay for a while before I go down the route of buying a new interface. The digi is perfect for my set up, so I want to be certain before I even consider buying a new interface. I'll update this thread as I go, in case anyone else hits a similar problem.

Robert_e_bone Hi - I am coming into this a bit late, but will try to help. Thanks Bob, I appreciate your offer of help. I'll answer your questions as best I can: On WDMKS: Digi 002 sample rate is 44.1k and buffer size 1024 samples (23.2ms).

Sonar on 44.1k, no round trip stated when in WDMKS, playback and record buffer both 256kb. I can't see a prepare using figure (nor field for that matter) On ASIO: Digi sample rate and buffer size the same. On the asio control panel the clock source is set to internal. Sonar on 44.1k, round trip 2398 samples (54.4ms), p and r buffers both 256kb.

Again, no sign of a prepare using field sorry. In the project section of preferences the source is set to audio as opposed to internal (as above). No idea if that has any relevance but thought I'd mention it. Thanks - It is not quite clear on your ASIO audio interface ASIO Buffer Size setting - I take it your comment meant that it being 'the same' meant that it is a sample rate of 44.1 k and 1024 for a buffer size.

PLEASE correct that if I am mistaken. Your Total Roundtrip Latency of 54 ms is WAY WAY WAY too high for recording.

Please try setting things as follows, for a test: Audio Interface: Sample Rate 44.1 k ASIO Buffer Size of 128 Sonar: Driver Mode of ASIO, Sample Rate of 44.1 k, Record Bit-Depth of 24 bits. You want to try to record with a Sonar-reported Total Roundtrip Latency of around 10 milliseconds, or just under it a little, as a good balance. Please give the above a shot, in a new project, with either audio or midi tracks, with NO added effects, just to see how it all plays back and records with the above settings I posted. Thanks, Bob Bone.

Robert_e_bone Thanks - It is not quite clear on your ASIO audio interface ASIO Buffer Size setting - I take it your comment meant that it being 'the same' meant that it is a sample rate of 44.1 k and 1024 for a buffer size. PLEASE correct that if I am mistaken. Hi Bob Your assumption was correct, the ASIO settings were 44.1 and 1024. I set up a new project in ASIO as per your suggested figures (round trip was 13.7ms) and set up a single midi track to record. Pre-record monitoring was all ok and on hitting record, the result was as follows: 1.

Monitoring was fine, it felt/sounded like a normal recording. The time line stopped at approx 250ms (done the procedure 3 times). Past 250ms the monitoring and metronome functioned as normal. Only the first 250ms of data was recorded. On playback, the 250ms worth of data sounded fine - then nothing. I wasn't sure if it was relevant but the 250ms corresponded with the value of the midi 'prepare using' field, so I changed it to 500, then 1000 but it resulted in the same 250ms being recorded.

Another point to note is that when pressing 'apply' after making changes in Prefs results in a delay of about 20 seconds (complete with spinning windows cursor) before being returned to the track view. This only happens in ASIO, not WDM. I've also tried this same test with the FW card drivers changed to Legacy mode as I'd read somewhere that this may have an effect but there was no joy there either. I also tried a buffer of 64 (10ms) but got the same results as above. So frustrating. This doesn't look like it's going to have a happy ending!

Thanks again for your help Bob. By chance, is your audio interface the default Windows audio device? If so, this may be interfering with it working in ASIO in Sonar. Just for a test, try setting your Windows default audio device to be your on-board sound chip, rather than the audio interface. Windows Xp Mui Pack Polish Download.

Then, try setting your audio interface back to the settings I suggested, and those in Sonar too (Sample Rate 44.1 k, ASIO Buffer Size of 128, Sonar Driver Mode of ASIO) Then give that a quick test in a simple project with no effects loaded and post back. Thanks, Bob Bone. In the sounds dialogue box, the only options were for the various digi I/O. I disabled all of them (the digi main outs had been selected when I went into the settings) and set up a project as per your post.

There was no sign of any option for onboard sound. On running a simple project, the outputs were the same as before i.e. Audio and midi start playing immediately, timeline stops after 250ms, audio continues to play as normal, midi instruments stop after a few seconds. The sound quality is all good throughout. Switching back to WDM results in the same outputs as before i.e.

2 second delay then all audio and midi play perfectly. It feels so close! Also, you might try setting your Windows Default Audio Device to be that of your on-board sound, and only have Sonar point to ASIO4ALL, until you can get rid of it. It has helped some others to run as above while they weighed options and planned for picking up a real interface for mobile work. Lastly, I would suggest temporarily disabling your laptop's Wi-Fi adapter just prior to running Sonar, and enable it again after completing a given Sonar session. Wi-Fi adapters are notorious for adding massive latency spikes when enabled to Windows.

Disabling it in Device Manager (or, turning off the switch if it has one, or using a function key to turn it off), does not remove the device from Windows, so you do not have to install it again - it will simply come back on when you enable it again in Windows. Apologies (especially to Bob) for not updating this thread - things have been kinda busy recently. Anyway, having tried lots of different ideas, the problem remained, so I tried out a borrowed interface and it's worked flawlessly ever since.

I remain convinced that it's a driver issue with the digi but have resigned myself to getting a new interface. It's been absolutely wonderful getting back into making music and, now that I've become much more familiar with Sonar, I really like it. Not mad about the midi editing but that's for another thread! Thanks for your help Bob, I guess this thread is 'solved' to a certain extent!

Sell by date at 9000 posts. @48/24 & 128 buffers latency is 367 with offset of 38. Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.