From the little I can gather from this, I assume the 1.43 is NOT for me.., using ROON and upnp.. Arrest me if I'm wrong 

I unpacked this firmware and it looks like Spotify and Tidal Connect support have been added. The Raspotify project was used to support Spotify and ifi_tidal-release was used to support Tidal. Both projects from GitHub.I installed, DSD not working properly via BubbleUpnP.
Tidal connect not connecting via Tidal App.
I uploaded firmware 1v43 and Tidal Connect works without any problems. In the TIDAL app it is seen as Gustard R26. Spotify also works but a Premium account is required. In the Spotify application it is seen as raspotify (Gustarender-1v43). Roon also works but you need to re-add R26 in your audio devices. As for Roon, there is no update here.Are you also using ROON? Please reply your findings
How about DSD?I uploaded firmware 1v43 and Tidal Connect works without any problems. In the TIDAL app it is seen as Gustard R26. Spotify also works but a Premium account is required. In the Spotify application it is seen as raspotify (Gustarender-1v43). Roon also works but you need to re-add R26 in your audio devices. As for Roon, there is no update here.
If this is the official firmware version, I will no longer have to prepare further versions with Tidal support. I haven't tested the memory load but I assume it will be no different from the previous version of Tidal + Roon
I only use Roon, so DSD works natively without any changes. Unfortunately there are no updates in GMediaRenderer so DSD over UPnP will still not workHow about DSD?
Tidal on Android requires special certificates and processing them through Gustard takes a long time and costs a lot, so only Apple hardware remains.Can confirm both Spotify connect and Tidal connect working.
For some reason Tidal connect is not working on Android Tablet but works on iPhone.
see it this way. You were asking whether R26 reclock I2S port. They misunderstood it, as their response is about converting DSD stream to the PCM or not, according to "Direct DSD" settings. It is obvious that with Direct DSD 'on' clock line is related to the 2.8MHz sampling frequency and with PCM stream (or after converting to PCM, but not before - I2S line clock). There is a conflict (highlighted) in what they say, it is why I deduct they talk about different things.
Question in regard whether the I2S clock line is fed to a PLL or bypassing PLL is still unresolved.
What kind of power supplies are you using? With a decent LPS you should be getting decent ground connection. If you want to go wild, you could always connect a grounding box, but it's a chunk of change for decent ones, perhaps Jake can chime in on that topic. Are you sure you have a ground issue?Hello All
Hope everyone is having a good weekend
I would like to pose a question which is probably mildly off-topic but given that there has been a large amount of talk on this forum about using FMC kits to improve network quality for use with the R26, I will try my luck
Question: I have a couple of 10GTek FMC's. How would I go about grounding these devices, please?
Many thanks
They do indirectly, when refering to the option Direct DSD and it gives me confirmation for not understanding a question. I am sure they talk about processing data (sound). In fact, when these two options (NOS and a Direct DSD) are ON, there is no sound DSP processing, this is what they say and I have no problem with it. But it is not what you have asked for.The Gustard response makes absolutely no mention of converting DSD to PCM. My take on this is that if I have PCM NOS ON and I am using the I2S input, then the R26 is not re-clocking but using the clock information provided by the streamer in the I2S data-stream.
How would you phrase the question to Gustard to get absolute clarity / confirmation on your statement below? I'm willing to go back to Gustard to try and clear this up![]()