|
Digital Drive Upsamplers, DACs, jitter, shakes and analogue withdrawals, this is it. |
For Sale Ads |
Use this form to submit comments directly to the Asylum moderators for this forum. We're particularly interested in truly outstanding posts that might be added to our FAQs.You may also use this form to provide feedback or to call attention to messages that may be in violation of our content rules.
Original Message
RE: Couple of corrections...
Posted by PaulMC on June 10, 2017 at 06:06:39:
I am not sure what "hyperbole" you're referring to.
But you are correct. The core module around which the Bridge II is built is from a South Korean company Converse digital. That's no secret. Never has been. We place that module at the core of the Bridge and then populate the balance of the PCB with memory and a Digital Lens to output to the DAC through I2S.
Converse, with our help, has implemented a number of features including Tidal, MQA, etc. We work directly with MQA on "tuning" the specific firmware version we use in the Converse module found in Bridge II because MQA requires it. They have a DirectStream in Cambridge and use their tuning methods to match DirectStream's impulse response. Converse then programs that into the module.
If by hyperbole you're referring to my many posts of how our programming efforts releasing Huron, the new operating system for DirectStream was held up by MQA programming, that is true. Our side is required as well as Converse. Remember, the Bridge has to communicate with the DAC and has to report its status to our front panel touch screen.
I am sorry you seem to feel there's some kind of BS or conspiracy to defraud our customers—which is simply not true. Hopefully this helps you understand what's going on and ferrets out the truth. I am always available via email for anyone with specific questions or needing help.
Thanks for the opportunity to respond.