Feature Requests

Description: Implement a feature in Loopy Pro that provides a quick-access shortcut or button to open the folder where the active project is currently saved. This could be via context menu, toolbar icon, widget, or keyboard/MIDI action. Problem: Users often need to locate project files (loops, audio stems, settings) in the filesystem but must navigate manually through directories. This process is time-consuming and disrupts workflow, especially when exporting, importing, or sharing project components. Lack of a direct shortcut increases friction during fast-paced live performances or studio sessions. Proposed Solution: Add a “Reveal in File Manager” action that opens the current project folder in Finder (macOS) or File Explorer (Windows). Optionally provide this as a UI element—such as a toolbar button or widget you can place anywhere. Also support triggering via keyboard shortcut or MIDI/stream-deck action for fast, hands-free access. Benefits: Streamlines file management tasks related to the active project. Saves time when exporting stems, backing up, or collaborating. Enhances efficiency during performance and production workflows. Examples: One-click access to the folder containing audio files for rapid drag-and-drop export. Instantly navigate to project assets to share with collaborators. Use a dedicated Stream Deck button to open project files during a live set. This summary was automatically generated by ChatGPT-4 on 2025-06-26. Original Post: Description: Add option to open the folder where the current project is located instead of opening of projects root folder Problem: Currently, each time a user opens the project browser, it defaults back to the top root level. This disrupts workflow, especially when repeatedly working within a specific folder. Even more frustrating when there are more complex folder structure. E.g. If I have opened project from folder structure Songs/Folk/Native and I want to go to other project in the same folder I have to click to folder button in the upper left corner, then click to Projects, then click to Songs, then click to Folk, then click to Native and finally choose project. Proposed Solution: Add a toggle setting that allow to directly reopens the folder where the current is located on. Benefits: Saves time by reducing repetitive navigation. Improves workflow efficiency, particularly during live performance preparation. Provides a more seamless and intelligent user experience across sessions.

Problem: Text in Loopy Pro widgets is static – there’s no way to display live values like AUv3 or MIDI, or to show dynamic status feedback. Users can’t show the value of a fader or knob, nor adapt text visibility, size or content dynamically. Proposed Solution: Text binding to controls: Let text widgets display live MIDI values from bound faders or knobs Placeholder system with support for: - $project.name$ , $bar.current$ , $channel_name_1$ , $AUv3_post_3$ - Current/total clip layers, named layers - Clip colors, groups, AUv3 plugin parameters User-defined labels for value ranges , e.g. 30–155 Hz = “Rumble”, 1000–3000 Hz = “Medium” Conditional formatting & visibility - Show exact value only while knob/fader is touched - After a delay, return to label display (e.g. "Range name") Text resizing logic - Auto-scale font size with widget/canvas changes - Manual ± font size per widget Formula-based expressions , like SWITCH(...) Text changes via actions , e.g. “Set label to: VERSE” Benefit: Real-time, intelligent feedback in the UI itself No need for extra screens or MIDI displays Clear overview of dynamic values, actions and playback states Great for live performance, section navigation, parameter feedback and more Customizable and responsive interface that adapts to user interaction Extension: Define Dynamic Behavior for Each Placeholder Ideally, each placeholder should have its own display logic – controlling when and how it appears. Examples: Always visible (default) Only visible during interaction , e.g. while a fader or knob is being moved Visible for a short time after interaction , e.g. 1 second after release Conditionally visible , e.g. only when a clip is playing or a value is in a certain range Toggle visibility via actions or logic This would allow for highly adaptive and context-aware UIs – showing the right info at the right moment without visual overload. It would give Loopy Pro a unique edge as a flexible, user-definable performance environment. This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Add an optional visual effect to clips in Loopy Pro that triggers once they have been played (e.g., border glow, color overlay, fade), helping users track which clips have been triggered in a session. Problem: During live looping sessions, it’s easy to lose track of which clips have already been triggered, especially in complex or dense arrangements. Current UI doesn’t provide persistent feedback after clip playback ends, causing potential confusion and missed entries. Users must mentally remember or rely on clip positions alone, increasing cognitive load and the risk of performance errors. Proposed Solution: Offer a toggleable visual effect for played clips (e.g., temporary glow, color fade, checkmark overlay). Allow configuration of duration and style—immediate fade, persistent markers, pulse animations, etc. Effects should not interfere with performance or obscure clip content; subtle and configurable is key. Benefits: Instantly shows which clips have been used during a session. Enhances situational awareness and performance flow. Reduces the chance of unintentional re-triggering or omission of clips. Examples: After triggering a loop, its thumbnail briefly pulses or glows to indicate activity. Played clips retain a faded overlay until reset or until a new session begins. User can set a checkmark badge on clips that have been triggered at least once. This summary was automatically generated by ChatGPT-4 on 2025-06-26. Original Post: Add a "Played/Unplayed" status to clips (loops and one-shots), and a toggle in clip settings which enables automatically setting their status to Played after they have stopped playing. If a clip's status is played, it will be visually altered - either dulled, so it is darker than unplayed clips, or its outer border can be dotted instead of solid. Also, add an Action to change clips' (individual clips, colour groups, global clips) Played/Unplayed status by trigger, so you can make a button that resets all clips' status to Unplayed, or use a gesture to reset a specific clip's status, etc.

