hmscott
1000+ Head-Fier
Interesting. You think 384k/352.8k is wrong?
In UAPP if we set up bit perfect + paid the MQA in app fee, and with the M11 / M15 recent 0604 update UAPP is able to do the complete unfold - not just the 1st but the full unfold - which will show as 352.8k or 384k, it's broken?, or it's working better?
Perhaps that's just a way for FiiO to indicate that the full unfold is happening?
That's why I posted here my experience with the M15 0604 upgrade + UAPP streaming Tidal, I hoped the M11 Pro / M11 could also experience the same MQA improvement.
That looks like Tidal - so I went and updated my M15's Tidal, but I'm still only showing 88.2k.
I'm getting 384k in UAPP streaming Tidal witih bitperfect enabled, but not in even the updated Tidal...
Is there another setting in the Android Tidal app I need to set, or set in my Tidal account through my PC's Tidal app?
Sorry, I had to look it up - MQA is new to me - it turns out that 384k output of a full unfolding MQA renderer isn't even the highest possible, that being 768k:Tidal company needs to fix app compatible with Android 7.Now is playing 16bit, so I think Fiio gave us this beta firmware to polish it before all will be definitely ready from both sides. So everyone, trie to post as many bugs you can so they can sort this out fast and we will be able to use the final release.
From: MQA Playback
http://bobtalks.co.uk/blog/science-mqa/mqa-playback/
Q4. What are advantages of an MQA Renderer?
- An MQA Renderer can provide a low-cost or lightweight upgrade for playback of music encoded in MQA.
- Some Class I USB devices can only receive 96 kHz audio. In these cases, a Renderer is able to take in the MQA Core and complete the unfolding up to 384 or even 768 kHz internally.
Update: In this case it's unknown to us - so far - as to why FiiO is display 385k / 352.8khz instead of the source sample rate.
Last edited: