120 albums on tidal (1480 tracks) - no locally stored files
Description of Issue
I browsed the forum and came across an old issue similar to my experience:
(Click and pops when changing songs). That case is marked is closed with the remark it seems fixed. My issue is; when skipping from one MQA track to another, clearly audible pops/clicks occur. It does not occur when playing just FLAC files. The issue isn’t there when just using the BluOS app via Tidal, so I asume it is Roon related!?
Not official support, just a friendly fellow user trying to be helpful.
Tthe user had corrected his issue with adding a -3 db headroom management.
Assuming it is not that:
try disabling all processing by the Core, even MQA processing, and just sending the raw file to the endpoint.
then, keeping those settings if the issue continues, I would try, setting your output to the laptop speakers and see if the pops clicks continue.
After that, I would try putting the laptop and the endpoint on ethernet and not Wifi, Reasons below
Having the core on Wifi can be problematic. Roon works by streaming the track to the Core, processing it to PCM (which is a larger stream), and then sending it back out to the endpoint. So, if the endpoint is not the laptop, then you are using the same wifi hop to get music in and out, which can cause issues.
thanks for reaching our as a community member - appreciate it.
I’ve tried using a wired connection and also to not let core do any MQA processing.
When skipping a track in a playlist of MQA tracks I still hear these clicks pops.
I can’t tell if it is an issue with the endpoint SW, which is a NAD C658.
would official support normally pick up an isshe posted here, you’d think?
Yep when changing away from the C658 just using a pair of cans connected to the Core PC then I hear no clicks when skipping in an MQA play list if that is the scenario you’re proposing. (I also tried to disable the cross feed filter I have when using headphones - no clicks via cans, either)
Well, then, it suggests the issue is with the NAD audio chain. At this point, going back to the NAD, if you remove the crossfed and having Roon do the first stage MQA decode and setting the NAD to NOT do the render step, do you get the clicks?
ok - thanks for the suggestoin. i’ve tried, but no matter what i set up the signal path always shows the NAD as full decoder. I don’t know how to change that - the drop down decoder capabilites seem to not change it and not the switch for letting core doing the first step - perhaps I’m missing something here?
Hi again Daniel, sorry you got dragged into this, but you asked earlier if there were differences when using the NAD as full decoder or just as renderer. I cant choose that manually, but when using cans and activating that cross feed, I think I get the scenario you was were asking about, and when that filter is applied and the NAD is only rendering the click/pops are not there anymore? The signal path look in the two scenarios like the the below…
I would have sworn my first test changing render/decoder settings in Roon did not make any difference. Anyhow - I can now conclude when the NAD is just rendering, the clicks/pops are not there at all when skipping or backing between tracks! …Now i don’t know if there is any down sides with this split, where Roon decodes and the NAD is only rendering - technically the NAD should do both with out the annoying popping, and when using the BluOS app there are no clicking/pop, so I’d still think this is a Roon related issue somehow, which is also why i’ve mailed the support direcly for their postion on it… Thank you for all the kind support and nice chat we’ve had on it… I wouln’t have come up with this idea to work around myself, honestly …
We’re happy to see that the wonderful and talented @Rugby was able to steer you through your troubles. We’re glad that things are working for you now! Please feel free to reach out if you ever have any other questions or issues. Happy listening