No, that’s all. They have decided not to really pass any version information over.
I’m putting a Zidoo forum post together but as I’m more active here I thought I’d start by trying to summarize the bugs… Please let me know if I’m missing anything or maybe something I’m experiencing has already been solved. I’m < 24 hours with this thing.
I picked up a T10 with the intention of making it my everything box. My primary signal path is Roon → HQPlayer → NAA → Intona → DAC200
I’m sending DSD512 to the T10
Bugs:
- No DAC ID passed back preventing DAC Correction from happening.
- Random skips / time jumps / repeats.
- Menus on USB support DSD1024 but reported NAA output maxes at output network format: 22579200/1/2 [dsd]
- No DSDx48 support.
- The VU meters keep dancing long after the music has stopped.
- Help me better understand the x48 issue please
My favorite setting is auto rate family so I don’t need to jump rate families. The DAC200 supports this without issue. Why a streamer cannot pass this is just confusing to me. However, my problem is deeper than just turning this off. Without this setting I’m locked out of a lot of filters that I used to use? To me, this lack of x48 is making rethink my purchase.
Not being able to do x48 with DSD is new to me so I’m assuming anything in the manual with a ratio of 2x or integer is off limits? Or am I reading this incorrectly?
No suitable output rate for 96000, stop
Anyone know if this is a software issue that could be fixed or a hardware issue? I’m guessing software. I hope it’s software. I’ll be opening bug reports.
Thanks!
In the manual filter table you can find supported conversion factors for each filter. So look for filters where the possible conversion factor is “Any” or “Any up”.
Then make sure “48k DSD” is disabled (likely not necessary in this case) as well as “Adaptive rate”. And then set output rate request/limit to a multiple of 44.1k.
1 Like
Hi @ipeverywhere ,
I asked the question of a knowledgeable forum member in their forums and I got this..
@Daniel Beyer aka Rugby, your friend is right about the older firmware, and it was the T10, not the May.
I run a May KTE with both a Holo Red (Signalyst NAA image, USB) and a T10 in NAA mode (I2S) on the same HQPlayer 5.17.2 instance. Same DAC, same server, same filters.
Red to May over USB: 48k-family DSD has always worked. DSD256 at 12.288 MHz, Auto rate family on.
T10 NAA to May over I2S: on the firmware I originally tested (1.1.55), the T10’s NAA client advertised 44.1k-family DSD only. 48k DSD checked plus bit rate Auto failed negotiation, and the workaround was a fixed bit rate of 11289600 with 48k DSD unchecked. That is fixed as of 1.1.60. 48k DSD on, Auto rate family on, and 96k and 192k sources go out at 12.288 MHz DSD256 with the T10 display confirming it. Current release is 1.1.80. Tell your friend to update, then re-enable 48k DSD and set bit rate back to Auto in HQPlayer, because the workaround settings will keep him pinned to the 44.1k family even after the fix. If he is current and it still fails, post the exact HQPlayer output settings, because it works here.
So the DAC, its clocks, the server, the software, and now the streamer all do it. The rate list the T10 hands HQPlayer was the only thing in the chain that did not, and Eversolo fixed it in firmware. That is the right outcome for a product marketed as an NAA endpoint: pass the DAC’s real capabilities through, same as a Pi running the NAA image does.
@Nutul, you are arguing against a claim nobody made.
48k DSD is not about half a megahertz more. Nobody is listening for 12.288 vs 11.2896 MHz. It is about the ratio. A 96k or 192k source modulated to a 44.1k-family DSD rate has a 160:147 rational resample stacked ahead of the sigma-delta stage. The same source to a 48k-family rate is a clean power-of-two integer oversample. HQPlayer’s entire reason for existing is choosing that math deliberately, and Auto rate family exists so every track stays in its own family. Forcing one family onto everything is the compromise, not the feature.
On “useless, mostly unsupported”: it is not a format, it is a rate. Any DAC that plays 48k PCM already has a 24.576 MHz clock on the board. The May has it, a sub-$100 Pi feeds it, most XMOS and Amanero USB receivers accept it, and Eversolo just shipped support for it on the T10. Disc standards are irrelevant here because nothing in this chain is a disc; upsampled DSD from a PCM source owes nothing to the SACD rate. (Incidentally, SACD is Scarlet Book. Purple Book is DDCD.)
The incompatibility you are describing was one streamer’s NAA implementation declining to advertise a rate its own I2S output could carry. It got reported, and it got fixed. That is how this thread is supposed to work.
For what it is worth, the DSD256 path is not an academic exercise here. Feeding the May a DSD256 stream from HQPlayer, in NOS, with the modulator and filter choices made upstream, is the best my system has sounded. The May runs a separate resistor ladder purpose-built for 1-bit, so the DSD stream hits analog without a PCM transcode, and NOS means the DAC is not re-processing a signal that HQPlayer has already shaped. The result for me is a lower noise floor between notes, less grain on strings and cymbals, and a soundstage that holds its depth at low levels instead of collapsing. I will not pretend that is a measurement. It is what I hear in my room, on my chain, over months, and it is why 48k-family support matters: I want every source getting the same clean integer path to that ladder, not most of them.
Original post link.. Feature request (T10 / NAA mode): USB DAC identity passthrough for HQPlayer DAC Correction, plus a l | Zidoo forum
1 Like
It is worth noting though, that not all DACs support this (most don’t), so caution should be used when enabling “48k DSD” from HQPlayer side.
Many DACs using stock XMOS code will play 48k-base DSD inputs using 44.1k-base clock. Which causes about 10% slow down and pitch shift. This includes for example first generation Holo Spring (was fixed from Spring 2 onwards), and from newer devices for example SMSL D200. Some other devices just go silent.
So this functionality needs to be confirmed by measurements for each DAC model to make sure it works correctly, before attempting to use it.
NAA shouldn’t be doing this rate filtering though, it is HQPlayer’s side to do it, based on the “48k DSD” setting.
I enabled the beta firmware this past weekend and am now on 1.1.90 with no change in 48k behavior as I get the same response of supported rates from the eversolo so something is a miss here. I’ll keep looking, thank you for the response. I’ll follow that post and upload my settings…
Are you using I2S? If not, try it and see if there is a difference.
With I2S it is at least more likely to work correctly on various DACs (except possibly ESS based), since the clock is selected/provided by the source and not by the DAC.
No I2S on DAC200. But, this needs to work on USB into the DAC200 please 
I can try it on another DAC I have once that comes back home as it’s at another place living its best life on another system right now.
1 Like