Feature Requests

Description: Improve Loopy Pro’s audio engine by enabling true multi-core (multi-threaded) CPU processing for audio rendering, especially useful with multiple AUv3 plugins and parallel signal paths. Problem: Currently, Loopy Pro does not seem to fully utilize multi-core CPU processing for audio tasks. This can quickly lead to CPU overloads in complex projects with several AUv3 plugins, effects, or multiple audio channels – even on high-end iPads. Proposed Solution: – Implement multi-threaded audio rendering – Distribute AUv3 plugin processing across available CPU cores – Prioritize per-track or per-plugin parallelization – Dynamically allocate threads based on system load – Add CPU usage per-core display (optional) Benefits: – Much better performance on modern multi-core CPUs – Lower risk of audio glitches and dropouts – Enables more complex, creative setups with more plugins – Extends device longevity by improving resource efficiency – Makes Loopy Pro more competitive as a DAW alternative This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable Loopy Pro to access and route individual outputs from multi-output AUv3 plugins. This would allow users to handle complex signal routing within Loopy itself, without needing to rely on external hosts like AUM. Problem: Currently, Loopy Pro does not expose the individual outputs of multi-output AUv3 plugins. As a result, users cannot route separate channels (e.g., drum parts or stems) to different buses, apply individual effects, or send them to discrete hardware outputs. This makes advanced mixing setups cumbersome and forces users to rely on external apps. Proposed Solution: – Detect and expose multiple output channels from AUv3 plugins – Allow routing of each AUv3 output to a different Loopy Pro bus or track – Enable per-output effect chains (e.g., reverb on snare, delay on hi-hats) – Permit discrete outputs to be routed to specific physical outputs on an audio interface – Maintain compatibility with AUv3 instruments like Digistix, Hammerhead, FAC Drumkit, Loopy AU (backing tracks), etc. – Provide clear UI to manage output-channel mapping within Loopy Pro’s mixer or plugin settings Benefits: ✅ Gives users full control over plugin output routing inside Loopy Pro ✅ Eliminates the need to use AUM or other routing apps for multi-output AUv3s ✅ Supports pro-level mixing setups with buses, FX, and separate audio interface outputs ✅ Makes Loopy Pro a more complete AUv3 host, especially for beatmakers and live performers ✅ Enhances flexibility for handling multi-part instruments and complex backing tracks This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the enhancement of Loopy Pro's MIDI binding capabilities to allow for the utilization of the full range of MIDI Continuous Controller (CC) values (0–127) in parameter mappings. The aim is to provide users with more granular and expressive control over parameters, facilitating smoother transitions and more dynamic performances. Problems Limited Expressiveness : Currently, Loopy Pro's MIDI Learn system interprets CC messages primarily as binary triggers (e.g., value 127 for "on" and 0 for "off"), which restricts the ability to perform nuanced parameter adjustments. Incompatibility with Certain Controllers : Some MIDI controllers are designed to send a range of CC values for parameters like volume, pan, or filter cutoff. The current implementation in Loopy Pro may not fully leverage these capabilities, leading to suboptimal integration. Workflow Inefficiencies : Users seeking to implement gradual parameter changes must resort to workarounds or external tools, complicating the workflow and potentially introducing latency. Proposed Solution Full-Range CC Value Support : Modify the MIDI Learn system to recognize and utilize the entire 0–127 range of CC values, enabling direct mapping to parameters that benefit from continuous control. Parameter Scaling Options : Introduce scaling options within the MIDI binding settings to allow users to define how the 0–127 CC range maps to specific parameter ranges, including inversion and custom curves. Visual Feedback Enhancements : Provide real-time visual indicators within the interface to reflect parameter changes driven by varying CC values, aiding in precise adjustments during live performances. Examples Volume Control : A user maps a MIDI controller's fader, which sends CC values from 0 to 127, to control a track's volume in Loopy Pro. This setup allows for smooth volume fades and precise level adjustments. Filter Modulation : A performer assigns a rotary knob sending CC values to modulate a filter's cutoff frequency, enabling dynamic tonal shifts during a live set. Effect Depth Adjustment : A DJ uses a MIDI controller to adjust the depth of a reverb effect in real-time, with the CC value directly influencing the wet/dry mix parameter for seamless transitions. Benefits Enhanced Expressiveness : Utilizing the full CC value range allows for more nuanced and dynamic control over parameters, enriching live performances and recordings. Improved Controller Integration : Better compatibility with a wider range of MIDI controllers enhances user flexibility and choice in hardware. Streamlined Workflow : Direct mapping of CC values to parameters simplifies setup and reduces the need for external processing tools, leading to a more efficient workflow. This summary was automatically generated by ChatGPT-4 on 2025-05-09.

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: Improve and unify the control of clip offset and cycle length in Loopy Pro by: Fixing the unreliable two-finger turn gesture Making it available in both the Clip Detail View and Clip Wave Editor Adding precise controls (e.g. slider or numeric field) to the Pencil/Waveform editors Enabling clip offset and cycle adjustment via assignable Actions Problem: The current two-finger gesture for adjusting clip cycles or offsets is inconsistent and glitchy. It requires precise simultaneous finger lifting and only works in limited views. There’s no way to apply this gesture within the Clip Detail View or Clip Wave Editor. Additionally, users cannot manipulate offset or cycle length via Actions — excluding clip timing from MIDI, automation, and live control workflows. Proposed Solution: Refine the two-finger turn gesture for better stability and precision Enable this gesture in both: - Clip Detail View (opened by tapping a clip) - Clip Wave Editor (e.g. Pencil view or waveform-only edit mode) Add UI elements to the Clip Editors for: - Clip Offset (slider, dial, or numeric field) - Cycle Length (optional) Introduce Action support for: - Increasing/decreasing clip offset - Setting specific offset values - Adjusting cycle length programmatically Benefits: Unified, intuitive editing across all clip-related views Greatly improved control for aligning loops (e.g. micro-nudging drum or vocal loops) Enables live and automated manipulation of clip timing via MIDI or widgets Removes the need for touch gestures entirely if preferred Examples: Use a mapped MIDI knob to nudge a clip's offset during performance Visually dial in a ±30ms offset on a drum loop using the Waveform Editor Precisely fine-tune a vocal entry point without glitchy two-finger gestures Make real-time offset corrections via automation or scripting This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: At the moment you have to decide if you want to the two-finger-turn of clip / cycle timeline OR have the clip window open. It would be more convenient to have access to everything without switching.

