Feature Requests

If I have a computer screen connected to my iPad, it would be good to have a second loopy per window. For example, you could operate the loops and controls on the Ipad, while the sequencer and the mixer are displayed on the screen.

Sometimes, a vocal part begins a half note before the bar. I would love Loopy to give me the ability to select where the bar beginning is in the loop and synchronize the loop so whenever starting it I can hear that beautifully groovy premptive word(s) before the bar groove takes over. Think Police’s « Roxanne », or the Beatles’ « All you need is love », or Prince’s « Purple Rain ». In the attached example, a yellow vertical bar marks where the bar starts. when the loop is activated, it should begin a bit before so the pre-start bit is played along with the rest in time. also, when the loop is deactivated, it should play until it’s very end: which is until the relooped part before the bar start.

Description: Add Actions to change a group’s mutual exclusivity behavior at runtime. This allows users to dynamically switch whether clips in a group can play simultaneously or whether starting one clip should stop the others. Problem: Mutual exclusivity is a powerful structural control (e.g., verse/chorus switching, one-of-many variations), but today it is typically a static configuration: Users may want the same group to behave differently at different times. - Example: during a build, allow layers to stack; during the main arrangement, enforce “only one at a time”. Without runtime control, users must create duplicate groups/pages or redesign clip layouts to achieve dynamic behavior. This limits performance flexibility and complicates controller-driven workflows. Proposed Solution: 1) Add group exclusivity Actions Provide Actions such as: Set Group Exclusivity: Exclusive / Non-Exclusive Toggle Group Exclusivity Optional: Set Exclusivity Mode variants if more than one exists (e.g., "Stop others on start" vs "Fade out others" if supported) 2) Scope and target selection Target a specific group by name/ID. Optional: apply to selected groups, or "current group". 3) Performance-safe timing (optional) Allow exclusivity changes to be: - immediate, or - quantized (next beat/bar) to avoid unexpected mid-bar stopping behavior. 4) Clear UI feedback Show an indicator that exclusivity was changed (and current state) to prevent confusion during performance. Benefits: Enables dynamic arrangement behavior without duplicating groups or redesigning layouts. Supports advanced performance macros: switch from “layering mode” to “section switch mode” instantly. Makes controller-driven rigs more expressive and less brittle. Reduces project complexity by keeping a single group that can change behavior when needed. Examples: Build-up layering: - Set group to non-exclusive so multiple clips can stack during a crescendo. - Then set group to exclusive for verse/chorus switching. Rehearsal vs show: - Non-exclusive during rehearsal for experimentation. - Exclusive during show for strict arrangement control. Footswitch macro: - One footswitch toggles group exclusivity while another triggers next clip, enabling different behaviors on demand. This summary was automatically generated by GPT-5.2 Thinking on 2026-01-09 . Original Post: An action to adjust group mutual exclusivity It would be great if there were an action to adjust group mutual exclusivity. This would allow me to easily create scenes on-the-fly.

AUM provides an Ableton Link offset adjustment feature. It would be great if Loopy Pro offered the same functionality.

I would like to have the option to select 8th ot 16th notes and triplets on the metronome

I tap tempo very often so i've put in on the most accessible button on my foot controller. This button is also quite easy to hit accidentally - sometimes even 2 times, which is enough to change the tempo. Happens quite a lot to me. Especially frustrating, 'cause tempo changes cannot be undone with Undo action. If I could set it to e.g. 4, I think it'd fix the issue - it's very low chance to tap 4 times accidentally in a short time

Description: Add an Action that selects a random preset for a chosen AUv3 plugin instance. The random selection should be usable from Actions, MIDI bindings, and Follow Actions, enabling controlled “happy accidents” and rapid sound exploration during performance and sound design. Problem: Preset browsing can be slow and distracting in live and creative workflows: Users often want fast inspiration (“give me a new sound now”) without scrolling long preset lists. Sound-design exploration benefits from quick randomization, but doing it manually breaks flow. Performance setups may want controlled variability (e.g., new texture each section) without touching the plugin UI. Without a built-in random preset action, users rely on external workarounds or abandon the idea. Proposed Solution: 1) New Action: "Select Random Preset" Target: a specific AUv3 plugin instance. Behavior: pick one preset at random and load it. 2) Define the preset pool (crucial) Provide options to constrain what “random” means: Source: Factory / User / Both Scope: Current bank/folder only (if applicable) or entire preset list Favorites only (optional) Exclude favorites (optional) Exclude current preset (default on) Optional “avoid repeats” window (e.g., do not repeat any of the last N presets) 3) Performance-safe switching (optional but valuable) Optional quantization: apply the new preset on next beat/bar to avoid abrupt mid-phrase changes. Optional short fade or “safe switch” mode (where feasible) to reduce pops/clicks. 4) Follow Actions + automation integration Allow Follow Actions to call "Select Random Preset" (e.g., at clip end, every N bars, on section change). Make the action bindable via MIDI so a footswitch can trigger “random next sound”. 5) UI/feedback Show the newly selected preset name immediately (in the AUv3 preset area and/or a small toast). If no presets exist in the selected pool, show a clear message and do nothing. Benefits: Faster sound exploration and inspiration without breaking creative flow. Enables controlled variability in live sets (new preset per section/loop/run). Reduces reliance on manual preset browsing and plugin UI navigation. Makes AUv3 preset workflows more performable and “instrument-like”. Examples: Sound design discovery: - A single button triggers "Select Random Preset" on a synth instance, excluding the current preset and avoiding the last 10 repeats. Live variation: - At the end of a clip, a Follow Action selects a random preset from Favorites only, quantized to the next bar. Foot-controlled exploration: - A footswitch triggers “random preset” on a texture plugin while playing, keeping hands on the instrument. This summary was automatically generated by GPT-5.2 Thinking on 2026-01-09 . Original Post: It would be amazing if button widgets etc had the ability to select a random preset from a defined list of presets for an effect or device (Similar to how the dial widget can select from a list of presets). This would make for some very fun improvisation

