Feature Requests

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: Enable the ability to copy, paste, duplicate, and merge MIDI/OSC bindings in the control settings. This would streamline repetitive setup work and support reusing bindings across projects. Problem: Currently, creating multiple similar bindings for different controllers or layouts is very time-consuming. There’s no easy way to duplicate a binding or reuse an existing set from another project or profile. Proposed Solution: – Add copy/paste functionality for individual bindings – Add "Duplicate" function to quickly clone a binding and tweak it – Allow selection of multiple bindings for batch copy/paste – Add ability to import or merge bindings from another control profile – Ensure copied bindings retain all mapped actions and parameters – Optional: offer search/filter to quickly locate bindings during merge Benefits: – Saves significant time when creating complex control mappings – Reduces user errors by avoiding repetitive manual setup – Encourages creation of reusable template bindings and modular profiles – Supports faster prototyping and experimentation – Ideal for users with multiple controllers or evolving live 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: Users would like the ability to cancel a current record or overdub session directly while it is in progress. This would be particularly useful when using a MIDI foot controller, where a single switch may be assigned for both rec/play/overdub functions. A long press could serve as the cancel action. Problem: Currently, once a recording or overdub has started, there is no simple way to immediately cancel it without disrupting the workflow. This can be problematic in live performance situations where quick reactions are crucial. Additionally, users often change their minds about recording or hit the switch accidentally, leading to unintended recordings. Proposed Solution: Implement a long-press or dedicated action that cancels the ongoing record or overdub. Provide an option to choose between: - Undo/redo cycle of an overdub - Undo/redo full overdub Prevent the initial recording of a clip from being deleted when using the cancel function. Benefits: Improves live performance control by allowing quick cancellation of unintended recordings. Reduces workflow interruptions when correcting recording mistakes. Provides flexibility to manage overdub layers efficiently. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

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: 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: Users would like a dedicated 'effects' section for MIDI sources in Loopy Pro, allowing for easy integration of MIDI processor AUv3 plugins. Currently, these plugins must be added as separate channel strips and manually connected, which can be cumbersome. Problem: The current method of adding MIDI FX as separate channel strips is inefficient and takes up unnecessary screen space. This approach also complicates the workflow when dealing with multiple MIDI FX plugins. Proposed Solution: Introduce a dedicated 'effects' section specifically for MIDI sources, similar to how audio tracks handle effects. This would allow users to directly place MIDI processor AUv3 plugins within the same channel, reducing clutter and improving usability. Benefits: Streamlined MIDI FX management. More efficient use of screen space. Simplified setup process for MIDI FX chains. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes the implementation of bi-polar faders and knobs within Loopy Pro. The goal is to provide users with controls that have a centered neutral position, allowing for symmetrical adjustment of parameters in both positive and negative directions. This functionality is particularly beneficial for parameters like panning, where a centered control reflects the neutral (center) position. Problems Limited Control for Bi-Directional Parameters : Currently, Loopy Pro's faders and knobs operate in a unipolar fashion, ranging from 0 to 100%. This design is not ideal for parameters that require a centered control, such as panning, where values should range from -100% (left) to +100% (right) with 0% representing the center. Inconsistent User Experience : The absence of bi-polar controls can lead to confusion and imprecise adjustments when managing parameters that inherently have a central neutral point. Workflow Inefficiency : Users may need to implement workarounds or use external MIDI controllers to achieve the desired bi-polar control behavior, disrupting the creative flow. Proposed Solution Bi-Polar Control Implementation : Introduce bi-polar fader and knob widgets that allow for symmetrical adjustment around a central neutral position. Visual Indicators : Design the bi-polar controls with clear visual cues to indicate the center point and the direction of adjustment (positive or negative). Customizable Range : Allow users to define the range of the bi-polar controls to suit different parameters and preferences. Integration with Existing Systems : Ensure compatibility with Loopy Pro's current action and MIDI mapping frameworks, providing a seamless user experience. Benefits Enhanced Precision : Bi-polar controls enable more accurate adjustments for parameters requiring centered control, improving the overall sound design and mixing process. Improved User Experience : Providing native bi-polar controls aligns with user expectations and reduces the need for external solutions or complex workarounds. Streamlined Workflow : Integrating bi-polar controls into Loopy Pro's interface facilitates a more efficient and intuitive workflow, allowing users to focus on creativity. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description This feature request proposes enhancing the MIDI routing interface in Loopy Pro by displaying the track name and icon within the MIDI destinations boxes. The goal is to improve clarity and usability when assigning MIDI outputs, especially in complex projects with multiple tracks and destinations. Problems Lack of Visual Identification : Currently, MIDI destinations are listed without accompanying track names or icons, making it difficult to quickly identify the target track, especially when multiple tracks are involved. Workflow Inefficiency : Users must rely on memory or trial-and-error to determine the correct MIDI destination, which can slow down the setup process and increase the likelihood of routing errors. Limited Scalability : As projects grow in complexity, the absence of clear identifiers in MIDI destinations hampers efficient management and scalability. Proposed Solution Display Track Names : Modify the MIDI destinations interface to include the name of each track, providing immediate textual identification. Include Track Icons : Alongside track names, display the associated track icon or color, offering a visual cue to further aid in quick identification. Consistent UI Integration : Ensure that these enhancements are consistently applied across all areas where MIDI destinations are selected or displayed, maintaining a uniform user experience. Examples Live Performance Setup : A performer sets up multiple MIDI tracks to control different instruments. With track names and icons visible in the MIDI destinations, they can quickly assign outputs without confusion, ensuring a smooth performance. Complex Project Management : In a project with numerous tracks, a producer can efficiently route MIDI signals by visually identifying tracks through their names and icons, streamlining the workflow. Educational Use : In a teaching environment, instructors can demonstrate MIDI routing more effectively, as students can easily follow along by recognizing track identifiers in the interface. Benefits Enhanced Usability : Provides clear visual and textual cues, making MIDI routing more intuitive and reducing the learning curve for new users. Improved Efficiency : Speeds up the process of assigning and managing MIDI destinations, particularly in large or complex projects. Reduced Errors : Minimizes the risk of routing mistakes by allowing users to easily confirm the correct destination through recognizable identifiers. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Enable stepped dials to have access to control loops and layers, allowing for more precise control over the looped and overdubbed audio layers directly through dial interactions. Problem: Currently, stepped dials do not have direct access to control loop and layer states, limiting their functionality for managing overdubs or triggering different layers in a loop. This reduces the potential for real-time performance control. Proposed Solution: Allow stepped dials to interact with and control specific loops and layers (e.g. controlling loop start/stop, triggering overdubs, adjusting volume, or switching between layers) Provide a way to map the dials to specific loop layers or overdubs so they can be accessed and controlled easily Allow for precise control of individual layers or loops via the stepped dial, including the ability to switch between overdubs and layers for more dynamic performances Optionally, add visual feedback for each layer/loop on the stepped dial to show which layer or loop is currently being controlled Benefits: Increases performance flexibility by giving real-time, hands-on control over loops and layers Enables more creative manipulation of overdubs and layered audio without needing to manually navigate through menus or screens Ideal for live performances or dynamic sound design setups Provides smoother transitions between loops and overdubs, enhancing workflow efficiency This summary was automatically generated by ChatGPT-4 on April 30, 2025.