Feature Requests

Description Users should be able to rotate/offset the playback phase of clips, groups or overdub layers, either after recording or already before recording. The following two modes should be available: • Rotation starting from the original phase zero (default clip start) • Rotation relative to current position (i.e., continue shifting from already rotated point) Implementation should be available both via Actions and Clip Detail Window. Functionality • Offset/rotation for individual clips • Offset/rotation for: • selected clips (regardless of color) • all clips of a specific color • first overdub layer • last overdub layer • overdub layers marked as Reverse • overdub layers not marked as Reverse • Option to predefine an offset before recording (clip is recorded normally but played back shifted) • Resetting phase should also support ramping Offset Units • Multiple formats: • Degrees (e.g. 90°, 180°, 270°) • Percent (e.g. 67.20%) • Milliseconds (e.g. 71 ms) = Micro steps • Samples (e.g. 228 samples) • Beats, bars or fractional clip units (e.g. 1/8 bar, 1/16 beat, 1/8 clip) • Combine quantized values with micro steps (e.g. 1 bar + 71 ms) • Nudge offsets by bars, beats or ms Offset Triggers • Immediately • At next clip cycle • Relative to current playhead (e.g. now + x ms) • Relative to clip start (0° + x ms) Special – Trigger Follow Action When Offset Position Reached Allow triggering a specific follow action when a defined offset position of a certain overdub (or overdub layer) is reached. The user should be able to choose: • Trigger once on the first cycle only • Trigger every time the playhead passes the offset position • Trigger on the last cycle before stop or count-out Additional Options • Undo/Redo support for offset operations • Snap-based or quantized shift (e.g. snap to 1/16, 1/8, etc.) • Reset to original phase via action or gesture • Offset logic defined via formulas (e.g. Offset = overdub number × 1/16) Benefits • Musical precision and expressive performance tweaks • Ideal for latency correction, live improvisation, structured rhythm shifts • Great for drum programming or glitch effects This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable saving and recalling entire channel strips (including all plugins and optionally widgets) as presets. This allows fast loading of complex FX/instrument chains across different projects. Problem: Rebuilding plugin chains and settings for each project or channel type (input, color, bus, master) is time-consuming, especially in live setups or when consistent tone is needed across songs. Proposed Solution: – Add a feature to save a full channel (strip) as a reusable preset – Optionally include bound widgets and layout elements – Allow importing/exporting channel strip presets – Add "recall channel preset" and "save channel preset" actions – Allow presets for: – input channels – color channels – bus channels – master channel – Optional: grey out unloaded channels to free up RAM/CPU – Optional: preload (but inactive) channel strips for fast switching – Optional: include full widget configuration (position, behavior, etc.) – Add tags or labels to organize channel strip types (e.g. “Guitar FX”, “Vocal Bus”) Benefits: – Save time during project setup – Allows modular, reusable channel configurations – Supports consistent tone in live and studio workflows – Ideal for musicians switching instruments/effects between songs – Reduces CPU/memory load by offloading unused channels – Encourages structured and repeatable setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Loopy Pro users would like the ability to create multiple timeline regions within the sequencer, allowing for more flexible arrangements and looping possibilities. Problem: Currently, the sequencer only allows for one continuous timeline looping region. This limitation makes it challenging for users who want to set up more dynamic and flexible arrangements, especially during live performances or when experimenting with song structures. Proposed Solution: Implement the ability to define multiple timeline regions that can loop independently or in sequence. These regions should be customizable, with options for setting different loop lengths and behaviors. Additionally, an arrangement widget that functions like a master timeline would allow for quick restructuring during performances. Benefits: Enhanced flexibility for live looping and performance. Ability to experiment with different song structures without stopping playback. Improved workflow for users who want to set up looping regions with minimal interaction during performance. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Introduce automation tracks in the Loopy Pro sequencer that allow both manual drawing and real-time recording of MIDI CC data, including from external MIDI controllers or hardware synthesizers. Additionally, enable time-based automation triggers that can be set to occur after a certain number of bars in the arrangement. Problem: Currently, there is no way to record MIDI CC data over time or draw automation lines directly inside the sequencer. This makes it hard to automate effect changes, synth parameter modulations, or scene transitions with precision. Users must rely on dummy clips or static widgets to emulate automation behavior. Proposed Solution: – Add automation lanes/tracks to the sequencer view – Record incoming MIDI CC data in real time, including from hardware synths – Option to automatically record any incoming CC without manual mapping (like Logic or Ableton) – Allow drawing and editing of automation curves and values (e.g. volume, FX wet/dry, AUv3 parameters) – Visual representation of automation values over time – Automations can target AUv3, internal effects, or external MIDI destinations – Add timed Follow Actions: • Trigger any action after X bars have passed • Examples: unmute audio source X after 8 bars, disable effect Y after 16 bars – Allow assigning actions based on sequencer bar position (e.g. “do X on bar 129”) Community Input: – Users want to “tweak knobs” live and have the automation recorded and played back – Drawing value lines would allow for better control than dummy clips – Automations should work like in Ableton or Logic on iPad – BeatMaker was mentioned negatively due to its manual mapping requirement – Ideal for both clip automation and long-form arrangement control Benefits: – Complete automation workflow for effects, plugins and MIDI – Captures live synth or controller tweaks without setup hassle – Enables dynamic, evolving arrangements and transitions – Great for hybrid setups (hardware + iPad) – Significantly improves sequencing, especially for live performances and structured song-building This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: The feature request proposes the ability to copy, move, or swap actions between two widgets within Loopy Pro. This would greatly streamline workflow, especially when working with complex setups. Currently, there is no efficient way to transfer actions between widgets without manually recreating them. Problem: When setting up multiple widgets, it can be tedious to replicate or transfer actions, especially in scenarios where similar actions need to be applied across multiple widgets. The lack of a copy, move, or swap function leads to redundant manual work. Proposed Solution: Introduce a feature to easily copy, move, or swap actions between two widgets. This could be implemented with a "Pin" function that allows the user to mark a widget, then switch to another widget and choose to copy, move, or swap the actions. Additionally, the feature should support replacing existing actions when moving actions from one widget to another. Benefits: Saves time when managing complex action setups. Reduces the need for manual copying and configuration of actions. Improves workflow efficiency by allowing users to quickly duplicate or transfer action sets. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Enable stepped dials to have access to control loops and layers, allowing for more precise control over the looped and overdubbed audio layers directly through dial interactions. Problem: Currently, stepped dials do not have direct access to control loop and layer states, limiting their functionality for managing overdubs or triggering different layers in a loop. This reduces the potential for real-time performance control. Proposed Solution: Allow stepped dials to interact with and control specific loops and layers (e.g. controlling loop start/stop, triggering overdubs, adjusting volume, or switching between layers) Provide a way to map the dials to specific loop layers or overdubs so they can be accessed and controlled easily Allow for precise control of individual layers or loops via the stepped dial, including the ability to switch between overdubs and layers for more dynamic performances Optionally, add visual feedback for each layer/loop on the stepped dial to show which layer or loop is currently being controlled Benefits: Increases performance flexibility by giving real-time, hands-on control over loops and layers Enables more creative manipulation of overdubs and layered audio without needing to manually navigate through menus or screens Ideal for live performances or dynamic sound design setups Provides smoother transitions between loops and overdubs, enhancing workflow efficiency This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Allow users to send MIDI messages such as pitchbend, modulation, and other control changes through actions in Loopy Pro, enabling more dynamic MIDI control during live performances or automated workflows. Problem: Currently, Loopy Pro does not support sending pitchbend or other MIDI messages through actions. This limits the ability to automate MIDI controls and use pitch bending or modulation effects dynamically during live performances. Proposed Solution: Implement actions that allow users to send MIDI messages, including pitchbend, modulation, and other common MIDI CCs Allow users to specify the MIDI message type, target, and value within the action setup Integrate these actions with Loopy Pro’s existing MIDI and OSC control capabilities Provide a clear, easy-to-use interface for configuring MIDI message actions Optionally, allow for real-time control of MIDI messages via external hardware (e.g., MIDI controllers or foot pedals) Benefits: Enhances live performance flexibility by enabling dynamic MIDI control through pre-defined actions Allows users to automate pitch bending and modulation without external MIDI equipment Great for sound designers and musicians who require precise MIDI control during performances Provides a powerful way to integrate MIDI manipulation with Loopy Pro’s loop and clip-based workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the ability to set the project tempo in Loopy Pro based on a selected clip. The goal is to streamline the workflow by allowing the project tempo to automatically match the tempo of a chosen clip, which is particularly useful when working with pre-recorded material. Problems Manual Tempo Adjustment : Currently, users have to manually adjust the project tempo to match the speed of an imported clip, which can be time-consuming and imprecise. Lack of Automation : There is no direct method to automatically align the project tempo with a specific clip, slowing down the creative process. Limited Flexibility : Without this feature, it becomes more challenging to integrate clips of varying tempos into a cohesive project. Proposed Solution Clip-Based Tempo Detection : Implement a feature that analyzes the tempo of a selected clip and adjusts the project tempo accordingly. User-Defined Selection : Allow users to choose a specific clip whose tempo will serve as the reference for the entire project. Optional Activation : Include a toggle to enable or disable this feature as needed, offering flexibility based on different workflow preferences. Benefits Improved Workflow Efficiency : Automatically setting the project tempo from a clip saves time and reduces manual adjustments. Seamless Integration : Facilitates working with pre-recorded material and clips of varying tempos without disrupting the project structure. Enhanced Accuracy : Minimizes the risk of timing issues and ensures consistent project tempo. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Enable multiple clip selection within Loopy Pro to allow users to choose a set of clips they want to trigger together, and then activate all of them with a single widget or action. Problem: Currently, users can only select and trigger clips one by one. There’s no built-in method for pre-selecting several clips and launching them simultaneously in a controlled and flexible way, which limits advanced live workflows. Proposed Solution: — Implement a multi-clip selection system for "Next Selected Clip" actions: Option 1: – Allow a multiple selection mode when using "Next Selected Clip" – Small toggles (radio buttons) appear on each clip for selection – Each clip can be toggled on/off via tap or a specific play/record action – A second trigger of the same action (e.g. a widget or MIDI button) will execute the selection and start the selected clips Option 2: – Extend the current "Select Clip" action to allow additive selection – New variant of the action would allow "add to selection", "remove from selection" or "replace selection" — The selected clips can then be triggered together via: – A widget (e.g. button or pad) – MIDI bindings – Follow actions Benefits: – Enables flexible and intentional clip launching – Great for musical setups requiring complex layer control – Ideal for performance scenarios where clip groups need to be staged and then launched together – Non-destructive and intuitive for live users and composers – Adds a missing link between sequencing and live triggering workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.