Feature Requests

Here's a scenario: I stop all clips (let's say there are 5 of them), and record a new clip. I like the new clip better than my old clips, and I want to clear all the non-playing clips to make room for new ones. As it is, the only way to do this is to manually delete each non-playing clip individually using a long-swipe. It would be nice if there were a way to delete all non-playing clips using a single action. Thanks!

Description: Enable moving or copying widgets to another page without rebuilding —preserving size/position, styling, actions, variables, and MIDI/OSC mappings. Offer Linked Instance (mirror-style) and Independent Copy modes, plus a Relink Wizard to adapt targets on the destination page. Problem: Recreating widgets on a different page is slow and error-prone: mappings break, actions must be rebuilt, and layouts drift. Duplicating by hand also risks conflicts (double-mapped MIDI, wrong targets). Users need a fast, reliable way to reuse existing UI across pages. Proposed Solution: Commands: Move to Page… and Copy to Page… (multi-select supported). Instance Modes: - Linked Instance (Mirror): shares logic/actions/parameters with the source; optional per-instance visual overrides (color/label). - Independent Copy: full duplicate; all bindings cloned with safe remapping. Relink Wizard (context-aware): - Auto-map targets by name/tag/color (e.g., reroute to local tracks/clips/groups). - Resolve MIDI/OSC conflicts (offer remap, scope, or disable). - Report dependencies (missing buses, AUv3, pages) with one-click fixes or placeholders. Layout Preservation: keep coordinates, size, z-order, anchors ; optional scale to destination grid and “keep safe text size”. Bundles & Library: save/load Widget Bundles (with assets/fonts/icons) and drop them onto any page. Cross-Page Links: show a small link badge on mirrored widgets; jump to Master ; command Make Independent / Re-link to… . Assets: carry embedded images/genmoji; de-duplicate on paste; warn on large assets. Safety & Undo: single undo step; late-press guard for widgets that trigger transport; dry-run preview. Actions & API: Move/Copy Widget(s) to Page , Create Linked Instance , Make Independent , Run Relink Wizard , Select Destination Page , Replace on Destination . - Vars: widget.instanceId , widget.linkGroupId , widget.isLinked , widget.pageName . Benefits: Build complex UIs faster—reuse proven widgets across pages without rebuilding. Fewer mapping mistakes; consistent behavior via linked instances . Clean migrations when reorganizing shows or making “performer vs. FOH” pages. Portable widget packs for teams and templates. Examples: Copy a Transport strip to a “Performer View” as a Linked Instance so one edit updates both pages. Move a Fader bank to a new FOH page; the Relink Wizard retargets sends/pans on that page. Duplicate a Scene Grid as an Independent Copy for the MD; MIDI inputs are auto-remapped to a different controller. Save a Looper Controls bundle (buttons + meters) and drop it onto new projects with all actions intact. This summary was automatically generated by GPT-5 Thinking on 2025-11-04. Original Post: Ability to Move Widgets to another page (without rebuilding after copying) Currently copying is the only options but it does not reserve and bindings or most of the linkings / connections of copied widget / Clips.

