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.

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

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: Enable the ability to copy, paste, duplicate, and merge MIDI/OSC bindings in the control settings. This would streamline repetitive setup work and support reusing bindings across projects. Problem: Currently, creating multiple similar bindings for different controllers or layouts is very time-consuming. There’s no easy way to duplicate a binding or reuse an existing set from another project or profile. Proposed Solution: – Add copy/paste functionality for individual bindings – Add "Duplicate" function to quickly clone a binding and tweak it – Allow selection of multiple bindings for batch copy/paste – Add ability to import or merge bindings from another control profile – Ensure copied bindings retain all mapped actions and parameters – Optional: offer search/filter to quickly locate bindings during merge Benefits: – Saves significant time when creating complex control mappings – Reduces user errors by avoiding repetitive manual setup – Encourages creation of reusable template bindings and modular profiles – Supports faster prototyping and experimentation – Ideal for users with multiple controllers or evolving live setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable reliable identification and reconnection of multiple identical MIDI controllers (e.g. several MC6/MC8 units) without them being randomly swapped by the system. Add clear visual feedback and manual reconnection options. Problem: Currently, when using multiple MIDI controllers of the same model, Loopy Pro does not reliably distinguish between them. After reboot or reconnection, the controllers can appear in a random order, breaking assignments. This makes stable setups for live performance difficult or impossible. Proposed Solution: – Assign unique IDs or names to each connected MIDI controller – Store and recall the correct port assignments for each controller – Automatically reconnect controllers to the correct virtual ports when they’re plugged back in – If a controller is missing, show a clear indicator (e.g. red label) – If a controller is connected, show a green label – Add manual reassignment: dropdown list to manually bind a saved port to an available device – Optional ‘Reconnect all’ button to match known ports to connected devices – Allow users to assign permanent user-defined labels to controllers – Show active connection status in a global list or in MIDI Learn Benefits: – Prevents confusion and setup loss when using multiple identical controllers – Allows robust multi-device setups (e.g. multiple MC6/MC8) – Improves live reliability – no more guessing or broken mappings – Faster troubleshooting with visual status feedback (e.g. green for connected, red for not connected) – Makes Loopy Pro a better solution for complex live and studio MIDI setups 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.

Allocate a dedicated spot on the canvas (a special widget type) to hold an AUv3’s UI (rather than that AU appearing in a movable and hideable window)