Well, as you use iPlug I guess you are abstracted for that, but I think that it's still possible for the DAW to send single precision if I'm not wrong. But yes, with reasonable latencies the blocks passed around by the DAW are tiny and we are probably splitting hairs.
The effects are cummulative for each plugin in the chain though, I assume that the memory can be prefetched most of the time, etc. For audio isn't probably worth mentioning unless we talk about reverbs using a lot of memory, samplers, but e.g. on machine learning they seem to store half-precision floats for this reason.
It would be nice to see a full benchmark with multiple 32 vs 64 bit reverbs in parallel. The problem is having a reverb allowing configurable bit depth. The only one I know is Turbopaco, but it's 16 vs 32 bit, so the float16 is slower because it isn't hardware aided, but done with bitshifting.
The effects are cummulative for each plugin in the chain though, I assume that the memory can be prefetched most of the time, etc. For audio isn't probably worth mentioning unless we talk about reverbs using a lot of memory, samplers, but e.g. on machine learning they seem to store half-precision floats for this reason.
It would be nice to see a full benchmark with multiple 32 vs 64 bit reverbs in parallel. The problem is having a reverb allowing configurable bit depth. The only one I know is Turbopaco, but it's 16 vs 32 bit, so the float16 is slower because it isn't hardware aided, but done with bitshifting.
Statistics: Posted by rafa1981 — Wed Jul 24, 2024 11:50 am