Description: Enable the ability to selectively mute, unmute, or delete individual MIDI notes and/or CC automation data within a specific clip in Loopy Pro. This would allow finer control over MIDI editing, particularly for freestyle composition and live arrangement workflows. Problem: Currently, users cannot isolate and remove specific elements within a MIDI clip (e.g. a single drum note or CC line). For example, muting or deleting a hi-hat from a full drum pattern is not possible without recreating the clip entirely. CC automation is treated as a monolithic layer, making it difficult to manage or isolate multiple modulation lanes within one clip. Proposed Solution: Add the ability to mute or delete individual MIDI notes or ranges within a clip. Implement per-lane control for CC data, allowing mute, solo, or deletion of specific CC lines. Integrate these functions via contextual actions, clip editors, or MIDI learn-style gestures. Benefits: Provides deeper MIDI clip editing capabilities without destructive workflows. Enhances creative flexibility for on-the-fly arrangement and live composition. Enables targeted modification of individual layers (e.g. hi-hats, snares, modulation curves) without affecting the entire clip. Examples: Mute just the hi-hat notes in a MIDI drum pattern during a breakdown section. Delete only one CC1 (modulation) automation curve while preserving CC11 (expression). Create variations of a groove by toggling muted MIDI notes live. This summary was automatically generated by ChatGPT-4 on 2025-06-30. Original Post: Muting notes and CCs will give deeper control on MIDI for freestyle/composing sessions. Let's say I have a midi drum pattern and I want to remove one element of the groove by muting or deleting it, currently we can't do that. Or we can't delete just "hihat" sequence to record another one on the fly. Same with CC lines, if we have multiple automations inside a clip, there no way to manage them.

Description: Introduce a “Select None” option in the clip action assignment interface, allowing users to clear existing actions from a clip without reassigning new ones. Problem: Currently, users cannot remove an assigned action from a clip easily; they have to overwrite it with another. This limitation complicates workflows where users want to disable an action temporary or reset a clip’s behavior. Removing actions often requires manual reconfiguration or workarounds. Proposed Solution: Add a “Select None” or “Clear Action” entry in the action dropdown menu for clips. Choosing this option removes any action binding from the clip. Ensure this clears visual indicators and disables associated triggers without affecting other clips. Benefits: Empowers users to disable clip actions easily and revert clips to default state. Enhances flexibility in dynamic setups, enabling quick changes without overwriting. Simplifies editing workflows and setup clean-up processes. Examples: Remove a clip’s “Mute” action during live performance without assigning another. Reset clip behavior in templates by clearing unwanted actions in bulk. Temporarily disable a clip-triggered effect and re-enable later by assigning a new action. This summary was automatically generated by ChatGPT-4 on 2025-06-30. Original Post: I imagine this would be very easy to add so I'll keep it brief.. Under Clip Actions > Select, can we please have the ability to select 'None'. I use clip select sometimes but other times I don't want anything to be selected (like when you first open a project). Thanks!

