Originally posted on 06/20/05 06:17 PM by soapbox (Geoff Grace):Haigbabe, after reading your post, I purchased a fiber-optic cable. I connected it, but I have yet to try tracking with it. However, I did toggle the settings to try both S/PDIF and ADAT sync with the new cable, and Digital Performer still refused to accept digital sync regardless of how the Digi CoreAudio Manager was set. Logic Pro, by the way, has no internal/digital option that I can find when it comes to word clock, so I don't know if it sees the clock or not. At this point in time, Cubase SX crashes upon booting, so I have more troubleshooting to do in that area before I can even see how it reacts to clocking via ADAT.
Fortunately, the new RTAS plug-ins for the main software library (East West Quantum Leap Symphonic Orchestra Platinum) that I'm using on my current project seem to finally be stable, making Pro Tools LE a viable choice for my current project; and the clocking issue has never been a problem with Pro Tools LE because it doesn't use Digi CoreAudio Manager to interface with the Digi 002. Therefore, since I'm running behind on my project, I plan to shelve troubleshooting on this issue for awhile and use Pro Tools LE. I do plan to try locking to ADAT with Pro Tools LE though to see if I like the results better than with S/PDIF. (
Edit: I subsequently tried this and I did like the results better.)
Sevenlights, were any of the other apps you launched third party DAWs, such as Digital Performer, Logic Pro, or Cubase SX? If so, I'd be interested to read how they reacted to your word clock settings.
It does occur to me, after reading your post, that I've let my eyes be my guide rather than my ears. I have yet to try tracking into Digital Performer, Logic Pro, or Cubase SX with my current setup. Perhaps the visual readings are lying about clock settings. When I find the time, I'll have to try tracking into those applications and listen for any of the telltale artifacts of bad clocking.
