Feature Requests

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.

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.

Description: Enable support for AUv3 plugins with multiple audio inputs, including standard sidechain inputs on FX and instruments (e.g. FabFilter Twin 3), and allow flexible audio routing between tracks to use this functionality. Problem: Loopy Pro currently doesn’t support AUv3 sidechain inputs or multi-input routing. This limits its use as a fully capable DAW for those relying on dynamics control or complex routing setups (e.g. ducking via sidechain compression). Proposed Solution: – Implement routing of audio from one track to the sidechain input of a plugin on another track – Support AUv3 FX plugins with standard sidechain inputs – Support instrument AUv3 plugins that also include sidechain inputs (e.g. FabFilter Twin 3) – Allow use of multi-output AUv3 instruments with flexible routing to Loopy tracks or groups – Provide clear UI elements to manage input/output routing between tracks and plugins Benefits: – Makes Loopy Pro viable as a standalone DAW for advanced users – Enables mixing techniques like ducking, pumping, spectral sidechaining – Makes full use of AUv3 plugins that already support these features – Greatly enhances creative potential in sound design, live setups and dynamic control workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: A MIDI keyboard widget that can be added to a layout in Loopy Pro, similar to the existing pads widget. This widget would facilitate a cohesive layout without the need to reposition or toggle the keyboard during a jam session. Problem: Currently, users rely on the Velocity Keyboard AU for most projects, but it lacks integration with Loopy Pro’s layout. Additionally, mapping a range of MIDI notes to multiple buttons is cumbersome, as each note must be assigned individually. There is also no simple way to transpose all keys together, such as using octave up/down buttons. Proposed Solution: Develop a built-in MIDI keyboard widget for Loopy Pro that offers: Velocity-sensitive key input similar to the Velocity Keyboard AU. Integrated octave up/down transposition for quick access to a broader note range. Flexibility to add, reposition, or hide the keyboard easily within a layout. Customizable layouts to accommodate different use cases, like live performance or studio setup. Benefits: Simplifies live setups by integrating a keyboard directly into the Loopy Pro interface. Reduces dependency on external AUs for basic MIDI input. Offers a more intuitive and flexible solution for MIDI control. Facilitates live looping by allowing quick transposition and note access. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes the enhancement of Loopy Pro's MIDI binding capabilities to allow for the utilization of the full range of MIDI Continuous Controller (CC) values (0–127) in parameter mappings. The aim is to provide users with more granular and expressive control over parameters, facilitating smoother transitions and more dynamic performances. Problems Limited Expressiveness : Currently, Loopy Pro's MIDI Learn system interprets CC messages primarily as binary triggers (e.g., value 127 for "on" and 0 for "off"), which restricts the ability to perform nuanced parameter adjustments. Incompatibility with Certain Controllers : Some MIDI controllers are designed to send a range of CC values for parameters like volume, pan, or filter cutoff. The current implementation in Loopy Pro may not fully leverage these capabilities, leading to suboptimal integration. Workflow Inefficiencies : Users seeking to implement gradual parameter changes must resort to workarounds or external tools, complicating the workflow and potentially introducing latency. Proposed Solution Full-Range CC Value Support : Modify the MIDI Learn system to recognize and utilize the entire 0–127 range of CC values, enabling direct mapping to parameters that benefit from continuous control. Parameter Scaling Options : Introduce scaling options within the MIDI binding settings to allow users to define how the 0–127 CC range maps to specific parameter ranges, including inversion and custom curves. Visual Feedback Enhancements : Provide real-time visual indicators within the interface to reflect parameter changes driven by varying CC values, aiding in precise adjustments during live performances. Examples Volume Control : A user maps a MIDI controller's fader, which sends CC values from 0 to 127, to control a track's volume in Loopy Pro. This setup allows for smooth volume fades and precise level adjustments. Filter Modulation : A performer assigns a rotary knob sending CC values to modulate a filter's cutoff frequency, enabling dynamic tonal shifts during a live set. Effect Depth Adjustment : A DJ uses a MIDI controller to adjust the depth of a reverb effect in real-time, with the CC value directly influencing the wet/dry mix parameter for seamless transitions. Benefits Enhanced Expressiveness : Utilizing the full CC value range allows for more nuanced and dynamic control over parameters, enriching live performances and recordings. Improved Controller Integration : Better compatibility with a wider range of MIDI controllers enhances user flexibility and choice in hardware. Streamlined Workflow : Direct mapping of CC values to parameters simplifies setup and reduces the need for external processing tools, leading to a more efficient workflow. This summary was automatically generated by ChatGPT-4 on 2025-05-09.