Description: Enable more flexible clip targeting by allowing selection based on both Colour and Play Group simultaneously. This eliminates the need for switching profiles on MIDI controllers just to target different Play Groups. Problem: In setups with multiple Colours and Play Groups, users often rely on MIDI controller profiles to switch between control targets. For example, a 6×4 grid controlled by a MIDI foot controller may require profile changes to address different Play Groups. Profile switching can cause visual glitches (e.g., flashing buttons on devices like the APC40 mkII) and disrupt live performance flow. Maintaining duplicate profiles adds unnecessary complexity. Proposed Solution: Allow clip selection using both Colour and Play Group together (e.g., “First Yellow Clip in Play Group 1” or “Next Empty Orange Clip in Play Group 3”). Optionally support setting a Control Group (or multiple) as active, so MIDI or button actions only affect those, without switching profiles. Benefits: ✅ Eliminates the need for profile switching in complex control scenarios ✅ Avoids disruptive controller behavior during live performance ✅ Enables faster and cleaner MIDI controller programming ✅ Simplifies setup and reduces configuration time ✅ Minimizes maintenance overhead when updating layouts This summary was automatically generated by ChatGPT-4 on 2025-06-30. Original Post: Description: Enable more flexible clip targeting by allowing selection based on both Colour and Play Group, eliminating the need for profile switching on MIDI controllers. Problem: I have a grid of 6 Colours by 4 Control Groups that I am controlling using 6 buttons on a MIDI foot controller (one for each colour), with Profile changes to control the selected Play Group. While my current setup achieves the needed functionality, switching profiles causes some buttons on devices like the APC40 mkII to flash briefly, presumably because they need to resync with the new Profile. This is distracting and makes the setup feel less robust. Proposed Solution: – Allow clip selection based on both Colour and Play Group (e.g., “First Yellow Clip in Play Group 1” or “Next Empty Orange Clip in Play Group 3”) – Alternatively or additionally, support setting a specific Control Group (or multiple) as active, and allow button/MIDI actions to target only the active group(s) — without requiring a change in MIDI Profile Benefits: ✅ Eliminates the need for profile switching in this scenario ✅ Avoids disruptive profile switching during live use ✅ Enables faster programming of MIDI controllers ✅ Speeds up and simplifies setup ✅ Saves time by eliminating the need to maintain duplicate profiles when updating controller layouts * written by chatgpt - excuse the strange and repetitive language (in the video you can see my APC40 flashing as I change between Profiles)

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: Enable a "MIDI Learn" mode for external plugin parameter controls within Loopy Pro. This feature would allow users to map hardware MIDI controllers (knobs, faders, pads) to automate plugin parameters like cutoff, resonance, mix level, and more using an intuitive learning workflow. Problem: Currently, users cannot dynamically assign MIDI hardware to control parameters of loaded external plugins. Each parameter must be manually adjusted via touchscreen, hindering hands-on performance and tweaking. Lack of MIDI mapping limits integration with hardware controllers and slows creative workflow. Proposed Solution: Introduce a dedicated MIDI Learn mode within the plugin interface. When activated, moving a desired MIDI control triggers a learn event, prompting the user to assign it to a specific plugin parameter. Allow users to save and recall MIDI mapping presets per plugin or overall project. Benefits: Enables tactile control over plugin parameters for live performance and studio use. Streamlines mapping workflows, reducing setup time and increasing flexibility. Enhances integration with MIDI controllers like Launchpad, MIDI Fighter, Novation Launch Control, Stream Deck, etc. Examples: Use a MIDI knob to adjust a plugin’s filter cutoff in real time during live performance. Map faders on a MIDI control surface to plugin mix and wet/dry parameters. Recall saved MIDI mapping presets when switching between different effect plugins. This summary was automatically generated by ChatGPT-4 on 2025-06-26. ** Original Post: Ability to learn midi by tap from external plugins window. I have a loopy pro midi AU, but when i tap to learn midi from it, the learn state automatically switching off. So i forced to go manually to assign all my buttons. Ideally I wish the solution was where LoopyAU doesn't require midi, but works transparently with a LoopyHost. So it actually is like a widget which can catch up with different parameters to select them directly.

Description: Integrate high-quality octave and pitch-shifting effects directly into Loopy Pro, either natively or by enabling access to system-level AU pitch effects like Apple’s AUPitch. Problem: While Loopy Pro supports AUv3 effects, users seeking clean, adjustable pitch-shifting—especially for live use—are currently limited. Notably, Apple’s AUPitch effect sounds better and provides more control than AUNewPitch, yet it is not easily accessible in Loopy Pro outside GarageBand. This creates a barrier for users needing reliable pitch control for vocals, instruments, or creative FX chains. Proposed Solution: – Make Apple’s AUPitch accessible within Loopy Pro as an effect option – Alternatively (or additionally), develop native Loopy Pro pitch/octave shifter with high-quality algorithms – Include real-time control via MIDI/automation – Offer parameters like coarse/fine pitch shift, formant control, mix/dry, and stereo width – Ensure low latency and stable performance suitable for live performance scenarios Benefits: ✅ Unlocks access to Apple’s superior pitch-shifting algorithm for Loopy Pro users ✅ Provides musicians with high-quality real-time pitch manipulation tools ✅ Useful for harmonizing, vocal doubling, creative sound design, and instrumental FX ✅ Helps avoid needing GarageBand or third-party hosts just for AUPitch access ✅ Makes Loopy Pro more self-contained and powerful as a live processor This summary was automatically generated by ChatGPT-4 on April 30, 2025.

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.