Search the Community
Showing results for tags 'lynx'.
-
Not a new thing at all but I wanted to make this approach more... approachable and moreover I am hoping to hear from someone experienced/knowledgeable with this approach for our general consumer use cases. Yeah and also just to start a discussion Caveat: I haven't tried this. The goal: Multi-channel The uses: Active speaker crossovers, Software Room Correction, Software Bass Management oh yeah and also the occasional original surround content The problem: Your favorite DAC is not multichannel/multichannel DACs are too expensive/consumer mch DACs could be counted on one hand/you are bored/etc The approach: Multi-Channel AES Interfaces Solution Ingredients: 1. A Computer (luckily this is the CA forum!) 2. A multichannel AES Interface, such as Lynx AES16e ($699) or miniDSP U-DIO8 ($275) - OR - 4. Your favorite AES/EBU or S/PDIF enabled stereo DACs Description: The OS and players will recognize the multichannel digital-to-digital interface as a single multichannel audio device which would allow mapping of the channels and would in turn use whatever downstream DAC is connected to each channel pair as the digital-to-analog interfaces. Example #1 - Value 8ch: 1x miniDSP U-DIO8 S/PDIF Edition - $275 4x Topping D30 - $480 4x BNC to RCA - $14 Total: $769 Example #2 - Multi Channel Yggdrasil: 1x miniDSP U-DIO8 AES/EBU - $275 4x Schiit Yggdrasil - $9,600 Total: $9,875 Example #3 - Mixed high end 2ch with value surrounds for 5.1ch: 1x miniDSP U-DIO8 S/PDIF - $275 1x Benchmark DAC3 - $2,195 2x Topping D30 - $240 4x BNC to RCA - $14 Total: $2,724 Example #4 - 2x 3Way Active Crossover: 1x Lynx AES16e - $699 3x Benchmark DAC2 DX - $5,985 Total: $6,684 You get the picture. Currently mapped notes/pitfalls: 1. Mind the difference between AES/EBU and SPDIF and pick units and cables accordingly (Could potentially use converters like the M-Audio CO3) 2. Volume control is only in software. I'm not sure if the miniDSP or Lynx map to the normal OS volume control which could then be used with PC remotes and keyboards with volume buttons. 3. Both miniDSP and the Lynx only supports 192kHz/24bit. 4. Not sure if the miniDSP or Lynx could be used as standard Windows audio devices and set as default or if they only support ASIO enabled players. If only ASIO is supported then I guess a virtual sound card (like Virtual Audio Cable) might be helpful. 5. DACs with volumes should be set at the same level 6. Mixing different DAC models should be accompanied by volume leveling on the channels (no different than speakers actually so this is usually recommended anyway) 7. Only PCM is supported 8. Clock drift - Good consumer DACs perform re-clocking on some/all of their inputs (not sure what is common with AES inputs) which is generally a good thing done to prevent Jitter. In this case though it is actually preferable to use the pro AES interface's clock which is build to function as professional grade low-jitter master clock for connected device, as per the original standard. Leaving each DAC to his own internal clock might result in clock drift between them. I have no real insight into this issue, if it's a problem and if/how is it avoidable. Re-clocking behavior should be evaluated per input type of a DAC model and I *think* we should prefer DACs with no reclocking on the AES XLR inputs. I might also be completely wrong on this whole thing Anybody with experience in these sort of setups? Insight? Tips? Corrections? Limitations? Other pitfalls? Jokes on the OP? Thoughts? Thanks to @Kal Rubinson for helping to map some of the pitfalls.