Feature Requests

Description This feature request proposes the implementation of an integrated sustain functionality within the application, enabling users to simulate sustain pedal behavior (MIDI CC64) without relying on external hardware. The goal is to enhance expressive capabilities for MIDI and AUv3 instruments, particularly in mobile setups where physical pedals may not be available. Problems Dependence on External Hardware : Users currently require physical sustain pedals to achieve sustain effects, which can be impractical in mobile or minimalist setups. Limited Expressive Control : Without a built-in sustain function, achieving natural legato and sustained notes on virtual instruments is challenging. Workflow Inefficiencies : The absence of an integrated solution necessitates workarounds, such as using third-party apps or complex MIDI mappings, complicating the user experience. Proposed Solution On-Screen Sustain Control : Introduce a virtual sustain button or toggle within the interface, allowing users to engage or disengage sustain manually. MIDI CC64 Mapping : Enable the mapping of MIDI CC64 messages to on-screen controls or external MIDI controllers, facilitating flexible sustain control. Action-Based Implementation : Utilize the existing actions system to create sustain behaviors, such as sending MIDI CC64 messages with values 127 (on) and 0 (off) to target instruments. Customizable Behavior : Allow users to configure sustain behavior per instrument or track, including options for latch or momentary modes. Examples Mobile Performance : A musician performing with a tablet and no physical pedals uses the on-screen sustain button to hold notes on a virtual piano instrument. MIDI Controller Integration : A user maps a button on their MIDI controller to toggle sustain, enabling hands-free operation during live performances. Automated Sustain : Through the actions system, a user sets up a sequence where sustain is automatically engaged during specific sections of a composition. Benefits Enhanced Expressiveness : Provides users with the ability to perform more naturally on virtual instruments, replicating traditional sustain pedal effects. Improved Accessibility : Eliminates the need for additional hardware, making sustain functionality accessible to users in various setups. Streamlined Workflow : Integrating sustain control within the application simplifies the performance and recording process, reducing reliance on external solutions. This summary was automatically generated by ChatGPT-4 on 2025-05-09. Original Post: Maybe this hardware unit function/schematics can be done via being implemented directly in Loopy Pro via sending actions/MIDI. See here what I mean, this pedal can do this: https://www.youtube.com/watch?v=W_2VPfISSik

Description: Currently, Loopy Pro allows actions to have a "delay" in execution, but this delay can only be expressed in beats or bars. Some actions also include a "RAMP" time setting, which provides a UI display to set time in milliseconds (ms) or seconds. This feature could be extended to cover all actions that require a delay. Problem: When users are not using the metronome or LP clock, it can be challenging to calculate delays solely in terms of beats or bars. This limitation makes it difficult to time actions precisely, especially when a non-musical or time-based reference is needed. Proposed Solution: Allow the delay for actions to be set in either: Beats/Bars (existing functionality) Milliseconds (ms) or seconds (new option) Reuse the existing "RAMP" interface to implement this feature. This will make it easier to set precise time-based delays without relying on the metronome or BPM-based calculations. Benefits: More flexibility when using Loopy Pro without a metronome or clock reference. Enables precise timing for actions not tied to musical beats. Simplifies the process of setting delays for users who prefer direct time input. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Allow mixer channels to be organized into subgroups that can be independently minimized or hidden, making it easier to manage large numbers of plugins and audio sources. Problem: Currently, dragging a plugin channel across another creates a new group, but minimizing affects all plugins in the same category. This makes it difficult to organize and focus on specific sections, as users cannot collapse just the subgroup they want without collapsing unrelated plugins. Proposed Solution: Introduce subgroup channel functionality in the mixer. Each subgroup can contain multiple plugins or channels and be minimized independently of other groups in the same category. This would give users precise control over visibility and organization in complex projects. Benefits: Cleaner mixer view when working with many plugins. Better organization of related channels into logical groups. Faster navigation during live performance or mixing. Reduces clutter without affecting unrelated plugin sections. Examples: Group multiple reverb and delay plugins into a “FX” subgroup, then minimize only that group while keeping instruments visible. Organize multiple layered synth channels into a subgroup and collapse them when not editing. For live looping, keep only the active subgroup open while minimizing background effect groups. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: Sub group mixer channels to hide. I.e ability to split audio sources into sub channel groups and minimize. If you drag a plugin channel across another section, it will create a separate group. However the new group will minimize with all the other plugins in the same category. It would be nice to be able to minimize just the groups separately so you could organize and minimize plugins.