Description: Add a true dual-screen workflow where the iPad shows a Control Canvas (editing, buttons, faders) while an external monitor shows an Independent Stage Display (clips, big meters, lyrics/teleprompter, flashing BPM, scene cues). Support Mirror or Extended modes, per-screen pages/layouts, and one-tap actions to send widgets/pages to the external screen. Problem: With an external monitor attached, performers typically get mirroring or a single shared UI. This limits stage use (audience/camera view, MD screen, confidence monitor) and forces page switching during shows. Users need separate, purpose-built layouts on each screen—without rebuilding projects or compromising touch control on the iPad. Proposed Solution: Screen Modes - Mirror (current behavior) or Extended ( Control Canvas on iPad, Stage Display on external). - Per-project default mode ; quick toggle in the title bar. Per-Screen Pages & Layouts - Assign any Page to Screen A (iPad) or Screen B (External) ; optional Follow Page rules (e.g., external follows the selected group/scene). - Screen-Only Widgets (e.g., fullscreen clip grid, lyrics/ChordPro, flashing BPM, big clocks/meters) that don’t appear on the iPad. - PiP support to embed a region of one page into the other screen. Placement & Styling - Resolution-aware layout with Fit/Cover/Pixel-perfect scaling, safe margins/overscan controls, and min text size guards. - Brightness cap / Night mode , theme overrides, and “high-contrast stage” preset. Interaction & Safety - iPad remains the sole touch surface ; optional pointer control for external focus switching. - Performance-Safe mode (frame-rate throttle, reduced animations) for the external output. - Privacy filter prevents edit overlays or dialogs from appearing on the stage screen. Routing & Sync - Transport/tempo/scene are shared; screen-specific quantize for visual cues (downbeat flash, lyric advance). - Optional Program/Preview pair: preview next page/scene on external, Swap on cue. Actions & Variables - Actions: Set Screen Mode (Mirror/Extended) , Show Page on Screen (A/B) , Send Widget to Screen B (Fullscreen/Panel) , Swap Screens , Toggle Stage Display Preset , Set External Brightness/Theme . - Vars: screen.mode , screen.external.resolution , screen.external.fps , screen.external.isSafeMode , page.screen . Presets & Export - Save Stage Display presets (e.g., “Clips+Meters”, “Lyrics+Timer”); recall per setlist item. - External screen respects Genmoji , pictograms, and large-type fonts. Benefits: Run two optimized UIs at once : hands-on control on iPad, clear stage/audience view externally. Fewer page switches and safer shows with persistent meters/lyrics/cues. Camera- and FOH-friendly output (contrast, margins, brightness). Reusable presets speed setup across projects and venues. Examples: iPad shows your Control Canvas ; the HDMI screen shows Lyrics + Big BPM + Scene Countdown with high contrast. A Program/Preview layout on the external display previews the next scene; tap Swap at the bar boundary. Send a Fullscreen Clip Grid to Screen B while keeping detailed faders/FX on iPad; PiP a small Master meter back onto the iPad. For theatre, recall the “Confidence Monitor” preset (clock, next cue, current bar:beat, transport state) on the external screen. This summary was automatically generated by GPT-5 Thinking on 2025-11-04. Original Post: Loopy Pro working with two screens at the same time (Ipad and external screen) 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.

