Feature Requests

Description: Add support for synchronized video loops that can be triggered alongside audio clips and displayed on an external screen (e.g. via HDMI or AirPlay). Problem: Currently, Loopy Pro offers no native way to integrate visual content. For performers who want to combine looping audio with live visuals (e.g. VJ-style video clips, synced animations, or ambient visuals), this creates a limitation. External tools are required to run video separately, making sync and control less reliable and harder to manage during a live performance. Proposed Solution: Implement support for attaching video files to clips or scenes, with playback triggered in sync with the clip’s timeline. Features could include: Fullscreen output to external displays (HDMI, USB-C, AirPlay, etc.) Start/stop video playback tied to audio clip state Looping or one-shot video options Basic video controls: opacity, scaling, fade in/out Possibly timeline-based automation or binding for live control Benefits: Enables audio-visual performances directly within Loopy Pro Reduces need for third-party video playback tools Enhances stage presence and immersion for solo performers Offers creative possibilities for ambient visuals, storytelling, or branding Examples: Triggering a looped visual animation alongside a bassline Projecting synced lyrics or background textures while playing live Creating a fully self-contained audio-visual setup using just Loopy Pro and a projector This summary was automatically generated by ChatGPT-4 on 2025-05-17.

Description: Enable support for AUv3 plugins with multiple audio inputs, including standard sidechain inputs on FX and instruments (e.g. FabFilter Twin 3), and allow flexible audio routing between tracks to use this functionality. Problem: Loopy Pro currently doesn’t support AUv3 sidechain inputs or multi-input routing. This limits its use as a fully capable DAW for those relying on dynamics control or complex routing setups (e.g. ducking via sidechain compression). Proposed Solution: – Implement routing of audio from one track to the sidechain input of a plugin on another track – Support AUv3 FX plugins with standard sidechain inputs – Support instrument AUv3 plugins that also include sidechain inputs (e.g. FabFilter Twin 3) – Allow use of multi-output AUv3 instruments with flexible routing to Loopy tracks or groups – Provide clear UI elements to manage input/output routing between tracks and plugins Benefits: – Makes Loopy Pro viable as a standalone DAW for advanced users – Enables mixing techniques like ducking, pumping, spectral sidechaining – Makes full use of AUv3 plugins that already support these features – Greatly enhances creative potential in sound design, live setups and dynamic control workflows 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: 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: Allow the ability to display user-defined images on buttons, one-shots, or other canvas elements. These images can serve functional or aesthetic purposes and adapt based on conditions (e.g. plugin parameters, volume level, etc.). Problem: Currently, Loopy Pro allows some custom visuals (like text on buttons), but there is no built-in way to use actual images or image changes to reflect states, structure, or provide visual guidance. This limits customization and performance feedback. Proposed Solution: – Enable importing custom images (JPG, PNG, SVG/vector) for use on: – Buttons – One-shot triggers – Canvas elements – Conditional image changes based on clip/color/group/plugin parameter values: – Use a different image – Make image greyscale (e.g. when inactive/off) – Add options for: – Image only – Text label only – Text label over image – Allow for example volume-dependent visuals (e.g. different cat images based on loudness) – Enable images to be shown instead of text in page switcher buttons (e.g. a cat image for a page of cat sounds) – Support greyscale + overlay white tint when “OFF” for clarity – Allow repositioning and scaling of image-based buttons – Images should grey out when not in use (like text currently does) – Add optional support for using images as chord references, song sections, reminders (e.g. as per guitar looping use cases) – Ideal for live use: easy recognition and custom visual feedback – Add toggle to hide the page switcher bar , so only image buttons on canvas are used instead – Add importable image-based canvas elements with font-size adjustability – Support simple image widgets that act as action triggers – Add fallback to default appearance if image is not defined Benefits: – Great for customizing layouts for live use, teaching, or creative performance – Adds huge flexibility to the UI – from playful (cat buttons) to educational (chord reminders) – Provides powerful conditional visual feedback – Enhances accessibility for those relying on visual structure – Fun and inspiring visuals to personalize each project – Great for visual cues across complex multi-page setups – Keeps screen clean by replacing redundant buttons with visual cues This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce a variety of new built-in effects in Loopy Pro, based on popular and unique suggestions from the community. This would include effects like beat-repeaters, delay, resonators, tuners, radio receivers, and noise reducers. Problem: Loopy Pro currently lacks certain essential and creative effects that are available in other software, limiting users' ability to fully manipulate their sound in a live or studio setting. Users want more options for sound design and creative performance. Proposed Solution: Beat-Repeat like Turnado: A versatile beat-repeat effect with flexible controls for stutter, time-stretching, and modulation. Delay: A classic delay effect with customizable time, feedback, and modulation options. Ableton-like Resonator: A resonator effect for creating rich, dubby, techno-style sounds. Precise Tuner (like Ableton Tuner): A highly accurate tuner for precise pitch control, suitable for instruments and vocal tuning. World Radio AUv3 Plugin: A "Radio Garden"-like plugin that allows users to tune into radio stations from around the world. This could be used to capture loops from random stations and change frequencies on the fly. Noise Reducer (like Klevgrand Brusfri): A high-end noise reduction plugin, featuring algorithms that provide clean noise filtering with zero latency, far beyond a basic gate effect. Benefits: Adds a wide range of creative possibilities for both live performance and sound design Enhances Loopy Pro’s capabilities by including effects that are already staples in other DAWs Improves user workflow with more accessible, intuitive, and specialized effects Expands the options for users to manipulate and transform their sound in unique ways Great for musicians who want to experiment with new audio sources like radio stations, or need precise audio tools for tuning and noise reduction This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce a DJ- or sampler-style “Slicer” mode that divides a clip into rhythmic slices and allows instant triggering of those slices — either via a grid, MIDI controller, or touch input — similar to features found in tools like the Korg Volca Sample, Roland SP-series, or Serato-style slicers. Problem: Loopy Pro currently lacks a dedicated slicer interface for rhythmic or pitch-based clip triggering. While clips can be manually trimmed or edited, there’s no native way to divide a loop into steps or beat slices and jump between them in real time. This limits live remixing, finger drumming, and creative beat manipulation — especially for users coming from DJ or sampler hardware. Proposed Solution: Add a Slicer Mode or Slicer Widget with the following capabilities: ✅ Core Features: Divide a clip into N slices (based on grid: 1/4, 1/8, 1/16, custom) Trigger slices manually via: - Touch (grid layout) - MIDI pad controller - Key or widget-based input Slices can either: - Jump playback instantly - Retrigger as one-shots - Sustain while held ("Hold-to-Play") ✅ Volca Sample–Style “Step Jump” Mode: Hold a step to jump playback instantly to that slice Release returns to original timeline (optional) Behavior: momentary jump vs. latch Compatible with looping playback or free-running ✅ Additional Options (as requested in comments): Slice-to-MIDI (assign slices to specific MIDI notes) Per-slice FX, reverse, or pitch control Sequence slices in the Step Sequencer Map slices to individual AUv3 chains (optional advanced use) Benefits: Enables performance styles like beat juggling, stuttering, slice remixing Opens new creative workflows for DJs, finger drummers, loop-based performers Bridges the gap between clip looping and classic sampler-style triggering Makes Loopy Pro more competitive with hardware samplers and iOS tools like Koala, Samplr, Blocs Wave Examples: Load a breakbeat, slice into 8 steps, trigger each slice live via MIDI pads Use a Volca-style jump to step 5, then release to resume loop from original timeline Play a sliced vocal phrase chromatically via MIDI mapping Trigger rapid-fire slices in sync with quantization for glitchy textures This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Slicer version that mashes up features from a DJ style slicer (as in Serato or Djay Pro) and Volca Sample's step jump feature. – Retrigger selected slice at adjustable timings (1, 1/2, 1/4, 1/8, etc) – Retrigger selected slices in sequence (as in Volca Sample Step Jump) – Hold function to keep slices selected after fingers lift off

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.

