Get familiar with measuring the frequency response of sound

How to read spectrographs and tables correctly

In our tests, you will increasingly encounter measurements of the “frequency response” of the sound of PC components. These are useful and rare measurements. As one of our readers has pointed out – for those who can read spectrographs, they are a gem. It’s worse if you don’t understand them. Then they won’t tell you much, and that’s a shame if you also care about the exact “noise” value of computer components, or their sound expression.

How to read spectrographs and tables correctly

Longtime readers know well why we began to measure the frequency response of the sound of PC components. However, this term may also be of interest to those of you who have not yet encountered it (you basically didn’t have a chance to in hardware tests…), but you still care about the sound the computer makes. It will matter to the vast majority, I dare say. After all, no one likes computers whose noise level reaches the level of vacuum cleaners, but also those where you, on the one hand, don’t measure high decibels on the sound level meter, but at the same time your ears are burning. This typically includes whistling, whirring and similar irritating noises.

The easiest way to analyze noise is to use a sound level meter. We also use it, but it has several limitations from the principle of its functioning. First of all, the disadvantage is that the sound level meter senses the noise level across an entire frequency bandwidth and gives you a value of “sound pressure” at the output. This quantity indicates whether, under certain conditions of use (measured device/sound level meter), the object of interest is noisy, quiet or something in between. But it will not give you a clear idea of ​​how the sound of the measured device sounds. That is, unless you currently have an extremely expensive sound level meter with its own spectrograph. But even these usually have a resolution of only 1/3 octave, i.e. lower than the one we work with. In any case, a standard sound level meter, which has only one value (dBa/dBc) at the output, evaluates it based on a mix of all frequencies, and the result says nothing about whether it is 40 dBA booming or squeaky. And this is a fundamental difference from the user’s point of view.

Imagine choosing the quietest in a test of thirty graphics cards, because its measured noise level is only “30.1 dBA” (that is, at the limit of what ordinary sound level meters can record), but in the end you find your old “32-decibel” card’s noise a bit more pleasant. This can easily happen, because the new card may have dominant frequencies that do not suit you. Therefore, in addition to taking into account the total noise level, it is appropriate to analyze which frequencies are more and which are less dominant in the overall sound of a particular cooler or graphics card as a whole (because non-cooling elements, typically coils, contribute to the results as well).

The human ear perceives sound frequencies in the range of approximately 20–20,000 Hz. Of course, everyone is different and it changes with age, too. But the reference scale is optimal and that is why we also measure in this range. Notice the horizontal axis in the graph below where 20 Hz is on the left and 20,000 Hz on the far right. You will know the difference between low and high frequencies and some more detailed descriptions and comparisons will not be necessary. In short, the higher the frequencies, the more squeaky the sound and vice versa (low frequencies, bass, are relatively dull). From 20 Hz to 20 kHz, however, the path is relatively long and the individual tones on it need to be distinguished with sufficient subtlety, in small steps. These are determined by fractions of an octave. We mentioned above that some expensive sound level meters have a spectrograph, which has only 1/3 octave, which can fit only 36 samples, or different frequencies that are analyzed. It’s better than nothing, but why impoverish the analysis when you get finer data from 240 samples in the same time unit at 1/24 octave. The highest paid version of TrueRTA also allows such accurate recording of the measured sound.

On the vertical axis there is then the intensity of the noise to which the specific frequency extends. That is, which is noisier and which is less. The shape of the spectrograph itself reveals the relative proportions of the frequencies within one measurement, but across multiple measurements (typically when comparing different components), it makes sense to operate with the intensity of the same frequencies. In the original tests, we extracted into the dominant graphs only the dominant frequencies in the three bands of low (20–200 Hz), middle (201–2,000 Hz) and high (2,001–20,000 Hz) tones. However, based on your feedback, we’ve determined and found it appropriate to indicate the intensity of specific frequencies. After all, a particular dominant frequency may be the same for two different sound sources, but one is more ear-piercing than the other.

And one important thing. Don’t be fooled by the dBu weight wide-spread in music. You usually encounter dBa in tests, which we also use when measuring the level with a sound level meter. However, we will stick to dBu for the frequency response of sound. There are several reasons for that. It is possible to convert, and if you need it for some reason, add the value 85 to our measured values and you have it in dBa. However, we will not do it (Miro, I’m sorry. I believe you will get over it…).

Considering that the used TrueRTA application does not natively evaluate the weight of dBa, even after that recalculation, these data could be misleading and someone could compare them with the measured noise levels with which the dBa measured by the miniDSP UMIK-1 microphone would be completely incompatible. On the one hand, we continuously calibrate the sound level meter with a calibrated digital sound level meter Voltcraft SLC-100 certified by a technical testing institute, compared to which the miniDSP UMIK-1 microphone would of course be inaccurate. It also has a calibrated profile, but to a different application (REW) and not TrueRTA. On the one hand, the Reed R8080 has a completely different measuring range for dB (our sound level meter has 30–130 dB) and after calculating the measured values ​​from TrueRTA, you will get values ​​well below 30 dBa. In short, a different metric with the same units, readers who are in a hurry would be offered meaningless comparisons. This is one of the reasons why we prefer raw results in dBu. Last but not least, it saves time when processing the results.

Anyway, these are not absolute numbers, we do not measure according to any standard, but in such a way that the measurements can be compared with each other as best as possible with regard to specific types of components. Mutual differences are important and it does not matter in which units they are interpreted. It is always true that a higher number means higher noise. But with dBu, keep in mind that they are expressed as a negative value. This means that the frequency that is closer to zero has a higher noise intensity. So -70 dBu means higher noise than -75 dBu.

The article continues with the second chapter, which you can go to with the red “Next Chapter” button on the right (or by clicking this link).


  •  
  •  
  •  
Flattr this!

Comments (2) Add comment

  1. I’ve been playing around with spectral analysis app on my phone to estimate RPM of various fans, by checking frequency peaks and calculate RPM via the formula RPM ≈ sound frequency of strongest peak/number of blades*60. From PC fans to floor fans, estimation by this method seem reasonably accurate.

    So the first question, how accurate is this actually? What are some factors that will make it deviate from the actual RPM as measured by laser tachometers?

    Going through multiple fan reviews, it is clear to me that one of the things that separates the best fans from the average fan is the supression of tonal peaks, and these peaks most often correspond to the blade pass frequency. I bet it’ll be near impossible to estimate RPM of the A12x25 using the frequency method…

    Next is an observation and suggestion to potential improvement of frequency analysis. Both by observing the app and by my ear, some very cheap 140 mm fans I have not only have an annoying whine, but they also fluctuate in intensity, especially apparent at certain speeds. The sound comes in waves which is extremely annoying compared to a static noise level. It’s also apparent on noise samples of the Arctic P12/P14 I can find online, for example in this video (https://www.youtube.com/watch?v=nt8Ao4GDmzY).

    I wonder if this is something that you can capture in the frequency analysis plots. I am sure it’s also something that separates the best fans from the others, but is barely mentioned in any reviews. If I understand the charts correctly, HW busters have been doing this since this August, so it might be something worth looking into.

    P.S. I have come across a paper that describes and investigates this phenomenon (https://www.mb.uni-siegen.de/iftsm/forschung/veroeffentlichungen_pdf/136_2014.pdf), which you may find interesting.

    1. To tell you the truth, we have not dealt with this issue too much. I consider the measurement of rpm with a laser tachometer to be sufficiently accurate. Anyway, the things you describe seem to be really interesting from a scientific point of view. I’ll definitely study the PDF in my spare time, thanks for the materials! 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *