WiiM Home App v3.2.8 Update – Jul 26, 2025

Please review the app update release notes below. If you encounter any issues, feel free to reach out to us.

App Release Version
v3.2.8

What's New:

1. Room Correction & EQ Integration: Room Correction and EQ now work together to enhance your listening experience (requires upcoming firmware). Learn More >
2. [iOS] TIDAL Enhancement: Alphabetical index support for quick access to artists, playlists, and albums when sorting by title.
3. EQ Status Display: View the EQ status directly on the playback screen.
4. [iOS] Instant Access: Tap on an album or artist name on the now-playing page for immediate access.
5. NAS Enhancement: Now supports viewing albums and artists in track options while browsing, and viewing the artist for composers on NAS.
6. Subwoofer Room Correction: Advanced Subwoofer Room Correction now supported for WiiM Sub Pro.
7. [iOS] Microphone Calibration File: Added iPhone and iPad calibration files to improve Room Correction accuracy.

Bug Fixes:

1. Amazon Music Login Fix: Resolved issue with logging into the incorrect account in the APAC region.

 

[KrimsonAudio]

We could really do with updated docs on Room Correction (now RoomFit) - Cut-Only Mode, Built-in Mic Compensation, how to use Moving Mic measurement, what does it mean RC and EQ working together, probably more...? Unless I missed it, couldn't find anything on these topics in the help?

I agree with your assessment, but I prefer they push out new features as soon as they are workable and let the documentation catch up. We don't want to see them push features back in time just for more documentation. They could do with a technical writing hire, but I sure don't want to pay for it haha!

@WiiM Team maybe you all could push out more documentation into these updates posts?

 

[harkpabst]

I agree with your assessment, but I prefer they push out new features as soon as they are workable and let the documentation catch up. We don't want to see them push features back in time just for more documentation. They could do with a technical writing hire, but I sure don't want to pay for it haha!

@WiiM Team maybe you all could push out more documentation into these updates posts?

Don't reference the agile manifest!

It will upset many seasoned developers and audiophiles.

 

[GregzzR]

Hello everyone,

Grégoire de France with installation in small room Focal Profile 918 speakers and little optimised Marantz pm35 amplifier.

Good sound with Qobuz connect!

What do you think of the new setting in the RoomFit menu: "attenuation only"?

Which ones do not increase the frequency but simply decrease these needs?

What do you think of these two results with the same settings except this feature?

Grand evening

 

[harkpabst]

Hello everyone,

Grégoire de France with installation in small room Focal Profile 918 speakers and little optimised Marantz pm35 amplifier.

Good sound with Qobuz connect!

What do you think of the new setting in the RoomFit menu: "attenuation only"?

Which ones do not increase the frequency but simply decrease these needs?

What do you think of these two results with the same settings except this feature?

Grand evening

Hi Grégoire,

In this case it is very obvious that the second RoomFit run provides much better results. The massive dips (in particular in the right channel between 50 Hz and 200 Hz) can be corrected for by applying positive gain. This proves that they are not caused by acoustic cancellation.

Did you allow a Max Gain value >0 dB in Cut-Only Mode?



I haven't tried Cut-Onle Mode with independent left and right RoomFit EQ yet.

 

[Wiimer]

Hi Grégoire,

In this case it is very obvious that the second RoomFit run provides much better results. The massive dips (in particular in the right channel between 50 Hz and 200 Hz) can be corrected for by applying positive gain. This proves that they are not caused by acoustic cancellation.

Did you allow a Max Gain value >0 dB in Cut-Only Mode?

View attachment 25058

I haven't tried Cut-Onle Mode with independent left and right RoomFit EQ yet.

Sorry, maybe I still don't understand Cut-Only Mode very well, but isn't this a function that enables only the negative gain and disables the positive gain?

Can you tell me why should turn on this mode and set the positive gain to 4 dB?

Thanks

 

[dominikz]

