Surprising as WiiM have not released MQA unfolding from the WiiM app, just via Tidal Connect as stated…Not realy. I was listening on wiim home app and it was working OK (my Yamaha was showing 96kHz from a file that in wiim home app was 48kHz).
WiiM Home app would show 96 kHz for unfolded 48 kHz content as it does show when Tidal Connect is used.Not realy. I was listening on wiim home app and it was working OK (my Yamaha was showing 96kHz from a file that in wiim home app was 48kHz).
You were correct. From WiiM support. "Your DAC only supports render only and now we don't support the MQA option for that. We will update our app to support it.Thought I'd post something that *might* be useful...
As noted, the options in WHA have changed.
Seems to me there are just 3 combinations now.
1. Mqa beta: off
2. Mqa beta: on, mqa capabilities: no mqa
3. Mqa beta: on, mqa capabilities: mqa
Maybe wiim need to clarify exactly what each combination does.
But here's one possible, hopefully logical, answer.
1. If everything else is set up to allow bit perfect, then surely this would mean an mqa-able signal is going to the dac? i.e. if the dac is a decoder, or decoder and renderer, then it could do so with this signal?
2. Wiim does the first unfold (decode), and that's it. Post processing, such as EQ, could still be done before output.
3. Choosing this says it will change the settings to enable bit perfect, except for max output resolution. The only thing that makes sense to me is that this is effectively stating that the dac is a renderer, so wiim does a decode and it automatically sets up the other settings to present that as bit perfect to the dac, i.e. no post processing.
Now, if only I leant the other way and had Tidal hifi plus to test any of this...
Interesting. If so I have no idea what the combination "mqa - on, dac - mqa capable" was supposed to do.You were correct. From WiiM support. "Your DAC only supports render only and now we don't support the MQA option for that. We will update our app to support it.
Meanwhile, please select the NO MQA to workaround this issue because our device will unfold the MQA file first and then your DAC can unfold the MQA file twice. Please tell us if this works for you." IT DID!
WiiM support said:First unfold in wiim, second in DAC?
Not sure myself. Just glad it was resolved.Interesting. If so I have no idea what the combination "mqa - on, dac - mqa capable" was supposed to do.
I'd assume it's like automating my option (1), simply setting up the wiim to allow a bit perfect signal to go to a decoder or decoder/renderer dac.Interesting. If so I have no idea what the combination "mqa - on, dac - mqa capable" was supposed to do.
Why are you not using tidal connect? Curious, as it works perfectly fine with me. Also I like the native app more than custom 3rd party in general.Can only confirm. I just checked and mqa unfolding is working only when playing on tidal app. What a mess...
It looses wiim on my smartphone. Must restart phone or on/off plane mode to bring it back alive...Why are you not using tidal connect? Curious, as it works perfectly fine with me. Also I like the native app more than custom 3rd party in general.
iirc, you couldn't cast from Amazon either.It looses wiim on my smartphone. Must restart phone or on/off plane mode to bring it back alive...
You could go back (forward?) to the new app again now, although the old one's options are certainly simpler.I would therefore assume the App update has caused these issues then?
The old App I downloaded has these options
![]()