Rotating machinery rarely misbehaves at every speed. A gear whine that is inaudible at idle can dominate at 3200 rpm; an electric drive can sound perfectly smooth until a narrow speed window in which the inverter sidebands fall into the roughness-sensitive modulation range. Plotting a psychoacoustic metric against time tells you when the problem occurs; plotting it against speed of rotation tells you where in the operating range it lives — which is the form an engineering team can act on.
Deepsona provides vs RPM variants for five psychoacoustic metrics. All of them are intended for run-up and coast-down measurements, and all of them require a recording that contains speed information.
| Analysis | Standard | Result Form | Detail Page |
|---|---|---|---|
| Sharpness vs RPM | DIN 45631/A1, Aures | Curve over the speed axis, in acum | Sharpness |
| Hearing Model Roughness vs RPM | ECMA-418-2 (hearing model) | Curve over the speed axis, in asper | Roughness |
| Fluctuation Strength vs RPM | ECMA-418-2 Edition 4 (hearing model) | Curve over the speed axis, in vacil | Fluctuation Strength |
| Tonality vs RPM | DIN 45681 / ISO/TS 20065 | Colour map: prominence ratio over frequency and speed | Tonality |
| Tone to Noise Ratio vs RPM | ECMA-418-1 | Colour map: tone-to-noise ratio over frequency and speed | Tone-to-Noise Ratio |
A sixth speed-resolved psychoacoustic result, Specific Fluctuation Strength (Hearing Model) vs. RPM, is documented together with its band-spectrum and vs Time siblings on the Specific Fluctuation Strength (Hearing Model) page.
Every vs RPM analysis starts from the same psychoacoustic model as its vs Time counterpart. The metric is evaluated along the recording, and the result is then expressed over the speed axis instead of the time axis: at each speed step the corresponding result is taken from the underlying analysis. Because a run-up passes each speed exactly once, the mapping is unambiguous and the result reads directly as "metric as a function of operating speed".
Two result forms occur, depending on what the underlying metric produces:
All five analyses share the parameters that define the speed axis. Every other parameter is inherited from the corresponding vs Time analysis and is documented on that metric's own page.
| Parameter | Options | Description |
|---|---|---|
| Speed Step | 50 rpm (default) | Spacing of the speed axis. Smaller steps give a finer picture of narrow speed windows but require a slower, more evenly executed run-up |
| Slope | Automatic (default) / Run-up / Coast-down | Direction of the speed change to be evaluated. Automatic derives the direction from the recorded speed trace |
| Channel Selection | Sound-pressure channels | Only sound-pressure channels are evaluated; the speed reference and other auxiliary channels are excluded automatically |
| Analysis | Result | Unit | Single Value |
|---|---|---|---|
| Sharpness vs RPM | S(n) | acum | Mean over the speed axis |
| Hearing Model Roughness vs RPM | R(n) | asper | 90th percentile over the speed axis |
| Fluctuation Strength vs RPM | F(n) | vacil | 90th percentile over the speed axis |
| Tonality vs RPM | PR(f, n) | dB | Tonal level difference with its frequency, the averaged level difference and the uncertainty |
| Tone to Noise Ratio vs RPM | TNR(f, n) | dB | Not reported (the result is read from the map) |
The vs RPM and vs Time variants of a metric are two views of the same evaluation, not two different models. Choosing between them is a question of what the result has to answer:
| Question | Use |
|---|---|
| "When during the test does it get bad?" | vs Time |
| "At which operating speed does it get bad?" | vs RPM |
| "Is the effect repeatable between run-up and coast-down?" | vs RPM, computed once per direction |
| "Does the sound stay acceptable at a fixed operating point?" | vs Time, or the stationary variant |
Because the speed axis removes the influence of how fast the operator ramped the machine, vs RPM results from different test runs — and from different vehicles or samples — can be overlaid directly. This makes them the preferred form for target setting, benchmarking and pass/fail limits, while vs Time remains the better tool for diagnosing a single event.
© 2026 Deepsona. All Rights Reserved.