Description This feature request proposes the implementation of an action within Loopy Pro that enables users to record directly into the next available clip of a specified color. The goal is to streamline the recording process, especially during live performances, by allowing for efficient and organized clip management based on color coding. Problems Limited Visual Feedback : On certain MIDI controllers, such as the APC40, it can be challenging to distinguish between clips that contain content and those that are empty, as the brightness levels are similar. This ambiguity can lead to recording over existing clips unintentionally. Workflow Inefficiency : Currently, users must manually select the next available clip for recording, which can be time-consuming and prone to errors, particularly in complex projects with multiple colors and pages. Limited MIDI Controller Integration : Users with MIDI foot controllers that have a limited number of buttons face challenges in assigning specific controls for each clip, restricting their ability to manage recordings efficiently. Proposed Solution "Record to Next Clip in Color" Action : Introduce an action that, when triggered, records into the next available (empty) clip of a specified color. This action can be assigned to on-screen buttons or MIDI controller inputs. Color-Based Clip Selection : Allow users to define the color context for the action, ensuring that recordings are directed to the appropriate set of clips. Integration with Existing Systems : Ensure compatibility with Loopy Pro's current action and MIDI control systems, allowing for seamless integration into existing workflows. Examples APC40 Integration : A user assigns the "Record to Next Clip in Color" action to the buttons beneath each column on the APC40. Pressing a button records into the next available clip of the corresponding color, simplifying the recording process during live performances. Multi-Page Template Management : A user has a template with multiple pages, each containing clips of different colors. By assigning the action to color-coded buttons on a dedicated page, the user can efficiently record into the appropriate clips across various pages without navigating through each one manually. MIDI Foot Controller Usage : A performer with a MIDI foot controller assigns the action to a limited number of footswitches. This setup allows for hands-free recording into designated clip colors, enhancing live performance capabilities. Benefits Enhanced Live Performance Flexibility : Enables performers to manage recordings efficiently, reducing the risk of overwriting existing clips and minimizing the need for manual navigation. Improved Workflow Efficiency : Streamlines the recording process by automating clip selection based on color, saving time and reducing the potential for errors. Expanded MIDI Controller Integration : Provides users with limited-button MIDI controllers the ability to manage recordings effectively, maximizing the utility of their hardware. This summary was automatically generated by ChatGPT-4 on 2025-05-09.

