Miska

No, you just have multiple configurations you can switch. That's perfectly fine to do.

When Direct SDM is active, only DSP you can perform is speaker delay processing. Everything else is disabled. If you have matrix processing enabled, Direct SDM is ignored apart from the locked volume control. Processing DSD256 -> DSD256 is with convolution or cross-feed is rather heavy operation, so in your case M1 runs out of steam doing that. It would need more processing power. In particular some operations can be slow on Apple silicon due to some hardware differences to Intel architecture. Please check that you have integrator set to for example FIR2. My M1Max 32GB can do DSD256 -> DSD256 with cross-feed without issues. But convolution at DSD256 is too much for it (of course always depends on the particular convolution filter though.

For the correct transient waveform shape yes. Are we now talking about fundamental of the transient, or something else? Since many transients don't have any fundamental frequency. I don't agree with that either. https://en.wikipedia.org/wiki/Ultrasonic_hearing In addition, it is too simplistic to view transient response from plain frequency response point of view. Limiting signal bandwidth to 20 kHz has much wider repercussions than just some disappearing frequency components. Do you hear any differences between any digital filters?

In playlist mode, HQPlayer is performing de-popping algorithm since the tracks are unrelated. This also means it is not completely gapless. In album mode it is assumed that that all the content belong together and are in correct order, and thus this is not needed and the playback can be completely gapless without the de-popping algorithm. So if you get pops in album mode, then you know those tracks have pop issues.

No, I certainly don't agree. No, I don't agree. For best transient reproduction we need at least 50 - 100 kHz bandwidth, depending on instruments. Real DSD256 recordings are best you can get these days, those have the least bandwidth limiting.

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