Description: Allow users to rename audio busses and optionally add visible notes or hints describing their function or purpose. Problem: Currently, busses in Loopy Pro are automatically named with letters (A, B, C...) upon creation, and users are unable to rename them. This makes it difficult to organize and recall bus functions, especially in complex projects with many busses. The default visual representation is also hard to distinguish from color groups, making the UI harder to parse quickly. Proposed Solution: – Allow users to rename busses at any time – Display the name prominently (e.g. at the top of the bus or next to the letter) – Optional: restore default letter-based name (e.g., "A") if custom label is deleted – Add support for a “hint” or “notes” field for each bus (shown e.g. on hover or toggle) – Consider visual improvements to further differentiate busses from color groups – Optional: provide a UI dialog showing an overview of a bus’s routing and settings, including name, balance, etc. Benefits: – Greatly improves clarity in complex routing setups – Reduces need for external “cheat sheets” – Helps identify and manage up to 24+ busses more efficiently – Enhances UI and UX, especially for live performance or sound design – Makes Loopy Pro more scalable and user-friendly for professional workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable saving and recalling entire channel strips (including all plugins and optionally widgets) as presets. This allows fast loading of complex FX/instrument chains across different projects. Problem: Rebuilding plugin chains and settings for each project or channel type (input, color, bus, master) is time-consuming, especially in live setups or when consistent tone is needed across songs. Proposed Solution: – Add a feature to save a full channel (strip) as a reusable preset – Optionally include bound widgets and layout elements – Allow importing/exporting channel strip presets – Add "recall channel preset" and "save channel preset" actions – Allow presets for: – input channels – color channels – bus channels – master channel – Optional: grey out unloaded channels to free up RAM/CPU – Optional: preload (but inactive) channel strips for fast switching – Optional: include full widget configuration (position, behavior, etc.) – Add tags or labels to organize channel strip types (e.g. “Guitar FX”, “Vocal Bus”) Benefits: – Save time during project setup – Allows modular, reusable channel configurations – Supports consistent tone in live and studio workflows – Ideal for musicians switching instruments/effects between songs – Reduces CPU/memory load by offloading unused channels – Encourages structured and repeatable setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the implementation of flexible groove quantization options for MIDI recording in Loopy Pro. The goal is to provide users with advanced tools to adjust the timing and feel of MIDI recordings, enhancing musical expression and aligning with various rhythmic styles. Problems Rigid Quantization : Currently, Loopy Pro offers basic quantization settings that may not accommodate the nuanced timing required for different musical genres or personal playing styles. Limited Groove Customization : Users lack the ability to apply swing, shuffle, or custom groove templates to MIDI recordings, restricting creative possibilities. Inconsistent Timing Feel : Without flexible groove quantization, achieving a humanized or genre-specific rhythmic feel requires manual adjustments, which can be time-consuming and imprecise. Proposed Solution Advanced Quantization Options : Introduce a range of quantization settings, including swing percentages, shuffle rhythms, and customizable groove templates. Real-Time Groove Application : Allow users to apply and adjust groove settings in real-time during MIDI recording and playback. Groove Template Library : Provide a library of preset groove templates representing various musical styles (e.g., funk, jazz, hip-hop) and allow users to create and save custom templates. Visual Feedback : Implement visual indicators within the MIDI editor to display the applied groove adjustments, aiding in precise editing and alignment. Benefits Enhanced Musical Expression : Flexible groove quantization enables users to infuse their MIDI recordings with desired rhythmic feels, enhancing the musicality of their productions. Streamlined Workflow : Real-time groove application and visual feedback simplify the process of achieving the intended timing, reducing the need for manual corrections. Creative Versatility : A comprehensive set of groove options allows users to experiment with different rhythmic styles, fostering creativity and innovation in their music. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Allow users to group multiple AUv3 plugins into a reusable "plugin group" that behaves like a single plugin container. This makes management easier and introduces powerful features at group level. Problem: Managing multiple plugins on a channel becomes complex. There is no way to treat a combination of AUv3s as a single, unified module. Also, many plugins lack a wet/dry mix and other basic options. Proposed Solution: – Treat plugin groups as if they were individual plugins – Groups show up in plugin lists (add to project, add via action, etc.) – Allow instantiating multiple plugin groups – Allow actions to apply to the group as a whole (e.g. enable/disable) – Provide group-level settings: • Group name (user-defined or internal) • Wet/dry mix control for the group • Reorder plugins in the group • Actions to enable/disable the group – Display group with visual indicators (e.g. folder-style icon, color tag, red/green circle for status) – Allow edit mode and save as preset or duplicate – Restrict to only unused plugin instances (avoid duplicate references) Stretch Goals: – Group presets for wet/dry mix and plugin order – Icon sets to help users identify groups – Choose from visual folder/container symbols – Future option to include plugin parameter presets per plugin inside the group Benefits: – Modular plugin workflow – Reusable effect chains – Add missing features like wet/dry to plugins that lack them – Better project organization – Faster setup and management – Enables actions and visual feedback at group level This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Allow users to assign custom names to individual AUv3 effect instances within Loopy Pro, enhancing clarity and organization in complex projects. Problem: Currently, AUv3 effect instances in Loopy Pro are labeled with their default names, which can lead to confusion when multiple instances of the same effect are used. This lack of distinction makes it challenging to identify and manage specific effects, especially in intricate setups. Proposed Solution: – Enable renaming of each AUv3 effect instance directly within the Loopy Pro interface. – Display the custom names prominently in the mixer and effect lists. – Ensure that these custom names are saved with the project and persist across sessions. – When the custom label is deleted, the instance should automatically revert to showing the default AUv3 name. – Optionally, allow for color-coding or tagging of renamed instances for additional visual organization. Benefits: – Improves workflow efficiency by making effect instances easily identifiable. – Enhances project organization, particularly in complex or collaborative environments. – Reduces the likelihood of errors caused by misidentifying effects. – Aligns with standard practices in other DAWs, providing a familiar experience for users. This summary was automatically generated by ChatGPT-4 on April 30, 2025.