Miska

Some testing results from today, for those who seek to build lower TDP servers for HQPlayer. My i9-13900T with DDR5-6400 CL32 memory can do DSD1024 with ASDM7EC-light when E-cores are set to filter. While i9-14900K can do the same with ASDM7EC-super. Both cases without GPU's help. So the E-cores offload helps quite a bit this case, since it enables the T-model to reach DSD1024.

Strange, because single tap has been working for me. Auto play is not related to this, it is a feature to let Qobuz automatically continue playing similar music when end of your current queue is reached. I'm using Client on Microsoft Surface tablet with Windows 11. And with iPad. I also have a Linux laptop with touchscreen. This is shown in the album view (cover flow)? I have personally added the version to the album title in HQPlayer's library database. Since I also have for example four or five different versions of Pink Floyd's Dark Side of the Moon album. OK, something I've never used... 😅

It is just a totally different DAC used that way. I would say quite far. And it is totally different especially with PCM inputs, because it has only a single DAC inside. It is a discrete SDM DAC and yes it has DSD direct.

Uhm where is this? Now it's at https://signalyst.com/quickstart-guide/ Double-click/double-tap it. This already happens? Then we cannot show you up to date list of available devices. This doesn't work on this like iPad or touch interfaces in general. But it is explained in the manual. HQPlayer cannot present you the output rate and PCM/SDM options if it is unable to access the DAC and figure out what it supports. This is intentionally not there... You can opt-in for such things by subscribing on Twitter or Facebook. Standard multimedia keys are already supported. Plus the alternatives. This is already there? There is no persistent connection to Qobuz, so I'm not sure what this means?

It says Intel ARC graphics, so integrated graphics in the CPU. So no CUDA offload. Technically it would be possible to run some offload on that GPU too.

Yeah, my thought too. That would keep it 100% loaded all the time. So HQPlayer is kind of easy case. Yes, certainly interesting one for use on the go. I need to check availability and pricing locally. Would be fun to try out!

I use both DAC 200 and HA 200. HA 200 with the Solitaire P headphones is my current primary development setup. DAC 200 is in my livingroom loudspeaker setup. I consider both the technical performance and the sound to be perfect combination for me, in these setups. I also use bunch of Holo Audio DACs as well. It is fine, but I never use it myself. I have DAC 200 and HA 200 directly connected to my servers, but through Intona USB isolator which is essential component here too. If I would have to choose a NAA for it, without Intona, Out of the ones I have, I would take Holo Red. You want a DAC with built-in oversampling? Or one that can use HQPlayer as external one? I personally don't want to pay for built-in DSP, so rather without built-in one. But around that price bracket, Holo May is worth checking out too. But you really should give these a listen yourself, as these are quite different and system / preference matching is important aspect too.

Looks kind of potentially interesting all-in-one device for running HQPlayer Deskop + HQPlayer Client for travel purposes or such. That small display may be challenging with the HQPlayer Client design though (using touch). I just wonder how the thermal management and battery life will be. But if one does something lighter on it, it could be even decently nice mobile player / DAP.

240 is playlist transport. You can also set it to audio transport for device input, instead of routing through a playlist. Playlist itself can operate as a playlist, and as a queue, or a mixed playlist & queue.

Please see the Transport enumeration in ControlInterface.hpp

SD cards are much slower than some high performance USB memory sticks. Since microSD can have very limited power consumption and thermal production. This means booting is slower. But so is also any power consumption and noise. In most cases the boot time is not critical factor for this use case.

You can safely ignore that unless you want to use the integrated motherboard audio (likely not).

There's now a fresh Ubuntu build of 5.5.3 available. Please give it a try and let me know. Now you can switch between PCM/SDM on the fly from Client, as well as switch output rates on the fly as well. I cannot reproduce the issue with this build and T+A HA200 as a DAC. Not so sure about the E30. It could be just a firmware issue... It sounds like one and what I tested it seems to be rather randomly happening (or I just didn't find the logic).

There are all kinds of strange bugs in these XMOS firmwares. Like iFi micro iDSD, if you power it up and start straight with 705.6/768k PCM, sound is loud and distorted. If you play any other format first, like 352.8/384k or DSD and then play 705.6/768k PCM it is fine. While, IIRC, on SMSL M400, if you play any other format after plugging in the USB, then 705.6/768k doesn't work correctly anymore (with this one I worked around the issue by using Holo Red's I2S output). So these kind of things have to be always tested with multiple different DACs before it is clear where the problem is...

I think the reason is that the XMOS controller or the DAC chip gets confused and misbehaves if the stop - switch mode - start cycle is too quick.