I switched from Gustard A26 to Holo Spring 3 in I2S without any change (cable or settings). No issue 😉

How many hours has the Cyan been running... I guess your Spring has been running for months (?). But it's only fair that the price hierarchy should be respected. :sunglasses: I had a Pegasus, just before my A26... the Cyan is on top ? And no possibility of testing another input... and DSD ?

No one has tried the I2S Lvds. input ? I'm hesitating to replace my A26... and go back to an R2R (I had a Pegasus just before).

Hav you some pics ?

I know of a Tambaqui for sale... 6 800€

I no longer use the ethernet input (Diretta > I2S) but with version 1.42, I used to use a fixed IP given by the DHCP server (OpenDHCP on my Roon/HQPlayer audio server).

No, i don't think but can you describe your network when you stream. The R26 had a 100mb network interface. Same for the A26, but the hardware (SBC) is different. There's no problem even with DSD 512, but your R26 is connected to what ? and how ?

But it is, even though it's hardly ever used. I removed it when I optimized the A26 system to run only networkaudiod (NAA) on one of the card's cores. Now that I have an external Diretta box, I no longer use the A26 streamer.

It's amazing... I'm on "DSD direct" / I2S / DSD 256*48 / sinc-MGa

I use 48kx256 in output with no problem.

Dsd direct is only on DSD 128 and 256, not in DSD64 or 512 (inside upsampling). But it's strange... nothing like that on my system. Same firmware as me ? A_115_131_234 I used I2S enter with DSD256.

For me it's normal. The detection circuit does its job. In case of no-detection, it displays the error but switches to the internal clock. If the internal clock is selected by default, the detection circuit simply displays "INT". In the AKM schematic, this is identified as "MCLK" (MCLK stop...

It would be another hallucination or cognitive bias to perceive a difference with or without an external clock (still in DSD direct - DSD256 via HQPlayer) ? Surprising that it is well identified (present or absent >> ERR Ext) and that it is not "connected" to the process. For me, the AK4499EX...

It works for me. The external clock is on, and "ext" is displayed. But if I leave the setting on external and restart the dac, with the clock off, the dac works. It must switch back to internal. I had done it by mistake. When I turn the clock back on, I see "ext" on the screen.

In the end, the K2 is sufficient and Gustard is planning the possibility of an external clock to sell its U18s ? Is this pure marketing ? Or maybe the idea is to use a master clock as a real master. In other words, one that sets the tempo on several devices : not only dac, eg. dac + Afterdark...