Completed Automatic timing alignment for Main Speakers and Subwoofer

[BK308]

Everything seemed to be working well on my end here too. I don’t this feature is on beta anymore. IOS app is updated as well.

 

[slartibartfast]

Everything seemed to be working well on my end here too. I don’t this feature is on beta anymore. IOS app is updated as well.

That is the beta firmware isn't it?

 

[BK308]

Initially it said beta in parentheses. I did a reboot and checked for a software update and it started working. The parentheses went away idk

 

[slartibartfast]

Initially it said beta in parentheses. I did a reboot and checked for a software update and it started working. The parentheses went away idk

Mine never had beta in parentheses. That definitely isn't official firmware the release date is 23 October.

 

[BK308]

I think you are correct. It gets confusing because the app updated and the feature showed up and it’s working for me. There’s no mention of beta anywhere so I assumed the feature ready for prime time. WiiM has made this a little confusing

 

[RyanWithWiim]

Hi everyone, thanks for testing! As @Smartplug indicated, this just went live with the update rolling out as of November 5th. You'll also need app version 2.12.2+ for this to work.

 

[Smartplug]

I hope before the end of this year independent peq rc and auto level will be out on public release. If not, I’m also interested on simultaneous usb with sub.

 

[pjorgenunes]

I hope before the end of this year independent peq rc and auto level will be out on public release. If not, I’m also interested on simultaneous usb with sub.

Two features I'm waiting the most, along with replaygain metadata support on local files

My Two very nice to have are:
- Playback screen independent for each input
- Some more vu-meters...

 

[Smartplug]

Auto timing works as advertised. I had trouble getting the right dial now it sync seamlessly. Thanks @WiiM Team @WiiM Support

 

[sNc]

Will this auto-sync speakers with subwoofer help me in any way?

L - left
R - Right
S - Subwoofer
1 - Main listening position
2 - Second listening position (when working at the desk)

It might seem that the sound would be tragic from the side of the speakers, but it is not at all

 

[Mr Ee]

It might seem that the sound would be tragic from the side of the speakers

I was just thinking that, and that it'd be a good excuse for a decent headphone setup or a smaller 2nd system
Go on... you know you want to!

 

[sNc]

I already have there standalone PC with DX7 Pro and HD 660s

 

[pieterv1]

I remember reading a review a while back about the WiiM Ultra, hooked up as preamp directly to a poweramp. When the guy found the sync feature (I believe to sync with other WiiM devices), the sync signal blasted through his speakers at full volume.

Seems like this speaker measurement feature is a bit of the same sort of measurement, between individual speakers... I hope the volume issue has already been adressed?

 

[s3igell]

Here are a couple of speed and measurement facts to digest while considering the treatment of subwoofer latency:

1. Sound travels at 1.13ft/millisecond - indicating that latencies within the low milliseconds range that WiiM addresses are well within the dimensions of a normal listening environment
2. Peak-to-peak distance of sound at 60hz is 18.83ft - meaning that the wavelength of Subwoofer output rarely fits within a listening room
3. Human Ears usually first detect latencies at about 5-10milliseconds - trained ears can do much better when specific notes are overlaid

 

[pjorgenunes]

Here are a couple of speed and measurement facts to digest while considering the treatment of subwoofer latency:

1. Sound travels at 1.13ft/millisecond - indicating that latencies within the low milliseconds range that WiiM addresses are well within the dimensions of a normal listening environment
2. Peak-to-peak distance of sound at 60hz is 18.83ft - meaning that the wavelength of Subwoofer output rarely fits within a listening room
3. Human Ears usually first detect latencies at about 5-10milliseconds - trained ears can do much better when specific notes are overlaid

I used to have a Denon 4306 (that measure distances) and, although my sub distance compared with main speakers was only +20% more distance, it calculated distances like: 3m for main speakers, almost 8m for sub. I remember reading about that and the apparent greater distance had to do with the fact that many SUBs have DSPs which add more latency (like if they where further away).
I remember that then I had the best timing integration between Main Speakers an SUB.

 

[Smartplug]

Do you run auto timing first before rc or doesn’t matter?

 

[MrA]

Do you run auto timing first before rc or doesn’t matter?

I have always applied time correction prior to any room correction. However the setup I use is rather complex, using outdoor 'anechoic' measurements for time alignment of all individual speaker (driver)s and subs, then alignment between all of these at the listening position followed by room correction with lower bass frequencies only (the room is acoustically treated including corner bass traps so very little RC is required)

 

[Smartplug]

I have always applied time correction prior to any room correction. However the setup I use is rather complex, using outdoor 'anechoic' measurements for time alignment of all individual speaker (driver)s and subs, then alignment between all of these at the listening position followed by room correction with lower bass frequencies only (the room is acoustically treated including corner bass traps so very little RC is required)

What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?

 

[MrA]

What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?

This should be addressed directly to WiiM.

 

[slartibartfast]

What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?

I always got 8ms unless I moved the sub.