Thank you for your continued patronage of our products.
We have recently discovered, during product support improvement work, that there is an issue with the averaging process in our 1/N octave analysis that needs correction. We sincerely apologize for causing this situation and promise to prevent such an incident from happening again. For customers using the affected product, our sales representative will personally deliver the corrected software and explain the details.
We sincerely apologize for any inconvenience this may cause to our customers using this product. We kindly ask that you install the latest version of the software that has been patched.
We sincerely apologize for bothering you during this busy time, but we would appreciate your understanding and cooperation.
If you have any questions or concerns, please contact our customer service department listed below.
Causes and symptoms of the malfunction
There was a partial error in the averaging process of sound pressure levels in the 1/N octave analysis. For signals where the sound pressure level changes significantly over time, the displayed value was lower than the actual average. This has little effect on stationary signals such as sine waves and random noise. The effect is most significant when averaging the signal including both the present and absent parts of a signal during periods of absence (averaging a burst signal across the entire signal).
ISO532B loudness and AI, which use 1/3 octave analysis results, are affected in a similar way.
Loudness, sharpness, roughness, variability intensity, and tonality (optional) for transient response are all fine.
Target Products
| Model name |
Software Version |
| WS-5160 Sound Quality Evaluation Software |
Ver. 3.00 ～ Ver. 3.34 |
countermeasure
Please install the updated software.
The corrected software will be delivered to you in person by one of our sales representatives, who will explain it to you before handing it over.
Please update your product's software to Ver. 3.35 by following the "WS-5160 Installation Instructions (PDF file)". This will fix the bug.
