Hi I use an Astell & Kern HC3 usb-c dac with my iPhone 15 Pro Max and can confirm it works brilliantly.

Hi I use the R6Pro with my Etymotic ER3-XR when travelling, but at home I use the R6Pro with my HD660s over a balanced connection, and they sound absolutely fantastic. Never have to have the volume high, the amp in the R6Pro drives them perfectly. Hope that helps - let me know if you have any...

I emailed HiBy and asked specifically if there was hardware in the R6Pro to unfold, but their answer was a little vague: “In the latest firmware version(1.86G) of HiBy R6 Pro, we've added MQA support in HiBy Music app and systemwide MQA decoding (Highest level 8x unfold).” I have replied...

I can’t say it’s a bug, it might be intended that the R6Pro doesn’t decode fully when it detects the headphones aren’t plugged in, for all I know. Unlikely I know. :wink: And firmware could have activated dormant hardware.... Even more unlikely, I know. But as I say, wild optimism.... I...

It’s quite confusing. The same tracks that showed 384K (and yellow LED) before the Tidal upgrade, then showed 96K (and green LED) are now back to saying 384K (yellow LED) again, but I have found out why. When you test play an MQA without headphones, it plays at 96K, plugin headphones and it...

So... I upgraded Tidal from the Play store, and now, my MQA tracks (such as the one above) show 96K when they play. The side button now lights up in green when playing MQA files (which I believe is correct for 96K), whereas previously it lit up yellow (which I believe is correct for the 384K...

I'm not sure what's happening - has anyone else seen this, or can anyone explain. If 192K is the maximum from Tidal, how is my R6Pro showing twice that, as below?

It definitely works - i just updated on wireless, version shows as 3.18.71-perf, Mon Apr 20 17:29:39, build 1.86G, and I see the same track in proper MQA at 384K.