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 advanced comping and multi-take recording workflows by allowing users to record loops in continuous overdub mode, where each overdub is treated as a separate "take". Provide an interface to select, preview, and combine takes after recording. Useful for songwriting, refining loops, and selecting the best performance. Problem: Currently, Loopy Pro doesn’t offer a dedicated take management system. Users cannot easily select from past overdubs or compile a composite loop from multiple takes. There's no support for comping workflows as seen in DAWs, which limits its use in detailed arrangement or songwriting sessions. Proposed Solution: – Allow continuous overdubbing where each layer is saved as an individual take – Provide a “loop re-record until tap” mode with last-take selection – Add a clip context menu or hold gesture to open a “Take Selection” window – Integrate zoom and grid snap for precise part selection (similar to AudioShare) – Enable MIDI-assignable switching between takes or random playback of takes – Allow replacing or inserting specific takes with velocity/FX presets (e.g., fade, stutter, LFO) – Option to play newly recorded overdubs in reverse – Quantized insert/replace options – Add support for slice-based comping (e.g., select bar 1 from take A, bar 2 from take B...) – MIDI long/short press behavior to control insert/replace start and stop – Append-before/after actions for looping logic – Temporal “takes” timeline overlay or pop-up to drag/select preferred versions – Enable randomized take playback for generative loop evolution Benefits: ✅ Unlocks powerful songwriting and loop refinement workflows ✅ Makes Loopy Pro more DAW-like for structured clip editing ✅ Adds creative options like reversed overdubs and stuttered inserts ✅ Great for live performance and recording multiple takes without stopping ✅ Brings best of “multitaking” and “comping” to Loopy Pro in an intuitive way ✅ Enables precise control and creative decision-making post-recording ✅ Makes Loopy Pro more competitive with DAWs like Logic and Cubasis for clip-based workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable pinch-to-zoom functionality in the canvas edit screen to allow users to zoom in and out while editing widgets and layout elements. Problem: Editing small elements or navigating dense canvases with many rows and columns can be cumbersome, especially on smaller screens like iPhones. Precise placement and alignment become difficult without zoom support. Proposed Solution: – Implement standard pinch-to-zoom gestures in the canvas edit mode – Allow zooming in for detailed work and zooming out for overview navigation – Maintain full interaction with elements while zoomed (drag, resize, etc.) – Optionally display current zoom level for orientation Benefits: – Improves precision and usability when working with complex layouts – Makes editing possible and pleasant even on small screen devices – Speeds up UI creation and editing by reducing scrolling and repositioning – Aligns with user expectations for standard gesture support This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Refine and enhance the user interface for binding effect parameters using XY pads and sliders, especially during the mapping process. Problem: When binding FX parameters to UI widgets like XY pads or sliders, the current UI provides little feedback or precision control. It can be difficult to visualize which parameter is being assigned, what the current value range is, and how multiple assignments are layered or combined. This lack of clarity can lead to mistakes or inefficient binding workflows, particularly when working with multiple FX or complex modulations. Proposed Solution: Improve the parameter binding interface for XY pads and sliders by: Clearly showing the parameter being assigned during touch or drag Displaying value ranges (min/max) visually Allowing real-time feedback of parameter value while moving the control Optionally showing all currently assigned parameters and their respective axes or directions Providing undo/reset binding options directly in the context UI Benefits: Makes FX parameter binding more intuitive and visual Reduces trial-and-error during widget setup Enables precise control for live performance and sound design Aligns UX quality of effect binding with the polish found in other Loopy Pro editing interfaces Examples: Touching a slider shows a tooltip with assigned parameter and current value Binding a second parameter to the Y axis of an XY pad highlights both X and Y roles clearly Real-time movement reflects changes on the FX UI for better understanding This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Currently the XY pad UI is pretty limited, allowing you to just select effect parameter targets. Would be good to add some extra options, like what to do on release (reset to some value?), and double-tap. This can all be set up by opening up custom mode, but it's a bit of a pain to have to manually pick the parameters again for each action.

