Feature Requests

Description: Introduce visual feedback for text widgets when they are triggered or active, similar to button widgets. Since text widgets do not have a visible body by default, state feedback could be implemented through color changes, such as text inversion or background highlighting. Problem: Unlike button widgets, text widgets currently offer no visual feedback when triggered. This makes it difficult to confirm whether a text-based trigger has been activated during performance or editing. The lack of state indication reduces usability for workflows that rely on text widgets as controls. Proposed Solution: Implement state feedback via visual changes such as: – Inverting text and background colors on trigger – Switching from default (e.g. white) to a user-defined highlight color Ensure the feedback is optional and configurable for each widget. Benefits: Provides immediate visual confirmation of trigger or toggle state. Makes text widgets more usable as interactive controls. Enhances accessibility and confidence in live setups. Examples: A text widget labeled “RECORD” turns red when activated. Text inverts to black-on-white when toggled, and reverts when idle. Color changes only last during the trigger state or remain toggled until reset. This summary was automatically generated by ChatGPT-4 on 2025-07-05. Original Post: Text widget state feedback Same as for the button, but because there is no "body" for the text widget, maybe a reasonable solution is to invert the color of the text widget. Or the default state is "white" and triggered is a specific color.

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: Add an option to toggle anchoring on or off for individual text widgets in the Text Edit window. This would allow some text widgets to remain anchored to screen positions, while others can be freely placed anywhere within the canvas. Problem: Anchoring is powerful and useful, especially for structured templates. However, there are situations where a user may want to position a text widget arbitrarily, without it snapping or sticking to layout constraints. Currently, anchoring behavior is not individually configurable, which limits flexibility for design workflows. Proposed Solution: Provide a per-widget toggle to enable or disable anchoring. When anchoring is off, allow freeform positioning within the canvas. This toggle should be easily accessible in the Text Edit window or widget settings. Benefits: Supports hybrid layouts with both structured and freely placed text elements. Enhances creative flexibility, especially in templates and visual arrangements. Enables users to preserve the power of anchoring without being restricted by it. Examples: Anchor one text label to the top-left corner, while placing another label arbitrarily for visual effect. Use precise anchored alignment for controls, and unanchored notes for user guidance or temporary info. This summary was automatically generated by ChatGPT-4 on 2025-07-05. Original Post: On/Off text anchoring inside Text edit window So I can set one Text widget sticking but another one is not. While anchoring is amazing and it is one of my core trick for my new template, sometimes I want to place text at a random position.

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: 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: 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: 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.

Request the ability to switch or control color destinations dynamically via actions. This enables workflows like toggling between routed effects (e.g., routing mic input only to one clip to avoid feedback, then switching it mid-set). Use case examples: – Route a signal (e.g. mic input) between colors during performance – One XY pad can control FX across color groups, switching dynamically – Multiple plugins mapped to the same controller, with the ability to target different color destinations Essential technical expectation: FX tails (e.g., reverb, delay) should not be cut off when color destinations are switched. The previous color's tail should remain active and fade naturally, preserving sonic integrity. This summary was automatically generated by ChatGPT-4 on May 2, 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: Add the ability to control MIDI transposition amount via widgets or buttons within Loopy Pro. Problem: Users currently lack a direct and flexible way to control MIDI transposition on a specific channel in real time. This makes it difficult to adapt to different keys or transpose input on the fly, especially when performing or working with MIDI controllers or apps like Onsong. Proposed Solution: Provide widget actions to increase/decrease or set MIDI transposition value per channel. Allow widgets like buttons, sliders, or dials to control this. Make transposition optionally recallable and automatable for live use (e.g. key changes). Benefits: Enables key changes and MIDI mapping workflows directly via touch or MIDI-bound widgets. Essential for users working with live MIDI input, key-based instruments, or backing tools like Onsong. Aligns with other MIDI control needs (e.g., LFOs, scale mapping), providing consistency in the interface. This summary was automatically generated by ChatGPT-4 on 2025-05-02.