It would be great if a collaboration was made with Alpha Labs. To integrate the De-feedback plugin directly into the UFX engine.
This it’s making a lot of movement in the industry right now. To natively have it before other manufacturers would be a big selling point.
Still don’t get, why anyone needs such a plugin. 
I have had the exact same thoughts about anti-feedback processing, but in this case I think de-feedback Is just a bad name. It definitely has its uses in extremely reverberant rooms. (we have a dLive in our symphonic hall, and I am sure de-feedback could improve things quite a bit)
I’m not sure what the system requirements are for the plugin though (not all arm chips are made equal), but worst of all, the licensing would probably be a nightmare.
Ah, yeah, that could be helpful.
+1000 for adding alphalabs defeedback or something similar but not only to the ufx card. Please make it available for every dlive user.
Features like this will increase and they will fundamentally change the methods and understanding of mixing in the future…
Do you have any idea how much processing power this requires? The Alpha Lab De-feedback plug-in recommended “option 1” requires a computer running a Intel N95 chip and 8 GB RAM to run a single mono or stereo instance. That is a A LOT of processing power.
There is ZERO chance the original DLive system has the processing power to run something like the Alpha Labs De-feedback plugin. I don’t know if the RUFX chip has enough processing power to run something like this either.
The Waves Livebox - which is a computer running an Intel Core i7-14700 processor with 32 GB RAM can run 8 instances of the plugin. It’s hard to know exactly how powerful the RUFX card really is because the architecture is completely different, but I doubt it has that much processing power.
Hi Brian,
Thanks a lot for your comment. You’re absolutely right with what you’re writing.
But…
Alphasound / Alphalabs did pioneering work in this field, which happily means we are only at the very beginning of this development. Right now, we can’t even foresee what else is coming in the future. It’s definitely not out of the question that these tools will become more efficient—meaning less CPU-hungry—down the road.
Furthermore, Alphasound / Alphalabs is focused on rentals and installations; they aren’t a traditional software development company. This means manufacturers like Allen & Heath are undoubtedly much better positioned here, whether we’re talking about pure manpower or development skills.
On top of that, there are already competing products on the market today that are far gentler on resources, such as “Clear Voice Live” or “everworks calm.” Both tools are obviously still in beta, but both are said to be way more resource-efficient.
So, to me, it doesn’t seem unrealistic that there are ways to make this available for all dLive users.
For example, this could be implemented just like we normally do on a PC today, where I sometimes intentionally kill certain processes to free up power for a CPU-intensive program.
In our church, for instance, Autotune isn’t relevant at all. If I could intentionally deactivate Autotune in the configuration, that would free up processing power for something like a de-feedback application…
Autotune doesn’t use any processing power if you aren’t using it.
It’s not so much about feedback, but the clarity it offers by eliminating a lot of spill - L Acoustics have just released something similar.