I was going to email to ask if my DVA dac/preamp could have an AES/EBU input added? It's my preferred interface rather than s/pdif (rca or bnc) or optical s/pdif.
This is a request we get almost never, so I thought I'd ask for some clarification and insight. There are three aspects of the AES3 professional protocol, or what we commonly call "AES/EBU":
- The physical connector: 3-pin XLR or BNC versus RCA for coaxial "S/PIDF".
- The electrical spec: 110Ω balanced 2-7Vp-p on XLR, 75Ω unbalanced 1.0–1.2Vp-p on BNC versus 75Ω unbalanced 0.5-0.6Vp-p for coaxial "S/PDIF".
- The data encoding, which differs from "S/PDIF" only in moderately arcane ways).
Which of these is the basis for your preference and why?
To answer the question of whether it's possible to modify a DVA Digital Preamplifier to take an "AES/EBU" stream: yes, it should be possible. It would require both hardware (obviously) and firmware modifications. Changing to BNC would be less physically traumatic than XLR; in fact, I don't know where you'd stick a full-size XLR connector. Would AVA be willing to do the work? I'm not sure. This would require discussion with upper management. Would it be a cost-effective modification? No. You're looking at several hours of new firmware development costs in addition to the time needed to design, fabricate, and assemble the required hardware and electronic modifications. Will a future AVA DAC have an "AES/EBU" input? Sure, if there's an unexpected swarm of requests asking for it.
Ultimately, it would be very attractive if the DVA dac/preamp could become a network device/streamer. Any consideration of adding this capability?
Again, I'd love some clarification or insight on this. Why is integrating the network/streaming data extraction with the DAC attractive? Is it just about box count? As I discussed in
The Right Amount of Integration, since protocols and expectations are still evolving wildly, we feel that separating these concerns is the way to go.
Which leads to the question: Why doesn't AVA develop a standalone streamer (i.e., one equipped only with a digital output)? The primary reason is that a standalone streamer is almost completely an IT/software product, and these require a very different kind of business. For example, how do you provide the intense level of user support s/w products invariably require? What's the process you'll use to invigilate upstream resources for security and other updates? How do you then push those updates out to users and (again) provide support when users invariably run into issues? AVA could set itself up to do these kinds of things, but none of this would make the audio itself better. It's even harder to justify when there already are folks providing products with decent standalone streamer functionality. What would AVA contribute to this?
Don't get me wrong -- I'm not shying away from software challenges. In my parallel life, I teach computer science at a local community college. I'm totally up for interesting software challenges. What I'm saying is that we have a hard time seeing the benefit for AVA clients when we could be using our finite time and other resources to develop solutions that directly make the audio better.