Using fluid.ampslice~ to extract amplitude information

[rodrigo.constanzo]

@tremblap

Now, this is an interesting question. I would use fluid.loudness for that, and get the RMS for the same price. You are in real time here, but the JIT approach is good here. Obviously that induces the latency of the window you want to analyse to ‘catch’ the peak.

Totally, but that brings me back to the “analyzing the correct frame” problem. There’s no way to get the output of fluid.loudness~ to be perfectly in sync with a triggered onset. I can take a whole window and then take a peak value from that, but again, a bit sloppy and susceptible to Max slop(?).

@tremblap

as it is very quick you could use its change of state 0->1 to trigger a sample and hold. if you tweak the latency right, you could catch the peak, especially if you are peak-riding with a fast attack and slow decay on the relative gate.

Again, possible, but if the decay is set too long, or if my criteria exceeds the threshold for a longer period of time, all of that adds to additional latency. Or worse, additional (pseudo)random latency, since it’s not something you have direct musical control over.

@tremblap

in the long term, there is another idea in the pipeline for a way to output the curves. that has been talked about in various threads, but will happen only after the 2nd toolbox has a viable alpha, so not for a good 6 months… @groma has some dreams and great ideas there.

That would be cool, and it would be less…erm… of a black box object than it presently stands…

For me, however, that would just be a workaround to the larger (in my case) problem of wanting something in real-time and being able to be sample accurate about it. Where presently is in a no-man’s-land in the fluid.-verse.