Description: Add a one-shot ADSR envelope with the ability to define a repeat region, enabling users to create more dynamic and evolving soundscapes with precise control over attack, decay, sustain, and release. Problem: Currently, there is no way to easily create one-shot envelope effects that loop or repeat within a defined region. This limits the creative possibilities when working with evolving sounds or automation, especially in situations where specific envelopes need to repeat without continuous triggering. Proposed Solution: Implement a one-shot ADSR envelope that triggers once but can repeat within a specific region of the clip or sequence Allow users to define a repeat region where the envelope will restart automatically after completion Provide options for adjusting the ADSR parameters (Attack, Decay, Sustain, Release) for each envelope repeat Include a visual interface that shows the active repeat region and the envelope behavior over time Enable users to trigger or automate this envelope via MIDI or on-screen controls Benefits: Gives more flexibility in creating evolving sounds that don't need to be re-triggered Ideal for effects that require periodic modulation or dynamic changes over time Enhances creative options for sound design, especially in genres like ambient, experimental, or electronic music Makes Loopy Pro more versatile by allowing for advanced sound manipulation in live and studio setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Add an option to hide all empty clips in the sequencer timeline for improved clarity and focus during editing and playback. Problem: Empty clips can clutter the sequencer view, especially in complex projects with many tracks and layers. This makes it harder to focus on the actual musical content and affects workflow speed and overview. Proposed Solution: – Add a toggle option (global or per-page) to hide all clips in the sequencer that currently contain no recorded material – Can be implemented as a visual filter (non-destructive) that does not delete clips – Could also include an "auto-hide when empty" mode – Optional keyboard shortcut or widget action to toggle visibility on/off – Ideally works dynamically: hidden when empty, shown when recording starts Benefits: – Cleaner and more focused sequencer view – Faster navigation and editing in dense projects – Useful for live performance setups with many unused placeholders – Reduces visual distractions and improves UX This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Allow users at the project level to set up the number of audio outputs they need, to align with their audio interface. Many, but not all, may have 2 outputs, one for the main and one output for the headphones or stage monitors. Some users with bigger audio interfaces and setup will have more. The user MUST give each output a name; and identify which audio interface channels the output aligns to. FYI - this is standard in most DAWs. FOR EACH predefined audio output, as described above; the current audio mixer display is replicated and can be selected. So I can switch, via an action, and see the same set of faders, but at at the end the last audio channel changes. Of course as I switch between the mixers (one for each defined output), I would visually see and control the faders for that mix. E.g. - if for "main" output the blue color group fader was about -14db, and if for the "headphone" output the same blue color group fader was about say -3db - then I would see the fader set at those positions when I switched between the mixers. The last audio channel on the right - will display the name of the output channel the user defined up front in the project. ADDITIONALLY: In addition to the mixer view per output channel; allow users to have a mixer view per audio bus channel - showing ONLY the channels routed to that audiobus. So if I have created an auidobus channel for (labeled) "DRUMS", and I have 2 MIDI audiosource and 3 input auido source and 1 other audiobus channel routed to this "DRUMS" audiobus - then when I switch (via actions ) to this MIXER VIEW - I will see only those channels routed to this audiobus. This will make adjusting audio signals sent to audiobuses - 4,320% EASIER than it is now..... where if I using the prefader routing to send audio to an audiobus, I have to adjust little tiny sender dials, that you need a microscope to see. SO - there are 2 major flavors of the mixer; one flavor is be able to switch the mixer to the output channels defined in the project setup; and the other is to be able to switch or see in the mixer a selected audiobus and all of its inputs. OUT OF SCOPE: Plugin settings per output channel. The plugins in any channel (of any type) are there and the settings in the plugins do not change between mixers. So if I have a reverb plugin on audiobus A, and the wet/dry mix on the reverb is 40%, then this is the wet/dry mix regardless of the output channel. RATIONALE: By jumping through careful, tedious and Rube Goldberg-like UI design, a user can adjust the mix between outputs in the current software, and the mix to audiobuses. But it bout' like to take a PhD. This MIXER switching approach, and the Matrix approach explained below - is so easy my 8 year old nephew can do it. BY - redesigning and revamping a "SWITCHABLE" mixer between the audio outputs supported by the audio interface, and (a must here) set up by the user for the project.... a simple action lets users ADJUST FADERS without trying to tweak tiny little dials on the screen; and without creating (yet even more) widgets to control the sends. ALSO.... it would be bodacious if, like AUM, there was a screen that showed the Matrix. No, not Neo or Morpheus - a matrix showing ALL the audio channels on the left, and all the outputs (set up by the user at the beginning of the project) on the top - and which are routed to which. A single routing view. Maybe even an audio matrix and a MIDI matrix would be so wonderful. This should also have viewing or switching options; like a Matrix for each of the audio outputs set up in the project profile, and a Matrix view for each audiobus that has sends going to it. This is a simplistic sanity check..... here's all my audio routings. The software IS AMAZING for sure....but one "challenge" is that you need a lot of functionality in a very, very, very, small screen space. The "SENDS" dials are somewhat typical on sound boards but sort of challenging to work with on the iPad UI (I can not even imagine it on the iPhone)..... ESPECIALLY if you rename audio bus channels. A "switchable" MIXER design can help here. PLEASE...... don't go off and "run with it" on your own, work with the folks who have suggested the feature to help make it the best it can be.

Would you consider creating something similar to “take folders”? Logic Pro has this feature to continue to record the same loop over and over until the the player decides that the take was perfect. It saves all the takes and the user can afterwards pick a selection from different clips to create the perfect loop.