Description: Allow users to group multiple AUv3 plugins into a reusable "plugin group" that behaves like a single plugin container. This makes management easier and introduces powerful features at group level. Problem: Managing multiple plugins on a channel becomes complex. There is no way to treat a combination of AUv3s as a single, unified module. Also, many plugins lack a wet/dry mix and other basic options. Proposed Solution: – Treat plugin groups as if they were individual plugins – Groups show up in plugin lists (add to project, add via action, etc.) – Allow instantiating multiple plugin groups – Allow actions to apply to the group as a whole (e.g. enable/disable) – Provide group-level settings: • Group name (user-defined or internal) • Wet/dry mix control for the group • Reorder plugins in the group • Actions to enable/disable the group – Display group with visual indicators (e.g. folder-style icon, color tag, red/green circle for status) – Allow edit mode and save as preset or duplicate – Restrict to only unused plugin instances (avoid duplicate references) Stretch Goals: – Group presets for wet/dry mix and plugin order – Icon sets to help users identify groups – Choose from visual folder/container symbols – Future option to include plugin parameter presets per plugin inside the group Benefits: – Modular plugin workflow – Reusable effect chains – Add missing features like wet/dry to plugins that lack them – Better project organization – Faster setup and management – Enables actions and visual feedback at group level This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Users would like to have a new type of loop specifically designed for automation within MIDI learning workflows. This loop type would exclusively record automation data, never audio, allowing for precise control over MIDI parameters. Problem: Currently, there is no dedicated loop type that can record and manage automation separately from audio. This limitation makes it difficult to create complex automation sequences, especially when using MIDI learning for live performances or automation stacking. Proposed Solution: Introduce an "Automation Clip" that functions solely as a container for MIDI automation data. These clips could support overdubbing, stacking, and be triggered via button presses or gestures. Additionally, users should have the option to combine one-shots or loops to control sequences and playback of other clips. Benefits: Enhanced control over MIDI automation workflows. Allows for complex automation stacking and precise triggering. Facilitates more dynamic live performances by separating audio and automation loops. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes enhancing the Clip Slicer in Loopy Pro to support multiple clip targets simultaneously. Currently, the Clip Slicer is limited to controlling a single clip, which restricts its utility in complex performance setups where simultaneous control over multiple clips is desired. Proposed Solution Multiple Clip Targeting : Enable the Clip Slicer to assign and control multiple clips concurrently, allowing for synchronized slicing and triggering across several clips. Group Control Mechanism : Introduce a grouping feature within the Clip Slicer to manage multiple clips as a single entity, facilitating collective actions such as play, stop, and slice. User Interface Enhancements : Update the Clip Slicer interface to accommodate multiple clip selections, providing clear visual indicators for each targeted clip. MIDI and Action Integration : Allow MIDI mappings and actions to be assigned to the group of clips controlled by the Clip Slicer, ensuring seamless integration into existing workflows. Problem Limited Control : The current single-clip limitation of the Clip Slicer hinders the ability to perform complex slicing operations across multiple clips, reducing creative flexibility. Inefficient Workflow : Managing multiple clips individually for slicing operations increases the complexity and time required during live performances or intricate arrangements. Inconsistent Synchronization : Without the ability to control multiple clips simultaneously, achieving tight synchronization between sliced clips becomes challenging. Benefits Enhanced Creative Flexibility : Supporting multiple clip targets allows performers to experiment with complex slicing patterns and arrangements, expanding creative possibilities. Streamlined Workflow : Managing multiple clips through a single Clip Slicer reduces setup time and simplifies live performance operations. Improved Synchronization : Simultaneous control over multiple clips ensures consistent timing and synchronization, essential for cohesive performances. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Introduce a new type of clip: AUv3 Clips. These would function similarly to Audio and MIDI Clips, but are directly tied to AUv3 plugins. Each clip could instantiate and control its own AUv3 plugin instance with specific state, allowing highly modular, per-clip plugin behavior. Problem: Currently, AUv3 plugins must be assigned at the channel level, limiting flexibility. If a user wants a specific plugin to behave differently across different clips, they must use multiple channels, which becomes inefficient and cluttered. There is no way to encapsulate AUv3 plugin states within a clip itself. Proposed Solution: – Add a third clip type: AUv3 Clip – Each AUv3 Clip can load and store its own AUv3 plugin instance and state – Clips can load different plugins, presets, or plugin configurations – Include per-clip plugin automation and recall – Allow AUv3 Clips to be used in the sequencer and timeline like any other clip – Support seamless switching between clips with different AUv3s, without audio dropouts – Provide options to pre-load plugins or load on activation to optimize performance Benefits: ✅ Enables highly modular setups with clip-specific sound sources ✅ Allows radically different processing chains per clip without extra channels ✅ Makes Loopy Pro more DAW-like while staying loop-oriented ✅ Ideal for creative sound design, plugin chaining, and live performance setups ✅ Simplifies session organization and expands creative potential of the clip model This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce new clip action targets that allow actions to be applied to random clips or empty clips of specific colors, as well as to exclude certain colors from being targeted. Problem: Currently, Loopy Pro doesn’t allow users to target random clips or empty clips of a specific color or group, limiting the ability to perform actions dynamically across multiple clips. Proposed Solution: Add new clip action targets to: - Random clip (of a specific color) - Empty clip (of a specific color) - Random clip (of all colors but exclude specific colors) - Empty clip (of all colors but exclude specific colors) The ability to execute actions such as play, stop, mute, or trigger specific effects on random or empty clips based on the defined color conditions. Benefits: Greatly enhances dynamic control over multiple clips, especially in live settings or with large projects Allows more creative freedom in automating clip behaviors Simplifies workflows where certain clips need to be triggered or altered randomly without affecting others Provides finer control over clip selection and action application based on color or status (empty/full) 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.