Description: Enhance the envelope follower in Loopy Pro by adding frequency band control, as well as adjustable attack and decay times, for more precise and flexible sound shaping. Problem: The current envelope follower lacks fine control over frequency bands and the attack/decay parameters, limiting its ability to adapt to different types of audio or performance needs. This makes it harder to tailor the effect to specific sound design goals. Proposed Solution: Introduce frequency band control, allowing users to apply envelope following to specific frequency ranges (e.g. low, mid, high) Add adjustable attack and decay parameters to fine-tune how quickly the envelope responds to changes in the audio signal Allow users to specify different envelope settings for each frequency band Optionally, enable independent attack/decay settings for each band or for the global envelope Benefits: Provides more detailed control over envelope following, ideal for dynamic sound manipulation Allows users to isolate specific frequency bands for more precise modulation Great for creative effects like dynamic filtering, sidechain compression, or rhythmic transformations Improves the flexibility of Loopy Pro for sound design and live performance workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce a complete set of clip region editing tools — including cropping, muting, navigation, snapping, and layer targeting — all accessible via Touch, MIDI, and Actions . The entire process should be usable flexibly with either direct interaction, external controllers, or programmable workflows. Problem: Currently, Loopy Pro requires touch interaction for detailed clip editing. There is no way to perform the full process — selecting a clip, defining a time region, and applying edits — via Actions or MIDI. This limits efficiency, prevents integration with hardware controllers, and interrupts creative or live performance workflows. Additionally, there's no way to toggle between snap-to-grid and free placement modes. Proposed Solution: Implement a fully parallel editing system where all functions can be used via: Direct Touch MIDI input Assignable Actions Feature Set: ✅ Clip Targeting: Open a specific clip Scroll/browse through clips on canvas or within groups (e.g. “next/previous clip”) Select clips via MIDI or widget actions ✅ Region Selection: Define editable region via bars, beats, %, samples, or milliseconds Use fixed-value actions (e.g. “crop bar 2 to 4.5”) Live “region cursor” control with MIDI or UI widgets – including during playback ✅ Editing Actions: Crop / Uncrop Mute / Unmute Apply to entire clip or individual overdub layers ✅ Snap Mode Toggle: Action to switch between Snap-to-Grid and Free editing modes Affects region selection precision (e.g. exact beats vs. free dragging or scrolling) ✅ Unified Access: Every step in the process is available via Touch, MIDI, and Actions — fully interchangeable Works with haptic controllers, footswitches, or touch-only setups No dependency on one specific input method Benefits: Maximum flexibility for performers, producers, and live users Enables complex, precise clip editing workflows without workflow interruptions Supports accessible and hands-free operation without limiting touch-based workflows Ideal for glitching, loop refinement, dynamic arrangement, or performance prep Examples: Touch to select a clip, then crop a bar with a two-finger gesture — or do the same using a mapped button Use MIDI to scroll through clips, define a time region with an encoder, and crop on beat 3 only Toggle Snap mode to align edits to bar grid or work freely with off-grid precision Mute overdub layer 2 from 1.5s to 2.2s using only widget buttons This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: I would love to be able to crop specific bars in a clip. Let’s say I record 16 bars of guitar and then decide that I want to keep bar 4-8. The editor makes it very hard to make the start/stop points fit perfectly to create a seamless loop. I can crop the clip perfectly in the sequencer, but I would like to be able to do the same at "donut level" :)

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