m-i-c-k-e-y
Headphoneus Supremus
download link pls...not still in their website
https://www.mediafire.com/file/m4pr4dz7185wt5h/R26_Gustarender_1v43_onlyR26_R26only.zip/filedownload link pls...not still in their website
I 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.Hello @sajunky :
This is what I asked Gustard:
"I own the R26 DAC and have a technical question which I would be very grateful if you can answer.
If I use the I2S input on the R26, will the R26 re-clock the data coming into the I2S input please? Or does the R26 use the clock information coming in via the I2S input?"
This is the cut and paste of their very brief reply:
"In most cases, R26 will retime.
When nos is enabled, the IIS clock will be used in pcm.
Enabling dsd direct will use IIS clock in dsd."
Based on the Gustard response, I would expect the I2S input on the Gustard to sound the best when PCM NOS is enabled. My experience (in the context of my system) is different in that the AES/EBU connection sounds appreciably better than I2S. But I am probably not comparing "apples with apples" in that I have a very good AES/EBU cable but have only tried a very basic HDMI cable for the I2S connection.
You are right. Technically with PLL reclocking method the internal clock is always in use to bring PLL working point close to the operational range, but its jitter has a limited influence on the output, as PLL use low-pass filter on a phase difference between these two clocks. This is a things that removes high frequency jitter. Whether it is fixed frequency internal oscilator, VCO or a digital synthesiser, is a different story.This suggested to me the K2/R26 does still refer the external clock (and/or by extension the internal oscillator if Ext Clock OFF) for some of its processes/functions, even if it is still 'using' the clock signal provided by the synchronous input.
Yes - are there any release notes for 1.43? I'm reluctant to "just" update since it always feels a little like playing Russian RouletteMore info on the 1.43 please
Anyone tried it yet?
Does it keep the Roon support, and how about DSD..?
Your point is exactly why I said USB is problematic for audio: it's noisy.It’s not quite as cut and dried as that.
In theory USB can be a great way to feed a dac, it is asynchronous and allows the DAC to do the clocking thus minimising jitter, the problem is that what is often on the other end of that USB is a very noisy computer which can induce noise into the DAC. The best method is often dependent on the particular DAC and streamer/computer implementation.
More info on the 1.43 please
Anyone tried it yet?
Does it keep the Roon support, and how about DSD..?
As it is said on the changelog:Yes - are there any release notes for 1.43? I'm reluctant to "just" update since it always feels a little like playing Russian Roulette
As it is said on the changelog:
- Added mainstream protocols
@amrutmhatre90
Thank you for being brave....![]()
Yes..
OK placed "proceed with caution" on page 1 since not still on their official website. And have this initial hiccup.
For FW 1.42 + Roon + Tidal go to this post instead HERE