Sorry, maybe I still don't understand Cut-Only Mode very well, but isn't this a function that enables only the negative gain and disables the positive gain?

Can you tell me why should turn on this mode and set the positive gain to 4 dB?

Thanks

"Cut-only" name is a bit misleading, individual positive gain filters are still used, it's just that there's no positive gain in the total/summed filter response - see here for an example.

Another example:
The individual positive gain filters are just used to shape the response, but with Cut-only mode the final filter response always stays below 0dB.

 

[Wiimer]

"Cut-only" name is a bit misleading, individual positive gain filters are still used, it's just that there's no positive gain in the total/summed filter response - see here for an example.

Another example:View attachment 25059
The individual positive gain filters are just used to shape the response, but with Cut-only mode the final filter response always stays below 0dB.

Ah!
I understand perfectly.
Thank you so much

... As always, the team is good at picking names

 

[Wiimer]

@RyanWithWiiM, @WiiM Support, @WiiM Team,

'Cut-Only Mode' is proposed to be changed to 'Non-Boost Mode'.

Also, this description is a bit abstract and esoteric for me.
'Lets you lower frequencies, reducing room resonances and unwanted responses for a more balanced sound"

How about changing it like this?
'In this mode, the sum of each correction value does not exceed 0 dB. This prevents distortion and clipping caused by boosting'

This is debatable, but personally I find it easier to understand.

I hope you will consider this

 

[EddNog]

@RyanWithWiiM, @WiiM Support, @WiiM Team,

'Cut-Only Mode' is proposed to be changed to 'Non-Boost Mode'.

Also, this description is a bit abstract and esoteric for me.
'Lets you lower frequencies, reducing room resonances and unwanted responses for a more balanced sound"

How about changing it like this?
'In this mode, the sum of each correction value does not exceed 0 dB. This prevents distortion and clipping caused by boosting'

This is debatable, but personally I find it easier to understand.

I hope you will consider this

I 100% second this excellent recommendation!

-Ed

 

[pjorgenunes]

I 100% second this excellent recommendation!

-Ed

+1

 

[Smartplug]

Maybe they might change on next app update.

 

[slartibartfast]

That is a hell of a large aircraft flying under the radar!

-Ed

Just tried the cut only mode with independent channels and this was the final assessment.

 

[EddNog]

Just tried the cut only mode with independent channels and this was the final assessment.

View attachment 25064

The most transparent system response I have EVER seen!

-Ed

 

[WiiM Team]

Just tried the cut only mode with independent channels and this was the final assessment.

View attachment 25064

Hi @slartibartfast

Our engineers have identified the root cause: the calibration file path was changed in the new app version. We will address this issue and release an updated app as soon as possible.

 

[slartibartfast]

Hi @slartibartfast

Our engineers have identified the root cause: the calibration file path was changed in the new app version. We will address this issue and release an updated app as soon as possible.

I have to say I have no idea how the calibration file can affect the display of the final assessment. Also the calibration file was displayed on the screen before I performed the room correction.

 

[harkpabst]

I have to say I have no idea how the calibration file can affect the display of the final assessment. Also the calibration file was displayed on the screen before I performed the room correction.

View attachment 25071

All true.

But just delete the current file and import it again. It will solve the issue.

Ask me how I know.

 

[Wiimer]

If a calibration file is applied at the final stage of RC, an error occurs and the screen goes black because the file path has changed. Presumably, the mic file path displayed at the start of the RC is due to the cache.

(To be honest, I don't really know what I'm talking about...)

 

[slartibartfast]

All true.

But just delete the current file and import it again. It will solve the issue.

Ask me how I know.

How do you delete the original cal file?

Never mind. You have to be really accurate when you click on the i icon

 

[harkpabst]

How do you delete the original cal file?

Never mind. You have to be really accurate when you click on the i icon

Yep, I've been trying a couple of patterns that did not work before I hit that info button and found the delete button.

 

[harkpabst]

WHA 3.2.10 has been released to fix this issue.