Feature Requests

If i have my ipad conected via hdmi to second display, create and option so when I open an app AUv3 within Loopy Pro, I can view it on that second display while the Loopy Pro homepage remains active and visible in the screen option. This way i can have windows open on secondary/external screens as other apps have as VS Visual Synthesizer This way, I can use both options and screens at the same time. This is VERY usefull for working with Loopy pro.

Would be great to have the option to sort the the MIDI destinations in the MIDI destination box by channel number .. when you have many plugins filtered by channel number but sorted by plugin name (current behavior), it feels a bit mixed up ..

Description This feature request proposes enhancing Loopy Pro's audio routing capabilities by allowing buses to be assigned as destinations and enabling buses to send their output to multiple destinations, including other buses. This would facilitate more complex and flexible routing configurations, such as creating monitoring buses with effects like reverb or delay that are applied across multiple channels. Proposed Solution Bus as Destination : Enable buses to be selected as destinations for audio sources, similar to how colors or outputs are currently assigned. Multiple Destinations for Buses : Allow a single bus to route its output to multiple destinations, including other buses, colors, or outputs. Dynamic Routing : Implement actions or controls that allow users to dynamically change bus destinations during live performances or within a project setup. Monitoring Enhancements : Provide options to monitor through buses, enabling users to hear the combined effects applied to multiple channels in real-time. Problem Limited Routing Flexibility : Currently, buses in Loopy Pro can only send their output to the main output, restricting the ability to create complex routing scenarios. Monitoring Challenges : Users cannot monitor the combined effects of multiple channels through a single bus, making it difficult to set up cohesive monitoring environments. Workflow Limitations : The inability to route buses to other destinations limits creative possibilities and complicates setups that require shared effects processing or parallel routing paths. Benefits Enhanced Creative Control : Users can design intricate audio processing chains, such as parallel effects or subgroup processing, improving the overall sound design capabilities. Improved Monitoring : Facilitates the creation of dedicated monitoring buses with specific effects, aiding performers in hearing exactly what they need during live sessions. Streamlined Workflow : Reduces the need for workarounds or external routing solutions, allowing for a more integrated and efficient project setup within Loopy Pro. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Allow any AUv3 instrument/effect to appear as a widget on the canvas—resizable, theme-aware, and mappable—so performers can tweak plugins directly without opening floating windows. Problem: AUv3s open in separate panels that obscure the layout, break flow on stage, and don’t persist well across pages. Users want always-visible, space-efficient plugin controls that live with their loops, faders, and macros. Proposed Solution: Widget Type: “AUv3 Widget” that hosts the plugin’s view inside a framed, resizable container (XS → Fullscreen). Layout & Views: Multiple view modes : Full UI , Compact UI (plugin-provided), and Mini Panel (user-selected parameters as knobs/faders + meters). Snap-to-grid, aspect locks, safe-area padding. Focus & Control: Optional Focus-Follow (hardware maps to the widget’s plugin when selected); Focus Lock to prevent steals. Parameter Mapping: Pick parameters into the Mini Panel, add per-control range/curve, and bi-directional feedback. Learn from gestures or MIDI. State & Presets: Per-widget Preset selector , A/B compare , and State recall with project; “Copy state to all instances of this plugin.” Performance: GPU-friendly compositing; Sleep when offscreen (optional), Auto-Suspend when silent; per-widget CPU meter and tail handling. Safety: Sandboxed; restore on crash; Safe Mode fallback to Mini Panel if the full UI fails to render. Actions & Variables: - Actions: Show/Hide AUv3 Widget , Toggle View Mode , Select Preset , Randomize Params , Bypass/Enable , Open Native Window . - Vars: au.name , au.preset , au.cpu , au.isBypassed , au.focused , au.param["Cutoff"] . Automation & Themes: Themeable frame (title, icon, color), title-bar shortcuts, and page-level visibility rules (only show on Page X). Benefits: Keep critical plugin controls in sight and integrated with the performance layout. Faster tweaks, fewer window toggles, less risk on stage. Consistent mappings and presets per page/project. Lower CPU surprises with suspend/sleep plus inline meters. Examples: Place a reverb AUv3 as a Mini Panel (Mix/Time/HP/LP) next to vocal loops; tap to expand to Full UI during soundcheck. Use Focus-Follow so an 8-knob controller always controls the selected AUv3 widget ; lock focus for precise edits. A synth AUv3 widget on the keys page shows macro knobs; a footswitch triggers Preset Next while the widget confirms the name. On dense pages, widgets default to Compact ; opening the editor temporarily pops the Full UI; closing returns to Compact automatically. This summary was automatically generated by GPT-5 Thinking on 2025-09-26. Original Post: AUv3 widget A widget acting as a place older for an AUv3 content, inside a page. This could be specially helpful for MIDI plugins, for things we cannot achieve with Loopy Pro widgets. Or to drop effect AUv3 in a page without having to remap anything.

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.

