JohnW
pfm member
I believe John refers to the ability to ADC the incoming signal and DAC it on the way out, achieving a similar effect to what an AV bypass would. Theoretically this could be very "transparent" as the signal could be kept in DSD256 (or so) between the ADC and DAC.
Yes - correct, thank you for helping with the clarification
WRT the MDAC2 & FDAC "SOC" as time to market is so important and with the pending release of the RPi CM3 we have given up on the H3 solution - with first Beagle hardware, then H3 we hope for 3rd time lucky with RPi CM3!
We plan to have the MDAC2 SOC PCB to you in the 1st or 2nd week of January - but as the RPi CM3 module is not currently available we will supply it to you with the CM1 - will this be enough for you to start on the MDAC2 software? (the CM3 / MDAC2 audio pathway is via a secondary internal USB connection).
We will also supply our miniDAC with our XMOS based USB solution that we plan to use on the MDAC2 so you can confirm the stability / performance of the Linux USB drivers etc. test PCM 768KHz / DSD256 etc...
Now that the RPi CM3 is on the Horizon and with development time most critical we plan to also use the RPi CM3 on the FDAC - the only real loss is independent Front panel LCD and rear HDMI output ... but IMO its compromise we will have to live with - we can still have internal SSD and DVD drive via internal USB to Sata...
We plan that the MDAC2 Stage2 (SOC) PCB will have a connector on the PCB to allow connection of the FDAC's LCD and touch panel to allow FDAC software development (UI) etc. once the MDAC2 software development is out of the way - IMO I believe this is the fastest and most sensible route to FDAC after MDAC2... In the future this same connector also allows the MDAC2 front panel to be upgraded to touch panel LCD as a user upgradable retrofit...