6 responses Add your response
After looking through countless forum entries throughout the entire day, I’ve come to the conclusion that, unless there was one (or maybe a few?) firmware updates that resolved this issue, then this is a lost cause. Of course if you know of anything at all, please do chime in. If I don't hear back in several days, the DAC's going back out for sale. :/
Sorry but passing clocks around is an 80's solution that never worked very well. Jitter is a inherent issue with clocks and signals, The best approach is an asynchronous DAC that simply rejects jitter - however do lots of research because many DACs add their own jitter through PLL adjustments which can be far worse than random jitter.
I’ve come to the conclusion that the Transporter’s word clock input (and/or associated software) is simply not functioning correctly, and that there’s nothing wrong with the DAC6. Considering how much I really do love the Transporter, and was just curious about older DACs (even though I didn’t quite take that exact route), the DAC6e SE is going back out on the market. That may sound hasty as all get-out, but I have no interest in combing the planet for a fix.