Description: Currently, the “Cancel Count-Ins/Outs” action applies globally—it cancels all scheduled count-ins and count-outs without the ability to target specific clips or types. Users often need more granular control to cancel only some scheduled actions without disrupting others. Problem: In scenarios like switching play groups, triggering multiple clips, or correcting a single mistake, cancelling all pending count-ins/outs is too destructive. Users may want to cancel a count-in for one clip but let others proceed. The lack of targeting results in unintended interruptions during live performance or recording workflows. Proposed Solution: Add standard targeting options (e.g. “this clip”, “play group”, “all clips”, etc.) to the “Cancel Count-Ins/Outs” action. Allow filtering by count-in/out type: - Any - Count-ins - Count-outs - Play count-ins - Stop count-outs - Record count-ins - Record count-outs This would enable gestures or MIDI actions to cancel only specific pending transitions for the targeted clip(s). Benefits: More precise live control over clip transitions. Avoids unintended cancellation of unrelated actions. Enables recovery from mistakes without interrupting the intended flow. Enhances expressive performance workflows and gesture-based control. Examples: Trigger a breakdown section and cancel only the count-in for the next chorus without affecting the rest of the loop transitions. Correct a mistakenly triggered recording count-in without stopping other play or stop transitions. Use a contextual gesture to cancel pending actions only for the clip it's performed on. This summary was automatically generated by ChatGPT-4 on July 24, 2025. Original Post: Allow targeting for “Cancel Count-Ins/Outs” action Currently the “Cancel Count-Ins/Outs” action does not have any targeting options, so it cancels all count-ins/outs. Sometimes users might only want to cancel some of the count-ins/outs. For example, after triggering a mutually exclusive play group to play in order to switch from one section of a song to another, I might then want to cancel the count-in for some of the clips that are about to play (for a breakdown section) while letting the other count-ins/outs continue. Or anytime I trigger multiple clips to play, stop, or record, and one or more but not all was by mistake, I could fix my mistake while still allowing the other actions that were on purpose to continue. This action should have all the targeting options that other actions have. Targeting “this clip” is the option I most want to have because I could set a gesture that cancels count-ins/outs for whichever clip that gesture is performed on. But I can see uses for other targeting options as well.

Description This feature request proposes the implementation of an "On Select" follow action within Loopy Pro. The goal is to enable users to trigger specific actions automatically when a clip is selected, without initiating playback or recording. This functionality would enhance workflow efficiency, particularly in live performance settings where rapid and precise control over clip-associated actions is essential. Problems Limited Pre-Recording Configuration : Currently, actions such as changing effect presets or sending MIDI messages can only be triggered during playback or recording. This limitation hinders the ability to prepare a clip's settings in advance. Workflow Inefficiency : The necessity to initiate playback or recording to trigger certain actions adds extra steps, disrupting the creative flow and potentially causing delays during live performances. Inflexibility in Clip Management : The absence of an "On Select" trigger restricts users from customizing clip behavior upon selection, limiting the dynamic control over clip-associated parameters. Proposed Solution "On Select" Follow Action : Introduce a new follow action type that activates when a clip is selected, allowing users to assign specific actions such as changing effect presets, sending MIDI messages, or adjusting parameters. Integration with Existing Systems : Ensure compatibility with Loopy Pro's current action and follow action frameworks, providing a seamless user experience. User Interface Enhancements : Update the clip settings interface to include configuration options for the "On Select" follow action, maintaining consistency with existing follow action setups. Benefits Enhanced Workflow Efficiency : Automating actions upon clip selection streamlines the preparation process, reducing the number of manual steps required during live performances. Improved Flexibility : Users gain greater control over clip behavior, enabling more dynamic and responsive performance setups. Seamless Integration : Incorporating the "On Select" follow action into the existing framework ensures a consistent and intuitive user experience. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Add Turkish language support to Loopy Pro’s interface, including menus, labels, and navigation elements, to improve accessibility and usability for Turkish-speaking users. Problem: The current app interface is only available in select languages and does not include Turkish. Turkish users may struggle to navigate the app and understand its extensive feature set due to the language barrier. This limits the user base and makes onboarding more difficult for non-English speakers. Proposed Solution: Translate the UI into Turkish, including all core menus, labels, settings, and onboarding instructions. Optionally include Turkish in the language selection screen with automatic fallback if partial translations are not yet available. Benefits: Makes Loopy Pro more accessible to Turkish-speaking users. Helps new users explore and understand complex features more easily. Expands global reach and user satisfaction in Turkish-speaking regions. Examples: Turkish-speaking musicians and producers can use the app without relying on English terminology. Menus, tooltips, and help prompts are shown in the user's native language. Turkish could be integrated alongside other major language options. This summary was automatically generated by ChatGPT-4 on 2025-07-05.

