Room correction

[Burnside]

Shame the developers can't be bothered to port it over to Android.

I don’t think it’s a case of not being bothered but not having the time - I think it’s a one man band

 

[slartibartfast]

I don’t think it’s a case of not being bothered but not having the time - I think it’s a one man band

True but with no competition it would be a worthwhile revenue stream.

 

[ArthurStereo]

Maybe because they think only iPhone microphones are suitable for measurements? HouseCurve supports all iPhone microphones with additional compensation. You may not like Apple, but their devices have many advantages. That's why I use them. If I used Android, I wouldn't find such an application. And now I'll stick with Apple just because of it

 

[slartibartfast]

Maybe because they think only iPhone microphones are suitable for measurements? HouseCurve supports all iPhone microphones with additional compensation. You may not like Apple, but their devices have many advantages. That's why I use them. If I used Android, I wouldn't find such an application. And now I'll stick with Apple just because of it

It supports external mics as well though.

 

[ArthurStereo]

Of course. It also supports external microphones and .cal files. I already wrote about it and even pasted a photo of my iPhone and Dayton IMM-6C.
I use them to make measurements.

 

[Smartplug]

True but with no competition it would be a worthwhile revenue stream.

True having both platforms will get this person more money for those who willing to pay. Other reason maybe this person realize the mic built on android are inconsistent that could produce erratic result.

 

[MCG555]

I like the solution in HouseCurve. First, a measurement is made. The graph is visible. Then, in the Equalize tab, you can change all the correction parameters and watch the correction and simulation graphs of the final effect on an ongoing basis. Only then can you save them.
I transfer the PEQ to RC and measure again on HouseCurve.
Such solutions in RC Wiim would be great.

That‘s all fantastic!
However, do you hear a „big“ difference?
I tried around a lot with RC. Now, if I put some gain e.g. +3dB at 200Hz or at 250Hz I do not hear a difference in the music.

People are saying, we need not 10, but 20 correction point settings in PEQ. Why not 200? Honstly - for me what counts is a hearable difference in the music and in the room.
If I use all 10 settings from 20Hz to 400Hz it sounds „the same“ as if I use 6 and intrapolate the measurements inbetween optically.

We can discuss - and it‘s fun to do - but there must be a hearable difference when we add complexity…

 

[eddie]

Can anybody tell me how to hold the IPhone 15 when meauseriing please ?

 

[Smartplug]

Can anybody tell me how to hold the IPhone 15 when meauseriing please ?

There’s a picture when you run rc. Bottom phone pointing between speakers.

 

[Smartplug]

That‘s all fantastic!
However, do you hear a „big“ difference?
I tried around a lot with RC. Now, if I put some gain e.g. +3dB at 200Hz or at 250Hz I do not hear a difference in the music.

People are saying, we need not 10, but 20 correction point settings in PEQ. Why not 200? Honstly - for me what counts is a hearable difference in the music and in the room.
If I use all 10 settings from 20Hz to 400Hz it sounds „the same“ as if I use 6 and intrapolate the measurements inbetween optically.

We can discuss - and it‘s fun to do - but there must be a hearable difference when we add complexity…

It’s funny many users been doing many rc sweep and just look at the graph without listening on the outcome. They get annoyed if rc boost something then run over again till they are satisfied with little boost or cut. They can simply avoid clipping if they lower the max volume. Too many measuring not enough listening!