I had problems measuring my HiFi.
When trying to continue a measurement the values for the distance between the speakers was forgotten by the software. Value: 0
If you try to enter the real value 2.34m (from memory) it stops at 80cm. Higher values can not be entered.
It is anyway a pain that you have to click with the mouse for every cm. Instead of allowing entering a value or to provide a repeat function.
Guess … to come from 0m to 2.34m 234 mouse clicks would be needed, this is really an annoyance.
But “luckily” your software refuses any further change over (if I remember right) 80cm.
Well but by this it is not possible to continue the measureing, you have to cancel it entirely and to start over freshly ..
For a software at v 4x. I regard all these things are really poor. The operation of Sonarworks is extremely user unfriendly and kind of bugged.
I spend today 9h and had nothng but issues with the softare.
The measuring results for my main speakers were not so good, Wet values over 40-50% really sound strange so that you put the whole concept of measuring “a little into question”. Fully linearized it does not sound linear, it simply sounds crappy.
And that I was unable to measure my HiFi boxes with all the flaws that I detected.
Gents, I am really disappointed about your product and will return it. I am sick of it that I wasted a whole day without satisfactory results.
2 comments
Andreas I know you've returned the product for a refund, but for others wondering, here's some context:
Manual text input for distance adjustments would be a helpful feature, and it's on the product roadmap for future implementation. However, the issue you faced with incorrect distance measurements (leading to excessive mouse clicks for adjustments) stems from a sample drift in the signal chain, likely due to one of the hardware devices in the chain (as commented in your other post here). We recommend reducing the setup to a single I/O device during the measurements.
The root problem here is the sample drift, which can be resolved by submitting a support request for a closer look at the signal chain. Once fixed, the distance measurement would be correct, and only minor adjustments would be needed. There isn’t an 80cm limit on speaker distance (they can be up to 6 meters apart); the 80cm restriction you encountered was due to the sample drift, which triggered a range limit as a preventive measure.
In summary, while the Measure app might seem to fall short, it’s trying to prevent further issues by flagging underlying problems. in such situations, it’s tough for the software to pinpoint exact setup errors when drift occurs as it has limited information to work with. If others face similar problems, submitting a support request is the best way forward. This would allow us to have a closer look at the signal chain, investigate, and advise and adjustments to be made
Kārlis
> However, the issue you faced with incorrect distance measurements (leading to excessive mouse clicks for adjustments)
> stems from a sample drift in the signal chain, likely due to one of the hardware devices in the chain
Here again my setup.
Mic input AN 11 IN
|
PC---USB3-----UFX III----ADAT1 OUT---SPDIF(o)------ADI-2 Pro FS R BE (Recording Corner)
\--------ADAT2 OUT--SPDIF(o)------ADI-2 Pro FS R BE (HiFi Corner)
Sample drift? I do not think so. BTW; we are not talking about some crap consumer components, I am using high quality RME gear.
But despite of this, two easy observations and questions to you, why I do not think that sample drift is an issue here:
1. Why does measurement finds out the correct values if the distance from the wall is ≥ 47cm?
2. Why does the measurement work in my Recording corner which has the same signal path over a 2nd ADI-2 Pro?
I tested and validated already that the measurement of distances only works reliably, if the measurement microphone has a distance to the back wall of at minimum 47 cm. But this doesn't help me in my case, because my listening position is 30cm in front of the wall.
Sadly it was also not possible to continue with the measuring at around 48 cm from the wall because then I ran into other problems with our software, that it timed out too early and complained about being unable to find the measurement Mic.
After a couple of times where I had restarted the process and had to go 3.5m to the couch to pick up the Mic and then it failed again and again.
Sorry, also this is a big malfunction of your software.
I have a certain feeling that you tested it in your test labor only under ideal conditions so that such cases did not show up.
Instead of making completely unfounded assumptions here that the problem must lie in the customer's equipment / setup, although it has already been proven that it is due to the distance between the measuring microphone and the wall, it would be better to try to recreate the problem and think about under what conditions your software fails and what can be done to fix it.