To provide the best experiences, we and our partners use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us and our partners to process personal data such as browsing behavior or unique IDs on this site and show (non-) personalized ads. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Click below to consent to the above or make granular choices. Your choices will be applied to this site only. You can change your settings at any time, including withdrawing your consent, by using the toggles on the Cookie Policy, or by clicking on the manage consent button at the bottom of the screen.
Technické uloženie alebo prístup sú nevyhnutne potrebné na legitímny účel umožnenia použitia konkrétnej služby, ktorú si účastník alebo používateľ výslovne vyžiadal, alebo na jediný účel vykonania prenosu komunikácie cez elektronickú komunikačnú sieť.
Technické uloženie alebo prístup je potrebný na legitímny účel ukladania preferencií, ktoré si účastník alebo používateľ nepožaduje.
Technické úložisko alebo prístup, ktorý sa používa výlučne na štatistické účely.
Technické úložisko alebo prístup, ktorý sa používa výlučne na anonymné štatistické účely. Bez predvolania, dobrovoľného plnenia zo strany vášho poskytovateľa internetových služieb alebo dodatočných záznamov od tretej strany, informácie uložené alebo získané len na tento účel sa zvyčajne nedajú použiť na vašu identifikáciu.
Technické úložisko alebo prístup sú potrebné na vytvorenie používateľských profilov na odosielanie reklamy alebo sledovanie používateľa na webovej stránke alebo na viacerých webových stránkach na podobné marketingové účely.
It looks like the frequency response charts do not show.
Thanks for the heads up, it’s now corrected.
In some of the older articles in English, imperfect processing techniques combined with a lack of focus resulted in incorrect paths to the spectrograms being left in the source code. If you should come across something like that again, the original language version (there are graphs with EN descriptions anyway, you can get to it by clicking the flag in the upper right corner of the page) is always correct. Alternatively, the spectrograms of the individual fans can be accessed by entering the URL according to the format “name-of-the-fan-g***”, where the *** a number from the interval 233 to 244. Of course, this is only a temporary solution until we fix it (after you reporting it). But otherwise it must always work without such complications. 🙂
Thanks, I will keep it in mind if I encounter such an issue in the future and report it so that everyone can have it fixed.
I wanted to see the frequencies because of Noctua NF-A12x25 which has a highly disturbing peak right before 400 Hz. The frequency response of SF120M looks so much better at “33dB” in comparison. That’s why it would be great to have at least 1 sound sample per fan at 33dB, to judge the noise according to personal preference.
This is true, but the reason for this is that the SF120M has an overall “dropped” aerodynamic noise spectrum in this mode due to the higher tonal peaks of the motor and bearings. This is also why it achieves a lower airflow. If the test modes were aligned for equal airflow (i.e., the SF120M would have higher RPM), I expect that the NF-A12x25 might not be noisier even at 380 Hz.