Feature Requests

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: 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: 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: Integrate high-quality octave and pitch-shifting effects directly into Loopy Pro, either natively or by enabling access to system-level AU pitch effects like Apple’s AUPitch. Problem: While Loopy Pro supports AUv3 effects, users seeking clean, adjustable pitch-shifting—especially for live use—are currently limited. Notably, Apple’s AUPitch effect sounds better and provides more control than AUNewPitch, yet it is not easily accessible in Loopy Pro outside GarageBand. This creates a barrier for users needing reliable pitch control for vocals, instruments, or creative FX chains. Proposed Solution: – Make Apple’s AUPitch accessible within Loopy Pro as an effect option – Alternatively (or additionally), develop native Loopy Pro pitch/octave shifter with high-quality algorithms – Include real-time control via MIDI/automation – Offer parameters like coarse/fine pitch shift, formant control, mix/dry, and stereo width – Ensure low latency and stable performance suitable for live performance scenarios Benefits: ✅ Unlocks access to Apple’s superior pitch-shifting algorithm for Loopy Pro users ✅ Provides musicians with high-quality real-time pitch manipulation tools ✅ Useful for harmonizing, vocal doubling, creative sound design, and instrumental FX ✅ Helps avoid needing GarageBand or third-party hosts just for AUPitch access ✅ Makes Loopy Pro more self-contained and powerful as a live processor This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce flexible arrangement markers in the sequencer that can define song sections, tempo changes, loop regions, and cue actions. Problem: Currently, there is no way to define structured sections in the timeline that allow dynamic tempo changes, looping, or cue-based control – all essential for live performance, DJ-style cueing, and structured playback. Proposed Solution: – Add arrangement markers in the sequencer timeline – Allow each marker to store: – BPM – Time signature – Section name – Loop status (loop once, loop until, no loop) – Support widgets or MIDI actions to jump to, loop, or stay in a given section – Option to assign markers as cue points for live use (forward, reverse, backward, etc.) – Allow linking markers to a master track (e.g., for backtracks or DJ use) – Visually identify and edit markers on the timeline Benefits: – Enables advanced song arrangement workflows (Ableton-style) – Ideal for live performance, jamming, songwriting and DJ sets – Enables seamless jumping between sections and live looping control – MIDI integration enhances live flexibility – Great for structured backtracks, arrangement rehearsal, and creative sectioning This summary was automatically generated by ChatGPT-4 on April 30, 2025.

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

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