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.

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 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: Introduce new actions that allow users to toggle, focus, or switch between specific effect panels (e.g., EQ, Delay, Reverb) directly through widgets, MIDI, or keyboard shortcuts, without manually opening panels via the UI. Problem: Currently, users must navigate through the interface to open or switch effect panels. This process disrupts live performance flow or precise studio work. Lack of programmable control hinders complex setups where quick effect access is essential. Proposed Solution: Add dedicated action commands such as “Open EQ Panel,” “Toggle Reverb View,” “Cycle Effect Panels,” etc. Make these actions available in the action list for widgets, MIDI, and keyboard sources. Provide optional configuration settings (e.g., whether panel remains open or auto-closes after use). Benefits: Enables faster access to effects during live performance or mixing sessions. Works seamlessly with external controllers like footswitches or Stream Deck. Supports fluid workflow with minimal visual distraction or UI navigation. Examples: A foot pedal opens the Delay panel when pressed, then returns to Mixer view when released. A MIDI button toggles the Reverb panel on the fly to adjust wet/dry parameters. Keyboard shortcut cycles through all active effect panels without touching the screen. This summary was automatically generated by ChatGPT-4 on 2025-06-26. Original Post: Actions exist for opening/closing/toggling the UI display for effects. It would be VERY helpful to also add the other items in the title bar such as "Panel on Left, Panel on Right, Panel on Bottom). I like to have a button for my Guitar Tuner, for a VU meter, for an EQ, etc. I design certain screens specifically to allow me to swap out one or another of these effects displays on the bottom portion of the screen. Sometimes though I hit the wrong button and they move on me. If you are playing live, it can be a problem to correct the display. With an action I could ensure that a stomp pedal button would always no just open the proper effect UI, but also make sure it and all the rest are in their proper places. Thank you! Carl Lance

Description: Add support in Loopy Pro for iPadOS multitasking modes—Split View and Slide Over—so users can run Loopy Pro alongside other apps simultaneously. Ensure UI components and audio engine behave correctly when Loopy Pro is in a secondary window or floating overlay. Problem: On iPadOS 26, Apple removed traditional Split View and Slide Over functionality. In earlier iPadOS versions, Loopy Pro may not fully support multitasking window sizes, leading to UI glitches or audio issues. Users working with reference tracks, notes, or control apps face workflow interruptions without reliable multitasking support. Proposed Solution: Ensure Loopy Pro adapts dynamically to multitasking window contexts (Split View 50/50, 70/30, Slide Over overlay). Test and fix audio/MIDI, interface scaling, and gesture handling when windowed. Optionally, provide UI hints or preferences indicating multitasking compatibility status. Benefits: Enables seamless workflow with reference tools, notation apps, or control surfaces alongside Loopy Pro. Supports modern iPad productivity and live performance setups. Enhances flexibility for users combining Loopy Pro with communication or scoring apps. Examples: Practice along a YouTube tutorial in Slide Over while looping in Loopy Pro. Use Notes or Notion side-by-side with Loopy Pro in Split View during songwriting sessions. Run a MIDI controller app in the floating window while directing Loopy Pro in the main view. This summary was automatically generated by ChatGPT-4 on 2025-06-26. Original Post: At least in portrait mode when "Split View & Slide Over" is enabled in iPadOS 18.x, those tiny 3 dots on top of the screen are positioned very close to the name of the clips. If you want to rename them, It’s very difficult to touch the name field and not the 3 dots with your finger, and with the Apple pencil it’s almost impossible to double click and/or select the text box and change it (copy/paste). To make things even more congested, on top of the screen there is also the AUM multitasking gesture!!! The only workaround is to DISABLE Split View in iOS settings so those 3 dots do not appear and thus not hinder the touch UI. Please look into this because it’s very annoying! (iPad Pro 13 inch in portrait mode)

Description: Extend the functionality of the existing “Assign Clip Settings” action in Loopy Pro to allow users to predefine and assign multiple clip parameters—such as gain, pan, pitch, speed, accent, and mute/unmute—in a single action trigger. Problem: Currently, "Assign Clip Settings" only applies default clip preset settings or single parameters. To change multiple clip attributes, users need to trigger separate actions sequentially for each parameter. This process is time-consuming and inefficient, especially during live performance or rapid creative adjustments. Proposed Solution: Enhance the “Assign Clip Settings” action to include configurable parameter fields (e.g., gain -6 dB, pan +30%, pitch +2 semitones, fade-in, etc.). Allow combining multiple settings in one action. Expose these extended actions in all trigger contexts (widgets, MIDI, keyboard shortcuts). Benefits: Streamlines workflow by reducing the number of actions needed to customize a clip. Enables precise and consistent clip adjustments via single triggers. Ideal for live performance setups, repetitive routines, or dynamic clip manipulation. Examples: A widget triggers an action that sets clip gain to –3 dB, pan to left, and apply a pitch shift. MIDI controller button simultaneously applies volume level, mute, and filter settings on the selected clip. Keyboard shortcut loads preset clip settings (e.g., “Night Mood” = low gain + reverb + slow pitch shift). This summary was automatically generated by ChatGPT-4 on 2025-06-26. Original Post: The Assign Clip Settings action lets you change a setting from one state to another. I propose adding this functionality: Toggle - allow the action to toggle between one state and another eg. turning Hold to Play One Shots on and off. Value change - allow the action to change a range of values eg. using a fader to adjust the fade-out value.

