Quote:
Originally Posted by ZEUSS
I don't understand why this problem does or should even exist at this point? How many years is it now? Why are they not fixing things like this? How many years does it take?
|
I have argued that for a long time. There might be algorithmic/signal handling/purity concerns... since what you would likely doing is deliberately dither/pollute extreme low level signals to avoid the CPU running into this denormalization. It’s not a “bug” in the sense that the CPU is doing what is expected and the code is running correctly, but that really is not good enough. I would have hoped Avid had thought about this in AAX and helped provide tools for developers to handle it (including avoiding plugin computational all when the input is intended to be effectively nothing). This does seem to have improved (and not that we have more CPU cores?), but still lurks as a potential problem.
Sent from my iPhone using Tapatalk