# Jaymie (@jstrecker)

• Vuo Founder
• Team Vuo

## Compositions

1 year ago
1 year ago
4 years ago
4 years ago
4 years ago
Jaymie commented on Kewl's Discussion, “Calculate Node: clamp to one bound?

Instead of the two-sided limit with `clamp`, you could do a one-sided limit with `min` or `max` — for example `min(value, highLimit)`.

The values scaling is different: is it now between 0 and 1?

Yes, assuming the input audio samples are between -1 and 1, the output amplitudes are between 0 and 1.

But the frequency bias has also changed: before, it was "pink is flat" (equal energy per octave), now it's "white is flat" (equal energy per frequency interval).

When Frequency Bin Averaging is None, isn't "white is flat" always the correct behavior? My understanding of white noise vs. pink noise is that white noise should (ideally / on average) have an equal amplitude for every frequency bin, and pink noise should have decreasing amplitudes as the frequency increases.

If you do want to go back to the old behavior, you can still use the old version of the node. In Vuo 1.2.3 and earlier, the Node Library lists `vuo.audio.analyze.fft`. In Vuo 1.2.4 and later, it lists `vuo.audio.analyze.fft2`, but `vuo.audio.analyze.fft` is still installed. If you create a composition in Vuo 1.2.3 containing `vuo.audio.analyze.fft` (the deprecated node) and open the composition in Vuo 1.2.4 or later, it will still contain the `vuo.audio.analyze.fft` node with the old behavior.

Or you can paste the old node directly from Vuo 1.2.3 to Vuo 1.2.4. Or just paste the following text onto the canvas:

``````digraph G
{
CalculateAmplitudeForFrequencies [type="vuo.audio.analyze.fft" version="1.0.0" label="Calculate Amplitude for Frequencies|<refresh>refresh\l|<samples>samples\l|<frequencyBins>frequencyBins\l|<frequencyBinAveraging>frequencyBinAveraging\l|<amplitudes>amplitudes\r" pos="459,67" _frequencyBins="\"255\"" _frequencyBinAveraging="\"quadratic\""];
}
``````