Description This feature request proposes the implementation of 14-bit MIDI support within Loopy Pro to enable high-resolution control over internal parameters as well as those of hosted AUv3 plugins. Supporting 14-bit MIDI would dramatically increase the resolution of parameter adjustments—from 128 steps to 16,384—making Loopy Pro suitable for precision-critical use cases in live performance, sound design, and professional production environments. Problems Insufficient Resolution with 7-bit MIDI : Current MIDI support is limited to 7-bit (0–127) messages, which causes stepping artifacts when controlling parameters like filter cutoff, reverb amount, or pitch, particularly on high-quality AUv3 instruments and FX. Limited Expressiveness and Control : Power users and live performers using expressive hardware struggle to achieve the desired smoothness and nuance, especially when dealing with fine-tuned parameters like EQ bands, compressor thresholds, or pitch bends. Underutilized Hardware Capabilities : Many modern MIDI controllers (e.g. Electra One, Faderfox EC4, BomeBox) already support sending 14-bit high-resolution CC (including NRPN and RPN). Without support in Loopy Pro, these devices can't be fully utilized. Proposed Solution Full 14-bit MIDI Support : - Recognize and respond to 14-bit high-resolution MIDI Control Change messages (using MSB/LSB pairs). - Support both NRPN and RPN-based control messages. Enhanced MIDI Learn Engine : - Extend the MIDI Learn system to detect 14-bit CC pairs and assign them as high-resolution parameter sources. Visual Feedback for High-Res Bindings : - Clearly indicate when a parameter is being controlled via 14-bit resolution (e.g., with a visual tag or tooltip in the UI). AUv3 Integration : - Ensure that high-resolution control is passed through to hosted AUv3 plugin parameters that natively support fine resolution. Examples Precise Filter Sweeps : A performer uses an Electra One to send 14-bit CC data to control a synth’s cutoff frequency inside Loopy Pro, achieving silky-smooth filter movements with no audible stepping. Plugin Automation : A producer records high-resolution automation into Loopy Pro using a Faderfox EC4, adjusting reverb decay and EQ gain curves with surgical precision. Cross-Platform Consistency : A user coming from Bitwig or Logic Pro wants the same level of resolution with their MIDI controller when using Loopy Pro live on iPad or macOS. Device-Specific Expectations : Controllers like the Electra One , Faderfox EC4 , and setups using BomeBox or Axoloti expect 14-bit support and already send such data. Without support, Loopy Pro remains the weak link in an otherwise high-res control chain. Benefits Professional-Grade Precision : Ensures Loopy Pro is capable of delivering the same level of detailed automation and live control as top-tier desktop DAWs. Expanded Hardware Compatibility : Allows seamless integration with hardware that sends 14-bit MIDI—common in studio and touring-grade MIDI setups. Improved Sound Design and Live Control : Enables smoother real-time parameter morphing, better modulation routing, and more expressive performances. This summary was automatically generated by ChatGPT-4 on 2025-05-17.

Each item on the button grid to have it's own colour for better visual feedback.

I have assigned an effect on/off to the press of the Radio button, but since it looks the same, it is difficult to tell the current status. I would like the color of the button to change.

Description: This feature request proposes the implementation of a MIDI-controllable scrub/scratch deck widget in Loopy Pro. The goal is to enable users to manipulate the playhead position of audio clips in real-time using MIDI controllers, such as jog wheels or touch-sensitive surfaces. This functionality would allow for DJ-style scratching, precise cueing, and dynamic performance techniques within the app. Problem: Currently, Loopy Pro lacks a dedicated widget that allows for real-time, MIDI-controlled scrubbing or scratching of audio clips. Users seeking to perform such actions must rely on less intuitive methods, limiting expressive capabilities during live performances. Proposed Solution: Develop a widget that responds to MIDI input for controlling the playhead position of audio clips. Features should include: High-resolution MIDI mapping for precise control. Compatibility with various MIDI controller types (e.g., jog wheels, sliders). Options for different playback behaviors (e.g., scratch emulation, smooth scrubbing). Visual feedback within the UI to reflect playhead movements. A "Flux Mode" where, upon release of the controller or cessation of movement, playback resumes in sync with the original timeline position. Optional "Tape Stop/Start" effects that emulate the acceleration or deceleration of tape machines, with configurable durations in beats or milliseconds. Benefits: Enhanced live performance expressiveness. Integration of DJ-style techniques into Loopy Pro workflows. Greater precision in navigating and manipulating audio clips. Expanded creative possibilities for users. Examples: Using a jog wheel to scratch a vocal sample in sync with a beat. Employing a MIDI slider to scrub through a loop to find a specific cue point during a live set. Applying a tape stop effect at the end of a loop for dramatic effect. This summary was automatically generated by ChatGPT-4 on 2025-05-09. Original Post: I would love a widget, where I can use my external DJ-Controller (Denon, NI, etc...) or the touchscreen to scratch samples that I recorded or imported into Loopy Pro. This would make Loopy Pro very interesting for DJs and artists, that like to add live-scratching effects to their loops.