Problem: Text in Loopy Pro widgets is static – there’s no way to display live values like AUv3 or MIDI, or to show dynamic status feedback. Users can’t show the value of a fader or knob, nor adapt text visibility, size or content dynamically. Proposed Solution: Text binding to controls: Let text widgets display live MIDI values from bound faders or knobs Placeholder system with support for: - $project.name$ , $bar.current$ , $channel_name_1$ , $AUv3_post_3$ - Current/total clip layers, named layers - Clip colors, groups, AUv3 plugin parameters User-defined labels for value ranges , e.g. 30–155 Hz = “Rumble”, 1000–3000 Hz = “Medium” Conditional formatting & visibility - Show exact value only while knob/fader is touched - After a delay, return to label display (e.g. "Range name") Text resizing logic - Auto-scale font size with widget/canvas changes - Manual ± font size per widget Formula-based expressions , like SWITCH(...) Text changes via actions , e.g. “Set label to: VERSE” Benefit: Real-time, intelligent feedback in the UI itself No need for extra screens or MIDI displays Clear overview of dynamic values, actions and playback states Great for live performance, section navigation, parameter feedback and more Customizable and responsive interface that adapts to user interaction Extension: Define Dynamic Behavior for Each Placeholder Ideally, each placeholder should have its own display logic – controlling when and how it appears. Examples: Always visible (default) Only visible during interaction , e.g. while a fader or knob is being moved Visible for a short time after interaction , e.g. 1 second after release Conditionally visible , e.g. only when a clip is playing or a value is in a certain range Toggle visibility via actions or logic This would allow for highly adaptive and context-aware UIs – showing the right info at the right moment without visual overload. It would give Loopy Pro a unique edge as a flexible, user-definable performance environment. This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce a Scrubber Widget that enables expressive, real-time control over clip playback position — inspired by the tactile interface of the iOS app Samplr . The widget should support both single-finger scrubbing and an advanced multi-finger mode that allows gesture-based selection and playback. Problem: Loopy Pro currently lacks an interactive surface to scrub through a clip's waveform in real time. This limits creative manipulation techniques like scratching, granular looping, pitch-like movements, and gestural expression. While playhead actions exist, they don’t offer the immediacy, precision, and tactile feel of a scrub-based interface — especially one designed for multiple fingers. Proposed Solution: Create a Scrubber Widget with the following capabilities: ### 🔹 Basic Scrubbing Features: Touch or MIDI control to drag the playhead within a clip’s waveform Bi-directional scrubbing (forward/backward) Option to scrub while holding playback (loop-locked) or while paused Playback can optionally follow the finger in real time or be quantized Audio preview on touch-down or continuous playback during scrubbing Optional pitch/time stretching for speed-variable scrub Assignable to MIDI CCs, XY pads, or widgets ### 🔸 Multi-Finger “Samplr-Style” Mode: One finger to define a region (start and end points) Second finger to scrub within that region , playing only the selected part Region remains fixed while user scrubs dynamically within it Ideal for slicing, glitching, ambient textures, granular gestures Also useful in clip-based live performance with looping control per region ### 🔧 Additional Features: Adjustable zoom and waveform scaling Toggle for snap-to-grid vs. freehand positioning Visual feedback for loop region and playhead Compatible with both audio clips and resampled material Full support for clip-layer interaction (if layers are visible/editable) Benefits: Unlocks expressive, hands-on control similar to Samplr and other gesture-based audio tools Supports experimental, live-looping, and remix workflows Great for performers using iPads with touch, as well as MIDI/hardware controllers Adds a dynamic way to interact with loops beyond static triggering or playhead jumping Enhances visual and physical engagement with sound in real time Examples: Loop a vocal phrase and use two fingers to isolate and rhythmically scrub one syllable Use a ribbon controller or MIDI CC to sweep playback across a texture in sync Scrub backward through a reversed reverb tail for sound design Define a short slice in a drum loop and repeatedly scrub it live for glitch FX This summary was automatically generated by ChatGPT-4 on 2025-05-17.