Enhanced Room Correction is Here!

[pjorgenunes]

The primary difference lies in performance between the 20-50Hz bass range and frequencies above 16kHz. The updated Room Correction provides better measurement of the room's transfer function, leading to more accurate calibration. This is especially beneficial if you're using subwoofers or speakers with strong bass in those rooms. Additionally, the new Room Correction improves treble adjustment, making it more effective for those looking to fine-tune higher frequencies.

And for those who love spoilers:

We're also working on a couple more things for Room Correction for the future:
1. Integrating independent PEQ Room Correction with subwoofer, enabling automatic level matching between the main speakers and the subwoofer.
2. Enhancing Room Correction by using multiple measurements at one spot to eliminate environmental noise.

Great!

 

[Wiimer]

Hey Wiimer,
This is exactly an approach I am considering using. How are you setting and fixing the relative levels between the mains (Ultra) and the sub (Pro)? Adjusting pre-gain by ear? I assume you are happy with the results?

Hi @Hazenhart,

I have adjusted other settings so that the Ultra and Pro volume bars match.


Specifically, for Ultra, I only used volume limit. I did not use pre-gain.

I had a little trouble adjusting the volume on the Pro and the sub; I adjusted the volume knobs to balance the two subs and adjusted the low pass on each channel while measuring the microphones. After roughly adjusting with the sub's built-in low pass, I used the L/R PEQ.

Finally, I fine-tune the sound with my ears. I may also adjust the volume of the sub (Pro) according to my physical condition and volume that day.

Post #32 curve is with the two subs. (Crossover is 120Hz.)

I feel that my musical experience has never been better with the two subs. I am very happy with the current results, but I think there is room for it to get even better with some adjustments.

 

[Smartplug]

To those with iPhone, I’m getting erratic rc. Using bottom mic it only compensate below 4k. Using the back mic where the camera I get wide range to 16 to 18khz. Does anyone getting this?

 

[Smartplug]

If you're noticing any negative changes, can you please submit feedback through the app with all the details so we can get it in front of engineering quick?

Feedback was submitted.

 

[Smartplug]

Yes, but if the following corrections were made, I would only need to manually adjust one or two band. (In any case, the detailed correction is not performed.)
View attachment 13185

Try to held your phone higher and you will see that roll off go away at 4k.

 

[MCG555]

Try to held your phone higher and you will see that roll off go away at 4k.

I do not see why this should make a difference? Is it dependent where the tweeter is located?

 

[Smartplug]

I do not see why this should make a difference? Is it dependent where the tweeter is located?

The tweeter is at ear level. Both dome and ring radiator get roll off but raising the phone higher I get flat response with compensation on treble range. Phone pointing between the speaker at ear level would get reading rolling off at 4k but not so above my head. This was measured on iPhone 16 pro max. I also tried older iPhone 13 and was same thing.

 

[slartibartfast]

This sounds mad but I changed the correction range to 30-400Hz, lowered the crossover to 70Hz and boosted the sub to +15dB (previously it was +5dB) and the result was this. I'll leave it like that for a while and see how I like it.

 

[Smartplug]

This sounds mad but I changed the correction range to 30-400Hz, lowered the crossover to 70Hz and boosted the sub to +15dB (previously it was +5dB) and the result was this. I'll leave it like that for a while and see how I like it.
View attachment 13204

If you do full 20 to 20k with the right height the way you held your phone you will get nice flat response.

 

[slartibartfast]

If you do full 20 to 20k with the right height the way you held your phone you will get nice flat response.

I will try that as an alternative but it sounds pretty good just correcting up to 400Hz. But of course the iMM6 microphone will be inaccurate above 4kHz.

 

[shuppatsu]

Thanks for your constant efforts! I ABd the old and the new and subjectively the new is much better. The old one had a bit of boominess to it that the new one dispenses with. Both are far better than without RC.

 

[Smartplug]

I will try that as an alternative but it sounds pretty good just correcting up to 400Hz. But of course the iMM6 microphone will be inaccurate above 4kHz.

Would umik 1 connect on phone would yield superior accuracy?

 

