Digi 002 work with pro tools 10

For whatever reason, though, I can not use the sliders to modify levels. I also can only hear sudio through the if I'm in software mode, which leads to a problem in that I need hardware mode to use my Kona LHi card. Are these two devices incompatible?

What hardware are you trying to co-install with? If it is operating correctly then you will see a green lit above your timeline. With modern cpus any 2 separate PCIe cards will do but they must be the approved 4k buffer ones. Slot configurations for various cpus are available in the Knowledge base. If these bus considerations are not followed you will get v-sync errors at least up to complete non-function of both hardwares.

I have it working with both analogue Mojo and Adenaline very well with MC5 and with analogue Mojo only with Protools LE 8 but there has been some problem with the Digidrivers compatability. For full functionality I have found that the Digidriver supplied with ProTools 8. There is one other consideration. There was a power loom defect on early units that up until recently Avid would replace for free.

If the unit has this defect then it can produce some very strange behaviour from firewire issues to no sync and funny scribble strip led readouts. If you have this defect you can still fix it usually without the replacement power harness by removing the bottom plate and carefully using some WD40 clean and remove the 2 long power connectors 5 or six times.

I have to do this about once every 1 to 2 years and it restores full functionalty perfectly till the next time! Finally if you get it working and have the right hardware it's a fantastic combination almost full controller functionality, surround monitoring with direct output in MC and mixing in ProTools Le with Neyrinck's Mix 5. It's at least worth it just to see those faders move by themselves! Mercer: What hardware are you trying to co-install with? Thanks Mercer - I appreciate your thoughts and have read most of your posts regarding the Digi If these are required to ensure functionali9ty of the Digi , then how can the be considered supported?

Correct, DNA support ended with 5. I am not sure of later versions using the Digi but I imagine it will work only for software. I am absolutely sure it says co-install with DX hardware is unsupported. I think all other 3rd party hardware too takes over the sound in MC 6 and above. The Digi with a good mic preamps attached I use Sonifex is still first class and ProTools mixing to picture especially with Surround is something I use a lot.

We liked it to - we had it connected with and analogue Mojo and it worked great. The problem is that because the white papers indicated compatibility I didn't have the powers-that-be budget for a new mixer, so now I'm kind of screwed. Do you think I could use the in Standalone mode and feed it an audio signal from my Kona LHi card so that I could at least monitor audio and have picture at the same time?

You can use it as a standalone quite well but it's a bit inconvenient having to switch it into that mode each time, or perhaps not, I don't know. It's not a great mixer though as a piece of hardware, a small Mackie is more convenient, but it will certainly suffice as a monitoring mixer. When budget allows from the bean counters and if you still have the analogue Mojo it would great to set up another pc for your audio sweetening station needs with it.

I can get to work on its own and I can get the Analog Mojo to work on its own but when they are connected together, the '' symbol above the timeline is not lit. If anyone has got it working under W7 bit, I'll be interested in hearing about it. This is using MC5. I know about your long history of probs with the Digi, we've talked about it before.

I have no experience with Win 7 64 so I cannot vouch for that but, I can't remember if you've tried all the legacy firewire driver bit and if you've got the right firewire cards, I'm sure you have because you've looked into that. Did I ever suggest the bit about looking at the power harness?

The unit can seem to work in almost respects but still have issues. When I last opened mine one of the plugs was almost hanging off and yet the unit lit up and seemed to work properly. Except I was getting all manner of sync issues like you and eventually MC hung at intialising audio on startup.

A quick clean and reseat solved this completely. Thanks for the info. I do know its a driver issue as I've tried an older driver and managed to get the to light but the audio has been distorted or it causes the system to crash. Yes, i do have right Firewire cards. Believe it or not, I did change the harness too. I had too because it wouldn't switch on and I discovered that this was a known problem makes a clicking sound on power-up but then switches off , so I managed to source one and change it.

That's all working fine. I have MC6 but I can't use it for all the reasons you've listed. I don't understand how Avid won't support their own hardware but do support third party hardware. With MC5. And to be perfectly honest, I'm not moving to MC6 any time soon either, like a many others I would imagine.

I agree there was real problems with the drivers as Avid began to merge their audio 'engines' between MC and ProTools. Even then there can be some funny behaviour if I enable the controller settings. I think it's all to do with driver incompatibility and increasing firewire traffic protocol problems hence why Avid moved to 4k buffer cards - I'm still using TI Ads Pyro 2k cards.

However the problem for you is that driver is 32bit XP only i think even though there were 64 bit flamethrower drivers since Vista. Now you may be right that it is just an insoluable driver issue for Win 7 64, which Avid will never sort now.

But if you'll forgive me you can't be sure until you completely eliminate every variable. I'm sure you have but just to go over it again, if it was me and I never give up until I get stuff working I'd approach it like this if you can spare the time:. Different sync cable. Reseat that harness, it doesn't matter if you replaced it they still had the same problem - a design flaw. This is the only way you can eliminate any device configuration problems.

I know it's awful lot to do just to confirm what you already knew: the digidriver was never fully sorted, but it's probably the only full answer. I'm going to load Win 7 64 on a spare drive for my setup soon to see so I'll report back to tell if I ever get it working. I know it's no consolation to you and is not practical to go back to XP but it does work. Thanks for all the info and all the help. Much appreciated.

I know, for example, that the CLK output works but in general I can listen to the output and hear the clock signal. You're right in your second point - get a clean install. I have a multi-boot machine so I can add a partition to that - I have a separate one for MC6. It's just matter of finding the time as at the moment I'm in the middle of a project but yes definitely worth a shot.

I've always run the Mojo on the in-built firewire port as I know it's on a separate bus but the has got its own dedicated firewire card. I got the specs out of Dell regarding the busses in the machine and who was on what to make sure everything was as separate as possible. In Audio Devices it shows up with 0 in and 0 outs.

Any help? My Studio. IF you haven't downloaded the latest drivers for PT 10 try that. I"ve also had to re-install drivers occasionally to get it to work properly. If you only installed the driver once, try installing a second time. Also if you have more than one firewire port, try another port, or another cable. Go into peripherals and change your playback to your rack. It sounds like a user error or a driver problem. When I go into my sound preferences on my laptop it recognizes my but says the device has no input controls.

I've got Pro Tools to recognize the and play audio through the speakers but when trying to track, it won't recognize any ins from the r. You may want to go into your IO setup and click "Default" on all the tabs. Been having the same issues the past couple days. Just downloaded the new OS update this week and had tracking to do this weekend and pt10 wasn't recognizing it there.

There's a lot of known issues all over the forums about firewire compatibility with the new update. Hopefully everything keeps running smoothly for you and me both. Thanks 2 years later! Simple solution but would've taken years to guess if ever.