Description:
Enable Loopy Pro to access and route individual outputs from multi-output AUv3 plugins. This would allow users to handle complex signal routing within Loopy itself, without needing to rely on external hosts like AUM.
Problem:
Currently, Loopy Pro does not expose the individual outputs of multi-output AUv3 plugins. As a result, users cannot route separate channels (e.g., drum parts or stems) to different buses, apply individual effects, or send them to discrete hardware outputs. This makes advanced mixing setups cumbersome and forces users to rely on external apps.
Proposed Solution:
– Detect and expose multiple output channels from AUv3 plugins
– Allow routing of each AUv3 output to a different Loopy Pro bus or track
– Enable per-output effect chains (e.g., reverb on snare, delay on hi-hats)
– Permit discrete outputs to be routed to specific physical outputs on an audio interface
– Maintain compatibility with AUv3 instruments like Digistix, Hammerhead, FAC Drumkit, Loopy AU (backing tracks), etc.
– Provide clear UI to manage output-channel mapping within Loopy Pro’s mixer or plugin settings
Benefits:
✅ Gives users full control over plugin output routing inside Loopy Pro
✅ Eliminates the need to use AUM or other routing apps for multi-output AUv3s
✅ Supports pro-level mixing setups with buses, FX, and separate audio interface outputs
✅ Makes Loopy Pro a more complete AUv3 host, especially for beatmakers and live performers
✅ Enhances flexibility for handling multi-part instruments and complex backing tracks
This summary was automatically generated by ChatGPT-4 on April 30, 2025.