I just gave Roon + HQPlayer a test and so far I’m pretty impressed, but:
Sometimes HQPlayer gets confused and I have to try skipping/pausing/etc to get it to fire up again. Once playing, its buttery smooth, but the changes sometimes get it confused. Is this something that is being addressed for a smoother overall experience?
George @ Exasound indicated they will come out with a hardware DAC volume control similar to the JRiver plugin which syncs the DAC hardware volume with the software when the “Control API” is out. When is this API going to be released?
I’ll probably have more later, but so far positive first impressions. Now to hook up Tidal…
What changes are you making that confuse HQ Player ? You should be able to control playback from Roon without experiencing any disconnections (there were initial problems in that regard which have been fixed). If making changes to HQ Player filters etc. it is best to wait until HQ Player stops (as distinct from pauses) before bringing up settings etc.
The API is in the works, but no announcement has been made as to release. I suspect it is likely to be in the next major feature release (whether that is 1.3 or not), but that is pure speculation on my part.
I haven’t heard of Tidal streaming 96 kHz source files. Can you upload a screenshot showing the audio path in Roon ?
Closed form filter won’t play certain sample rates (I think the source has to be an exact multiple of 44.1 kHz), but in my experience it just doesn’t play those files rather than causing glitches. Try another filter and see if that makes a difference.
Do you have “Auto rate family” enabled in HQPlayer settings and rate drop-list set to “Auto” in HQPlayer main window? closed-form doesn’t allow upsampling to different base-rate, so the output sampling rate needs to be switched when necessary. e20 should support DSD256 with both 44.1 and 48 base rates (rate families).
Plain “Auto” as rate should be enough as such, then it’ll stick to highest rate that is equal or less than the set rate limit and is possible with the currently selected filter.
I do have Auto Rate family enabled. The dropdowns in HQplayer were forced to various settings for testing. I changed them back to auto (except closed-form on the left)
Still experiencing flaky behavior. This time with local 16/44.1 material. I tried changing zones but roon+HQplayer doesn’t handle that very well. Other general instability. Its not a very smooth experience I’ll be honest. Here’s an example where the HQplayer NAA crashed when I tried to change zones and I had to restart the NAA daemon. I had no idea it crashed.
This also meant having to restart HQplayer because reloading the NAA daemon wasnt sufficient. I had no way of knowing this. Not good.
[networkaudiod] (4764): Using ASIO default buffer size
[networkaudiod] (4764): Using ASIO buffer size: 8192
[networkaudiod] (4764): Latencies: 8192/24576
[networkaudiod] (4764): Not using ASIO output ready notifications
[networkaudiod] (4764): start failure: clASIOMiniEngine::StartAudioClient(): ASIOStart()
[networkaudiod] (4764): enter streaming mode
[networkaudiod] (4764): exception: clAlignedAlloc::SetSize(): lAllocSize < 0
You may not want to set output mode to auto, because then it’ll start switching between PCM and DSD output modes. Just the sampling rate.
This error is from the ASIO driver (failed to start playback) and rest of the errors are result of the earlier failure. networkaudiod may exit if it encounters unrecoverable error, it doesn’t mean it crashes.
If you can email me your exported settings, log file from start to a crash and exact steps how to reproduce the crash, it would help a lot finding where the problem is and fixing it.
Here are my exported settings when it crashed. I can’t give you steps to reproduce, I was just browsing a combination of tidal and local (nas) music. I was also swapping roon between exsound direct, and via hqplayer. I usually pause the first stream, but not always. It could be related.
Found another issue. skipping tracks in tidal doesn’t always play (unrelated to the issue mentioned above which I havent been able to reproduce yet). About 1 in 10 “next” starts looks like it is starting to play but doesn’t.
Here is what happens:
the audio of the currently playing song stops
according to the gui its playing the next song (I see the animation)
according to hqplayer the stream is still going (the drop downs are all greyed out)
no cpu activity on the hqplayer machine, and no audio.
If I pause, I will hear audio as if the state is backwards… but then stops a few seonds later as the buffer runs out
Here’s a good example. If I play from Tidal (season 2 episode 3, glass animals) using Exasound direct, it works just fine. However, if I use HQPlayer streaming DSD256 to my DAC I get dropouts exactly at the same spots… my USB connection light is going crazy and I hear audio dropouts as if the buffer is running out on the DAC.
This is all on the same network. I tried increasing HQPlayer buffer to 100 and 250 but it drops out at the same spot.
Any ideas? This is poly-sinc-2s, DSD5v2 256+fs. cpu usage on that machine is 20-30% while HQPlayer is playing. I have auto rate family and pipeline SDM enabled
Update: seems to be really program material dependant. Some songs work fine, while this glass animals song drops out in exactly the same spots.
Yes - sounds very frustrating - Apologies if I sounded dismissive in my last post - I have been playing with HQ player settings for a couple of weeks - I have been trying the same with DSD 256 files via Roon/ HQ Player - and have tried a matrix of settings for a smooth output (see my other post which shows the settings I have settled on for my Devialet) - I can’t seem to get a smooth output via HQ Player. The problem is that the HQ Player guide is not as clear for a “man on the street” to understand in terms of what are the optimum settings - I have sent an email to Signalyst for guidance - waiting to hear back. For now I am simply using Roon direct to Devialet via AIR protocol - the SQ is pretty good, including playing back DSD 128 which is processed by Roon at 176k.
Well I just purchased HQPlayer, so I hope there is a fix for this, otherwise I will have to consider cancelling that purchase until this matures
More info - its definitely program specific as it happens in exactly the same spot. Doesn’t matter i its DSD256 or DSD128. It sounds like a bug in HQplayer.
Another update: Only happens with upscaling PCM to DSD. PCM upscaled doesn’t have this issue.
Could it have anything to do with handling silent passages?
Thats both of us purchasing HQ player - so I do share your sentiments.
No issues for with various PCM audio and DSD 64 files/ streams. PCM upscaling for TIDAL works fine for me - except I cannot see any SQ benefits as compared to straight Roon/ Devialet via AIR - the Dev up samples TIDAl to 192 k in its DAC - perhaps HQ Player cannot add any more to SQ here. This was mentioned to me by another Dev owner at this forum.
With DSD 128 - I do experience clicks in the playback - at first I thought it was my AIR protocol with DEV (as widely reported here and other internet chat forums) - but I eliminated that by doing tests without HQ Player etc - and tested different scenarios with and without HQ Player - suffice to say I am pretty sure its not AIR as it has not played up once with Roon/ Dev. I did the test with USB and the HQ player provided the same issue on playback of DSD 128 files. I am hoping its the settings on the HQ player and like you am looking for a resolution.
I apologize about my snarky comment questioning HQPlayer maturity. I agree it was uncalled for.
I also have verified this is not an HQPlayer (only) problem. I do not encounter any issues (so far) playing back lots of local pcm files in HQPlayer’s interface (no roon).
The issue appears to be either entirely roon, or a roon/HQPlayer integration issue.