Description: Introduce UI performance optimizations and toggles to improve responsiveness, especially on older or less powerful iPads. Allow users to disable performance-intensive visual effects such as blur, motion blur, and UI animations. Problem: On certain iPads or lower-end devices, UI elements such as the AUv3 selection window cause performance lags and micro-freezes. This can be frustrating during live performances or intensive sessions. Additionally, UI blurs and transitions add unnecessary GPU load. Proposed Solution: – Add a global toggle to disable all UI animations (e.g. widget transitions, fades) – Add an option to disable motion blur and background blurring effects – Optimize AUv3 plugin selection UI to reduce GPU/CPU demand – Add a "Low Performance Mode" setting for devices with fewer resources – Show memory/CPU warnings for high-load elements if relevant – Make these settings easily accessible via a “Performance” tab in preferences Benefits: – Reduces lag and freezes on older iPads or when using many plugins – More stable performance in live settings – Gives users visual control vs. performance trade-off – Helps ensure smoother experience for all hardware tiers This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the implementation of an action in Loopy Pro that allows users to reset the playhead of selected clips or entire color groups to a specific position. The goal is to enhance live performance capabilities by enabling precise control over clip playback positions without initiating playback. Problems Lack of Precise Control : Currently, Loopy Pro lacks an action that allows users to reset the playhead of a clip or group of clips to an exact position without starting playback. This limitation hinders the ability to prepare clips for synchronized playback during live performances. Workflow Inefficiency : Without the ability to reset playheads precisely, users may need to manually stop and reposition clips, disrupting the flow of a live set and increasing the risk of timing errors. Limited Automation : The absence of a dedicated playhead reset action restricts the automation potential within Loopy Pro, limiting complex performance setups that require precise clip positioning. Proposed Solution Implement Reset Playhead Action : Introduce a new action that allows users to reset the playhead of selected clips or color groups to a user-defined position without initiating playback. Integration with Existing Systems : Ensure compatibility with Loopy Pro's current action framework, including MIDI bindings, widgets, and follow actions, to facilitate seamless integration into existing workflows. Quantization Options : Provide quantization settings for the reset action to align playhead positions with the project's tempo and rhythm, enhancing synchronization during performances. Benefits Enhanced Performance Control : Enables performers to prepare clips for playback with precision, improving timing and synchronization during live sets. Streamlined Workflow : Reduces the need for manual adjustments, allowing for smoother transitions and more dynamic performances. Expanded Automation Capabilities : Facilitates the creation of complex, automated performance setups by providing precise control over clip playhead positions. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description This feature request proposes the implementation of a "Next Empty Clip" target option for record actions in Loopy Pro. The goal is to streamline the recording process by allowing users to automatically record into the next available empty clip slot, reducing manual intervention and enhancing workflow efficiency. Problems Manual Clip Selection : Currently, users must manually select an empty clip slot before initiating a recording, which can be cumbersome during live performances or rapid recording sessions. Inefficient Workflow : The lack of an automated method to target the next empty clip slows down the creative process, especially when dealing with multiple clips or pages. Complex Clip Transfer : Transferring clips between pages or colors requires multiple steps, making it time-consuming and interrupting the creative flow. Proposed Solution Next Empty Clip Target : Introduce an option in record actions to automatically target the next empty clip, either globally or within a specified color group. Send to Next Empty Clip Action : Implement an action that allows users to send or duplicate an existing clip to the next empty slot, facilitating quick transfers across pages or colors. Customizable Context : Provide settings to define the scope of the "next empty" search, such as limiting it to the current page, color group, or the entire project. Benefits Enhanced Efficiency : Automating the selection of empty clips accelerates the recording process, allowing users to focus more on creativity and performance. Improved Live Performance : Reduces the need for manual navigation during live sessions, enabling smoother transitions and loop layering. Streamlined Clip Management : Simplifies the process of organizing and transferring clips, making project management more intuitive. This summary was automatically generated by ChatGPT-4 on 2025-05-08.