Description: Enable stepped dials to have access to control loops and layers, allowing for more precise control over the looped and overdubbed audio layers directly through dial interactions. Problem: Currently, stepped dials do not have direct access to control loop and layer states, limiting their functionality for managing overdubs or triggering different layers in a loop. This reduces the potential for real-time performance control. Proposed Solution: Allow stepped dials to interact with and control specific loops and layers (e.g. controlling loop start/stop, triggering overdubs, adjusting volume, or switching between layers) Provide a way to map the dials to specific loop layers or overdubs so they can be accessed and controlled easily Allow for precise control of individual layers or loops via the stepped dial, including the ability to switch between overdubs and layers for more dynamic performances Optionally, add visual feedback for each layer/loop on the stepped dial to show which layer or loop is currently being controlled Benefits: Increases performance flexibility by giving real-time, hands-on control over loops and layers Enables more creative manipulation of overdubs and layered audio without needing to manually navigate through menus or screens Ideal for live performances or dynamic sound design setups Provides smoother transitions between loops and overdubs, enhancing workflow efficiency This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Introduce automation tracks in the Loopy Pro sequencer that allow both manual drawing and real-time recording of MIDI CC data, including from external MIDI controllers or hardware synthesizers. Additionally, enable time-based automation triggers that can be set to occur after a certain number of bars in the arrangement. Problem: Currently, there is no way to record MIDI CC data over time or draw automation lines directly inside the sequencer. This makes it hard to automate effect changes, synth parameter modulations, or scene transitions with precision. Users must rely on dummy clips or static widgets to emulate automation behavior. Proposed Solution: – Add automation lanes/tracks to the sequencer view – Record incoming MIDI CC data in real time, including from hardware synths – Option to automatically record any incoming CC without manual mapping (like Logic or Ableton) – Allow drawing and editing of automation curves and values (e.g. volume, FX wet/dry, AUv3 parameters) – Visual representation of automation values over time – Automations can target AUv3, internal effects, or external MIDI destinations – Add timed Follow Actions: • Trigger any action after X bars have passed • Examples: unmute audio source X after 8 bars, disable effect Y after 16 bars – Allow assigning actions based on sequencer bar position (e.g. “do X on bar 129”) Community Input: – Users want to “tweak knobs” live and have the automation recorded and played back – Drawing value lines would allow for better control than dummy clips – Automations should work like in Ableton or Logic on iPad – BeatMaker was mentioned negatively due to its manual mapping requirement – Ideal for both clip automation and long-form arrangement control Benefits: – Complete automation workflow for effects, plugins and MIDI – Captures live synth or controller tweaks without setup hassle – Enables dynamic, evolving arrangements and transitions – Great for hybrid setups (hardware + iPad) – Significantly improves sequencing, especially for live performances and structured song-building This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Improve control settings and preset management by adding undo/redo, search, filter, and advanced sorting options for MIDI bindings, actions, OSC directions, and plugin presets. Problem: Currently, managing large sets of mappings and actions is tedious and prone to error. Deleting entries in bulk is not possible. Labels can remain even after deletion due to bugs. There's also no way to recover deleted entries or track changes without undo/redo functionality. Proposed Solution: – Add Undo/Redo buttons scoped per section (e.g., MIDI bindings, actions, OSC, plugin presets) – Make list entries deletable via swipe (e.g., after accidental import) – Fix bug where labels don’t disappear after full deletion – Add search with auto-focus – Enable filtering – Support drag & drop sorting by: • Global profiles • Project settings • MIDI bindings • Actions • OSC directions • Plugin presets • Control Settings categories – All list items should support: • Reorder • Move between categories • Copy to category • Delete • Copy/paste • Move to another profile • Move up/down • One-click top/bottom move Benefits: ✅ Massively improved efficiency when editing bindings or presets ✅ Prevents accidental loss of work ✅ Much better clarity and control over large setups ✅ Brings consistency to all control-setting areas ✅ Saves time by avoiding full rebuilds of profiles This summary was automatically generated by ChatGPT-4 on April 30, 2025.