I vaguely recall reading something (it's not currently in the documentation that I could find) about the use of really short feedback times in MXXX feedback loops being costly in terms of processing power. Is there a penalty to be paid for using a one-sample feedback period? Is so, what's the point at which things are more reasonable? Is one millisecond better? Would 100 samples be OK?
In most situations, the user is not going to notice the difference between a one-sample period and a 100-sample period. But one sample is effectively instantaneous, so that would be preferable if there's no penalty to pay.
MXXX Feedback Question
-
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Above 1ms things get a lot more CPU friendly.Below that is pretty harsh.
Personally, I just leave it on the default of 10ms, it sounds fine and is super low CPU.
Personally, I just leave it on the default of 10ms, it sounds fine and is super low CPU.
Jason @ Melda Production
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
That's correct. Think about this - all audio algorithms are processing blocks, because that provides lots of ways to optimize, plus each algorithm needs some say "start->process->end", just some interface around it. By using a feedback of 1 sample you basically force the engine to use one sample at a time, so no buffering and everything gets reaaaally slow. I also don't think it is too useful actually.