[slartibartfast]

Would umik 1 connect on phone would yield superior accuracy?

If it is flatter without calibration file then yes.

 

[MCG555]

The tweeter is at ear level. Both dome and ring radiator get roll off but raising the phone higher I get flat response with compensation on treble range. Phone pointing between the speaker at ear level would get reading rolling off at 4k but not so above my head. This was measured on iPhone 16 pro max. I also tried older iPhone 13 and was same thing.

Strange… I always try to imagine why something happens. Here I have no idea why…

 

[ArthurStereo]

Yesterday until late at night I experimented with RC. I used different combinations: RC + iPhone mic, RC + iPhone + Dayton mic, HouseCurve + iPhone mic, Housecurve + iPhone + Dayton mic. I made a lot of measurements. I tried to keep my position the same, sometimes I held the phone higher or lower to check if there was a difference.
My conclusions in my conditions and equipment are that RC definitely works better after the update. The graphs are similar to HouseCurve + Dayton calibrated, but only at low frequencies up to 1 kHz. At higher frequencies there are significant differences and lack of repeatability.
Only HouseCurve + Dayton calibrated gave me a result of +/- 3 dB in the range of 24 -16000 Hz. RC + Dayton gives quite good results, RC + iPhone gives the worst. RC is more inaccurate despite several sweeps.
I keep repeating: to measure something, the input signal must be accurate and reliable. Otherwise, each of us can paste here graphs from RC, which do not mean much.
Wiim should first allow the use of calibration files. Then we can assess whether RC works well or not, the results will be more accurate, more repeatable. It will even be possible to consciously change the sound, if Wiim added target curve editing - this is my next conclusion.
But at the moment the results are inconsistent, so this can't be done.
These are just my conclusions, you don't have to agree with them. I'm sticking with HouseCurve + Dayton for now. But I'm a big supporter of Wiim and I'm waiting for more updates.

 

[MCG555]

Yesterday until late at night I experimented with RC. I used different combinations: RC + iPhone mic, RC + iPhone + Dayton mic, HouseCurve + iPhone mic, Housecurve + iPhone + Dayton mic. I made a lot of measurements. I tried to keep my position the same, sometimes I held the phone higher or lower to check if there was a difference.
My conclusions in my conditions and equipment are that RC definitely works better after the update. The graphs are similar to HouseCurve + Dayton calibrated, but only at low frequencies up to 1 kHz. At higher frequencies there are significant differences and lack of repeatability.
Only HouseCurve + Dayton calibrated gave me a result of +/- 3 dB in the range of 24 -16000 Hz. RC + Dayton gives quite good results, RC + iPhone gives the worst. RC is more inaccurate despite several sweeps.
I keep repeating: to measure something, the input signal must be accurate and reliable. Otherwise, each of us can paste here graphs from RC, which do not mean much.
Wiim should first allow the use of calibration files. Then we can assess whether RC works well or not, the results will be more accurate, more repeatable. It will even be possible to consciously change the sound, if Wiim added target curve editing - this is my next conclusion.
But at the moment the results are inconsistent, so this can't be done.
These are just my conclusions, you don't have to agree with them. I'm sticking with HouseCurve + Dayton for now. But I'm a big supporter of Wiim and I'm waiting for more updates.

For me the most important is the low frequency part, as I have modes in my room. If this is working even better now, perfect! I will be able to test next week…

 

[Smartplug]

@RyanWithWiim are you able to find bugs on beta? We’re counting on you to speed up the development!

 

[RyanWithWiim]

@RyanWithWiim are you able to find bugs on beta? We’re counting on you to speed up the development!

I can flag it with the team to check out. Most of them have had a few days off, so they're just getting back to checking this out.

 

[aguzz132]

@RyanWithWiim are you able to find bugs on beta? We’re counting on you to speed up the development!

Chill man

 

[steadyshot]

Ideas for RC from the release notes of HouseCurve

1. Use of shelve filter less corrections better results

2. Headroom calculation

3. Measurement sweep fades more gently to be kind to systems without infrasonic filters