Enable Multi-Core Audio Rendering for Better CPU Performance
planned
ultracello
Description:
Improve Loopy Pro’s audio engine by enabling true multi-core (multi-threaded) CPU processing for audio rendering, especially useful with multiple AUv3 plugins and parallel signal paths.
Problem:
Currently, Loopy Pro does not seem to fully utilize multi-core CPU processing for audio tasks. This can quickly lead to CPU overloads in complex projects with several AUv3 plugins, effects, or multiple audio channels – even on high-end iPads.
Proposed Solution:
– Implement multi-threaded audio rendering
– Distribute AUv3 plugin processing across available CPU cores
– Prioritize per-track or per-plugin parallelization
– Dynamically allocate threads based on system load
– Add CPU usage per-core display (optional)
Benefits:
– Much better performance on modern multi-core CPUs
– Lower risk of audio glitches and dropouts
– Enables more complex, creative setups with more plugins
– Extends device longevity by improving resource efficiency
– Makes Loopy Pro more competitive as a DAW alternative
This summary was automatically generated by ChatGPT-4 on April 30, 2025.
Pier
Isn't Loopy m1 ready?
Morton Feldman
M1 iPad is so powerful. +1 for unleash the beast.
ultracello
ultracello
planned