Newbie trying speaker placement and roomfit - looking for guidance

[dominikz]

I ran it and it gave 3ms, phase is 180, crossover 70

Nice, the fact that you get lower delay estimates with phase set to 180° compared to 0° IMHO confirms that setting sub phase to 180° was the right decision.

I will try these next. Let me know if the right sequence of steps to do roomfit after crossover changes are as below:

1. Change crossover value
2. Keep the phase as same (180)
3. Run sub sync (auto) to set the delay
4. Run roomfit

That looks correct to me, yes.
Though you could also omit step 3 and just keep delay at 0ms or use the 3ms delay value which the auto function suggested.
As I will explain next, there are still limitations to the auto sync function.

I also wonder if the speaker latency of 7ms is correct. My device is placed like below and speakers are on either side of the wooden unit so anything above 3ms should be processing latency?

View attachment 33798

Let me start by saying that WiiM automatic delay estimation function is not 100% accurate, at least not yet - so honestly I wouldn't put too much faith into it.

The main limiting factor is the fact that the auto sync function uses the microphone built into the WiiM device.
This means that the it measures the time-of-arrival delays at the position where the WiiM device sits, rather than at your listening position (which is what it should measure). The current approach (with WiiM device mic) can give a rough estimate of the delays (especially when a lot of processing delay is added by the sub or the speakers), but it won't be 100% accurate in most cases.

Luckily, this limitation is already being worked on - latest WiiM Home app already implemented support to use the mobile device microphone instead of the WiiM device microphone (see release notes), so now we're just waiting on a device firmware update to be able to actually use it:

3.4.12
Release date:
Jan 26th, 2026
Beta Features
1. Sync Main Speakers & Sub: Align main speakers and subwoofer for the listening position using the phone’s microphone (requires an upcoming beta firmware update).

Next, while the WiiM device will estimate individual delays for both the speakers and the sub, we don't really know what is its own timing reference.
Luckily the absolute delay values aren't really important - we're only really interested about the *delay difference* between the speaker and the sub to be able to sync them. In the screenshot you pasted this difference is +3ms on the sub, so the auto sync function adds 3ms delay to the main speakers to compensate.

Based on the system layout you described (and your sub model) I'd actually expect 1-2ms delay would be needed on the speakers for perfect sync, while the function estimated 3ms - which is not that far off!
We'll see if the auto delay estimation changes once the improvement to the auto sync function is fully implemented by WiiM.

 

[satheesht]

Based on the system layout you described (and your sub model) I'd actually expect 1-2ms delay would be needed on the speakers for perfect sync, while the function estimated 3ms - which is not that far off!

Thank you for the explanation. With phase as 0 earlier, the delay values were identified by WiiM as 7ms for speaker and 15ms for sub for arriving at delay of 8ms to be applied. The speaker delay values are consistent across measurements as 7ms. But I understood from previous replies that 8ms delay (distance difference from speaker + processing) for sub was considered high/abnormal, so I was wondering if the delay of passive speakers being 7ms was accurate (3ms can be attributed to physical distance from speaker to wiim and remaining should be processing). I wanted to rule out WiiM being placed in sort of a partial enclosure may be skewing it somehow.

That looks correct to me, yes.
Though you could also omit step 3 and just keep delay at 0ms or use the 3ms delay value which the auto function suggested

I will keep the phase 180 and 3ms delay as the baseline going forward. When I get some time will get the roomfit done again for MMC and also check the sweep results for other crossover values.

Thank you.