Description: Loopy Pro users would benefit from a feature allowing them to set a project key and automatically convert imported melodic loops to the current key. This functionality is particularly useful for loops from external sources (e.g., BlocsWave), where pitch correction to match the project key is essential. Problem: Imported loops may not match the project key, requiring manual adjustment. This can be time-consuming and impractical when dealing with multiple samples. Current solutions like Launchpad can apply pitch shifting globally, per group, or per clip, but they rely on metadata (e.g., filename information) rather than analyzing the audio content itself. Proposed Solution: Allow users to set a global project key in Loopy Pro. Provide automatic pitch detection for imported loops, adjusting them to the set key. Include options for common pitch modifications, such as: - Current key ± 5th up/down - Current key ± 1x and 2x octave up/down Enable a pitch wheel for manual adjustments, similar to Launchpad's functionality. Benefits: Streamlined workflow when integrating external loops. Minimizes the need for manual pitch correction. Ensures harmonic consistency across the project. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Currently, Loopy Pro’s session recording captures either a combined mix of all tracks or whole input/output groups. The request is to allow users to select individual tracks (e.g. specific loops, inputs, buses) to include in or exclude from the session record. Problem: Recording always captures everything passed through the mixer (e.g. combined inputs/outputs), making it impossible to isolate specific elements. Users can’t choose to record only certain tracks or stems, limiting flexibility for multitrack recording workflows. This current limitation hinders recording individual loop layers separately or exporting stems for mixing in a DAW. Proposed Solution: Add a UI for session record configuration that lists all tracks/buses/inputs. Allow users to toggle on/off each individual track for inclusion in session recording. Recording session should then produce separate audio files per selected track, similar to the “Individual Outputs” feature but user-selectable. Benefits: Supports flexible multitrack recording and stem exporting workflows. Enables deeper integration with external DAWs by providing isolated tracks. Enhances user control over what is captured during live or studio sessions. Examples: Record only drum and bass loops into separate files while excluding vocal loops. Capture just the guitar input along with selected loops for focused editing. Include only bus outputs for stems like “drum bus” or “synth bus”. This summary was automatically generated by ChatGPT-4 on 2025-06-10. Original Post: Sometimes I have unused bus’s and recording them all is wasting space.

Description: Allow users to defer project tempo detection to a loop other than the first — enabling Loopy Pro to set the project tempo based on a later, user-selected loop. Problem: Currently, Loopy Pro determines and locks the project tempo based on the very first recorded loop. This limits flexibility in sessions where the first loop is not rhythmically relevant or is intended to be free-tempo (e.g. ambient texture, drone, or vocal swell). Users have no option to tell Loopy Pro to wait and derive the tempo from a different, later loop that better represents the intended timing. Proposed Solution: Add a feature that allows users to: Bypass tempo detection from the first loop Optionally choose which loop (e.g. second, third, or any later one) should define the project tempo Or let Loopy Pro auto-detect tempo from the first rhythmically meaningful loop This could be implemented as a toggle or dropdown in the project/session settings. Benefits: Greater control over when and how project tempo is set Enables free-form intros and ambient starts without locking the grid too early Better suited for complex arrangements and live workflows where rhythm develops gradually Improves compatibility with creative, non-linear loop layering Examples: First loop: ambient pad (no timing) → ignored Second loop: rhythmic guitar riff → sets tempo Third loop: beatbox loop → sets tempo while earlier ones remain unquantized This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Currently, LP fix the project tempo thanks to the first loop recorded. The aim of this new feature is for LP to fix the project tempo thanks to the detection of the tempo of a loop other than the first one (or first ones pre-chosen).