I want to do plugins for AAX DSP.
But there are problems.
AAX achieves its stability by virtue of each plugin being able to report its cpu usage ahead of time. This means that the system can determine in advance how to arrange things, and provide an incredibly stable system. It’s great.
However, consider EQuality. In Digital mode, with all bands disabled, it uses essentially no CPU. However, stick it in linear phase and select a 3second IR length (max IR length pref), and it uses a LOT of cpu… plus a (completely uncompensatable) 1.5sec of latency from the IR. In fact, I’d be impressed to see any DSP pull that off – it’s basically an offline process for ultra hi-res mastering… but I +do+ need to provide the option.
Even in Digital mode, the cpu usage varies a lot; enable all three filters at 48db/oct, automate them all, and it uses effectively 12 bands of EQ for the filters, and a lump of extra cpu to prevent pops and clicks from the automation. So, CPU can vary wildly. What do I report? The case is worse with EQuick which can have 32 bands of 48db/oct filters…
Likewise with compassion, as soon as you add sidechain EQs, linear-phase splitting, the clip-limiter and transient shaper… cost rises.
Historically, people have provided for this by having versions with features cut out – 3 band EQs and the like… but in this case, I’d need to make dozens of different cutdown versions so you could enable a few features without paying cpu cost for a few others you didn’t need.
So, there is my quandary with AAX-DSP. It’s a fantastic system, and I +REALLY+ want to get things running there, but I can’t work out how to do so without hugely complicating things, or dropping features. Consider this a solicitation for ideas 😉