I want to be able to create a midi bus and have the possibility to redirect the out of plugins and of buttons to it and from then send it to midi destinations For example currently in my template I have 8 buttons that sends note messages to digistix If I want to change the destination to another plugin I have to edit my template and change it to another plugin (16 times) Would be easier to have a midi bus in my project and send the output of the buttons to that bus and from the buss then add midi plugins into it so I can quickly switch between multiple applications fire example

Description: Allow users to freely reorder the items/options inside Stepper Dial and Radio List widgets via drag-and-drop (or Move Up/Down), without having to rebuild actions or rename items. Problem: Today, changing the order of items is only possible with a clumsy workaround: manually drag actions from one item to another and then rename each item. This is slow, error-prone, and especially painful when many items have nontrivial action stacks and labels. Proposed Solution: Drag & Drop Reorder: Reorder items with grab handles; support Move Up/Down, cut/copy/paste, and multi-select reordering. Action & Mapping Preservation: Actions, colors, icons, and bindings travel with the item as it moves. Stable Item IDs: Internally assign each item a persistent ID so expressions, feedback, and external mappings remain correct even if display order changes. Bulk Tools: Quick sort by name/index; “reverse,” “shuffle,” and “renumber” utilities; duplicate item with actions. Safety & Preview: Show before/after order, affected references, and offer Undo. Parity: Same capabilities for Stepper Dial and Radio List widgets. Benefits: Edit lists in seconds instead of rebuilding them. Eliminates mistakes from re-assigning actions by hand. Keeps controller mappings and expressions stable while improving UI order. Encourages iterative design (try new orders without fear). Examples: Rearrange a 16-step dial so “Scenes” appear in performance order; all step actions follow automatically. Sort a Radio List of fade-time presets by shortest→longest without breaking any targets. Duplicate a step (with actions) and drag it to a new position to create a variant. This summary was automatically generated by GPT-5 Thinking on 2025-08-25. Original Post: Ability to re-order stepper dial items (see screenshot) and radio lists Currently only doable with a workaround: you have to drag individual actions from item to item. Then rename the items. This is a bit ouchy, especially if you have a lot of actions.

Description: Add a built-in MIDI arpeggiator and/or step sequencer to Loopy Pro that can be used to send MIDI notes to instruments or plugins, either internally or externally. Problem: Currently, users who want arpeggiator or step sequencing functionality need to rely on external AUv3 plugins or external devices. This adds complexity, latency, and limits integration with Loopy Pro's internal action system and widget-based workflows. Proposed Solution: – Provide an internal MIDI arpeggiator with configurable note order, octave range, rhythm, gate length, and sync to clock – Add a step sequencer for MIDI notes with adjustable step count, note values, velocities, and per-step probability – Allow full widget and action system integration for triggering, pattern switching, parameter control, and sequencing automation – Optional AUv3-hosted UI or simplified grid editor for quick setup and live manipulation Benefits: ✅ Seamless integration with Loopy Pro’s interface and action system ✅ No need for third-party AUv3s, resulting in lower CPU usage and tighter sync ✅ Enables creative live performance setups including melodic looping and generative MIDI ✅ Opens new possibilities for Loopy Pro as a comprehensive live instrument and controller hub This summary was automatically generated by ChatGPT-4 on May 2, 2025.

With iOS 2026 came Genmoji This may help with customization of UI for various music theory and elements and explanations